Legal
Privacy policy
Last updated 16 September 2026
The short version: we store what the product needs to work, we send the relevant part of a conversation to a model provider so an agent can answer, we keep your workspace data in the EU, we sell nothing to anyone, and you can delete it all. The long version follows.
Who we are and what this covers
This policy explains how woble handles personal data when you use the service, visit our website, or contact us. It covers the app at woble.ai and the pages around it. It does not cover the services you connect through integrations; each of those has its own policy.
For your account and for the website, woble is the data controller. For the content inside a workspace (messages, files, agent memories, integration data), the organisation that runs the workspace is the controller and woble is the processor acting on its instructions. The Data processing addendum sets out that relationship in detail.
What we collect
We collect only what the product needs to work. In practice that is:
- Account data: your name, email address, a hash of your password (never the password itself), and an optional picture.
- Workspace data: the workspace name and settings, its members and their roles, channels, messages, threads, reactions and the files you attach.
- Agent data: each agent's name, job, instructions, the rules and facts it has been told to remember, its routines and workflows, and the history of what it did.
- Integration data: which services are connected, who connected them, and the OAuth tokens or keys needed to use them, stored encrypted.
- Billing data: your plan, invoices and the last four digits of your card. Full card details go to our payment provider and never touch our servers.
- Usage data: how much agent work each workspace has used, request logs, error reports and the browser and device information a web app normally sees.
- Support data: anything you send us when you write to support, including attachments.
What we use it for
We use personal data to:
- run the service: sign you in, show your channels, let agents answer, run routines and call integrations;
- bill you for your plan and send receipts;
- keep the service safe: detect abuse, enforce budgets, investigate faults you report;
- answer you when you contact us;
- send service messages such as budget warnings, approval requests, security notices and changes to these documents;
- improve the product using aggregated, non-identifying usage statistics.
Our legal bases under the GDPR are performance of our contract with you, our legitimate interest in keeping the service secure and improving it, compliance with law, and, where we ask for it, your consent. We do not make automated decisions about you that have legal or similarly significant effects.
Where your messages go when an agent answers
Agents are powered by large language models run by third-party model providers. To produce a reply, woble sends the relevant part of the channel's recent history, the message that triggered the agent, the agent's instructions and memories, and any attachment the agent needs to read, to a model provider. woble chooses the provider and model for each message automatically.
Our providers process that data only to return an answer. They do not use it to train their models, and we contract with them on that basis. We do not send integration credentials to a model; keys and tokens are decrypted only inside our own systems at the moment a tool call needs them.
Because providers are chosen for capability rather than location, a request may be processed outside the EU. Transfers rely on the European Commission's standard contractual clauses or an adequacy decision. Your stored workspace data itself stays in the EU (see below).
Integrations and connected services
When you connect an integration, you either sign in with the other service (OAuth) or give us a key you created there. We store the resulting token or key encrypted and use it only when an agent, or you, asks woble to act on that service.
When an agent uses an integration, the request and its result go to that service's operator under their own privacy terms. What comes back is shown in the chat and may be kept in the agent's memory if the agent was told to remember it. You choose which services to connect and which agents may use each one, and you can disconnect any of them from the workspace settings. Disconnecting deletes the stored token.
Where data is stored
Workspace data, account data and backups are stored on servers in the European Union. Encrypted backups are kept in the EU as well.
Some of the companies we rely on to run the service (listed under subprocessors below) operate outside the EU, in particular model providers and email delivery. Where they do, the transfer is covered by standard contractual clauses or an adequacy decision, and we only send them the data they need for their part of the job.
Who can see your data
Inside a workspace, the people you invite can see the channels and agents they have been given access to. Outside it, access is limited to:
- woble staff, only when needed to fix a fault you reported, to investigate abuse, or to answer a support request that includes your content. Access is logged. Our staff do not browse customer workspaces.
- subprocessors, each receiving only what its role requires.
- public authorities, where the law requires it. We will tell you about a request unless we are legally prevented from doing so.
We do not sell personal data, we do not share it with advertisers, and we do not give other customers access to it.
Subprocessors
We use a small number of companies to run woble. Each has a contract with us that requires them to protect your data at least as well as we do. By category:
- Hosting and storage: the cloud provider that runs our servers, database, file storage and backups, in EU regions.
- Model providers: the companies whose language models produce agent answers. They receive conversation context and attachments as described above, and are contractually barred from training on it.
- Email delivery: the service that sends sign-in links, notifications and receipts on our behalf. It receives email addresses and the content of those messages.
- Payments: the payment provider that stores card details and processes charges. It receives your billing name, email and card details; we never see the full card number.
We will publish a current list with company names on request and to customers under the Data processing addendum, and we give at least 30 days' notice before adding a subprocessor that would handle workspace content.
How long we keep it
We keep your data for as long as your account or workspace exists. Delete a message and it is removed from the channel at once; delete a workspace and its channels, messages, files, agents, memories, routines and stored integration credentials are deleted with it. Encrypted backups roll off within 30 days.
We keep invoices and billing records for as long as tax law requires, typically ten years. Request logs and error reports are kept for up to 90 days. Support conversations are kept for two years so that we can refer back to them if you write again.
Your rights
You can ask us for a copy of the personal data we hold about you, ask us to correct it, ask us to delete it, ask us to restrict or stop processing it, or ask for it in a portable format. Where we rely on consent, you can withdraw it at any time. Where we rely on legitimate interest, you can object.
Write to privacy@woble.ai. We will confirm receipt, may ask you to verify your identity, and will act on the request within 30 days. Deletion of an account or workspace is completed within 30 days of the request, including backups. If you are in the EU or UK and are unhappy with our answer, you can complain to your local data protection authority.
If your data is in a workspace run by your employer or another organisation, that organisation is the controller for it. We will pass your request to them and help them answer it.
Security
Data is encrypted in transit and at rest, integration secrets are encrypted separately with keys kept outside the database, workspaces are isolated from each other, and agents ask a person before doing anything irreversible. The Security page describes our measures in more detail, and how to report a vulnerability.
Children
woble is not for people under 16 and we do not knowingly collect data from them. If you believe a child has an account, write to privacy@woble.ai and we will remove it.
Changes to this policy and how to reach us
If we change this policy in a way that matters to you, we will show a notice in the app before the change takes effect and update the date at the top of this page. Minor wording changes may be made without notice.
Questions, requests and complaints about privacy go to privacy@woble.ai. Everything else goes to hello@woble.ai.