This policy describes how the operator of this application (“we”) handles information in this application. It is written to describe what the software actually does.
What the application is
The application connects to CRM accounts you already own, reads data out of them, and writes data into them — either as a one-off migration or as a continuing two-way sync. It is a pipe between your own systems. We do not sell, rent, or share your data, and we do not use it to train models or build profiles.
What we store
- Account details — your email address, an optional name, and a hashed password. Passwords are hashed with bcrypt and are never stored or transmitted in plain text.
- Connection credentials — the OAuth access and refresh tokens, or API keys, for each account you connect. These are encrypted at rest with AES-256-GCM before they reach the database.
- Job configuration — the names of your migrations and syncs, which data types you enabled, your field mappings, and your conflict settings.
- Operational records — for each record processed, the identifier it has in each connected system, a content fingerprint used to detect changes, timestamps, and the outcome of the operation. Run logs may quote a record’s name, email or title to make an error message useful.
What we do not store
The application does not keep a copy of your CRM records. Data read from a source is held in memory only for as long as it takes to write it to the destination, and is then discarded. The identifiers and fingerprints described above are what remain, and they exist so a repeat run does not duplicate your data.
Why we hold each thing
- Credentials, so that scheduled syncs can run without asking you to re-authorise every time.
- Identifiers and fingerprints, so a migration is resumable and a sync can tell a genuine change from a record it wrote itself.
- Logs, so you can see what happened and why something failed.
Third parties
Data flows only between you and the CRM providers you connect. Their own privacy policies govern what happens to it once it is in their systems. If AI-assisted field mapping is enabled for this deployment, field names and data types from your schema are sent to Anthropic to propose a mapping; your records are not. That feature is optional and can be switched off by removing the API key.
Retention and deletion
- Disconnecting an account deletes its stored credentials.
- Uninstalling the marketplace app revokes and clears the credentials for that account automatically, and pauses any sync that used it.
- Deleting a migration or sync job deletes its logs, mappings and identifier records.
- Deleting your account removes everything associated with it. Contact us to request this.
Security
- All stored tokens and API keys are encrypted with AES-256-GCM.
- Sessions are signed, HTTP-only cookies.
- Credentials are never exposed to the browser or included in client-side code.
- All production traffic is served over HTTPS.
No system is perfectly secure. If you believe you have found a vulnerability, please contact us before disclosing it publicly.
Your rights
You can access, correct, export or delete your data at any time — most of it directly in the application, and the rest by contacting us. Depending on where you live, you may have additional rights under laws such as the GDPR or CCPA; we will honour those requests.
Changes
If this policy changes materially we will update the date at the top and, where the change affects how your data is handled, notify you in the application.
Contact
A support contact address has not been configured for this deployment.