Privacy policy

1. Who we are

TideWright is run by [Company legal name], [Registered address] (“we”, “us”). We are the controller of your account data and of the data we use to run and protect the service. For the content your organisation puts into TideWright, we act on its behalf as a processor, as section 4 explains.

Questions about privacy, and requests about your data, go to [Privacy email].

2. What we collect

• Your GitHub account. You sign in with GitHub. We receive and store your GitHub user ID, login, display name, avatar, email address and whether GitHub has verified it, and update them each time you sign in. We also store the access and refresh tokens GitHub issues, encrypted.
• Your sign-in sessions. For each session we store the IP address and browser details it started from.
• What you and your team put in. Orgs, products, members and invitations, tasks, specs, designs, comments, approvals, uploaded files and images, and your settings and preferences.
• Repository content. Code from the repositories your org connects through the TideWright GitHub App. Agents read and change it in an isolated sandbox and open pull requests on it, and the app keeps a copy of the files it shows you.
• Run records. The steps, logs, files, diffs and pull requests each agent run produces, and the model usage and cost of each run.
• Bosun. The questions you ask TideWright's assistant, its answers, and the notes, briefs and nudges it writes for you.
• Activity. A record of who did what in each org, such as approving a spec or changing a setting.
• Keys and connections your org adds. Model provider keys and connector credentials. They are encrypted so that only the model gateway can read them; we show only the last four characters of a key.
• Technical data. IP addresses, used briefly to limit abusive requests, the cookies described in our cookie policy, and error reports when something breaks on our servers. Error reports contain the kind of error and where in our code it happened, and may name the org or run involved. They do not contain your name, email, IP address or the content you work on.
• Product usage. When you are signed in and working in an org, we record which TideWright features you use, such as opening Bosun or a review stage, with your user ID, your org's ID and, where there is one, the product's ID. These records never contain what you type, titles, notes, file names, code, your name, your email or your IP address, and no cookie is used for them. You can turn this off with Share how I use TideWright in your account menu, and we treat a browser's Global Privacy Control signal as turning it off.

We do not use advertising or analytics cookies, we do not track you across other sites, the public pages (the home page, the blog and these policies) record nothing about your visit, and we do not sell or share personal data for advertising.

3. How we use it, and why we may

• To provide TideWright: signing you in, running agent crews on your org's tasks, showing your team the board, answering your questions through Bosun, and keeping the record of runs and decisions. Legal basis: performing our contract with you or your organisation.
• To keep it secure and working: checking who may sign in, rate limits, abuse prevention, error tracking and support. Legal basis: our legitimate interest in a safe, reliable service.
• To improve TideWright: counting which features are used, and where people stop, from the product usage records above. Legal basis: our legitimate interest in improving the service. You can object at any time by turning off Share how I use TideWright in your account menu; from then on nothing more is recorded about you.
• To enforce usage limits: measuring each run's model usage against the caps your org sets and any allowance we give it. Legal basis: contract.
• To meet legal obligations, such as answering lawful requests from authorities. Legal basis: legal obligation.

We do not use your code or content to train AI models, and we do not ask the model providers to. We use your email address only for your account; TideWright does not send marketing email.

4. Data we process for your organisation

The content your team adds to an org, the repositories it connects and the runs it starts belong to that org. We process them on the org's behalf and on its instructions, and its admins decide who can see them. If your organisation needs a data processing agreement with us, ask at [Privacy email].

A small number of TideWright staff can open an org to give support, investigate abuse or keep the service running. They do so only when needed, every change they make is recorded in the org's activity, and each org can see which staff have this access under Settings.

5. Who we share it with

We share personal data only with the service providers that run TideWright for us, and only what each needs:

If your org turns on Claude Managed Agents, the files and messages of those runs are held by Anthropic until the run ends. Connectors your org turns on, such as an issue tracker, receive what your runs send them, under your org's own agreement with that service.

We may also disclose data when the law requires it, or to a buyer as part of a merger or sale of our business, in which case we will tell you first.

6. International transfers

Our servers are in the United States, and some providers process data in other countries. When we transfer personal data out of the UK, the European Economic Area or Switzerland, we rely on an adequacy decision, such as the EU-US Data Privacy Framework where the provider is certified, or on the European Commission's Standard Contractual Clauses with the UK Addendum. You can ask us for a copy of the safeguards at [Privacy email].

7. How long we keep it

• Your account and your organisation's content are kept while the account or organisation exists.
• Bosun's conversations, messages and notices are deleted after 90 days, and you can delete a conversation sooner.
• An unused invitation stops working after 7 days.
• When you ask us to delete your account or your organisation, we do so within 30 days, apart from records we must keep by law. Copies in our database backups expire within a further 7 days.
• Product usage records are kept for [Product usage retention], then deleted.
• Error reports and server logs are kept only as long as we need them to fix problems and keep the service safe.

8. Security

GitHub tokens, model keys and connector credentials are stored encrypted, and model keys and connector credentials can be read only by the model gateway. Each organisation's data is kept apart by row-level security in the database. Agents run in isolated sandboxes that can reach only a short list of hosts. TideWright staff must use two-factor authentication. No system is perfectly secure; if a breach affects your data, we will tell you and the authorities as the law requires.

9. Your rights

Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal data, to object to or restrict how we use it, and to withdraw any consent you gave. To use any of these rights, email [Privacy email]. We will answer within one month, and we may ask you to confirm who you are first.

If the data belongs to an organisation's content, we may pass your request to that organisation, which decides on it. If you live in a US state with a privacy law, such as California, you have the same rights, and we will not treat you differently for using them. We do not sell personal information or share it for cross-context behavioural advertising.

You can also complain to the data protection authority where you live or work. Our lead authority is [Supervisory authority].

10. Children

TideWright is a tool for work and is not meant for anyone under 16. We do not knowingly collect their data.

11. Changes to this policy

We will post any change here and update the date at the top. If a change is significant, we will tell you in the app before it takes effect.

12. Contact

Questions about this policy: [Privacy email], or write to [Company legal name], [Registered address].