Privacy Policy

How AI Transform Studio handles personal data.

Last updated 27 October 2026

Who we are

This Privacy Policy explains how AI Transform Studio Ltd (registered in England and Wales) (“we”, “us”) processes personal data when you use AI Transform Studio at aitransformstudio.com and related application surfaces.

Contact for privacy requests: support@aitransformstudio.com.

Further company particulars are available on request at support@aitransformstudio.com.

Scope

This policy covers personal data we process as a controller for account, billing, and website operations. When you upload or connect Customer Data that includes personal data about your employees or other people, you are typically the controller and we act as your processor for that Customer Data. A separate data processing agreement is available on request for enterprise buyers; self-serve card checkout is governed by this policy and our Terms.

Personal data we collect

Depending on how you use the Service, we may process:

  • Identity and contact data — name, email address
  • Account and organization data — membership, roles, preferences
  • Authentication data — password hashes (where used), session tokens, Google account identifiers if you sign in with Google
  • Billing data — organization billing status; payment card details are handled by Stripe and not stored on our servers
  • Usage and technical data — IP address, device/browser metadata, approximate logs needed to operate and secure the Service
  • Support content — messages you send to support
  • Mailing-list data — if you ask for the EA-Bench question kit: your email address, and the dates you asked, confirmed or unsubscribed
  • Customer content — prompts, artifacts, and data retrieved from systems you connect, which may incidentally include personal data

Sources

We collect data from you directly, from your organization’s admins, from authentication providers (e.g. Google), from Stripe for payment status, and from systems you connect when you authorize those connections.

Purposes and legal bases

We process personal data to provide the Service (contract), to bill and prevent fraud (contract / legitimate interests), to secure and debug the platform (legitimate interests), to send service emails such as verification codes (contract), to send the EA-Bench emails you ask for (consent), and to comply with law.

Where UK GDPR requires consent for a specific optional processing activity, we will ask for it. We do not currently run marketing cookies or advertising trackers on the marketing site.

EA-Bench emails

If you ask for the EA-Bench question kit on our website, we put your email address on the EA-Bench mailing list and send one email asking you to confirm it. Once you confirm, we email you when the EA-Bench results are published and when its next edition is out, and nothing else. Our legal basis is your consent.

Every email has a link to unsubscribe, and you can also withdraw consent by writing to support@aitransformstudio.com. If you don't confirm within 30 days, we delete the address. If you unsubscribe, we email it no more and keep it, marked unsubscribed and with the dates, as the record of your choice; ask us and we will delete it.

To stop the form being used to send unwanted email, we count requests by IP address and by a one-way digest of the email address and its domain, for up to a day; the counters hold no readable address. Resend delivers these emails (see Sharing). We do not sell the list or share it for anyone else's marketing.

AI and data path

When you chat or run an agent, prompts, tool results, and related context are sent to the large language model provider whose credentials your organization has configured. An assessment sends the records it grades to the decision model your organization has configured. That processing is under your provider relationship. We do not train third-party foundation models on your Customer Data for the benefit of other customers.

Tool calls may retrieve data from MCP servers and systems you connect. Treat tool output as untrusted input in your own processes. Artifacts are stored in our application database and file storage so you can reopen them.

Web search is on unless you turn it off. While it is on, the search queries the agent writes are sent to Tavily, and they can include words from your chat; pages the agent opens are fetched from our runtime host. So that a long run can resume after a restart, the runtime host also keeps each agent session’s log, including full tool results, until the session has not changed for 30 days; a session whose goal is still open, or that the runtime still holds in memory, may be kept longer, for as long as that lasts (see the Security page).

Sharing

We share personal data with subprocessors that help us run the Service (listed on our Security page and below), with professional advisers if required, and with authorities when law requires. We do not sell personal data.

  • Convex — Application database, authentication sessions, and backend functions
  • Vercel — Web application hosting, edge delivery, and cookieless site analytics
  • Fly.io — Agent runtime host (keeps agent session logs and full tool results on an encrypted volume until a session has not changed for 30 days; one whose goal is still open, or that the runtime still holds in memory, may be kept longer, for as long as that lasts; volume snapshots can hold a copy for up to 14 days after that) and its attach gateway; collaboration sidecar, visual MCP rendering, and the MCP connector servers Studio hosts
  • Stripe — Subscription billing and payment processing
  • Resend — Transactional email (sign-in and sign-up codes, welcome, access requests, invitations, password reset, agent run notices that name the thread and may say in a sentence or two why a run stopped, and alerts to our operators that name the organizations and threads affected), and the EA-Bench mailing list's emails
  • Tavily — Web search for agent runs while web search is on (receives the search queries the agent writes, which can include words from your chat)
  • Google — Optional sign-in via Google OAuth (when you choose Google), and the optional YouTube film player
  • Customer-chosen LLM providers — Model inference using API keys you connect (OpenAI, Anthropic, etc.), including the decision models that grade assessments and check goals
  • Customer-connected systems (MCP) — Architecture, delivery, ITSM, and knowledge sources you connect

International transfers

We and several subprocessors operate outside the UK. Where we transfer personal data internationally, we rely on appropriate safeguards such as the UK International Data Transfer Agreement / Addendum or adequacy regulations, as applicable to each subprocessor.

Retention

We keep account and organization data while your account is active and for a reasonable period afterward for backups, disputes, and legal obligations. You may request deletion via support@aitransformstudio.com. Billing records may be retained as required by tax and accounting rules.

Agent session logs on our runtime host are deleted automatically once a session has not changed for 30 days. A session whose goal is still open, or that the runtime still holds in memory, may be kept longer, for as long as that lasts. Deleting a thread also has the runtime host delete its copy, including its subagents’ sessions; if the host cannot do that straight away, the request is kept and sent again until it has, and the 30-day cleanup still applies in the meantime. Threads deleted before we began sending deletes to the runtime host, and threads whose agent has not run since early October 2026, may be left to that cleanup instead, and so may be kept longer in the same cases. Volume snapshots, kept for 14 days, can hold a deleted log for up to 14 days longer. A record of each tool call that could change data in a connected system (which tool, who decided, and the outcome, never what was sent) is kept for 365 days, even after its thread is deleted. Deleting an organization deletes all of its data from the application database, including that record, its connections, keys, files and workbenches, and has the runtime host delete the organization’s whole folder at once; if the host cannot do that straight away, the request is sent again until it has. Volume snapshots can hold that folder for up to 14 days longer. The Security page has the details.

Security

We use access controls, encryption in transit and at rest, organization-scoped authorization in the application, and least-privilege server secrets. The product runs on a shared multi-tenant stack with logical isolation by organization. See the Security page for a plain-language summary. No method of transmission or storage is perfectly secure.

Your rights

If UK GDPR applies to you, you may have rights to access, rectify, erase, restrict, object, and data portability, and to withdraw consent where processing is consent-based. Contact support@aitransformstudio.com. You may also complain to the UK Information Commissioner’s Office (ICO).

If you are an end user of a customer organization, please contact that organization first — they control much of the Customer Data in the workspace.

Children

The Service is for business use and is not directed to children under 16. We do not knowingly collect personal data from children.

Changes

We may update this policy by posting a new version and changing the “Last updated” date. Material changes will be called out where practicable.

Privacy Policy · AI Transform Studio