Skip to content

Privacy policy

What Terere collects, why, and your rights.

Last updated 5 October 2026

In short

  • Terere Harness sends your prompts, code and the model’s replies straight to the AI endpoint you choose. They never pass through Terere, and we can’t see them.
  • The app has no telemetry, analytics or automatic crash reporting.
  • This website uses no analytics or advertising trackers. Its cookies keep you signed in to an organisation account, and Stripe sets its own fraud-prevention cookies when an admin buys seats.
  • Without an organisation account, we only receive the technical details any website or update server sees, and the emails you send us. With one, we and our providers hold what the account needs: your sign-in details, your organisation and role, and your token counts.

Who we are

Terere, including terere.ai and Terere Harness, is run by an individual based in England. For the purposes of UK data protection law, that person is the controller of the personal data described here. Contact: contact@terere.ai.

The Terere Harness app

Your model provider

When you use the app, it sends your prompts, the files and command output it works with, and your API key to the endpoint you configured. That provider handles this data under its own privacy policy and terms. If you use a model on your own computer, your prompts and code stay on it.

When the agent uses a tool that reaches the internet, such as fetching a web page or searching the web, it contacts the site or search service involved, as your browser would.

If you switch on the Claude Code or Codex agents, the app hands tasks to Codex, which comes with Terere Harness, or to the Claude Code you installed yourself. They run with your own sign-in and send the task and your project files to Anthropic or OpenAI under those products’ own terms and privacy policies. Terere doesn’t receive any of it.

Stored on your computer

Your settings, sessions, API keys and logs are stored in your user profile on your computer. We never receive them. Crash reports are saved there too and are not sent anywhere.

Update checks

The app contacts terere.ai to check whether an update is required, and downloads.terere.ai to download updates. These requests include your IP address and the app version, operating system and processor type. We use them only to decide which update to offer and to deliver it. They are not linked to your name, email or any account.

Connecting to an organisation

If your organisation uses Terere Harness Enterprise and you connect the app to it (Settings, Organisation), the app sends terere.ai the token counts of each model request and when it happened. Your organisation’s admins see these counts per member. Prompts, replies, code, file names and model names are never sent with these counts. Disconnecting stops it, and your admins can also disconnect a computer.

Shared context

If your organisation allows it, you can share short facts from a chat with your colleagues, such as who owns a service or how to run a project. You review each fact before it is shared. The app encrypts facts on your computer with a key that only your organisation’s connected computers hold, so terere.ai stores them only in encrypted form and can’t read them. Alongside each fact we store who shared it, its kind, and when it was shared and expires. Facts expire 180 days after they were last confirmed and are deleted the next time any member’s app syncs with terere.ai; the author or an admin can delete them sooner. An admin can turn shared context off for the whole organisation.

Organisation accounts

Anyone can sign up at terere.ai and create an organisation, becoming its admin. WorkOS runs sign-in and holds your account: your name, email address and password or sign-in method, and which organisation you belong to. Our database, hosted by Neon, holds your organisation, each member’s WorkOS user ID and role, the seats bought, the computers connected, and each member’s token counts. It holds no names or email addresses; we fetch those from WorkOS when someone in the organisation views its members in the dashboard, and don’t store them.

Carbon estimate

If an organisation turns on the carbon estimate, its admins record which AI model the organisation uses and where it runs, chosen from a list. We store that choice, the date it was made and the organisation it belongs to, and use it only to work out the estimate shown in the dashboard. Terere Harness itself still never sends model names.

Invitations

When an admin invites someone, the admin gives us that person’s email address. We pass it to WorkOS, which sends the invitation email and keeps the address with the invitation. We also record the invitation in your organisation’s activity log, with the invitee’s email address, the admin who sent it and when. We keep those records for 400 days, then delete them. We rely on the organisation’s legitimate interest in giving its staff access. A pending invitation expires after 7 days, and a revoked one stops working straight away.

Billing

Stripe handles seat checkout and collects what it needs from the admin, such as their email address. We never see card details; we keep only the Stripe customer and subscription IDs, the plan and the number of seats.

Keeping and deleting

We keep account data while your organisation uses Terere. To close an account or organisation, email contact@terere.ai.

This website

terere.ai and downloads.terere.ai are hosted by Cloudflare, which processes your IP address and request details (such as the page requested, browser type and time) to deliver the site and protect it from abuse. We have not turned on request logging or analytics.

If you choose a light or dark theme, your browser remembers that choice in its local storage. It stays on your device and is never sent to us.

If you sign in to an organisation account, the site sets a wos-session cookie that keeps you signed in until you sign out, the session ends, or at most 400 days pass, and, while you sign in, a wos-auth-verifier cookie that lasts 10 minutes and protects the sign-in from tampering. Both are strictly necessary, so we don’t ask for consent.

When an admin buys seats, the checkout is Stripe’s, and Stripe sets its fraud-prevention cookies, __stripe_mid (one year) and __stripe_sid (30 minutes). They protect the payment and are strictly necessary for it, so we don’t ask for consent. Stripe’s privacy policy covers them.

When you email us

Messages to contact@terere.ai are forwarded to our inbox by Cloudflare Email Routing. We use your email address and message only to reply, and keep them for as long as the conversation needs, then for up to two years unless the law requires longer.

Legal basis

We rely on our legitimate interests in delivering the website and app updates securely, and in answering the messages you send us. For organisation accounts, we rely on the contract with your organisation to provide the service, and for invitations on the organisation’s legitimate interest described above. We don’t sell personal data or use it for advertising.

Who else handles data

These companies process personal data on our behalf:

  • Cloudflare, Inc. hosts the website and downloads, and routes email.
  • WorkOS, Inc. runs sign-in, holds accounts and organisations, and sends invitation emails.
  • Stripe handles billing and payment details.
  • Neon hosts our database, which holds organisation and member records and token counts.

They may process data outside the UK, under the safeguards UK law requires for such transfers. Otherwise we share personal data only when the law requires it.

Your rights

Under UK data protection law you can ask to see the personal data we hold about you, correct it, delete it, restrict or object to how we use it, and receive a copy. Email contact@terere.ai; we’ll reply within one month. If you’re unhappy with how we handle your data, you can complain to the Information Commissioner’s Office at ico.org.uk.

Children

Terere is not aimed at children under 13, and we don’t knowingly collect their personal data.

Changes

If we change how we handle personal data, we will update this page and the date at the top before the change takes effect.