GDPR

GDPR at Wellence

Who is responsible for your data, where it goes, and how you stay in control of it, under the UK GDPR and the EU GDPR.

Who we are

Wellence Ltd, a company registered in England and Wales (company number 15287383), 167-169 Great Portland Street, 5th Floor, London W1W 5PF. We're registered with the UK Information Commissioner's Office (registration ZC084891). Data protection contact: legal@wellence.me.

Who is responsible for what

Your company is the controller of the personal data it puts into Wellence: its people, teams, goals, tasks, messages, files and what its agents produce. Wellence is the processor: we process it only to run the service, on your instructions, under our Data Processing Agreement.

Wellence is the controller for a small amount of data we use to run our own business: website visits, sign-up progress, early-access requests, sales conversations, billing and support. Our Privacy Policy covers that.

What we process in the app

  • Account details: name, work email, role and team.
  • The work your company puts in: goals, tasks, messages, files and workflows.
  • What agents produce, and the ratings and feedback people give.
  • Usage and cost records, answers to the AI diagnostic, and Get help conversations.
  • A record of each item agents read from your connected tools: the tool, its id and name, never its content.
  • Requests to join from your company's email domain, when an admin approves new people.
  • A record of each change a workflow saves to a connected tool (the tool, the item, a short description, who approved it), kept with the company's data, in its download, and deleted with the company.
  • Data another app sends to start a workflow, or an event from a connected tool (Typeform, Google Sheets, Gmail or Pipedrive, through Composio), only when your company sets that up, kept with a record of each request to run that workflow. What was sent is cleared after 30 days; the record stays with the company's data, is in its download, and goes when the company is deleted.

Product analytics hold no names, emails or content, only an internal id, and respect Global Privacy Control and Do Not Track. Session replays (PostHog, EU) hide all text, inputs and images, block customer content entirely and store nothing on the device. Anyone can switch them off in Settings.

How AI uses your data

Wellence's AI runs on Anthropic's Claude by default, through its API. A company can choose ChatGPT (on Microsoft's Azure OpenAI Service, or OpenAI's own API when Azure isn't available) or Google's Gemini instead, or run agents in its own AI. Interviews (including building an agent) and Get help run on Claude. If the AI a piece of work was sent to fails, it's tried once more on Wellence's Claude, except for a company that runs its own AI or has switched on "Only use our own AI": then nothing runs on Wellence's AI keys or falls back to another provider, and the work stops and says why (Get help, which is Wellence's own, stays on Wellence's key). To do their work, agents receive the context your company has set up and the task in hand, which can include people's names and work content. On the plans Wellence uses, none of these providers train their models on data sent through their APIs, and Microsoft doesn't share it with OpenAI. Each one's terms, including how long it keeps data, are on our security page.

A company can also run its agents' AI in its own cloud account: Claude on AWS Bedrock (sent to the AWS region it picks, such as Ireland or London), Claude on Google Vertex AI (global, the EU or US multi-region, or one region for older models), or ChatGPT on its own Azure OpenAI resource (in the region it deployed it). That provider then works under the company's own contract, not as Wellence's sub-processor. Claude on Bedrock can't search the web, and agents are told so.

No decision with legal or similarly significant effects is made about anyone by AI alone: agents ask a named person before anything is sent, posted or changed, and every agent has an owner accountable for its work.

Subprocessors and where data is stored

SubprocessorWhat forDataWhereTransfers
AnthropicAI models (Claude): Wellence's default for agents, and always for building agents and Get helpThe task, your company's context and what agents read from your tools, which can include names and work contentUnited States (Anthropic's API has no UK or EU processing option)Standard Contractual Clauses with the UK Addendum (Anthropic's DPA)
Microsoft (Azure OpenAI Service)AI models (ChatGPT) for agent work, when a company or Wellence picks themAs for Anthropic, for the work sent thereRegion set by WellenceMicrosoft's DPA: Standard Contractual Clauses with the UK Addendum, and the EU-US Data Privacy Framework
OpenAIAI models (ChatGPT) through OpenAI's own API, only when Wellence's Azure set-up isn't availableAs for Anthropic, for the work sent thereUnited StatesStandard Contractual Clauses with the UK Addendum (OpenAI's DPA)
Google (Gemini API)AI models (Gemini) for agent work, when a company or Wellence picks themAs for Anthropic, for the work sent thereUnited StatesGoogle's data processing terms: Standard Contractual Clauses, and the EU-US Data Privacy Framework
ComposioConnections to your company's tools (such as Google, Slack and HubSpot): keeps their sign-in tokens, reads for agents and saves what a person approvesSign-in tokens for your tools, and the items read from or saved to themUnited States (Composio doesn't publish its hosting region)Standard Contractual Clauses with the UK Addendum (Composio's DPA)
SupabaseDatabase, sign-in and file storageEverything your company keeps in WellenceEuropean Union (Ireland)Stored in the EU. Any support access from outside it: Standard Contractual Clauses with the UK Addendum
VercelHosting and running the applicationEverything your company keeps in Wellence, while a request is handledUnited Kingdom (London) for the app's servers; Vercel Inc. is in the United StatesStandard Contractual Clauses with the UK Addendum (Vercel's DPA)
StripePayments and billingBilling contact, company name and payment details (card numbers go to Stripe, never to Wellence)United StatesEU-US Data Privacy Framework and its UK Extension, and Standard Contractual Clauses (Stripe's DPA)
ResendSending email (sign-in links, notifications)Names, email addresses and the text of each emailUnited StatesStandard Contractual Clauses with the UK Addendum (Resend's DPA)
Microsoft (Microsoft 365)Wellence's own email, including support requestsEmails and attachments you send usEuropeStored in Europe. Microsoft's DPA covers any access from outside it
SentryError reports, so we can find and fix faultsTechnical details of an error, which can include an internal idEuropean Union (Germany)Stored in the EU. Standard Contractual Clauses with the UK Addendum (Sentry's DPA)
PostHogProduct analytics and session replay, with all content hidden, to improve the productAn internal id and how the app is used; no names, emails or contentEuropean Union (Germany)Stored in the EU. Standard Contractual Clauses with the UK Addendum (PostHog's DPA)

If your company runs its agents' AI in its own cloud account (Claude on AWS Bedrock or Google Vertex AI, or its own Azure OpenAI), that provider works under your own contract with it, not as Wellence's sub-processor. The work is sent from Wellence straight to your account, in the region you chose.

We tell customers at least 30 days before adding or replacing a subprocessor, by updating this list and emailing your admins, so you can object (DPA clause 6).

Changes to subprocessors

22 October 2026. You can object until 21 November 2026.

  • Added Composio: connections to your company's tools and their sign-in tokens.
  • Added Stripe: payments and billing.
  • Added OpenAI: ChatGPT models through OpenAI's own API, only when Wellence's Azure set-up isn't available.
  • Added Microsoft 365: Wellence's own email, including support requests.
  • Listed the data each one handles and how transfers are covered, and confirmed the database is in Ireland and the app's servers in London.

International transfers

Where data goes outside the UK or the EEA (for example to the United States), the transfer is covered by the UK International Data Transfer Addendum and the EU Standard Contractual Clauses, or by the UK and EU adequacy decisions for the EU-US Data Privacy Framework where the provider is certified.

Using your rights

People have the right to access, correct, delete, restrict, object to and port their personal data.

  • Companies: an admin can download everything the company has in Wellence, or delete the company and all its data, from Settings at any time. Deletion is immediate and can't be undone: it removes every record and file, disconnects the company's tools, cancels its subscription and gives the admin a receipt. The download leaves out secrets and work from someone's own files that they haven't shared.
  • People at a customer: your company is the controller, so ask its admin first. You can also ask us in the app's Get help, or email legal@wellence.me, and we'll work with your company to respond, within one month.
  • You can complain to the UK Information Commissioner's Office at ico.org.uk, or your local data protection authority in the EU.

Keeping data safe

Each company's data is kept separate; people see their own team and what's shared with them; sign-in is by single-use, expiring email links with no passwords; files are private and opened through short-lived links; a company's own AI keys and cloud credentials are stored encrypted. Agents read people's files, email and messages only through the own connection of the person they work for, and, where items are picked in their setup, only those; each read is recorded. More on our security page.

If a personal data breach affects your data, we tell you without undue delay, and within 72 hours of becoming aware of it, with what we know and what we're doing about it.

How long we keep data

Your company's data is kept while its account is active. It's deleted straight away when an admin deletes the company, and within 30 days of a contract ending unless the law requires otherwise. Backups roll off on our database provider's schedule.

Data Processing Agreement

Our Data Processing Agreement sets out these commitments as contract terms (UK GDPR and EU GDPR Article 28). For a countersigned copy, email legal@wellence.me.