Legal
Data processing agreement
Last updated:
This agreement forms part of our terms of service. It applies when we process personal data on your behalf, for example your agency clients' data. It sets out the terms required by Article 28 of the UK GDPR.
1. Roles
You are the controller of personal data you put into the service about your clients and their customers. We are your processor for that data.
For your own account and billing data, we are a separate controller, as our privacy notice explains.
2. What we process
- Subject: providing the service under our terms.
- Duration: for as long as you use the service, and until deletion under section 7.
- Nature and purpose: storing client business details, tracking questions in AI engines, analysing answers and producing reports.
- Types of data: names and contact details of client staff, business details, and any personal data that appears in AI answers (for example, a sole trader's name).
- Data subjects: your clients' staff and contacts, and people named in AI answers.
3. Our commitments
In line with Article 28, we will:
- process the data only on your documented instructions, which are these terms and how you use the service, unless the law requires otherwise;
- make sure anyone who processes the data is bound by confidentiality;
- keep appropriate security measures in place (see section 5);
- only use sub-processors under section 4;
- help you respond to requests from data subjects exercising their rights;
- help you meet your security, breach-notification and data protection impact assessment duties;
- delete or return the data when the service ends (see section 7);
- give you the information you reasonably need to show compliance, and allow reasonable audits (see section 8).
We'll tell you if we think an instruction breaks data protection law.
4. Sub-processors
You give us general permission to use the sub-processors below. Each is bound by written terms that protect the data at least as well as this agreement.
| Provider | What they do for us | What they receive | Where | When we use them |
|---|---|---|---|---|
| Cloudflare | Hosting, database, background jobs, bot protection (Turnstile), text analysis (Workers AI), routing of AI API calls (AI Gateway) and email sending | All service data, as our host | Global network; US company | Always |
| Stripe | Payments, invoices and subscriptions | Name, email, billing address, payment details. We never see your full card number | UK, EU and US | When you buy a plan |
| DataForSEO | Collects answers from ChatGPT, Gemini, Google AI Overviews and Google AI Mode, as the public sees them | The questions we track and the locations they're asked from. Not your personal data | Location: see DataForSEO's privacy policy | Always (every plan and the free check) |
| Anthropic | Claude API: Claude answers (with web search), and quality checks on a small sample of answer analysis | The questions we track, the location they're asked from and the text of AI answers | US | Always on paid plans |
| Perplexity | Sonar API: Perplexity answers (with web search) | The questions we track and the location they're asked from | US | Always |
| xAI | Grok API (with web search): Grok answers | The questions we track and the location they're asked from. Not your personal data | US | When Grok is configured on our service. It is not opt-in per organization: while configured, it receives the questions of every project that tracks Grok |
| DeepSeek | DeepSeek API: DeepSeek answers from model knowledge (no web search) | The questions we track and the country they're asked from. Not your personal data | People's Republic of China | When DeepSeek is configured on our service. It is not opt-in per organization: while configured, it receives the questions of every project that tracks DeepSeek |
| OpenAI | Optional ChatGPT developer-API lane, for comparison with consumer ChatGPT answers | The questions we track and the location they're asked from | US | Not in use: no OpenAI connection is switched on today. Consumer ChatGPT answers come through DataForSEO |
| Google sign-in, and the Search Console and Analytics APIs when you connect them | For sign-in, your Google account name and email. For connected properties, access tokens and the search and analytics data you choose to connect | US company; global infrastructure | Only when you sign in with Google or connect a Google property | |
| Resend | Transactional email, only as a backup to Cloudflare email sending | Your email address and the email content | US | Off today. Switched on only if Cloudflare email sending fails |
Consumer ChatGPT and Google AI answers are collected through DataForSEO, so we don't send your questions to OpenAI or Google for them, and we never send them your personal data. Integrations you connect yourself (such as your identity provider for SSO) receive data on your instructions; they are your providers, not our sub-processors.
We'll give you at least 30 days' notice of any new sub-processor by email. You can object on reasonable data protection grounds. If we can't resolve it, you can cancel and we'll refund prepaid fees for the unused period.
Transfers outside the UK use the safeguards described in our privacy notice.
5. Security measures
- Encryption in transit (TLS) and at rest.
- Each customer's data is kept separate, with access checked on every request.
- Staff access limited to what's needed.
- No IP addresses stored (abuse checks use a salted one-way hash, deleted within 48 hours). Bot protection and rate limiting on public forms.
- Secrets and API keys kept out of code.
- Backups and logs kept for limited periods only.
6. Personal data breaches
If we become aware of a personal data breach affecting your data, we'll tell you without undue delay. We'll give you the information you need to assess it and to notify the ICO and data subjects if required.
7. Deletion at the end
Before your account closes, you can ask us for a copy of your data. We then delete your personal data within 30 days, unless the law requires us to keep it.
Copies in backups are overwritten in the normal backup cycle and are not restored in the meantime.
8. Audits
We'll answer reasonable written questions about our data protection practices. If that isn't enough, you may audit our compliance once a year, with 30 days' notice, at your own cost, and under confidentiality.
9. Liability and law
The liability limits in our terms of service apply to this agreement. It's governed by the law of England and Wales.
Questions about this page? Email hello@glossydata.com. Written replies by email, usually within one working day.