Data processing statement

Kamelo Business · For IT, privacy officers and DPOs · Last updated 12 October 2026

This statement explains which personal data Kamelo Business handles, where, and for how long, so your organisation can record it in its own register of processing activities and privacy assessment.

Summary

• Kamelo Business runs entirely in the browser on each computer. The extension makes no network requests to Kamelo: there is no Kamelo server, no account and no analytics.
• Kamelo never receives the text your people type, the data of your clients, or the masked details. We have no way to see them.
• For that content, Kamelo is therefore not a processor under Article 28 of the GDPR. Your organisation stays the controller.
• Kamelo only receives the business contact and billing details of your organisation, and issues a licence with your organisation's name, the number of seats and an expiry date.

How Kamelo Business works

When someone at your organisation types in ChatGPT, Claude, Gemini, Copilot or an AI field in Gmail, Slack or Notion, Kamelo replaces names, email addresses, phone numbers, addresses, IBANs, card numbers, secrets, company names and your own client and project terms with placeholders such as [PERSON_1]. This happens on the computer, before the text is sent. In the answer, Kamelo puts the real details back, again only on that computer. The AI service receives the placeholders, not the real details. What the AI service does with the rest of the text is governed by your organisation's agreement with that service.

Not a processor for what your people type

A processor processes personal data on behalf of a controller. Kamelo Business is software that your organisation installs and runs on its own computers. Kamelo, as the supplier, has no access to anything typed or stored in it, and receives none of it. Kamelo therefore does not process that data on your behalf and is not a processor for it under Article 28 GDPR, and no processing agreement is needed for it. Your organisation decides how Kamelo is set up, through its own policy, and remains the controller of the data on its computers.

What Kamelo does receive

• Business contact and billing details: the name of your organisation, the name and work email address of your contact person, and, once billing starts, billing details such as an address and VAT number. Kamelo is the controller for these and uses them only to provide the licence, to bill, and to answer questions.
• Licence data: the licence code we issue contains your organisation's name, the number of seats and an expiry date. The extension checks it offline, on the computer, with a digital signature (Ed25519). Kamelo is not told where, when or by whom the code is used.
• Emails you send us: only what you choose to write. Please never send client data or a licence code through a public channel. When someone uses "Report a problem" in the extension, it opens the support contact your IT team set (or an email to hello@kamelo.eu if none is set). An email is prefilled with only the website's name, the version of Kamelo and the browser. Nothing is sent automatically.

What stays on each computer, and for how long

• The vault: which placeholder belongs to which real value, so the answer can be restored. Stored in the browser's extension storage on that computer, kept separate per website, never synced or uploaded. Deleted automatically after 30 days by default; your organisation can set another period with the retentionDays policy (0 means never). Kamelo checks this when the browser starts and every 12 hours. People can lock the vault with Touch ID or a password; it is then encrypted with AES-256-GCM.
• Monthly overview: per type of detail, how many were masked (for example "3 names, 1 IBAN"). Counts only: no values, no websites, no times. Kept for 12 months, and shown only in the extension's popup on that computer. There is no central dashboard.
• Settings and the licence code: until they are changed or the extension is removed.
• Melo (private chat): questions and answers are kept only while the chat window is open; closing it removes them. Answers come from the AI built into the browser, on that computer; where that isn't available, Kamelo offers a temporary chat in the AI service instead. Your organisation can turn Melo off with the privateChat policy.

Removing the extension (for example by taking it out of the forced installation) deletes all of the above from that computer.

How your IT team can check this

• Network: open chrome://extensions (or edge://extensions), turn on Developer mode, open the extension's service worker and watch the Network tab while someone uses an AI tool. Kamelo sends nothing to us.
• Policy: chrome://policy (or edge://policy) shows exactly which settings your organisation applied to Kamelo.
• Permissions: storage, scripting, alarms, sidePanel and access to websites. The reasons are listed on Security for business and in the security overview (PDF).
• Code: Kamelo's own code ships unminified inside the extension, so your security team can read what is installed. The free edition's source code is public on GitHub.

Sub-processors

For the content your people type: none. Kamelo doesn't receive it, so no one else does on our behalf.

For billing: during the pilot there is no billing. Before billing starts, the payment provider we use will be listed here.

A signed statement or your own agreement

Need this statement signed, or does your organisation want to use its own processing agreement? We have a standard agreement available on request. Email hello@kamelo.eu.

Changes and contact

If this statement changes, the new version will be published at this address with a new date. See also the privacy policy and the terms of use. Questions: hello@kamelo.eu. Security problems: please report them privately, as described on the security page.