Privacy by architecture, not by slogan.

1. Who controls personal data

The data controller is the operator identified in Trigner's Legal Notice.

• Operator: Andris Tukiss
• Address: Pending publication before external commercial launch
• Privacy contact: info@trigner.com

2. What Trigner currently processes

Browser workspace data. Startup ideas, assumptions, missions, evidence, decisions, outcomes, research notes, rollback copies and related workspace state are stored in your browser using local storage. This data is designed to remain on your device unless a specific feature sends the minimum needed information to a Trigner API or you export/share it yourself.

Public API request content. The current Reality Check, evidence-normalization and Proof State endpoints process the request you send and return a result. The application code does not write those request bodies to a Trigner application database in this build.

Security metadata. Hosting infrastructure necessarily receives network request information. The Trigner request guard may use forwarded network and user-agent hints transiently to derive an ephemeral in-memory rate-limit hash; the application does not intentionally retain the raw network identifiers in product telemetry.

Optional local product telemetry. If you choose “Allow optional local analytics,” Trigner stores a bounded set of allowlisted product events and properties on this device. Founder-authored startup/customer/evidence text and top-level startup/session identifiers are excluded. If you reject or withdraw permission, new telemetry is disabled and stored telemetry is cleared.

Local feedback. When you deliberately save founding feedback, the rating and optional note are stored in this browser. Comment text is not copied into product telemetry.

Payments and accounts. This build does not provide live paid subscriptions or user accounts, and Trigner does not store raw payment-card credentials.

3. Purposes and legal bases

• Provide the product actions you request and maintain your local workspace.
• Protect the service, rate-limit abuse and diagnose technical failures.
• With your consent, keep optional local product-usage events on your device.
• Store feedback you deliberately ask the browser to save.
• Meet legal obligations and establish, exercise or defend legal claims where necessary.

Where the GDPR applies, relevant bases may include performance of the service/steps requested by you, legitimate interests in security and service integrity, consent for optional processing, and compliance with legal obligations.

4. Cookies and browser storage

Trigner uses one technical consent-preference cookie and browser local storage. Optional analytics storage is disabled until you opt in. See the Cookie & Local Storage Policy for the current inventory and how to change your choice.

5. Hosting and recipients

Trigner is currently deployed using Vercel infrastructure. Infrastructure providers may process technical request data as necessary to host and secure the service. Trigner does not currently include advertising networks or third-party analytics scripts in the application code.

The current public Reality Check route uses Trigner's rules engine in application code rather than a third-party generative-AI model. If external AI/research processors are enabled later for private founder data, this policy will be updated before that processing is activated.

6. International transfers

Infrastructure providers may operate internationally. Where GDPR transfer rules apply, Trigner will rely on an applicable adequacy mechanism or appropriate safeguards required by law. Specific processor and transfer details will be finalized with the operator information before broader external launch.

7. Retention and deletion

Local workspace data remains in your browser until you delete it, replace it, clear site storage/browser data, or use Trigner's Vault controls. Optional local telemetry is capped and remains local until deleted or permission is withdrawn. The consent-preference cookie lasts up to 180 days unless you change or clear it sooner.

Trigner's application code does not intentionally persist current public API request bodies in an application database. Hosting/security infrastructure may maintain operational logs according to provider configuration and applicable law.

8. Your rights

Where GDPR or similar law applies, you may have rights to access, rectify, erase, restrict or object to processing, receive portable data, and withdraw consent without affecting earlier lawful processing. You may also complain to the competent supervisory authority; in Spain this is the Agencia Española de Protección de Datos (AEPD).

For data kept only in your browser, Trigner provides direct export and deletion controls in the Vault. For server-side rights requests, contact the operator using the details in the Legal Notice.

9. Automated decisions and founder responsibility

Trigner structures evidence and suggests next actions, but it is not designed to make legally significant automated decisions about you. Business decisions remain yours. Simulation, scores, heuristics and generated suggestions should not be treated as verified facts.

10. Sensitive data and children

Do not submit passwords, payment-card data, government identifiers, health data, special-category personal data, confidential customer data, or other regulated information unless Trigner explicitly introduces a feature designed and documented for it. The alpha service is intended for adults using it for business/startup work.

11. Changes

We may update this policy as the product, processors or law change. Material changes will be reflected by updating the date above and, where required, by requesting a new choice or consent.