Your data in Tessa Cloud
Die deutsche Fassung ist massgebend / The German version is binding. Binding German version
In short: everything your team creates in Tessa Cloud belongs to you. You can export it at any time, free of charge, in every state of your organisation. And when you leave, we delete it.
What you own
Scenarios, test plans, schedules, reports with screenshots and logs, recordings, the App Map, uploaded builds, and the member list. We store and process this data only to run Tessa Cloud for you. We do not train AI models on it and do not pass it on, except to the subprocessors we need for operations and to the AI provider you configured yourself with your own API key.
Export: any time, free, in every state
During the trial, on an active subscription, in read-only state, and after a lock: export is always open to you until the data is deleted. It costs nothing, and you do not need to give a reason. This is not goodwill; it is written into the General Terms, section 11.
What the archive contains
- Scenarios with all their versions
- Test plans and schedules
- Reports of every run with screenshots and application logs, plus recordings where you enabled them
- The App Map with the observed screens and transitions
- Your organisation’s settings and integrations
- The member list of your organisation, including open invites
- Your organisation’s plan and billing state, with the versions of the legal documents you accepted
Everything is in open formats: JSON, PNG, text, MP4. A README explains the layout, and a manifest lists what is in and what was left out, and why. Stored secrets such as API keys never land in the archive, and neither do uploaded builds – you hold the originals.
Retention after cancellation
At the end of the paid period your organisation is locked. We then keep the data for 90 days so you can export at your own pace or come back. After those 90 days we delete it for good. If you are in a hurry, we delete earlier on request. Details are in the General Terms, section 8, and in the Data Processing Agreement.
The exit that is always open: Tessa Sovereign
Would you rather run Tessa in your own infrastructure? Tessa Sovereign is the same Tessa stack, on Docker or Kubernetes in your environment, with your identity provider and your AI endpoint. Your export from Tessa Cloud is the basis for the move. More about Tessa Sovereign.
How to export
As an owner of your organisation, open the organisation settings and start the export with one click. Tessa packs the archive in the background, and as soon as it is ready you download it as a ZIP file. The same archive is available through the API, so a script can fetch it too.