← Privacy policy

Data Processing Agreement

Version 1, November 5, 2026

1. Parties and how this agreement applies

The processor is Surfzone OÜ, registry code 14052124, Toome pst 51a, 10913 Tallinn, Estonia ("IndieBob"). The controller is the customer who uses IndieBob's tracker or support chat on their own site ("you").

This agreement forms part of IndieBob's Terms of Service and applies from the moment IndieBob first processes personal data for you. If you need a signed copy, complete the block at the end and send it to the address above; IndieBob will countersign it. If this agreement and the Terms disagree on personal data, this agreement wins.

2. What IndieBob does with the data

IndieBob processes personal data only to run the service for you, as Annex I describes, and only on your documented instructions. Your use and settings of the service, these terms and the Terms of Service are those instructions.

If the law requires other processing, IndieBob tells you first, unless that law forbids it. If IndieBob thinks an instruction breaks data protection law, it tells you and may pause that processing until you confirm or change it.

3. Confidentiality

Everyone at IndieBob with access to the data is bound to keep it confidential.

4. Security

IndieBob keeps the measures in Annex II in place (GDPR Art. 32). It may change them as long as the protection does not fall.

5. Sub-processors

You authorise the sub-processors in Annex III. IndieBob tells you at least 30 days before adding or replacing one, by email and on this page. You may object on reasonable data protection grounds within that time. If the objection cannot be resolved, you may end the affected service and are refunded for the unused paid period.

IndieBob binds each sub-processor to data protection duties that match this agreement, and stays liable to you for their work.

6. Helping you

IndieBob helps you answer people who use their data protection rights, and passes on any such request it receives instead of answering it. It also helps with security, breach notices, data protection impact assessments and prior consultation (GDPR Arts. 32 to 36), as far as the nature of the processing allows.

7. Personal data breaches

IndieBob tells you without undue delay, and within 48 hours of becoming aware of a breach that affects your data, with what it knows then: what happened, the data and people affected, what it has done and who to contact. It sends the rest as it learns it.

8. Deleting or returning the data

You can export your data at any time. When your account closes, IndieBob deletes your personal data within 30 days, and from backups as they expire, unless the law requires it to be kept. Annex I gives the retention while the account is open.

9. Audits

IndieBob gives you the information you need to show this agreement is being kept, and answers reasonable written questions. If that is not enough, or a regulator requires it, you or an independent auditor bound to confidentiality may audit the processing, on 30 days' notice, in working hours, at your cost, and without access to other customers' data.

10. International transfers

Personal data leaves the EU only as Annex III describes, on the basis given there.

11. Liability, term and law

Liability follows the Terms of Service. Nothing here limits the rights of the people whose data this is, or either party's liability to them under GDPR Art. 82.

This agreement lasts as long as IndieBob processes personal data for you. It is governed by the law of the Republic of Estonia, and the courts of Estonia have jurisdiction, unless the law requires otherwise.

Annex I: the processing

Subject matter and purpose: web analytics and support chat for your site, shown to you in IndieBob.

Nature: collecting, storing, aggregating, showing and deleting.

Duration: as long as you use the service, then as clause 8 says.

Whose data: visitors to your site, and people who write to you in the chat.

Tracker data:

  • Used and then dropped: the IP address and the user agent, for the daily hash and the location lookup.
  • A daily visitor ID: a hash of a daily salt, your project, the IP address and the user agent. With full attribution, a random ID from the visitor's browser instead.
  • Page path, title and address, with only the utm_* and ref parameters kept; the referrer's site and path.
  • Country, region and city from the IP address; browser, operating system and device type; screen size, language and time zone.
  • Time on the page, how far it was scrolled, and clicks on outbound links and downloads.
  • Anything you send yourself: event names and properties, and the user ID and traits from identify().

Chat data: messages and images, an email address if the visitor leaves one or your site signs them in, the page the chat was opened on, the browser's language and time zone, and the country. The privacy policy has the detail.

Special categories: none are intended, and the Terms of Service do not allow you to send them through the tracker.

What links a visitor: after the salt is deleted nobody can work out a daily ID again, so a visitor cannot be followed from one day to the next. The ID stays on that day's rows and links that day's events to each other. Unless you use full attribution or identify(), nothing else on a row is an identifier, though its location, browser and screen size stay on it.

Tracker dataKept
Events (page views, your events)Free plan: 90 days. Paid plans: until you delete them or close your account.
Visits (one row per visit)Free plan: 13 months. Paid plans: until you delete them or close your account.
Visitor rows (one per daily ID, with its first source and totals)Until you close your account.
The daily saltDeleted when the next day's salt is made, so about 24 hours.
IP addressNot written to the database. Held in memory for the request, and for up to two minutes by the rate limiter.

Support chats are deleted 12 months after their last message (you can choose less), and unanswered anonymous ones after 30 days.

Annex II: security measures

  • Encryption in transit: HTTPS for all traffic, and encrypted connections to the database.
  • Encryption at rest: database and file storage, and support messages are encrypted again by the application.
  • Network: the database is reachable only from IndieBob's application servers, not from the public internet.
  • Access: limited to the two people who run IndieBob. Customers see only their own projects, and every service key is limited by scope.
  • Data minimisation: the IP address is not written to the database, addresses lose every query parameter but campaign ones, on the server as well as in the tracker, and the daily salt is deleted.
  • Availability: automated daily database backups, and rate limits on the collection endpoint.
  • Images in the chat are re-encoded to remove their metadata and kept in a private bucket.

Annex III: sub-processors

These handle data about the visitors of a site running the tracker:

ProviderPurposeLocationTransfer basis
DigitalOcean, LLCHosts the application, database, file storage, the tracker script and IndieBob Mail.Frankfurt, Germany. The company is in the United States.EU–US Data Privacy Framework (the company is certified); Standard Contractual Clauses if that stops applying
Cloudflare, Inc.Network in front of DigitalOcean's hosting and CDN, engaged by DigitalOcean as its own sub-processor. Sees each request, including the IP address, and supplies the country header.Worldwide network; Cloudflare keeps its logs in the United States and Europe.EU–US Data Privacy Framework (the company is certified); Standard Contractual Clauses if that stops applying

These never receive a visitor's row. They serve your account, or see totals only:

ProviderPurposeLocationTransfer basis
IndieBob's own machinesAI work. For analytics they see totals only, never a visitor's row.EstoniaNone needed: in the EU.
Google Cloud EMEA Limited (Workspace mail)Delivers IndieBob's own email and customers' broadcasts.Ireland, with processing in the United StatesEU–US Data Privacy Framework (the company is certified); Standard Contractual Clauses if that stops applying
Google Cloud EMEA Limited (Gemini API)Writing tasks when IndieBob's machines are busy: product facts and the request.Ireland, with processing in the United StatesEU–US Data Privacy Framework (the company is certified); Standard Contractual Clauses if that stops applying
Google Ireland Limited (sign-in, Google Analytics)Sign-in to IndieBob, and counting visits to indiebob.com itself with consent. Never a customer's site.Ireland, with processing in the United StatesEU–US Data Privacy Framework (the company is certified); Standard Contractual Clauses if that stops applying
Stripe Payments Europe, LimitedPayments for IndieBob plans, and customers' own connected Stripe accounts.Ireland, with processing in the United StatesEU–US Data Privacy Framework (the company is certified); Standard Contractual Clauses if that stops applying
Anthropic Ireland, LimitedOptional AI analysis. Only aggregated project metrics are sent.Ireland, with processing in the United StatesStandard Contractual Clauses (not on the Data Privacy Framework list). No personal data is sent.
OpenAI Ireland LtdDraws a picture from its text description when IndieBob's own server cannot.Ireland, with processing in the United StatesStandard Contractual Clauses (not on the Data Privacy Framework list). No personal data is sent.
Replicate, Inc.Draws a picture from its text description when IndieBob's own server cannot.United StatesNo personal data is sent, so no transfer takes place.
SerpApi, LLCProspect search on Plus: only a kind of business and a place.United StatesNo personal data is sent, so no transfer takes place.

Signatures

For the controller

Company:

Name and role:

Signature:

Date:

For IndieBob

Company:

Name and role:

Signature:

Date: