Data processing agreement
This agreement sets the terms on which MASDE Agency processes personal data about visitors to its customers' websites when providing Spurn.
1. About this agreement#
This data processing agreement ("DPA") is between you, the customer that holds a Spurn account ("Customer"), and MASDE Agency of Cape Town, South Africa, which runs Spurn ("Spurn"). It forms part of our terms of service ("Terms") and applies automatically when you accept them. No signature is needed. For a countersigned copy, email legal@spurn.io.
On data protection, this DPA prevails over the Terms, and the Standard Contractual Clauses, where they apply, prevail over this DPA.
2. Definitions#
- Data protection law: every law on personal data that applies to processing under this DPA, including the EU GDPR, the UK GDPR, the Swiss Federal Act on Data Protection (FADP) and South Africa's Protection of Personal Information Act (POPIA).
- Customer personal data: personal data Spurn processes for the Customer through the service, as described in Annex I.
- Controller, processor, data subject, personal data and processing have their GDPR meanings. Under POPIA, a controller is a "responsible party" and a processor an "operator".
- Subprocessor: a third party Spurn engages to process Customer personal data.
- Security incident: a breach of security leading to the accidental or unlawful destruction, loss, alteration or unauthorised disclosure of, or access to, Customer personal data.
- SCCs: the standard contractual clauses approved by Commission Implementing Decision (EU) 2021/914.
3. Roles#
The Customer is the controller of Customer personal data, or a processor acting for its own clients, such as an agency. Spurn is the Customer's processor, or subprocessor. Where the Customer acts for a client, it confirms the client has authorised these instructions and this DPA, and the Customer remains our single point of contact.
Spurn is a controller in its own right for account, billing and support data, as our privacy policy describes. This DPA does not cover that data.
Ad platforms the Customer connects, such as Google, Microsoft and Meta, receive data under their own terms with the Customer. They are not Spurn's subprocessors.
4. Subject matter, duration, nature and purpose#
- Subject matter: detecting invalid clicks on the Customer's paid ads and keeping invalid traffic away from those ads.
- Duration: for as long as the Terms apply, and until Customer personal data is deleted under section 11.
- Nature: collection, storage, analysis, scoring, reporting, transmission to the Customer's ad platforms on the Customer's instruction, and deletion.
- Purpose: to detect invalid and fraudulent clicks, report on them, block the networks and audiences behind them in the Customer's ad accounts, and build evidence for refund claims.
5. Customer instructions and obligations#
The Terms, the Customer's settings and its use of the dashboard and API are its complete documented instructions. Other instructions must be in writing and consistent with the service.
The Customer must:
- have a lawful basis for the processing. For most customers this is the legitimate interest in preventing fraud and wasted ad spend under GDPR Article 6(1)(f), which Recital 47 recognises, and POPIA section 11(1)(f);
- tell its visitors about Spurn in its privacy notice. A sample it may use: "We use Spurn, a click-fraud protection service run by MASDE Agency, to detect fraudulent and invalid clicks on our paid ads. When you arrive from one of our ads, Spurn processes your IP address, browser and device details and how you use the page, and may share details of flagged visits with our ad platforms, based on our legitimate interest in preventing ad fraud.";
- decide whether ePrivacy or similar rules require visitor consent for the tag's browser storage, and configure Spurn to match, for example by loading the tag through its consent tool or using a server integration alone;
- not send special category data, data about children, or names, email addresses or other personal details in landing page URLs or UTM tags;
- make sure its instructions comply with data protection law.
6. Spurn's obligations#
Spurn will:
- process Customer personal data only on the Customer's documented instructions, unless the law requires otherwise, and tell the Customer first unless the law forbids it;
- tell the Customer if it believes an instruction breaks data protection law;
- make sure everyone authorised to process Customer personal data is bound by confidentiality;
- apply the measures in Annex II;
- not sell Customer personal data, use it for its own purposes or combine it with other customers' data to profile individuals, except to compile aggregated statistics that identify no person, customer or site, as the Terms allow;
- help the Customer with data protection impact assessments and prior consultations, as far as the nature of the processing and the information available to Spurn allow;
- keep a record of its processing activities.
7. Data subject requests#
Spurn will pass any data subject request about Customer personal data to the Customer without undue delay, and will only answer it to say it has done so. Where the Customer cannot fulfil a request through the dashboard or API, Spurn will help, for example by finding, exporting or deleting a visitor's clicks by IP address or click id.
8. Subprocessors#
The Customer gives general authorisation for Spurn to use the subprocessors listed on our subprocessors page. Spurn has a written contract with each one that protects Customer personal data at least as well as this DPA, and Spurn remains liable for their work.
Before a new subprocessor starts processing Customer personal data, Spurn will update that page and email account owners at least 14 days in advance. The Customer may object on reasonable data protection grounds by emailing legal@spurn.io within those 14 days. We will discuss the objection in good faith and may offer an alternative. If we cannot resolve it, the Customer may end the affected service by written notice before the change takes effect, and we will refund any prepaid fees for the period after it ends.
If Spurn must replace a subprocessor urgently to protect the service or Customer personal data, it will give notice as soon as it can, and the right to object runs from that notice.
9. Security incidents#
Spurn will notify the Customer without undue delay, and in any case within 72 hours, after becoming aware of a security incident. The notice will describe, as far as known, the nature of the incident, the categories and approximate number of data subjects and records concerned, its likely consequences, the steps taken or proposed, and a contact point. Information may follow in stages.
Spurn will contain and investigate the incident and help the Customer notify authorities and data subjects where it must. A notice is not an admission of fault.
10. Audits#
Spurn will make available the information needed to show it meets this DPA, starting with documentation: this DPA and its annexes, the subprocessor list and answers to a reasonable security questionnaire once a year.
If that is not enough, or a supervisory authority requires it, the Customer may audit Spurn on site on at least 30 days' written notice, no more than once in 12 months unless after a security incident. Audits take place in business hours, at the Customer's cost and under confidentiality, by the Customer or an independent auditor who is not a competitor of Spurn. They may not expose other customers' data or weaken security. Subprocessors' facilities are covered by their own audit reports.
11. Deletion and return#
While the Terms apply, click data is deleted when the plan's retention period ends (Annex I). Before an account closes, the Customer may ask for an export of its click data. Spurn deletes Customer personal data within 30 days after the account closes, and backups that contain it roll off within a further 30 days. Anything the law requires Spurn to keep is protected and used only for that purpose. Spurn will confirm deletion in writing on request.
12. International transfers#
EEA. Where Customer personal data is transferred from the EEA to Spurn in South Africa, the SCCs are incorporated into this DPA by reference: Module 2 where the Customer is a controller and Module 3 where it is a processor. The Customer is the data exporter and Spurn the data importer. Clause 7 (docking) applies. Under Clause 9(a), Option 2 applies with 14 days' notice. The optional wording in Clause 11(a) does not apply. The supervisory authority under Clause 13 is the one that clause points to for the Customer. Under Clauses 17 and 18, the SCCs are governed by Irish law and disputes go to the courts of Ireland. Annexes I to III of the SCCs are completed by Annexes I to III of this DPA.
UK. For transfers from the UK, the Information Commissioner's International Data Transfer Addendum to the SCCs (version B1.0) is incorporated. Annex I completes its Table 1, the modules and options above its Table 2, and this DPA's annexes its Table 3. Either party may end it as its Section 19 allows.
Switzerland. For transfers from Switzerland, the SCCs apply with the changes the FADP requires: the Federal Data Protection and Information Commissioner is the competent authority, references to the GDPR include the FADP, and data subjects in Switzerland may sue where they usually live.
South Africa. Under POPIA section 72, Spurn only transfers personal information outside South Africa to recipients bound by a law, binding corporate rules or a binding agreement giving adequate protection, or where another ground in that section applies. Customer personal data is hosted in the EU under the GDPR.
Onward transfers. Transfers to subprocessors outside the EEA and UK rely on an adequacy decision, including the EU-US Data Privacy Framework where the recipient is certified, or on the SCCs.
13. Liability#
Each party's liability under this DPA is subject to the limits in the Terms, except where the SCCs or data protection law do not allow those limits.
14. Changes#
We may update this DPA to reflect changes in the law or the service, with notice as the Terms describe. No change will lower the protection given to Customer personal data.
15. Annex I: description of the processing#
Parties#
- Data exporter: the Customer, as named in its Spurn account. Contact: the account owner's email address. Role: controller, or processor for its clients.
- Data importer: MASDE Agency, Cape Town, South Africa. Contact: legal@spurn.io. Role: processor, or subprocessor.
Each party signs by accepting the Terms, on the date of acceptance.
Data subjects#
- People who arrive on the Customer's websites from a paid ad, for the rest of that paid session.
- People who click the Customer's ads, as recorded by the tracking template or in the Customer's Google Ads click data.
- People who buy after such a landing, through order details only.
Personal data#
- Network: IP address, and the country and network derived from it locally.
- Browser and device: user agent, time zone, language, screen and hardware characteristics, a device fingerprint hash, and automation and consistency signals.
- Landing: landing URL, referrer, ad click id, UTM tags and campaign parameters.
- Engagement: time on page, scroll depth, pointer, touch and keyboard interaction counts, and pages viewed.
- Identifiers: random pageview and visitor ids, and Meta
_fbpand_fbcvalues when present. - Conversions: order id, value and currency.
Organic visits are not collected. No special category data is processed, and the Customer must not send any.
Frequency, nature and purpose#
Continuous, for every paid-ad landing on the Customer's sites. Nature and purpose are set out in section 4.
Retention#
Click data is kept for the plan's retention period: Free 30 days, Starter 90, Growth 180, Pro 365 and Agency 730. Lifetime tiers: tier 1 180 days, tiers 2 and 3 365 days, tiers 4 and 5 730 days. Exclusions stay until the Customer removes them, Spurn rotates them out or the site is deleted. Deletion on closure follows section 11.
Transfers to subprocessors#
As listed in Annex III, for the same subject matter, nature and duration.
Competent supervisory authority#
As determined under Clause 13 of the SCCs. For POPIA, the Information Regulator of South Africa.
16. Annex II: technical and organisational measures#
- Encryption in transit: TLS on every public endpoint, with HTTPS enforced and TLS 1.2 as the minimum.
- Encryption at rest: ad platform OAuth tokens, Shopify tokens and alert webhook URLs are encrypted with AES-256-GCM, with the key held outside the database. Backups are encrypted.
- Network: all traffic passes through Cloudflare. The application server has no public listener and is reached only through an outbound tunnel.
- Access control: staff access to production data is limited to people who need it, on a least-privilege basis, with individual credentials.
- Customer isolation: every query is scoped to the workspace, and workspace roles limit what each member can see and change.
- Authentication: passwords are stored only as hashes, email addresses are verified, sign-in attempts are rate limited and sessions expire after 30 days without use.
- Data minimisation: organic visits are never collected, location is derived to country level only, and error monitoring is configured not to collect IP addresses, cookies, request bodies, query strings or email addresses.
- Retention: click data is deleted when the plan's retention period ends, and backups roll off within 30 days.
- Logging: an audit log records workspace changes, and every exclusion Spurn adds or removes is recorded.
- Incident response: incidents are investigated and notified as section 9 sets out. Vulnerabilities can be reported to security@spurn.io.
More detail is on our security page.
17. Annex III: subprocessors#
The current list is on our subprocessors page, which forms part of this DPA. Changes follow section 8.