Privacy
Privacy Policy
How Wellence collects, uses, shares and protects personal data, and how you stay in control of it.
Effective 15 November 2026
Who we are
Wellence Ltd ("Wellence", "we", "us") is a company registered in England and Wales (company number 15287383), at 167-169 Great Portland Street, 5th Floor, London W1W 5PF, and registered with the UK Information Commissioner's Office (ZC084891). Our data protection contact is legal@wellence.me.
This policy covers the Wellence app at app.wellence.ai, our websites, and how we deal with customers, prospects and people who contact us.
Our role
Inside the Wellence app, your company is the controller of the personal data it puts in, and we are its processor: we process that data only to provide the service, on your company's instructions, under our Data Processing Agreement. If you use Wellence through your employer, your employer's privacy notice also applies.
We are the controller for the data we use to run our own business: website visits, early-access requests, accounts and sign-in, sales conversations, billing, support and product analytics.
What we collect
- Early-access requests: your name, work email, company, job title, role, department, company size and any promo code.
- Signing up: the work email and name you enter, the company domain, and how far you got (link sent, link opened, finished), so we can help if a step doesn't work. If your company asks an admin to approve new people, your request to join, and whether it was accepted or declined.
- Your account: name, work email, role and team, and the records that let you sign in.
- What your company puts into the app (as processor): goals, tasks, messages, files, workflows, what agents produce, ratings and feedback, answers to the AI diagnostic, usage and cost records, and a record of each item agents read from your connected tools (its tool, id and name, never its content).
- What workflows save to other tools (as processor): when a workflow saves to a connected tool, a record of each change: who it was for, the tool, the item, a short description of the change, and whether it was made. Never the tool's reply. It's kept with the company's data.
- Data other apps send to a workflow (as processor): when your company sets a workflow to start from another app (Zapier, n8n, a form) or an event in a connected tool (a new Typeform response, new Sheet rows, a new Gmail email, a new Pipedrive deal), whatever that app or event sends, and a record of each request: when it came, whether it was accepted, and the task it started. Requests that fail the checks are recorded without what they sent. It's used only to start and run that workflow.
- Help and support: your Get help conversations, and anything you send our team.
- Sales: business contact details and professional information, including a LinkedIn profile you share with us, which we may use to prepare a tailored demo. When you open a demo link we sent you, we record that it was opened and how the demo was used. When you open a personal page we made for you, we record the visit: when, the kind of device, the site you came from, how far you scrolled, how much of the video you watched and which buttons and examples you clicked. A random id kept in your browser links your visits; it holds no name or email. We don't record this if your browser sends Global Privacy Control or Do Not Track.
- Product analytics: which pages and features are used, with an internal id but no names, emails or content. Signed-out visitors are counted without cookies, using a daily hash that changes every day. We respect Global Privacy Control and Do Not Track.
- Usage and session replay (PostHog): page views and recordings of how the app and website are used, with all text, inputs and images hidden. See below.
How and why we use it
| Purpose | Legal basis |
|---|---|
| Providing the Wellence service to your company | Performance of our contract with your company |
| Signing you in and keeping your account secure | Contract, and our legitimate interest in security |
| Answering early-access requests and setting up workspaces | Legitimate interests (and steps before a contract) |
| Answering help and support requests | Legitimate interests, and contract |
| Sales outreach and tailored demos to businesses | Legitimate interests (you can object at any time) |
| Improving the product with analytics that hold no names or content | Legitimate interests |
| Improving the product with usage events and session replays, all content hidden (PostHog) | Legitimate interests (you can object at any time) |
| Billing, record keeping and legal compliance | Legal obligation, and contract |
We don't sell personal data, and we don't use it for advertising.
Product analytics and session replay
To see where people get stuck and make Wellence easier to use, we use PostHog (PostHog Inc., on its EU Cloud in Frankfurt, Germany) on our website, sign-up, onboarding and the app.
- What it collects: which pages you visit and when, the kind of device and browser, and a recording of the screen as you use it, with all text, inputs and images hidden. Only our own menus, buttons and headings show.
- What it never collects: names, emails or your company's content. Tasks, messages, agent work, documents, files, setup answers, goals, invites, client briefs and people lists are blocked from recordings entirely. Addresses are cleaned before they're sent, so company names and ids never reach PostHog, and we don't keep your IP address.
- Who it is linked to: when you're signed in, your internal member id and your company's workspace key, so we can see where a company gets stuck. Never your name or email.
- No cookies or device storage: PostHog sets no cookies and keeps nothing in your browser's storage.
- Legal basis: our legitimate interest in improving the product. It doesn't run if your browser sends Global Privacy Control or Do Not Track, or for test and demo workspaces.
- How to object: switch off "Help improve Wellence" in Settings, or email legal@wellence.me and we'll switch it off for you.
How AI is used
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, Microsoft doesn't share it with OpenAI, and we don't use it to train models either. Each one's terms 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.
When you describe a new agent, the agent builder sends Claude what it needs to draft it: your words, your company's and team's context, your colleagues' names and teams, the names of the company's tools, and the names of folders or lists already picked for the company's agents (never another person's own email, calendar or meeting files). Before the agent is made you can try it once on one of your own recent tasks or on text you paste. That trial doesn't open your connected tools and sends nothing anywhere; its result isn't saved, only its cost. Nothing is kept as an agent unless you make it.
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 who is accountable for it.
Sensitive data
Wellence isn't designed to collect special category data (such as health, ethnicity, religion or sexual orientation). Some HR work can touch it, for example a parental leave question. Your company decides which agents run and what they can see, and is responsible for having a lawful basis for that data. We don't use it for analytics or product improvement.
Who we share it with
We use these subprocessors to run the service, each under a written agreement that protects your data:
| Subprocessor | What for | Data | Where | Transfers |
|---|---|---|---|---|
| Anthropic | AI models (Claude): Wellence's default for agents, and always for building agents and Get help | The task, your company's context and what agents read from your tools, which can include names and work content | United 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 them | As for Anthropic, for the work sent there | Region set by Wellence | Microsoft's DPA: Standard Contractual Clauses with the UK Addendum, and the EU-US Data Privacy Framework |
| OpenAI | AI models (ChatGPT) through OpenAI's own API, only when Wellence's Azure set-up isn't available | As for Anthropic, for the work sent there | United States | Standard Contractual Clauses with the UK Addendum (OpenAI's DPA) |
| Google (Gemini API) | AI models (Gemini) for agent work, when a company or Wellence picks them | As for Anthropic, for the work sent there | United States | Google's data processing terms: Standard Contractual Clauses, and the EU-US Data Privacy Framework |
| Composio | Connections to your company's tools (such as Google, Slack and HubSpot): keeps their sign-in tokens, reads for agents and saves what a person approves | Sign-in tokens for your tools, and the items read from or saved to them | United States (Composio doesn't publish its hosting region) | Standard Contractual Clauses with the UK Addendum (Composio's DPA) |
| Supabase | Database, sign-in and file storage | Everything your company keeps in Wellence | European Union (Ireland) | Stored in the EU. Any support access from outside it: Standard Contractual Clauses with the UK Addendum |
| Vercel | Hosting and running the application | Everything your company keeps in Wellence, while a request is handled | United Kingdom (London) for the app's servers; Vercel Inc. is in the United States | Standard Contractual Clauses with the UK Addendum (Vercel's DPA) |
| Stripe | Payments and billing | Billing contact, company name and payment details (card numbers go to Stripe, never to Wellence) | United States | EU-US Data Privacy Framework and its UK Extension, and Standard Contractual Clauses (Stripe's DPA) |
| Resend | Sending email (sign-in links, notifications) | Names, email addresses and the text of each email | United States | Standard Contractual Clauses with the UK Addendum (Resend's DPA) |
| Microsoft (Microsoft 365) | Wellence's own email, including support requests | Emails and attachments you send us | Europe | Stored in Europe. Microsoft's DPA covers any access from outside it |
| Sentry | Error reports, so we can find and fix faults | Technical details of an error, which can include an internal id | European Union (Germany) | Stored in the EU. Standard Contractual Clauses with the UK Addendum (Sentry's DPA) |
| PostHog | Product analytics and session replay, with all content hidden, to improve the product | An internal id and how the app is used; no names, emails or content | European Union (Germany) | Stored in the EU. Standard Contractual Clauses with the UK Addendum (PostHog's DPA) |
We may also share data when the law requires it, to protect our rights or people's safety, or with a buyer if Wellence is sold or merged, in which case we'll tell you first. If you connect your own AI, use your own Anthropic, OpenAI or Gemini key, or run it in your own cloud account, that provider handles the data under its own terms.
International transfers
Your company's database is stored in the European Union. 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 EU-US Data Privacy Framework and its UK Extension where the provider is certified.
Cookies
The app uses only the cookies it needs: two secure sign-in cookies that keep you signed in, a cookie that remembers whether the sidebar is open, and, when you open a demo link we sent you, a cookie that connects what you do in that demo to the link. A personal page we made for you keeps a random visit id in your browser's storage (see above). Our public pages keep one more item in your browser's storage, wellence.from-page, which says which of our pages you came from (for example the agencies page) so sign-up can start from it. It holds no personal data and never leaves your browser unless you sign up. There are no advertising or third-party analytics cookies in the app, and PostHog, which we use for product analytics, stores nothing on your device.
How long we keep it
- Your company's data in the app: while its account is active. It's deleted straight away when an admin deletes the company, with its files, and its connected tools are disconnected. Otherwise it's deleted within 30 days of the contract ending.
- Data other apps send to a workflow: what was sent is cleared after 30 days (or straight away when an admin deletes the company). The record that a request came in, and what became of it, is kept with the company's data.
- Invoices and payment records: kept by Stripe, our payments provider, as long as tax law requires.
- Sign-up progress: up to 90 days.
- Early-access requests that don't become a customer: up to 12 months.
- Help and support conversations: up to 24 months.
- Sales and demo records: up to 12 months after our last contact.
- Product analytics: up to 24 months.
- Session replays: up to 90 days.
Backups roll off on our database provider's schedule.
Keeping it 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 links with no passwords, files are private, and data is encrypted in transit and at rest. Agents read people's files, email and messages only through the own connection of the person they work for, and work from someone's own files is shown only to them until they share it. More on our security page. If a breach affects your data, we tell the right people without undue delay.
Your rights
You can ask to access, correct, delete, restrict or port your personal data, and object to how we use it, including to sales outreach at any time. For data your company put into Wellence, ask your company first, as the controller; we'll help it respond. Otherwise, email legal@wellence.me or ask in the app's Get help. We reply within one month.
You can complain to the UK Information Commissioner's Office at ico.org.uk or to your local data protection authority.
Children
Wellence is for businesses and isn't meant for anyone under 18.
Changes
When we change this policy, we update this page and its date. For significant changes, we tell customers by email or in the app first.
Contact
Wellence Ltd, 167-169 Great Portland Street, 5th Floor, London W1W 5PF. Email legal@wellence.me.