Data processing
Your data, our job.
The data processing addendum, for business customers and agencies: how we handle personal data for you as your processor. Part of our terms. Last updated 15 November 2026.

What this addendum covers
This addendum is part of our terms for every business customer. It applies whenever we process personal data on your behalf while providing LLM Monster: for example personal data on the websites you have us scan, the Search Console and Google Analytics data you connect, client sites an agency adds, and the leads an agency's website widget collects. You do not need to sign it; if you want a signed copy for your records, write to help@llmmonster.com.
For this data you are the controller (or, for an agency acting for its client, a processor, and we are your sub-processor) and we are your processor. For our own customer records (your account, team members, orders, support mail) we are a controller, and our privacy notice applies instead.
If this addendum and the terms disagree about personal data, this addendum wins. Where the European Commission's standard contractual clauses or the UK addendum apply (section International transfers), they win over both.
The processing
| Subject and purpose | Providing the scans, audits, AI visibility checks, Search Console and Google Analytics readings, reports, agency features and support you signed up for. |
|---|---|
| Duration | While you use the service, then until the data is deleted as set out under End of the service. |
| What we do with it | Collect (crawl public pages, read connected Google properties, receive widget leads), store, analyse, combine into reports, show to your organisation's members, send by email at your request, and delete. |
| Kinds of personal data | Whatever personal data your websites publish (such as staff names, contact details and text on public pages); search queries and page addresses in Search Console data, which may contain names or other personal details people searched for; page addresses and visit counts from Google Analytics (no visitor, device or user details); for agencies, the name, email address, website and message a visitor types into the lead widget. |
| Whose data | People named on your websites, people whose searches appear in your Search Console data, and, for agencies, visitors to the agency's website who use the widget. |
| Special categories | Not intended. If your public pages or search queries contain health, religious or other special category data, we process it only as part of the page or the query, never sorted or profiled by it. |
Your instructions
We process this data only on your documented instructions: these terms, this addendum, and the settings and actions you take in the service (what you scan, what you connect, what you share, what you delete). We do not use it for our own purposes, with one exception: we may count and measure the use of our own service in a form that identifies no person and no customer. If we believe an instruction breaks data protection law, we tell you. If the law makes us process the data in another way, we tell you first unless that law forbids it.
You are responsible for having a lawful basis for the data you give us, for telling the people concerned what they need to know, and, as an agency, for your client's authority to scan its sites and connect its Google properties.
Confidentiality
Only people who need access to run, support or secure the service can reach the data, and each is bound to keep it confidential. Nobody at LLM Monster reads your Search Console or Google Analytics data unless you ask us to for support, security needs it or the law requires it.
Security
We keep technical and organisational measures that fit the risk, including:
- Encryption in transit (TLS) between your browser and our servers and between our own servers.
- Google access permissions stored encrypted (AES-256), kept apart from the servers that read the data, which only get access that expires within an hour.
- Backups encrypted on our servers before they leave them, so the backup provider cannot read them.
- Access by organisation and role on every request: owner, admin, billing, member and viewer.
- Firewalls that limit what our scanning machines can reach, separate system users for paid and free work, and limits on requests and emails against abuse.
- Servers in the European Union, kept up to date, with access for named staff only.
We may change these measures, but not in a way that lowers the protection overall.
Sub-processors
You give us general permission to use sub-processors. The kinds we use today are listed in the privacy notice: hosting in the European Union, encrypted backups, email sending, payments, the AI assistants we ask, and data providers for search results, web access and text labelling. We give business customers the name, location and role of each sub-processor on request, and we keep that list current; because the list shows how our service works, we ask you to keep it confidential.
Before we add or replace a sub-processor that will process your data, we tell the owner of your organisation by email at least 30 days ahead (or as soon as we can, if a provider fails and we must replace it to keep the service running). If you object on reasonable data protection grounds, tell us within that time. We will try to find a solution; if we cannot, you may end the affected service and we refund any fee paid for the time after the change.
We bind each sub-processor by contract to data protection duties at least as strict as these, and we remain responsible to you for its work.
Helping you
- Requests from people. If someone asks us directly about data we process for you, we pass the request to you and do not answer it ourselves unless you tell us to. Most data can be found and deleted in the service itself (delete a report, remove a site, disconnect a Google property); for the rest, we help you within a reasonable time.
- Breaches. If we become aware of a breach of security that affects your personal data, we tell your organisation's owner without undue delay, and within 48 hours where we can, with what we know then and updates as we learn more, so you can meet your own deadlines.
- Assessments. We give you the information you reasonably need for a data protection impact assessment or a consultation with a supervisory authority about the service.
Checks and audits
We make available the information you need to show that we meet this addendum. Write to help@llmmonster.com with your questions; we answer in writing. If a written answer is not enough, or a supervisory authority asks for it, you or an independent auditor bound to confidentiality may audit us once a year, on 30 days' notice, during business hours, at your cost, in a way that does not expose other customers' data or our trade secrets.
International transfers
We keep your data on servers in the European Union. Some sub-processors (AI assistants, email, payments, encrypted backups) are in, or may reach the data from, other countries, including the United States. We transfer data out of the European Economic Area or the United Kingdom only to a country with an adequacy decision (such as a company certified under the EU-US Data Privacy Framework and its UK extension), or under the European Commission's standard contractual clauses (module 3, processor to processor) with the UK addendum where UK data is involved, and with the extra measures those need.
If you are outside the European Economic Area and we receive personal data from you, the clauses in module 4 (processor to controller) apply where the law requires them. The clauses, when they apply, are part of this addendum: the governing law and courts for them are those of the Republic of Cyprus, and the supervisory authority is the Cyprus Commissioner for Personal Data Protection.
End of the service
When your organisation leaves, deletes a site, a report or a connection, or deletes its account, we delete the data concerned as the retention table sets out: Search Console and Google Analytics data within an hour of disconnecting (and once the organisation has had no paid plan and no sign-in for 12 months), reports and site data with the organisation. Copies in encrypted backups drop out within 40 days on the scanning servers and within about 7 months on the account servers, and are never restored for use in the meantime except to recover from a failure. Before you leave, you can download your reports. We keep data longer only where the law requires it, and then only for that purpose.
Liability
Each party's liability under this addendum is subject to the limits in the terms, except where data protection law does not allow a limit. Nothing here limits the rights of the people whose data it is.
