Security & data

We take the security of your data seriously. Reverse Migrations combines layered encryption with an AI provider that does not retain your data. Here is what we use and how we protect it.

Database schema

Table and column definitions, relationships, indexes, schema comments, and schema changes provide context about your database. We use schema metadata, rather than application rows.

Required permissions vary by engine. MySQL’s required SELECT privilege also permits reading table data. See the account guides for PostgreSQL, MySQL, or SQL Server.

Repository content and instructions

Source code and project files from your connected repository, together with the instructions you provide, give context about your application and its conventions. This information and the relevant schema content are used in AI processing.

Account and connection information

We use account and organisation details, database connection credentials, repository and branch information, and run history to provide the service.

Layered encryption

We protect stored data with database-level encryption. Database credentials, schema definitions, and schema diffs are also encrypted at the application level before storage, giving this sensitive information two layers of encryption.

AI data retention

Our AI provider does not retain any data submitted for AI processing. This includes the schema information, repository content, and project instructions used in requests.

Questions about your data?

Contact [email protected].