Privacy Policy

Effective October 10, 2026hi@usetrinity.ai

Trinity connects the tools your team already uses and turns them into a shared project memory, which means it draws on a great deal of your team's work. This policy sets out what we collect, how we use it, who else it reaches, how long we keep it, and the rights you have over it.

Overview

This policy describes how Trinity (“Trinity,” “we,” or “us”) collects, uses, and protects information in connection with the site at usetrinity.ai, the application at app.usetrinity.ai, and any correspondence you send us. It applies to everyone who visits the site or uses the product.

For workspace content, your organisation is the data controller and Trinity is its processor: we handle that content on your organisation's instructions. If your organisation has signed a separate agreement with us, that agreement governs its workspace and takes precedence over this page wherever the two differ.

Information we collect

Account information

You sign in with Google or GitHub. From that provider we receive:

  • Full name
  • Email address
  • Profile picture
  • The provider's account identifier

We never see or store a password. We also record the workspace and organisation name you set up.

Workspace content

Once you connect a tool, Trinity reads the project activity you've given it access to. This is the raw material your project memory is built from, and it typically includes:

  • Messages in the channels you connect
  • Issues, tickets, and their status and assignees
  • Commits, pull requests, and repository metadata
  • Documents and pages
  • Meeting notes and transcripts
  • Calendar entries

Connected services data

With your explicit authorisation, Trinity accesses data from the third-party services you choose to connect, including Slack, Linear, Jira, Notion, GitHub, Granola, and Google Calendar. Each connection is made through that service's own authorisation flow, with the scopes you approve and no more.

For Google Calendar, Trinity asks for read-only access to your calendar list and to events on calendars you select in Trinity or explicitly share with a project. Calendar data can include calendar names, time zones, sync status, event titles, descriptions, times, locations, organisers, attendees, conferencing details, recurrence, visibility, and update or cancellation status. Trinity does not create, edit, or delete Google Calendar events.

Trinity uses Google Calendar data to keep selected calendars synchronised on Trinity's servers and to show the upcoming events you selected for personal use in Trinity. Your selected Calendar data stays private to you unless the calendar owner explicitly shares that calendar with a project.

Agent activity

If you use the agent context layer, we record coding-agent sessions along with their token usage, cost, and the model used, so the work can be measured.

Billing information

Payments are handled by Stripe. Card details go directly from your browser into Stripe's card vault and never reach our servers. We keep your plan, seat count, billing email, invoice history, and the last four digits of the card.

Technical and usage information

We collect what's needed to run and secure the Service, and to understand how it's used:

  • Authentication and service-access logs
  • API usage records for connected services
  • System performance and error diagnostics
  • Anonymous public-site page and app-link counts, optional public-site visitor analytics, and product analytics in the app: pages viewed, features used, browser and device type

Communications

If you email hi@usetrinity.ai or book a call, we keep the conversation.

How we use information

  • Running the product: building and maintaining your project memory, answering questions and citing the activity behind the answer, keeping issues in sync, routing work, and preparing digests.
  • Account creation, authentication, and access control.
  • Integration with the third-party services you authorise.
  • Billing, and essential emails about your subscription.
  • Support, when you write in.
  • Security monitoring and operational maintenance.
  • Understanding in aggregate which parts of Trinity get used, so we know what to improve.
  • Meeting our legal obligations.

We don't use your workspace content for advertising, and we don't disclose it to other customers.

Cookies and tracking

Strictly necessary. We store what Trinity needs to work: what keeps you signed in, what remembers your workspace, and the record of the cookie choice you make below. These don't need your permission, because without them the product doesn't function.

Analytics. We count public-site page loads and app-open clicks in aggregate whether you accept or decline cookies. Those counts do not use cookies, visitor identifiers, full URLs, query strings, referrers, or user agents, and we do not forward visitor IP addresses with them. They do not let us recognise you across visits. With your permission, PostHog stores an identifier so we can tell a returning visitor from a new one and measure visits from this site into the app. That consent-based analytics starts only after you accept.

Changing your mind. Use the Cookies link in the footer of any page. Withdrawing permission is as easy as granting it, takes effect immediately, and we ask again every six months regardless.

There are no advertising or cross-site tracking cookies on the site or in the app, and we don't run ad-network pixels.

Third-party AI processing

Trinity's answers, summaries, and digests are generated by large language models. To produce them, the relevant slice of your workspace content is sent to OpenAI through their API and the result comes back to you. Only what a given request needs, or what maintaining your project memory needs, is sent: never your whole workspace at once, and only at your direction.

Content sent through the OpenAI API is processed to serve your request and, under OpenAI's API terms, isn't used to train their models. We don't train any model of our own on your workspace content either.

Trinity's use and transfer of Google Calendar data follows the Google API Services User Data Policy, including its Limited Use requirements: we use Calendar data only to provide or improve user-facing Calendar features in Trinity, for security, for legal compliance, or in other cases the policy permits. Google Calendar data is not used to train general AI or machine-learning models, and it is not used for advertising.

On Enterprise you can bring your own model keys. Your content then goes to your provider account under your own agreement with them, and we don't hold it.

Third-party service integrations

Connecting a tool requires, in every case:

  • Your explicit consent, through that service's own authorisation flow
  • The scopes you approve, and no more
  • Whatever admin approval your organisation's rules require

You can disconnect any tool at any time from the app, and our access to it ends when you do. Content already synchronised stays in your project memory until you delete it or close your workspace.

Disconnecting Google Calendar clears Trinity's stored Calendar access and refresh tokens and stops new Calendar reads. It does not revoke Google sign-in or remove Trinity from your Google Account permissions; you can manage that separately in your Google Account permissions.

Data security

Encryption

Data is encrypted in transit using current TLS, and encrypted at rest in the databases and object storage behind the Service.

Access control

Access to production is limited to the small team building Trinity, granted on a least-privilege basis, and tied to individual accounts rather than shared credentials.

Infrastructure and processing partners

These are the providers that handle data on our behalf. It's the complete list:

  • CloudflareHosts and protects the public website and related edge services.
  • Google CloudHosts the production app, application databases, and service infrastructure.
  • OpenAIGenerates answers, summaries, and digests from the content sent for a request.
  • StripeTakes payments and stores card details. Cards go from your browser straight to Stripe and never reach us.
  • PostHogProduct analytics for the site and the app.
  • Google, GitHubSign-in providers. They send us your profile details for account authentication.

Each is bound by its own data processing terms. If we bring in anyone else who handles your data, they appear here before they start.

Certifications held by our providers

Several providers that handle data for Trinity maintain independent audit reports or certifications. Cloudflare holds ISO/IEC 27001 and a SOC 2 Type II report. OpenAI, which processes content for AI features, holds ISO/IEC 27001:2022 and a SOC 2 Type 2 report. Stripe, which handles payments, is certified to PCI DSS Service Provider Level 1, the most stringent level in the payments industry. PostHog, which provides product analytics, holds a SOC 2 Type 2 report.

Trinity itself complies with the UK and EU GDPR and the CCPA, set out under legal compliance below, and a data processing agreement is available on request.

Where data is processed

Trinity's public website runs on Cloudflare, and the production app runs on Google Cloud. The processing partners above operate in their own regions, including the United States, so your data is handled in more than one jurisdiction. See international transfers for the safeguards that apply when data crosses a border. Enterprise customers who need data to stay in one place can run Trinity in a private cloud or self-hosted, in which case workspace content stays where they put it.

Reporting a vulnerability

Found a security issue? Email hi@usetrinity.ai with “security” in the subject line. We aim to acknowledge within one business day and will keep you posted until it's fixed. Please give us a reasonable window to resolve it before disclosing publicly, and don't access or modify other people's data while testing.

Information disclosure

We do not sell, rent, or otherwise commercially distribute personal information, and we don't share it for marketing. Information is disclosed only in these circumstances:

  • To the infrastructure and processing partners listed above, as needed to operate the Service.
  • To OpenAI, when you use AI features, for the content a request needs.
  • To the third-party services you have explicitly connected, as you have authorised.
  • Where required by applicable law, regulation, or valid legal process. Where we're permitted to tell you, we will.
  • To protect the rights, property, or safety of Trinity, our customers, or the public.
  • In connection with a corporate transaction such as a merger, acquisition, or sale of assets, in which case the acquirer is bound by this policy or gives you notice before anything changes.

Data retention and deletion

Workspace content lives as long as your workspace does. Disconnect a tool and we stop reading from it, though content already synchronised stays until you remove it.

Delete your workspace or close your account and we delete the content, and the memory built from it, within 30 days, with backups rolling off on the same schedule. Invoices we keep longer, because tax rules require it. Enterprise plans can set their own retention windows.

Your rights

Subject to applicable law, you may:

  • Request access to your account information and stored data
  • Request correction of anything inaccurate
  • Request deletion of your account and its data
  • Request a portable copy of your data
  • Manage or revoke any connected third-party integration
  • Object to, or ask us to restrict, certain processing
  • Withdraw consent where processing rests on it

Write to hi@usetrinity.ai. We'll get to it in a few days and always within thirty. If your organisation needs a data processing agreement in place, ask and we'll send one. If you're a member of a customer's workspace, we may direct your request to that organisation, since it controls the content.

Every product email we send includes a way to opt out. Emails about your account and your bill aren't optional while you have one.

International transfers

Information may be transferred to, stored in, and processed in countries other than the one you live in, including the United States, where several of our processing partners operate. Where data leaves the UK or the EEA, we rely on the transfer safeguards in each provider's data processing terms, such as the European Commission's standard contractual clauses.

Who Trinity is for

Trinity is a product for teams at work, not for children. To use it you need to be old enough to enter into a contract where you live, and at least 16. We don't knowingly collect information from anyone younger; if we learn that we have, we delete it.

Policy updates

If this policy changes, we'll update it here and change the effective date at the top. If a change meaningfully affects what happens to your data, we'll email account holders before it takes effect.

Contact

Questions about this policy, or about how your data is handled, go to hi@usetrinity.ai. To exercise any of the rights above, use the same address.

Keep work moving

Connect your tools and set the direction. Your AI-native closed loop project OS handles the tasks, milestones and follow-ups from there.

© 2026 Trinity. All rights reserved.

TRINITY