Last updated: 19 November 2026.
This policy describes what Trigger & Trial does with personal data. It covers this website and the Trigger & Trial platform. The contracting entity is stated on your order form; for early access participants, it is the entity named in the individual agreement.
The short version
- This website runs no third-party analytics, advertising or tracking scripts. No cookie banner is required because no non-essential cookie is set.
- We collect the minimum we need to run the service, and we say what it is below.
- You can ask us to export or delete your data at any time, and we will do it.
- We do not sell personal data. We do not share it with advertisers, because we have no advertisers.
Data we collect
When you use this website
Server logs. Like any web server, we log requests: IP address, timestamp, requested URL, user agent, referrer. These are used for security (abuse detection, intrusion investigation) and for capacity planning. They are retained for 30 days and then deleted.
No analytics. We do not embed Google Analytics, Plausible, Fathom, Hotjar, Meta Pixel, or any comparable script. We do not build cross-site profiles. The only thing we count is aggregate request volume, computed on the server.
Cookies. None are set by this website. The platform itself sets a single strictly-necessary cookie for session continuity when you are logged in.
When you use the platform
Account data. Email address, display name, organisation name, and authentication identifiers. Retained for the life of the account.
Tenant content. Your specifications, the code generated from them, verification results, defect records, and audit logs. This is the substance of the service, and it is retained for as long as your account is active, then per your retention settings.
Build and environment metadata. Which model version was used, which tools ran, how long each stage took, resource consumption, and the identity of the user who approved each clause. We need this to reproduce a build, to bill accurately, and to answer "who approved this?".
Operational logs. Build logs and environment logs, which are large and low-value, and are deleted on a rolling retention window (30 days by default). They do not go into the primary database.
Payment data. Card details are handled entirely by our payment processor. We receive a token and the last four digits. We never see or store a full card number, and we are therefore not in scope for cardholder-data self-assessment under PCI DSS.
Why we are allowed to process it
| Data | Legal basis |
|---|---|
| Account data | Performance of a contract with you |
| Tenant content | Performance of a contract with you |
| Build and environment metadata | Performance of a contract with you; legitimate interest in operating and improving the service |
| Operational logs | Legitimate interest in security and service stability |
| Server logs on this website | Legitimate interest in security |
| Payment records | Legal obligation (tax and accounting) |
| Marketing email, where you asked for it | Consent |
We do not use your tenant content to train third-party models. Where a model provider processes your content, the provider operates under contract on our instructions and the data is not retained by them beyond the request.
International transfers
The control plane runs in Southeast Asia. Trial environments are deployed in the region closest to you, which may be North America, Europe, or Asia-Pacific. Some processors are located elsewhere, including in the United States.
Where personal data leaves the EEA or UK, transfers are covered by Standard Contractual Clauses or an applicable adequacy decision. A list of subprocessors with their locations is available on request.
Retention
| Category | Retention |
|---|---|
| Server logs (this website) | 30 days |
| Operational build logs | 30 days by default, configurable up to 90 |
| Verification results and defect records | Life of the account, unless you set a shorter window |
| Approval and audit history | Life of the account |
| Inactive account tenant content | 90 days after account closure, then deleted |
| Invoices and accounting records | As required by tax law |
Your rights
Depending on where you are, you may have the right to:
- Access — get a copy of your personal data
- Rectification — correct inaccurate data
- Erasure — have your data deleted
- Restriction — limit how we use it
- Portability — receive it in a machine-readable format
- Object — object to processing based on legitimate interest
- Withdraw consent — for anything done on consent
- Complain — to your supervisory authority
Under the UK GDPR and EU GDPR, we are the data controller. Under the CCPA/CPRA, we are a "business" and you have the right to know what we collect, to delete it, and to opt out of its sale or sharing — we do neither, so there is nothing to opt out of.
To exercise any of these, email privacy@tnthub.com. We respond within 30 days. We will verify your identity before acting, and we will tell you if we need more information.
If you are in the EEA or UK and we have not resolved your complaint, you may complain to your local supervisory authority.
Data deletion requests
We can locate your data across the systems that hold it: the primary database, the audit store, object storage (build artifacts, logs, recordings), your Git repository (which you own and control directly), and any regional trial environment.
Deletion from your Git repository is your action, not ours — we commit to your repository, we do not administer it. We will tell you where to look.
Children
The service is not directed at children, and we do not knowingly collect data from anyone under 16.
Security
Transport encryption everywhere, including into build environments. Secrets are injected into running processes and never written to logs. Build environments run with read-only root filesystems, an outbound allowlist, and per-tenant credentials. Trial environments are single-tenant and destroyed on request or after their idle window.
A detailed description of our security model is in the security documentation.
Changes
Material changes are announced at least 14 days before they take effect. Changes that reduce your rights take effect only after direct notification.
Contact
privacy@tnthub.com — or use the contact page.