// PRIVACY POLICY · TURING CMS

Turing CMS Privacy Policy

Last updated: November 16, 2026 · Support: support@periwin.com
Periwin Solutions Ltd ('Periwin', 'we', 'our') built Turing CMS as a commercial multi-tenant business management application. This Privacy Policy explains how Turing CMS handles account, workspace, media, and device permission data on iOS, Android, and Web.

Device Permissions Overview

Camera

Capture and crop property or workspace photos directly from the field.

Stored locally in the app outbox until uploaded to your organization's CMS workspace.

Photo Library

Select existing photos for listings and attach cached listing images when sharing.

Only selected photos are read and uploaded to your authorized workspace.

Location (When In Use)

Record property coordinates on-site, display distance in km, and filter nearby listings by radius.

Used in real time on-device and sent only when performing nearby queries or saving coordinates you confirm.

Local Storage & Cache

Store encrypted session tokens, offline drafts, and cached listings/images for 2G resilience and offline sharing.

Kept locally on your device (`FlutterSecureStorage` / app support cache) and cleared on sign-out or uninstall.

1. Information We Collect

Account Information: When you sign in to Turing CMS, we collect and verify your name, work email address, company/tenant identifier, and role permissions provided by your organization administrator.

Workspace Content: Listings, descriptions, lead/enquiry contact details, notes, and uploaded media that you or your team submit are stored in your organization's isolated workspace on Periwin CMS (`cms.periwin.com`).

Device & Diagnostic Context: Basic network connectivity status is checked on-device to queue offline drafts and prevent duplicate submissions. We do not sell personal data or run third-party advertising SDKs.

2. How We Use Information

Authenticate your session and enforce company-level tenant isolation and role-based permissions.

Synchronize properties, leads, and photos between your mobile device and your organization's CMS backend.

Provide location-based nearby filtering and distance calculations when location permission is granted.

Enable offline viewing, local draft queuing, and zero-duplicate synchronization when connectivity is restored.

3. Data Sharing & Third Parties

We do not sell, rent, or trade your personal or workspace data.

Turing CMS contains no third-party advertising networks or cross-app ad tracking.

When you explicitly tap Share or Social Post, only the listing details and photos you choose are handed off to the OS share sheet or the app you select.

4. Security & Retention

All API traffic between the mobile app and `cms.periwin.com` is encrypted in transit using HTTPS/TLS. Authentication tokens are stored in platform secure storage (iOS Keychain / Android EncryptedSharedPreferences).

Workspace records are retained for as long as your organization maintains an active workspace or as required by your administrator. Signing out clears local cached tokens and workspace cache on the device.

5. Your Rights & Account Deletion

You may request access, correction, export, or deletion of your account and personal data by contacting your organization administrator or emailing us directly at support@periwin.com.

We respond to verified privacy and deletion requests within 30 days.

6. Contact Us

If you have questions about this Privacy Policy or Turing CMS data practices, contact Periwin Solutions at support@periwin.com.

← Back to Turing CMSTerms of Service →