Data handling
What happens to your data, what we keep, for how long, and where it lives.
| Processed, not stored | Your rows are loaded into a private working file for the job, profiled and checked, then deleted. Rows are never kept. |
|---|---|
| Hosted in the European Union | Account data and results are held on a server hosted in the European Union. This website is served from a global network and holds no customer data. |
| Retention you can set | Profiles, reports and the audit log have default periods that an organisation administrator can change. Deleting an organisation removes its data. |
How a job processes your data
- A job reads your source (an upload, a file or table you point us to, or an object store) with read-only access.
- The data is loaded into a private working file that is locked down: no file or network access from your rules.
- The profile and the rule results are computed, and the results are saved.
- The working file is deleted when the job ends. An upload is kept only if you tick "Keep file for re-runs".
What is stored
| Results | Column types, counts, statistics, histograms and rule results. By default also top values, minimum and maximum, and up to five failing example values per rule. |
|---|---|
| Sensitive columns | For columns detected as sensitive, no top values are stored and minimum, maximum and failing examples are redacted. Detection is a heuristic and is labelled inferred; it can miss a column. |
| Strict privacy mode | Stores no sample values at all. |
| Catalogue and account | Dataset names, descriptions, owners, tags, rules, schedules, reports, the audit log, and your organisation, membership and sign-in records. Source connection details are stored encrypted. |
| On-device mode | The console can profile a file in your browser. The file stays on your device. Only if you choose to publish the result is it sent to us. |
How long it is kept
| Record | Kept for |
|---|---|
| Profiles and assessments (the latest per dataset is always kept) | 365 days |
| Reports | 90 days |
| Audit log | 12 months |
| Usage records | 13 months |
| Request logs | 30 days |
| Account data after you close it | 30 days |
| Encrypted database backups | 14 days |
| Uploaded files you chose to keep | Until you delete them or delete the organisation |
An organisation administrator can shorten the periods for profiles, reports and the audit log in Settings. Organisations created before these defaults were set may have longer periods until an administrator changes them.
Where it is hosted and who processes it
The API and the stored data are on a server hosted in the European Union. The website and console are static pages served by Cloudflare, which also carries traffic to the API. GitHub receives the sign-in request. Some providers operate outside the EU and the UK; for those transfers we rely on the providers' own safeguards. We do not sell your data and the site uses no analytics or advertising trackers.
Deleting and exporting
An organisation owner can export the organisation's configuration and metadata and can delete the organisation with everything in it. Closed accounts are purged after 30 days. To ask for anything else, use the contact address in the page footer.
This page summarises the Privacy Notice, which is the full statement. DQaaS holds no certification, and making a claim of legal compliance is a matter for each deployment and its users, so please read the notice before you load personal data.