Privacy notice

1. Who this notice covers

This notice covers visitors to teev.ai, people who contact us, and users of the Teev console and control plane. Teev is responsible for account, website, support and service-operations information described here. Contact hello@teev.ai with privacy questions.

Before publication: add the full legal entity name, company number, registered office, data-controller address and any required representative or data protection contact.

2. Information we receive

• Account and team: name, work email, account number, role, authentication events and session records.
• Service metadata: repository names, pull request identifiers and bounded facts, benchmark definitions, selected tools and models, result summaries, token counts, cost, timing, runner health and capabilities.
• Communications: name, email, message, page address and related correspondence when you contact us.
• Public repository screening: public repository and pull request content used to screen the public catalogue.
• Technical records: IP address, user agent, request time, errors and security events produced by the website, API and hosting providers.

3. Information that stays with you

For customer-controlled repositories, source code, snapshots, patches, diffs, agent transcripts, container logs, full run artifacts, GitHub tokens and model credentials stay in the customer environment. The runner polls outward for work; Teev has no inbound connection into that environment.

Private-repository screening sends linked issue text to the third-party model configured for the runner. Benchmark agents send task content to the customer-selected model provider. Those transfers originate from the customer environment and do not pass through Teev.

4. Why we use information

We do not use customer source code to train models because Teev does not receive that source code.

5. Who receives information

We use service providers for cloud hosting, authentication email, support-message delivery, fonts and public-repository model review. The current list is on our Subprocessors page. Customer-selected GitHub and model providers process information under the customer’s own accounts and instructions.

We may disclose information where required by law, to protect rights or safety, or during a corporate transaction subject to appropriate safeguards.

6. International transfers

Teev’s control plane currently runs in AWS us-east-1 in the United States. Other providers may process information outside the United Kingdom. Before production publication, Teev will document the applicable adequacy regulations, contractual safeguards and how to obtain a copy.

7. Retention

We keep information only while needed for the purposes above, account operation, security, disputes and legal obligations. Deleting a workspace removes its users, sessions, runs, runners, commands, benchmarks and grants from the control plane. A bounded deletion audit record remains to evidence the action. Customer-side artifacts remain under the customer’s control.

Before publication: insert reviewed periods or objective retention criteria for account, authentication, support, audit, backup and public-screening records.

8. Your rights

Depending on the circumstances, you may ask for access, correction, deletion, restriction, portability or objection, and may withdraw consent where processing relies on consent. Email hello@teev.ai. You may also complain to the UK Information Commissioner’s Office at ico.org.uk.

9. Cookies and similar storage

The marketing site does not use analytics or advertising cookies. The console uses strictly necessary session storage and cookies for sign-in and security. If Teev adds non-essential analytics or advertising technology, it will update this notice and request consent before enabling it where required.

10. Changes

We will update the date above when this notice changes and bring material changes to account users’ attention where appropriate.