Data Processing Agreement

Last updated 15 November 2026

This is a draft. The highlighted details are still to be filled in, and the text has not been checked by a lawyer yet.

This agreement is between you, the customer, and [COMPANY NAME], and is part of the Terms of Service. It covers the personal data we process for you when your sites and servers send data to SiteGoose, as Article 28 of the EU GDPR and of the UK GDPR require. You accept it when you create an account. If it and the Terms disagree about personal data, this agreement wins.

  1. 1. Roles and scope
  2. 2. Your instructions
  3. 3. Your part
  4. 4. Our people
  5. 5. Security
  6. 6. Sub-processors
  7. 7. Transfers outside the EU and UK
  8. 8. Helping with people’s requests
  9. 9. Personal data breaches
  10. 10. Other help we give
  11. 11. Deletion at the end
  12. 12. Information and audits
  13. 13. General
  14. Annex 1: the processing
  15. Annex 2: security measures
  16. Annex 3: sub-processors

1. Roles and scope

  • You are the controller of the personal data your sites, apps and servers send us, and of what you and your team put into SiteGoose. We are your processor. If you run SiteGoose for a client, you are their processor and we are your sub-processor.
  • Annex 1 describes the processing: whose data, what kinds, why, and for how long.
  • For data about you and your team as our customers (accounts, billing, support), we are the controller, and our privacy policy applies instead.
  • “GDPR” here means the EU GDPR and the UK GDPR, whichever applies. Other terms such as “personal data”, “processing” and “personal data breach” mean what they mean there.

2. Your instructions

  • We process the personal data only on your documented instructions. Those are the Terms, this agreement, and what you set up and choose in SiteGoose: which features you turn on, what the tracker collects, how you mask, filter and share. You can give further instructions in writing.
  • We may process it otherwise only where the law we are under requires it, and then we will tell you first, unless that law forbids telling you.
  • If we think an instruction breaks data protection law, we will tell you.
  • We don’t sell the personal data, use it for advertising, or combine it with data from other customers to learn about the same person.

3. Your part

You are responsible for having a lawful basis for the processing, for the privacy notice you give your visitors, for getting consent where it is needed, and for not sending us special categories of data, card numbers, passwords or government ID numbers. SiteGoose’s settings (the cookie banner, masking, excluded pages, IP and visitor options) help, but choosing them is yours.

4. Our people

Only people who need it to run the service can reach the personal data, and each of them is bound to keep it confidential. Our staff open a customer’s account only to give support the customer asked for, to investigate a fault or abuse, or where the law requires it.

5. Security

We keep the measures in Annex 2 in place, and keep them appropriate to the risk as Article 32 asks. We may change them, but never to give less protection overall.

6. Sub-processors

  • You allow us to use the sub-processors in Annex 3, which is kept up to date at /subprocessors.
  • Before we add or replace one, we will email the account owner and update that page at least 30 days ahead. If you object on reasonable data protection grounds, tell us within those 30 days. We will try to find a way round it; if we can’t, you may close your account, and we will refund any time you paid for and can no longer use.
  • Each sub-processor is bound by a written contract giving the personal data the same protection as this agreement. We remain responsible to you for what they do.

7. Transfers outside the EU and UK

Your data is stored in the EU. Some sub-processors in Annex 3 process some of it in other countries. Each such transfer rests on an adequacy decision (including the EU–US Data Privacy Framework where the recipient is certified) or on the European Commission’s Standard Contractual Clauses, with the UK Addendum for UK data. Where we are the exporter, those clauses are part of this agreement.

8. Helping with people’s requests

When one of your visitors asks you to see, correct or delete their data, or objects to its use, we will help you answer, as far as we reasonably can. If they ask us directly, we will pass the request to you and not answer it ourselves.

One limit is by design. A visitor who has not agreed to be remembered gets an ID that changes every day and that nobody, including us, can tie back to them afterwards. Their data can be found only by what else identifies them: a user ID or email address you sent, a form they filled in, or a survey they answered.

What you can do yourself: delete a site and all its data, delete all session replays or heatmap snapshots of a site, and delete leads, form entries and testimonials.

9. Personal data breaches

  • We will tell you without undue delay, and in any case within 48 hours, after we become aware of a personal data breach affecting your data. We write to the account owner’s email address.
  • We will tell you what we know: what happened, what data and roughly how many people are affected, what we have done and are doing about it, and who you can talk to. If we don’t know everything yet, we will send what we have and follow up.
  • We will help you meet your own duties to notify the authority and the people affected.
  • Telling you about a breach is not an admission that we were at fault.

10. Other help we give

We will give you the information you reasonably need for a data protection impact assessment or a prior consultation with an authority about SiteGoose.

11. Deletion at the end

  • While your account is open you can export reports as CSV and PDF.
  • When you delete a site or close your account, we delete its data from our live systems: the account and site records at once, the event and recording data within 7 days.
  • Copies in our backups are not edited; they expire on their own. Backups of event and recording data expire within 65 days, backups of account and site records (which include leads, form entries and testimonials) within 13 months. Until then they are used only to recover from a failure, and deleted data is not restored into the service.
  • We keep nothing longer unless the law requires it.

12. Information and audits

We will make available what you reasonably need to show that we keep to this agreement, and answer your written questions about it. If that is not enough, or an authority asks, you may audit us, or have an independent auditor bound to confidentiality do so, once a year, with 30 days’ notice, at your cost, in a way that does not expose other customers’ data or our security.

13. General

This agreement lasts as long as we process personal data for you. Liability under it is as set out in the Terms. It is governed by the same law as the Terms, except where the Standard Contractual Clauses require otherwise. Questions about it: info@sitegoose.com.

Annex 1: the processing

Subject matter, nature and purpose

Running SiteGoose for you: collecting, storing, analysing and showing data about visits to your sites and apps, and about your servers, so you can see your traffic, find problems, check security and uptime, and act on what you find. Only the features you turn on run. When you approve a testimonial, we also publish it for you: on your site through the testimonials block, and to your own code and API keys, until you reject or delete it.

Duration

As long as your account is open, then as in section 11.

Whose data

  • Visitors to your sites and users of your apps.
  • People who fill in your forms, surveys, feedback and lead forms, send you a testimonial, or buy from your shop.
  • People whose requests reach your servers, when you install a server package or the agent.
  • Anyone else whose data you choose to send.

What kinds of data

  • Visit data: pages viewed, where the visit came from (referrer and campaign tags), time on page, scrolling, clicks, events you define, Core Web Vitals, browser, operating system, device type and screen size, language.
  • Approximate location: country, region and city, looked up from the IP address on our own servers.
  • Online identifiers: a visitor ID made from the site, the browser and the IP address with a random value that is thrown away at the end of each day. If you turn on remembering visitors, a visitor who agrees gets a random ID kept in their browser. IP addresses are used when a request arrives and are not stored with analytics. They are stored only with firewall events (requests your firewall rules blocked or flagged), in the audit log your site’s server package sends (logins and changes on your site), and with the logins from it we list as unusual, for up to a year.
  • Recordings and snapshots, when you turn them on: what a page showed and how the visitor moved through it, with the addresses (never the query or contents) of the page’s requests that failed or were slow, and its console errors and warnings. Typed input and textareas are left out, and email addresses and long numbers on the page, in those addresses and in console messages are masked, by default.
  • What people send you: form, survey, feedback and lead-form answers and testimonials, which may include names, email addresses and phone numbers.
  • Data you identify people with: user IDs and properties you send with identify, and order data (a customer ID or an email hashed in the browser) from your shop.
  • Errors: error messages, stack traces and the page they happened on.
  • Server data, from the packages and agent: request paths, response times, crawler visits, database query text and timings, and the machine’s resource figures.

No special categories of data are meant to be processed (see section 3).

How long

Each kind of data is kept for the time your plan gives it, shown under Compare plans on the pricing page, then deleted automatically. Some are kept for a fixed time on every plan: cookies seen on your site 90 days, heatmap page images 120 days, identify records 13 months, experiment exposures 13 months, the audit log 1 year. Leads, form entries and testimonials are kept until you delete them or the site.

Annex 2: security measures

  • Where: all data is stored in Hetzner data centres in Germany and Finland.
  • In transit: every connection to the dashboard, the API and the collector uses HTTPS.
  • Visitors: daily visitor IDs keyed with a value deleted at the end of each day; no IP address stored with analytics; recordings mask typed input by default; you can exclude pages and elements.
  • Sign-in: passwords stored only as bcrypt hashes; two-factor authentication for every account and required for our staff; an emailed code when someone signs in from a browser we haven’t seen; limits on sign-in attempts.
  • Access: each site has its own team with roles (owner, admin, editor, viewer), checked on every request. Each of our services uses its own database user with only the rights it needs.
  • Our systems: a network firewall in front of every server; passwords and keys kept out of the code, in files only the service that uses them can read; changes to your team and settings written to an audit log.
  • Backups: nightly, kept in a different data centre from the live data, file backups encrypted, and a restore tested every month.
  • Monitoring: the service is watched for errors, outages and overload, and alerts reach us by email.
  • Breaches: a written procedure for finding, containing and reporting a personal data breach (section 9).

Annex 3: sub-processors

CompanyWhat forWhat it getsWhereTransfer basis
Hetzner Online GmbHOur servers, databases, file storage and backupsEverything we hold for you: it is where the data is keptGermany (Falkenstein, Nuremberg) and Finland (Helsinki)Stays in the EU
Anthropic, PBCThe AI features: the assistant, insights, writing and translating help, heatmap explanations, session replay summaries and accessibility textOnly when someone on your team uses an AI feature: their question, the report figures needed to answer it, page addresses and page text, and, when the question is about them, feedback messages, survey answers and error messages. For a session replay summary, the steps of the recordings asked about: the page addresses, the text of what was clicked, the names of fields typed in, failed requests (without their query) and console and error messages, with each visit’s device, browser, country and source. Never what was typed, the recorded pages themselves, or who the visitor isUnited StatesThe Standard Contractual Clauses (modules 2 and 3) with the UK Addendum, in Anthropic’s Data Processing Addendum, part of its Commercial Terms
Cloudflare, Inc.Our DNS, always. Status pages, always: each one passes through Cloudflare, which keeps a copy of what the page shows so it still answers while our servers are down. Carrying your visitors’ other requests only while an emergency switch is on: a flood our servers can’t hold, or tracker files that aren’t the ones we releasedFor status pages: the requests of the people who open one, with their IP address, and a copy of what each page shows publicly. While a switch is on: the requests your visitors’ browsers send to us, with their IP address, passed on to our servers unchanged. At other times nothing about your visitorsWorldwide, at the data centre nearest each visitorEU–US Data Privacy Framework, and the Standard Contractual Clauses with the UK Addendum in Cloudflare’s DPA should that ever lapse
Zoho CorporationSending the emails you set up: new lead and form alerts, double opt-in confirmations to the people who sign up, and alerts and reportsFor a lead alert, the answers given in the form, which may include a name, email address and phone number. For a double opt-in, the email address of the person who signed up. For other alerts and reports, what they show, such as an error messageUnited StatesThe Standard Contractual Clauses in Zoho’s DPA
Apify Technologies s.r.o.Reading the public social and competitor pages you ask us to watchThe addresses of those pages, and what they publicly show. Nothing about your visitorsCzech Republic, and the United States and other countries where its own sub-processors runAn EU company. Its own transfers outside the EU rest on the Standard Contractual Clauses in Apify’s DPA, part of its terms

Some features send data to services you connect yourself, such as Google, Slack or a webhook address. That happens on your instruction, under your own agreement with that service, and those services are not our sub-processors. See /subprocessors.

Terms of ServicePrivacy policySub-processorsSecurityinfo@sitegoose.com