Legal
Platform Privacy Notice
Last updated: 2026-11-14
Scope
This notice covers the platform app.trausto.com: what RiskZone GmbH processes about the people who hold an account there or are invited to it by e-mail. The public website trausto.com has its own privacy policy.
Your organisation's data and ours
For project content, and for the user data a customer organisation manages on the platform (its members, their roles and its invitations), the customer organisation is the controller and informs its own users; RiskZone GmbH processes that data on its behalf as processor. A data processing agreement under Art. 28 GDPR and Art. 9 FADP is concluded with each customer organisation before processing begins; it sets out the details.
This notice describes what RiskZone GmbH processes for its own purposes: providing accounts and sign-in, securing the platform, sending its e-mails and operating the service.
Project content is encrypted in your browser before it is stored, and the server stores it as ciphertext it cannot read. The exception is an AI import through a server-routed AI model: that request passes through our server in the clear while it runs, and its content is not stored. What the server can read is set out item by item in section 7 of the whitepaper.
1. Controller
RiskZone GmbH, Schützenweidstrasse 4, 6023 Rothenburg, Switzerland. Contact for privacy requests about the platform: privacy@trausto.com.
2. Data we process
- Account: your e-mail address, your language and region settings, and when the account was created.
- Passkeys: for each passkey its public key, the device name, when it was created and last used, and whether it was removed. Your private key is stored only in encrypted form.
- Sessions: when a session was created and when it expires, your browser's user agent, and a coarse prefix of the IP address it was created from.
- Memberships and invitations: the tenant, organisations and projects you belong to, with your role and since when; for an invitation, the invited e-mail address, the role and the times, also when that address has no account.
- Audit log: what was done on the platform, by which account, when and with what result, together with a keyed pseudonym of the IP address. Entries about identity, such as an invitation or an e-mail change, carry e-mail addresses in plain text. Text you write, such as project or organisation names, is never written to the audit log.
- Protection against misuse: rate-limit counters, each under a keyed hash of what it counts: an e-mail address, an IP address, or a session, user or project id.
- E-mail: the recipient address and the content of the platform's e-mails: sign-up and address-change codes, invitations and notices.
- Operational logs and metrics: the platform's workers write operational logs, and the platform records operational metrics. The operational logs contain technical details of requests: time, requested path, result and duration, account, organisation and project IDs, and e-mail addresses shortened to their first and last two characters. They never contain project content.
- AI import through a server-routed model: the content you choose to send (the names of the project's entities, the files you attach and the prompt you type) passes through our server for the duration of the request and is not stored. The audit log records for each attempt who ran it, on which project, the provider, the model where known, success or failure and its duration, and the token counts the provider reported.
3. Purposes
We process this data to provide your account and sign-in, to protect the platform and its users against misuse, to send the e-mails the platform needs, to keep the audit trail that customer organisations rely on, and to operate the service and investigate faults.
4. Legal basis
For users in the EU or EEA, the processing rests on these legal bases under the GDPR:
- Account, sign-in, passkeys, sessions, memberships, invitations and the platform's e-mails: performance of the contract, Art. 6(1)(b) GDPR.
- Protection against misuse (rate limits), security, audit log, operational logs and metrics: our legitimate interest in secure and stable operation, Art. 6(1)(f) GDPR.
- Retention where the law requires it: legal obligation, Art. 6(1)(c) GDPR.
- AI import through a server-routed model: performance of the contract; you start the import yourself, after giving your consent in the app beforehand.
For users in Switzerland we process the data under the Swiss Federal Act on Data Protection (FADP) for the purposes stated.
5. Recipients
The platform runs on Cloudflare (compute, database, object storage and key-value store), and its e-mail is sent through Mailgun in its EU region. A server-routed AI request goes to the provider of the AI model it uses. All of them, each with what it sees, are listed on the subprocessors page. If your organisation connects its SIEM, that endpoint receives the audit events, including the e-mail addresses they carry.
6. Location
The platform's database, object storage and key-value store were created in Cloudflare's EU jurisdiction. Cloudflare stores operational logs and operational metrics in its global network; they may be processed outside Switzerland and the EU, including in the USA. Cloudflare is certified under the EU-U.S. Data Privacy Framework and its Swiss extension; in addition, the standard contractual clauses in Cloudflare's data processing addendum apply.
7. Retention
- Account and passkeys: until the account is deleted.
- Sessions: at most 30 days.
- Audit log: 90 days by default. After an account is deleted, its audit entries stay for that time. The account is no longer linked as the acting account, but entries that concern it, including the one that records the deletion, still name its id and e-mail address. Copies in your organisation's SIEM follow your organisation's retention.
- Invitations: 7 days while pending; once accepted, revoked or declined, 90 days after they ended.
- Onboarding codes bound to an e-mail address: 90 days after the code expired, was revoked or was used up.
- Rate-limit counters: until their counting window ends.
- Sign-in, registration and recovery records: from a few minutes to 7 days; a confirmed e-mail change until it is applied or cancelled, at least 72 hours.
- Operational logs: 3 days; from 1 December 2026, 7 days.
- Operational metrics: 3 months.
- Point-in-time history of the platform database: 7 days, kept by the database provider for disaster recovery. A restore from it would bring back rows deleted since.
- E-mails at the mail provider: Mailgun keeps delivery logs and stored copies of the messages for at most one day.
8. Your rights
Under the FADP and the GDPR you can ask for access to your data, for its correction or erasure, for restriction of processing and for data portability, and you can object to processing. Before we hand out data or delete an account we verify that the request comes from you; an e-mail alone is not enough.
Some of this you can do yourself: Account → Profile → Export Account Data gives you your account data, Account → Devices lists your passkeys, and you can delete your account once you no longer own an organisation or project and are not a tenant administrator.
For project content and for data your organisation manages, please contact your organisation: it is the controller for that data, and we support it as its processor.
You can lodge a complaint with the Swiss Federal Data Protection and Information Commissioner (FDPIC). Users in the EU or EEA can also contact the supervisory authority of their place of residence or work.
9. Changes
We update this notice when the platform or its processing changes. The current version is available at /en/platform-privacy.