We do not keep your production data
Migratrix operates on a zero data-retention principle for customer database contents and credentials. The platform is useful because of metadata who approved what, which script ran, which environment exists not because we copied your tables.
What is stored where
| Kind of data | Where it lives |
|---|---|
| Database rows and result sets | Not copied or retained on Migratrix servers. Transient results used to render Explorer or a diff are encrypted in transit and discarded after processing. |
| Database credentials | Encrypted on the Executor host under your control. Never stored on the Migratrix platform. Never written to logs. |
| Drift snapshots | Schema snapshots for Drift Monitor are stored in a _migratrix schema on the monitored database, on the Executor side. |
| Operational metadata | Users, roles, pipeline definitions, change-script metadata, Git linkage, licence details, and audit events on the control plane. |
| Audit payloads | Who did what, when, and in which environment. Designed to exclude secrets and sensitive row contents. |
The smallest set that still runs the product
No standing copy of production
A compare or an Explorer query is a live call through the Executor. It is not a warehouse of your data in our cloud.
Logs without secrets
Application, Executor, and infrastructure logs are aggregated with defined retention. Customer secrets and sensitive payloads are excluded by design.
You can still export
Explorer can export CSV, SQL, or JSON to the person who is allowed to see those rows. That export is an attributed action in the audit trail, not a copy we keep.
No masking product
Access is governed and logged. Irreversible anonymisation of exports is not a Migratrix feature today. Do not write that into a control mapping as if it exists.