---
title: "Security: How FlitStack AI Handles Your Data"
description: "How FlitStack AI protects data in a migration: in-memory processing, TLS 1.2+ in transit, AES-256 for cached metadata, scoped access, published subprocessors."
url: "https://flitstack.ai/security"
---

# 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.

In short

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.

[Ask a security question](https://flitstack.ai/contact)

![Records pass through a protected, in-memory process and are not stored](https://flitstack.ai/images/illustrations/security.webp)

✓ In memory only ✓ TLS 1.2+ ✓ AES-256 metadata ✓ Scoped access

### 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](https://flitstack.ai/legal/privacy-policy).

Security

## Security review for your migration?

Send us your questionnaire or ask for a call with an engineer.

[Contact us](https://flitstack.ai/contact)
