Data export and deletion policy.

This policy explains what data a customer (“you”) can take out of the hosted Supersecret service at platform.supersecret.ai and how, what happens when data is deleted while you use the service, how long backups keep deleted data, and what Supersecret Technologies OÜ (registry code 17468227, Veetorni 11, Rapla, Estonia) (“we”, “us”) does with your data when the agreement ends.

Version 1.1 · Last updated: 16 November 2026

Scope

This policy applies to the hosted service. Read it with the Data Processing Agreement (“DPA”, in particular its section 9 and Annex II), the Security overview and the Sub-processor list. If this policy and the DPA conflict, the DPA prevails.

1. What data the service holds

Workspace and people

Your workspace settings, members, roles, sign-in settings, approved connections.

App code

Every version of every app your people or their AI tools deployed.

App data

The database inside each app that declares one (SQLite), and the app’s own disk.

Uploaded files

Documents and media people upload through your apps.

Audit trail

A record of administrative changes and sensitive actions in your workspace.

Usage figures

Resource use and backup health per app (kept 90 days hourly and 400 days daily).

Adoption figures

Which apps people use and how. Each person’s figures per app and day are kept 13 months, single visits with their paths 90 days; totals per app carry no names and are kept.

Backups

Encrypted copies of app databases, and our hosting provider’s backups of the platform database.

2. Exporting your data

You can export your data yourself at any time during the term, without asking us. There is no single “export everything” button today; each kind of data has its own export:

App code

  • Who can export: The app’s owner and workspace administrators, and their AI tools

  • How: Download any version as a zip from the app’s history; clone it with git (every version is a git commit); or set up a copy to your own git repository (for example on GitHub or GitLab), which is updated after every new version

  • Format: Zip of source files; git repository

App data (database)

  • Who can export: The app’s administrators and their AI tools

  • How: Export a table, or the result of a query, from the app’s data screen, the API or the AI tool connection

  • Format: CSV or NDJSON (one JSON record per line)

App data with personal data

  • Who can export: As above; an export that reads columns marked as personal waits for a workspace administrator’s approval

  • How: Request the export; download it after approval

  • Format: CSV or NDJSON

One person’s data (data subject request)

  • Who can export: Workspace administrators

  • How: Open a privacy request for the person; download a copy of their records from every app that holds them

  • Format: Zip

Audit trail

  • Who can export: Workspace administrators

  • How: Start an export for a date range from the Audit log screen or the API

  • Format: Zip with the records (CSV or JSON Lines), a file of daily SHA-256 digests that lets you check that no day was changed, and a README explaining how to check them

App inventory, data map, privacy register

  • Who can export: Workspace administrators

  • How: Download from the admin screens

  • Format: CSV (data map also NDJSON)

Uploaded files

  • Who can export: People with access in the app

  • How: Download through the app that holds them, one file at a time

  • Format: Original files

Limits and expiry

  • Audit trail exports are prepared in the background and stored for 7 days, then deleted. Each download link works for a few minutes and is created again when you click Download.

  • App data, code zips, inventory and privacy exports are produced at the moment you download them and are not stored by us.

  • A workspace can start up to 10 background exports a day.

  • There is no bulk export of uploaded files today. Until there is, on request we provide an archive of all of a workspace’s uploaded files during the exit window (section 5), at no charge.

  • Data in your apps is exported in the shape your apps store it. We do not convert it to another app’s format.

3. Deleting data during the term

An app (by its owner or an administrator)

  • What happens: The app stops at once and can no longer be opened. Its running copy and disks, including its live database, and its adoption figures are removed immediately.

  • When it is gone: Database backups: purged from 7 days after deletion (the next maintenance run after that). Stored code versions: purged 30 days after deletion. Uploaded files: moved to the trash with the app and purged under the files rules below. A record that the app existed (name, owner, dates) stays in the audit trail.

A file in an app

  • What happens: Moved to the trash. A workspace administrator can bring it back while it is there.

  • When it is gone: Purged after the workspace’s trash window (30, 60 or 90 days; default 30), or at the end of the workspace’s minimum retention for files (none, 1, 3, 5, 7 or 10 years from upload), whichever is later, and never while a legal hold covers it. Overwritten storage versions expire 14 days after that.

A person removed from the workspace

  • What happens: Their membership, sharing grants and API keys end at once, and their access to apps stops.

  • When it is gone: The apps they own stay, for an administrator to keep, hand over or delete. Their adoption figures are deleted. Their name stays in the audit trail as the author of past actions.

A person’s data inside apps (erasure request)

  • What happens: A workspace administrator confirms an erasure for the person; matching records are deleted from every app that holds them, including data apps share with each other.

  • When it is gone: At once in live data. Backups keep the old copy until they expire (section 4). If an app’s database is later restored from a backup, the erasure is applied again automatically after the restore.

Data your app deletes itself

  • What happens: Deleted in the live database by your app.

  • When it is gone: Remains in that app’s backups until they expire (section 4).

Audit records

  • What happens: Cannot be deleted or changed by anyone.

  • When it is gone: At the end of the retention period your administrators choose: 1, 3, 5 or 7 years. Shortening it takes effect after 7 days.

Drafts. An app only its owner can see that nobody has used for 30 days is archived (stopped), not deleted. Its owner can start it again.

4. Backups

App database backups

  • What it holds: Each app’s database, copied continuously, encrypted with a key specific to that app (AES-256-GCM)

  • How long it is kept: History for restores goes back 30 days (the default). A deleted app’s backups are purged 7 days after deletion.

Platform database (workspaces, people, settings, audit records not yet archived, app metadata)

  • What it holds: Daily backups with point-in-time recovery, taken by our hosting provider’s managed database service

  • How long it is kept: 7 days

Archived audit records and stored app code

  • What it holds: Kept in encrypted object storage, not as separate backups

  • How long it is kept: As in section 3

Uploaded files

  • What it holds: Kept in object storage with versioning

  • How long it is kept: Older versions expire 14 days after they are replaced or deleted

Backups are kept in DigitalOcean’s Amsterdam region (AMS3); see the Sub-processor list. We do not delete individual records from backups; deleted data leaves backups when they expire.

5. When the agreement ends

Exit window: your administrators keep access to export data (section 2). Apps are stopped on the day the agreement ends; administrators can still sign in to export.

30 days after the end of the agreement

On request during the exit window, we help with exports the product does not offer itself (for example, all uploaded files).

Within the exit window, at no charge

We delete the workspace’s live data: apps and their disks, app code, uploaded files, audit archives, members and settings.

Within a further 30 days after the exit window

Encrypted backups that still hold your data expire.

Within 30 days after live deletion

We confirm deletion in writing, if you ask in writing.

Within 10 business days of the deletion being complete, or of your request if later

Deleting a whole workspace is carried out by our staff following a written procedure; the product has no self-service workspace deletion today.

Exceptions

  • Legal retention. We keep data only as long as a law that applies to us requires (for example, invoices and contract records under Estonian accounting law, 7 years). That covers our records about you as a customer, not the content of your apps.

  • Audit records you chose to keep. If you ask us to, we deliver your audit trail export before deletion. Otherwise audit records are deleted with the workspace, whatever retention you chose.

  • Legal holds. Data under a legal hold you placed is deleted at the end of the agreement like other data unless you ask us in writing to keep it, and we agree, for a stated time.

  • Copies outside our service. Copies you made yourself (exports, git copies on your own git host, data your apps sent to outside services) are yours to manage; we cannot delete them.

6. Customer-run installations

If you run Supersecret on your own infrastructure under a separate licence, your data never passes to us, and you control export, deletion and backups yourself. This policy does not apply to that data.

7. Timeline at a glance

App deleted

  • Day 0: Live app and its disks removed

  • +7 days: Database backups purged

  • +30 days: Stored code purged; files leave the trash (default window)

  • +60 days: |

File deleted

  • Day 0: In the trash

  • +7 days: | Purged (default 30-day window, no minimum retention or hold); old versions expire 14 days later

  • +30 days: |

Audit export created

  • Day 0: Available

  • +7 days: Expires

  • +30 days: |

Agreement ends

  • Day 0: Exit window opens

  • +7 days: | Exit window closes; deletion starts

  • +30 days: Live data deleted (latest)

  • +60 days: Backups expired (latest)

8. Contact

For export help, deletion confirmations and questions about this policy, write to privacy@supersecret.ai.

Change history

0.1

  • Date: 2 November 2026

  • Change: First draft for review.

1.0

  • Date: 16 November 2026

  • Change: Placeholders completed; first published version.

1.1

  • Date: 16 November 2026

  • Change: Adoption figures and their retention added; contact section added; timeline simplified.

© 2026 Supersecret Technologies, Estonia