Your records pass through. They don't stay.
A migration touches every record you have. Here is how FlitStack AI handles them, as set out in our privacy policy.
FlitStack AI processes CRM records in memory only: they are never written to disk or kept after the migration. Traffic is encrypted with TLS 1.2+, cached metadata with AES-256, access is scoped per migration, and subprocessors are published.

Processed in memory
Records are processed in memory and never written to disk or kept after the session.
Encrypted in transit and at rest
TLS 1.2+ in transit. Cached schema metadata is AES-256 encrypted and erased after.
Scoped access
Credentials are scoped to one migration and used only by the migration systems.
Published subprocessors
Every provider is under a Data Processing Agreement and listed in the privacy policy.
Breach notification
You are told of a confirmed breach affecting your data within 72 hours.
Regulatory alignment
Aligned with GDPR and CCPA. Certifications and audits are under way.
The full detail, including the subprocessor list, is in the privacy policy.
Security
Security review for your migration?
Send us your questionnaire or ask for a call with an engineer.
Contact us