Your data
The short version, in the order it matters. The binding version is the legal page, linked below; this is here so nobody has to read a policy to learn what happens.
What leaves your database
The shape — table names, column names and types, how many rows. And a sample of rows where a screen needs one: the preview of five rows, the tree of keys inside a cell, the names of the attributes a table uses. Those are read when a screen asks, answered, and not stored.
A migration, when you run one, reads the rows it is migrating. That is the work itself, and it goes from your source to your target.
What we keep
A measurement of an analysis — the difficulty level, the size band, how many tables, what would not be carried — so an estimate can be quoted and an invoice can name the figure it was raised against. The schema itself is not kept.
Your corrections, where you have a licence that keeps them: which link is wrong, what a table holds, which key inside a cell goes where. Those are decisions about a schema rather than the data in it.
The binding pages
- Keeping an analysis — what is kept when you ask us to keep an analysis, and for how long.
- Privacy Policy — everything about personal data, including yours as a customer.
- Data Processing Agreement — the terms under which we process data on your behalf.
What this does not do
This page is a summary and binds nobody. Where it and a legal page differ, the legal page is the one that counts — and the difference is a defect worth telling us about.
We do not keep a copy of your database. There is no import that takes everything and works on it later: reading happens when a screen asks, and the answer is not stored.
A dump uploaded for an estimate is yours and goes when you delete it. Nothing in this product trains on anything.