We never sell your data. Here is exactly what we store.

Privacy Policy

Last updated: July 24, 2026 · Applies to VITNA and all COS TRINITY products

[ TL;DR — the short version ]

✓Cloud storage is the default. Your agents send events and checks to our API and we store them.
✓We store less than you send: raw action text and raw payloads from checks are not stored.
✓Rate limits are enforced server-side, so we do hold per-agent request counts.
✓We never sell your data or share it with third parties for their own purposes.
✓Want zero cloud storage of events? Local and desktop mode keeps them on your device, with the tradeoff that we cannot sign an evidence package for data we never receive.

1. Who We Are

VITNA is a product of COS TRINITY ("COSTRINITY"). We build developer tools for AI agent operators. Our registered contact is hello@costrinity.xyz.

2. What Data We Collect

Account data

Your email address and a hashed (bcrypt) password when you create an account. We never store plain-text passwords.

Billing data

If you upgrade, billing is handled by our payment processor. We never see or store your card details.

Agent events (cloud mode, the default)

In the default cloud mode your agents send events to our API and we store them. This is the mode you get from the REST API and the MCP server unless you explicitly choose local mode. See section 3 for exactly which fields are sent and stored.

Decision and evidence records

When your agent calls a compliance or safety check, we store a decision record server-side so it can be exported later as a signed evidence package. These persist on our servers for the retention window in section 5.

Operational metadata

Rate limits, plan caps, and the global trial ceiling are enforced server-side, which means we do hold per-agent request counts and timestamps. We are explicit about this because an earlier version of this policy incorrectly said we did not.

3. Exactly What Is Sent and Stored

This mirrors the "What VITNA sends and stores" section of our docs, and the two are kept in sync deliberately.

What is sent on a check

Whatever you pass to the tool. For action_preflight that is the proposed action text, an optional structured payload, and an optional short action-type label, plus your owner id and API key in headers. For the compliance checks it is the fields that check needs, for example purpose and data categories.

What is stored

Less than what is sent. The decision record stores the action TYPE label, the threat category and the pattern name that matched, the verdict and reason, timestamps, and owner and session identifiers. The raw action text and the raw payload are NOT stored. Data principals are referenced by UUID only, and detected secrets and PII are redacted before anything is written.

Ingested events

In cloud mode, the events you POST to the ingest API are stored as sent, including any payload you choose to include. You control what you put in a payload. Secrets and PII that our detectors recognize are redacted or tagged, but detection is heuristic and we do not guarantee it catches everything, so do not send material you do not want stored.

What we never collect

We do not pipe agent activity into Google Analytics, Mixpanel, Sentry, or any third-party analytics service. We do not build behavioral profiles for advertising, training data, or resale. We do not want your private keys or seed phrases; if you log one, treat it as compromised and rotate it.

4. How We Use Your Data

We use account data to authenticate you, bill the plan you signed up for, reach you about security or material policy updates, and answer support requests you start. We use agent event and decision data to operate the product for you: running the checks you call, enforcing plan and rate limits, producing your evidence exports, and debugging faults you report. We do not use it to train models, we do not sell it, and we do not share it for advertising.

5. Storage, Retention, and Security

Account credentials (email + bcrypt hash) and agent data live in a PostgreSQL database (Supabase), encrypted at rest and in transit. Retention depends on your tier: Free keeps event payloads 7 days and incident records 30 days; Pro and Team keep event payloads 90 days and incident records 1 year; Enterprise is custom per Master Services Agreement. Stating this plainly: no tier below Enterprise retains event payloads for six months, so if you have a six-month logging obligation, do not rely on our hosted retention alone. The way any tier satisfies it is to export the Ed25519-signed evidence package and keep it yourself. Once exported it is a self-contained artifact that does not depend on our retention or on our servers continuing to exist.

6. Local and Desktop Mode

Local mode is the alternative to cloud storage, and it is opt-in, not the default. With storage_mode set to local, events are written to your device rather than to our database: browser-mode events to your browser's IndexedDB, VITNA Desktop events to a local SQLite file in your OS user data directory. In that mode those events do not reach our servers and there is no server-side copy of them to read, share, or delete. Two honest limits. First, this scoping applies only to the event payloads held locally; account authentication, billing, and any check you explicitly call still involve our servers. Second, we cannot produce a server-signed evidence package for data we never receive, because signing happens where the signing key is, so local mode trades the signed evidence artifact for zero cloud storage of events.

7. Data Sharing

We do not sell, rent, lease, or share your data with any third party for their own purposes, ever. We use a small set of sub-processors to run the service, currently our database and hosting providers and our transactional email provider, each of which processes data only to deliver the service to you. Our payment processor receives your email when you upgrade, subject to its own privacy policy. The current sub-processor register is published at /api/compliance/sub-processors.

8. Your Rights

Export

Download your event history as JSON or CSV from the dashboard, and export signed evidence packages via the evidence export endpoint. In local mode the export is a local read with no server roundtrip.

Delete

Delete individual agents, their events, or your whole account from the dashboard. Account deletion removes your events, agents, alerts, incidents, data principals, and consent artifacts. Append-only security and audit log rows are retained with the owner reference removed, because a tamper-evident audit log we can silently rewrite would not be an audit log.

Correction

Update your account email from the dashboard.

GDPR / CCPA / DPDP

If you are in the EU, California, or India you have the right to access, rectify, erase, and port your data. In cloud mode we hold the data, so contact us and we will action it. In local mode most of these rights are already exercised on your own device. Contact hello@costrinity.xyz.

9. COS TRINITY, All Products

This policy applies to all current and future COS TRINITY products including VITNA (compliance and safety evidence for AI agents), GRiiD (Solana trading primitives, archived), CRYpT (desktop file encryption, archived), and any products we release in the future. The core principle is the same across all of them: your data is yours, we do not sell it, and we do not share it with third parties for their own purposes.

10. Changes to This Policy

If we make material changes to this policy, we will notify you by email (at the address on your account) at least 14 days before the change takes effect. The updated date at the top of this page always reflects the last change.

11. Contact

Questions, data requests, or concerns: hello@costrinity.xyz. We respond within 48 hours.

← Back to VITNA Terms Docs Dashboard