We use third-party providers for cloud hosting, email, and payments. Publishing a named list on a marketing page ages badly and would be treated as a control. Scale customers can request the current list and change notifications as part of their agreements.
| Category | Why it exists | Customer data involved |
|---|---|---|
| Cloud hosting | Control-plane compute, storage, and networking. | Operational metadata. Not customer database rows or passwords. |
| Transactional mail such as invites and notifications. | Names and email addresses you give us. Not query results. | |
| Payments | Billing for paid plans. | Billing identity. Card data is handled by the payment provider, not stored as a Migratrix product feature. |
| Natural-language SQL | Generating SQL from natural language, when AI SQL is switched on for your organisation. | The prompt and schema context required to generate SQL. Not a standing copy of your tables. |
Email legal@migratrix.com or start a security review. We will send the current list, not a screenshot of this page with invented vendor names.
Database passwords stay on the Executor. Production rows are not retained on the Migratrix control plane. See data handling.