Data handling
POS-Sync uses customer records to keep your accounts in sync. It does not use those records to measure visits or signups.
Current behavior
POS-Sync stores names, email addresses and phone numbers needed to match and sync customers. It also stores which provider accounts they appear in, sync status, issues and change history. Details specific to one provider stay linked to their source account and are not copied to other providers. Product catalog sync is currently off.
POS-Sync stores your provider account IDs and encrypted sign-in tokens so it can sync and help recover failed work. Do not send credentials by email. They are not used for site analytics.
An organisation owner can request an export through support. We verify ownership, check that the export contains only that organisation’s data, and send it through an approved secure channel. We do not attach customer records to ordinary support email.
Closing an account removes its access and team memberships immediately and removes identifying details from the login. Where supported, POS-Sync revokes provider access. Organisations owned by that account alone, their workspaces, connections and customer records are disabled and marked for deletion. The final schedule for deleting primary data and expiring backups must be approved before production release.
If you agree, POS-Sync records only these steps: landing on the site, registering, verifying an account, connecting a provider, starting sync and becoming a paid subscriber. We use a random browser ID and turn it into a one-way hash before storage. The analytics service rejects other data, including account IDs, emails, customer details, provider credentials, page URLs, referring sites and form entries.
Choosing “Essential only” creates no analytics ID. You can reopen “Analytics choices” in the footer. Declining removes the browser ID and stops future analytics events.