Keeping an analysis
Last reviewed 6 October 2026
What this is
An addition to the Terms and the data processing agreement, agreed separately because it changes one thing: whether we keep the shape of a database you analysed.
By default we keep nothing. An analysis runs in your own browser, or over a connection that closes when it is finished, and what stays with us is the measurement - how many tables, how hard the job is, what it would cost. This page is about choosing otherwise, for one workspace at a time.
What is kept, exactly
- Table names, and for each table its column names, their types, which are keys, how many rows and how many bytes.
- Every relationship found, with how it was established: declared by the database, declared by the engine, inferred from values lining up, or inferred from a name.
- The corrections you made by hand: which links you confirmed, which you rejected.
- The engine the database was recognised as.
What is never kept
No values from your database. Not a row, not a sample, not a preview, not a column comment. The record is built from the fields listed above rather than by removing what we do not want, so a field invented tomorrow cannot arrive with data behind it.
Nothing identifies the people in your database, because nothing from inside the tables is read into it.
The one thing you can put there yourself
Where you describe a rule of your own - a column computed from others, a constant like "country: BG", a correction to one row - what you type is kept with it, because a rule without its own words is not a rule.
That is the only way a value reaches us, and it reaches us because you wrote it. Everything said above still holds for what we read from your database; this paragraph is about what you write by hand. Keep out of those boxes anything you would not want on our server, and remember that the same switch removes all of it.
Where it is, and for how long
On our servers in the European Union, for 90 days from the day it was kept, and then deleted automatically. Sooner if you ask: turning the switch off deletes what was kept, and so do Delete my data and closing the account.
Who can see it
- You, in your account.
- An agent you connect, if you also open that workspace to agents — a separate switch, with its own token you can take back at any time.
- Us, only while you open a workspace for support, which you set for a few days and which closes itself. Every time we look is written in the history you can read. We do not keep or read schemas for our own purposes.
What this does not change
This is your instruction to keep it, which is what the law asks to be documented. It is not a transfer of responsibility: we remain responsible for protecting what we hold, for telling you about a breach, and for everything else the data processing agreement says. A term that tried to take that away from you would not be worth the pixels, and we have not written one.
What you are responsible for is the choice — whether the shape of this particular database may sit on our server at all. Nobody but you can answer that.
If you change your mind
Turn the switch off. What was kept is deleted in the same action, and nothing new is kept. You do not have to ask us, and you do not have to explain.