Skip to content

Last updated 19 November 2026 · Version history

Data processing agreement

Draft under legal review. This text may still change before it is final. Questions: [email protected].

This data processing agreement ("DPA") applies when your organization uses SpoorFox. It sets out how SpoorFox B.V. in formation ("SpoorFox", "we") processes personal data on your behalf, as Article 28 of the General Data Protection Regulation (GDPR) requires. It follows the European Commission’s standard contractual clauses between controllers and processors (Implementing Decision (EU) 2021/915), filled in for SpoorFox.

Contents

Section I: Purpose, scope and interpretation

Clause 1. Purpose and scope

  1. This DPA ensures compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 (the GDPR) for the processing of personal data in SpoorFox.
  2. The customer that orders SpoorFox ("you", the controller) and SpoorFox ("we", the processor) have agreed to this DPA. The parties are described in Annex 1.
  3. This DPA applies to the processing of personal data described in Annex 1.
  4. Annexes 1 to 3 are an integral part of this DPA.
  5. This DPA is without prejudice to the obligations of the controller under the GDPR.
  6. This DPA does not by itself ensure compliance with the rules on international transfers in Chapter V of the GDPR. Clause 7.8 sets out how transfers are covered.

Clause 2. How this DPA is agreed and changed

  1. This DPA is part of the agreement under our terms of service. You accept it when you accept the terms, at checkout, by signing an order or by using the service. Acceptance in electronic form meets the requirement of Article 28(9) GDPR that this DPA is in writing. If you need a signed copy for your records, email [email protected].
  2. We change the list of subprocessors only as described in Clause 7.7. We may update the measures in Annex 2, as long as the overall level of security does not decrease. Other material changes to this DPA are announced at least 30 days before they apply, as described in section 18 of the terms.

Clause 3. Interpretation

  1. Terms defined in the GDPR, such as personal data, processing and personal data breach, have the same meaning in this DPA.
  2. This DPA is read and interpreted in the light of the GDPR.
  3. This DPA is not interpreted in a way that runs counter to the rights and obligations in the GDPR, or that prejudices the fundamental rights or freedoms of data subjects.

Clause 4. Hierarchy

If this DPA conflicts with the terms of service, an order or any other agreement between the parties, this DPA prevails for the processing of personal data. An order may add protections to this DPA but cannot reduce them.

Clause 5. Docking clause

Not used.

Section II: Obligations of the parties

Clause 6. Description of the processing

The processing operations, in particular the categories of personal data and the purposes for which they are processed on behalf of the controller, are described in Annex 1.

Clause 7. Obligations of the parties

7.1 Instructions

  1. We process personal data only on your documented instructions, unless EU or Member State law requires otherwise. In that case we inform you of that legal requirement before processing, unless the law prohibits this. Your documented instructions are the agreement, this DPA and the way you configure and use SpoorFox: the tracker and workspace settings you choose, the features you turn on, and the requests you make in the application or by email, such as erasure requests. You may give further instructions during the processing.
  2. We inform you immediately if, in our opinion, an instruction infringes the GDPR or other EU or Member State data protection law.

7.2 Purpose limitation

We process the personal data only for the purposes in Annex 1, unless you give further instructions. Aggregated, anonymous data about how the service is used, as section 10 of the terms describes, is not personal data and is not covered by this DPA.

7.3 Duration of the processing

Processing takes place only for the duration set out in Annex 1.

7.4 Security of processing

  1. We implement at least the technical and organisational measures in Annex 2 to ensure the security of the personal data. This includes protecting the data against a breach of security that leads to accidental or unlawful destruction, loss, alteration, unauthorised disclosure of or access to the data. In assessing the appropriate level of security, we take into account the state of the art, the costs of implementation, the nature, scope, context and purposes of the processing, and the risks for the data subjects.
  2. We give our staff access to the personal data only to the extent strictly necessary for carrying out, managing and monitoring the agreement. Everyone authorised to process the personal data has committed themselves to confidentiality or is under an appropriate statutory obligation of confidentiality.

7.5 Sensitive data

SpoorFox is not intended for special categories of personal data (Article 9 GDPR) or data about criminal convictions and offences (Article 10 GDPR). You do not send such data to SpoorFox on purpose. On pages that may show such data, you use masking, blocking or excluded paths so that it is not recorded. If such data still reaches SpoorFox, the measures in Annex 2 apply to it, and you can remove it with the erasure tool.

7.6 Documentation and compliance

  1. Both parties must be able to demonstrate compliance with this DPA.
  2. We deal promptly and adequately with your questions about the processing under this DPA.
  3. We make available to you all information necessary to demonstrate compliance with the obligations in this DPA and in Article 28 GDPR. At your request, we also allow for and contribute to audits of the processing at reasonable intervals, or when there are indications of non-compliance. In deciding on an audit, you may take into account relevant certifications we hold.
  4. You may carry out the audit yourself or mandate an independent auditor who is bound by confidentiality. Audits may include inspections at our premises or physical facilities where appropriate. You give at least 30 days notice, except after a personal data breach or when a supervisory authority requires a shorter period. Audits take place during Dutch business hours, no more than once in any 12 months unless there are indications of non-compliance, and at your cost unless the audit reveals a material breach of this DPA by us.
  5. We make the information in this clause, including the results of any audits, available to the competent supervisory authority on request.

7.7 Use of subprocessors

  1. You give us general written authorisation to engage the subprocessors in Annex 3. We inform you in writing of any intended addition or replacement of a subprocessor at least 30 days in advance, by email to the account owners of your SpoorFox environment, in SpoorFox and on our subprocessors page, so that you can object before the change applies.
  2. You may object to the change on reasonable grounds relating to data protection, by email to [email protected] within those 30 days. We then look for a solution in good faith. If we cannot agree on one, you may cancel the affected subscription with effect from the date the change applies. We then refund prepaid fees for the period after that date.
  3. When we engage a subprocessor to carry out processing on your behalf, we do so by a contract that imposes on the subprocessor, in substance, the same data protection obligations as this DPA imposes on us. We ensure that the subprocessor complies with the obligations we are subject to under this DPA and the GDPR.
  4. At your request, we provide a copy of such a subprocessor agreement and of later changes to it. To the extent necessary to protect business secrets or other confidential information, including personal data, we may redact the text before sharing it.
  5. We remain fully responsible to you for the performance of the subprocessor’s obligations under its contract with us. We notify you if a subprocessor fails to fulfil its contractual obligations.

7.8 International transfers

  1. Customer environments, their databases and their backups are stored in the European Union (Microsoft Azure, West Europe). We transfer personal data to a third country or an international organisation only on your documented instructions or to fulfil a specific requirement under EU or Member State law, and in compliance with Chapter V of the GDPR.
  2. You agree that where we engage a subprocessor under Clause 7.7 for processing in a third country, the transfer is covered by an adequacy decision of the European Commission, in particular the EU-US Data Privacy Framework (Implementing Decision (EU) 2023/1795) where the subprocessor is certified under it. Where it is not, the transfer is covered by the standard contractual clauses adopted by the Commission in Implementing Decision (EU) 2021/914 (Module 3, processor to processor), with supplementary measures where necessary. Today this applies to Twilio SendGrid and Anthropic in the United States, and to Stripe and Cloudflare where they process data outside the European Economic Area. Annex 3 shows the basis for each subprocessor.

Clause 8. Assistance to the controller

  1. We notify you promptly of any request we receive directly from a data subject. We do not respond to the request ourselves, unless you have authorised us to do so.
  2. We assist you in responding to data subjects’ requests to exercise their rights, taking into account the nature of the processing. SpoorFox gives you tools for this: you can look up a visitor or contact and the events, sessions and recordings linked to them, and you can erase all data about a person across a workspace by email address, phone number or visitor id.
  3. Taking into account the nature of the processing and the information available to us, we also assist you in ensuring compliance with:
    1. the obligation to carry out a data protection impact assessment where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons;
    2. the obligation to consult the competent supervisory authority before processing where the impact assessment indicates a high risk that you cannot mitigate;
    3. the obligation to keep personal data accurate and up to date, by informing you without delay if we become aware that personal data we process is inaccurate or has become outdated;
    4. the obligations in Article 32 GDPR.
  4. The technical and organisational measures that help us assist you are set out in Annex 2.

Clause 9. Notification of personal data breaches

In the event of a personal data breach, we cooperate with and assist you so that you can comply with Articles 33 and 34 GDPR, taking into account the nature of the processing and the information available to us.

9.1 A breach concerning data you process yourself

We assist you:

  1. in notifying the competent supervisory authority without undue delay after you became aware of the breach, where relevant, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons;
  2. in obtaining the information that Article 33(3) GDPR requires in your notification;
  3. in complying with Article 34 GDPR, communicating the breach to the data subjects without undue delay where it is likely to result in a high risk to their rights and freedoms.

9.2 A breach concerning data we process

If a personal data breach concerns personal data we process on your behalf, we notify you without undue delay, and in any case within 48 hours after we become aware of it, by email to the account owners of your SpoorFox environment. The notification contains at least:

  1. a description of the nature of the breach, including, where possible, the categories and approximate number of data subjects and of personal data records concerned;
  2. the details of a contact point where more information about the breach can be obtained;
  3. its likely consequences, and the measures taken or proposed to address the breach, including measures to mitigate its possible adverse effects.

Where it is not possible to provide all this information at the same time, the first notification contains the information then available, and further information follows without undue delay as it becomes available.

Section III: Final provisions

Clause 10. Non-compliance and termination

  1. If we breach our obligations under this DPA, you may instruct us to suspend the processing of personal data until we comply with this DPA or the agreement is ended. We inform you promptly if we are unable to comply with this DPA, for whatever reason.
  2. You may end the agreement insofar as it concerns the processing of personal data under this DPA if:
    1. you suspended the processing under paragraph (a) and compliance is not restored within a reasonable time, and in any event within one month;
    2. we are in substantial or persistent breach of this DPA or of our obligations under Article 28(3) GDPR;
    3. we fail to comply with a binding decision of a competent court or supervisory authority about our obligations under this DPA or the GDPR.
  3. We may end the agreement insofar as it concerns the processing of personal data under this DPA if, after we informed you that an instruction infringes the law under Clause 7.1(b), you insist on compliance with that instruction.
  4. When the subscription ends, you can export your data until the end date. After the end date we delete your SpoorFox environment and all personal data in it, and confirm the deletion to you on request. A final backup is kept for 90 days, so that we can restore the environment at your request, and is then deleted. This does not apply where EU or Member State law requires us to keep the data. Until the data is deleted, we continue to ensure compliance with this DPA.

Clause 11. Liability, governing law and disputes

The liability of the parties under this DPA is subject to section 16 of the terms of service, to the extent the GDPR and other applicable law allow. This DPA is governed by Dutch law, and disputes are submitted to the court named in section 20 of the terms.

Annex 1: Parties and description of the processing

A. Parties

Controller. The customer named in the order or at checkout, at the address in its billing details. Contact: the account owners of its SpoorFox environment. Role: controller.

Where the customer uses SpoorFox for its own clients, for example in client workspaces, the client is the controller for that workspace and the customer is its processor. This DPA then applies between the customer and us as an agreement with a subprocessor, and the customer makes sure that its agreement with its client allows this.

Processor. SpoorFox B.V. in formation, Buitenom 251, 2711 KB Zoetermeer, the Netherlands. Contact for data protection: [email protected]. Role: processor.

Signature and date. Agreed electronically on the date the customer accepts the terms of service, as described in Clause 2.

B. Categories of data subjects

  • Visitors of the controller’s websites, landing pages and apps where the controller installs the SpoorFox tracker.
  • People who fill in forms, answer surveys or send feedback on those websites, and the leads and contacts identified from them.
  • Recipients of the controller’s email: subscribers, contacts and leads to whom the controller sends campaigns, automated journeys and transactional email through SpoorFox, and people who sign up through its SpoorFox forms and landing pages.
  • Prospects the controller’s users contact through SpoorFox outreach, and the people they correspond with there.
  • The controller’s own users of SpoorFox, such as its employees and the agency staff it invites.

C. Categories of personal data

  • Identifiers. A random visitor id (cookie and local storage _rv_id) and a session id (_rv_s). In cookieless mode nothing is stored in the browser; the server derives a visitor id that changes daily from a salted hash of the IP address and the browser’s user agent. Advertising click ids in landing URLs (such as gclid and fbclid) and the Meta browser and click ids (_fbp, _fbc).
  • IP address and device. The IP address is used to derive the country, to filter bots and excluded addresses, to limit request rates and, where company lookup is enabled, to look up the visiting company. It is stored only as a salted hash, unless the controller turns off IP anonymization. Device type, browser, operating system, screen size, language and time zone.
  • Page and click behaviour. Pages viewed (address, title and referrer), the campaign parameters of the landing page, clicks on links and buttons (with up to 80 characters of their text), scroll depth, engaged time, form submits (with the field names), click and movement positions for heatmaps, frustration signals such as rage and dead clicks, JavaScript errors, and the goals and custom events the controller sends.
  • Session recordings. For sessions the controller chooses to record, by sample or by rule: a recording of the page as the visitor saw it and the changes to it. Every input, select and text area is masked in the browser before anything is sent, and passwords are never recorded. Email addresses and numbers of 9 or more digits are masked in all page text. The controller can mask or block more elements, or mask all page text.
  • Email addresses and phone numbers from forms. When a visitor submits a form, the values of email, phone and name fields. When the controller enables field capture, email addresses and phone numbers as they are typed into a field. Email addresses the controller passes with the identify command or in a link. In privacy mode, email addresses and phone numbers are hashed in the browser before they are sent, and only the email domain is sent in clear text. In stored events, email addresses and phone numbers are replaced by hashes; the contact record of an identified person holds the email address and name.
  • Survey answers and feedback that visitors give through SpoorFox surveys and the feedback widget.
  • Email. Email address, name and the contact properties the controller uses in emails and segments; list and segment membership; each recipient’s subscription status with its consent evidence (the status, legal basis, source such as a form, import or double opt-in, the consent wording, the time, and a daily rotating hash of the IP address; the IP address itself is not stored), unsubscribes and preferences; suppressed addresses, kept only as a hash once the person is erased, so that they are never mailed again; the emails sent; and delivery and engagement events (delivered, bounced, opened, clicked, unsubscribed, marked as spam). For transactional email, the data the controller’s application passes in each message.
  • Outreach. Prospects’ name, job title, company, email address and LinkedIn profile address, the profile details a user imports, the connection state, and the tasks, LinkedIn messages, emails, replies and notes exchanged with them.
  • Customer user accounts. Name, business email address, role and permissions, sign-in data (single sign-on identity, or a password hash and two factor authentication settings), and the audit log of the user’s actions. For outreach, the mailboxes a user connects, with their sign-in secrets stored encrypted, and the user’s LinkedIn profile address.

D. Sensitive data

None intended. See Clause 7.5.

E. Nature of the processing

Collection through the SpoorFox tracker and the application, storage, structuring, analysis and combination into visitor, session, contact and account profiles, display and reporting in the application, AI analysis when the controller uses AI features, transmission to the controller’s connected platforms when the controller instructs it, sending email on the controller’s instructions (through our email provider, or through the email provider account or mailbox the controller connects) and receiving the replies, bounces and delivery events, and erasure.

F. Purposes

To provide SpoorFox to the controller under the agreement: website and behaviour analytics, heatmaps and session replay, surveys, attribution of leads and revenue to channels and campaigns, identification of leads and the companies they work for, email marketing and transactional email, sales outreach, reporting, AI assistance, and the security, support and billing of the service.

G. Duration and retention

For the duration of the subscription. During the subscription, data is kept according to the retention settings the controller chooses, and data about a person is removed when the controller erases it, except the hash of a suppressed email address, which is kept so that the address is never mailed again. After the subscription ends, the data is deleted as described in Clause 10(d), with a final backup kept for 90 days.

H. Processing by subprocessors

The subject matter, nature and duration of the processing by each subprocessor are set out in Annex 3.

Annex 2: Technical and organisational measures

These measures are described in more detail on the security and hosting page.

Isolation and hosting

  • Each customer runs its own SpoorFox application containers and its own database, on its own address. No shared application holds several customers’ data.
  • Customer environments run in Microsoft Azure, region West Europe (the Netherlands).
  • Traffic reaches customer environments only through Cloudflare, with TLS end to end. Data is encrypted in transit and at rest.

Access control

  • Users sign in with single sign-on through OpenID Connect (Entra ID, Google or Okta), or with a password and mandatory two factor authentication.
  • Access within an environment is limited by permissions per workspace.
  • Our staff access personal data only to the extent strictly necessary, under a duty of confidentiality (Clause 7.4).

Availability and backups

  • Each customer database is dumped every hour to immutable storage.
  • Restores are tested to prove that the backups work.

Privacy by default in the tracker

  • Session replay masks every input, select and text area in the browser, never records passwords, and masks email addresses and long numbers in page text. These defaults cannot be switched off.
  • A cookieless mode, a consent mode that holds all measurement until the visitor consents, and an option to respect Do Not Track and Global Privacy Control.
  • A privacy mode that hashes email addresses and phone numbers in the browser.
  • IP addresses are stored as salted hashes. Email addresses and phone numbers in stored events are replaced by hashes, and email and phone parameters are removed from stored page addresses.
  • Bots are filtered out, and the controller can exclude IP addresses and paths from collection.
  • The collection endpoint accepts data only from the domains configured for the workspace, and limits request size and rate.

Accountability

  • Sign-ins, settings, approvals and every change to an ad account are recorded in an audit log per workspace.
  • Nothing the AI agent or a rule proposes reaches an ad platform until a person approves it, and every change is read back after execution.
  • Customer data sent to our AI provider is not used to train AI models.

Data subject requests

  • An erasure tool removes a person’s events, recordings and identity data across the workspace, by email address, phone number or visitor id.

Annex 3: Subprocessors

You authorise the subprocessors below (Clause 7.7). We announce changes to this list at least 30 days before they apply. The same list is on our subprocessors page, with its history, and in our privacy policy.

SubprocessorPurposeLocationTransfer basis
Microsoft AzureHosting of customer environments, databases and backupsEU (West Europe)Stored in the EU
CloudflareNetwork delivery, TLS and protection against attacksGlobal network, EU originEU-US Data Privacy Framework, or standard contractual clauses
StripeSubscription billing and paymentsEU and USEU-US Data Privacy Framework, or standard contractual clauses
Twilio SendGridEmail: service messages such as invitations and password resets, messages from the website contact form, and the campaigns, journeys and transactional email customers send through SpoorFox Email (not when a customer uses its own SendGrid account)USEU-US Data Privacy Framework, or standard contractual clauses
AnthropicAI agent answers, only when a customer uses AI features; not used to train modelsUSEU-US Data Privacy Framework, or standard contractual clauses

Contact

Questions about this DPA or about how we process personal data: [email protected]. Company details are on the company details page.