Privacy policy
This policy explains what personal data MASDE Agency handles to run Spurn, why it does so, and the rights you have over that data.
1. Who we are#
Spurn is a click-fraud protection service at spurn.io, run by MASDE Agency of Cape Town, South Africa ("Spurn", "we", "us"). For questions about this policy or your data, email legal@spurn.io. Our information officer under South Africa's Protection of Personal Information Act (POPIA) can be reached at the same address.
2. Our two roles#
We handle personal data in two roles.
- As a controller (a "responsible party" under POPIA), we decide how data about our own customers and website visitors is used: account, billing and support data, and visits to spurn.io. Sections 3 and 4 cover this data.
- As a processor (an "operator" under POPIA), we handle data about visitors to our customers' websites, collected by the Spurn tag, apps, plugins and server integrations. The customer who runs the website is the controller of that data, and our data processing agreement governs how we handle it. Sections 5 and 6 describe it so visitors know what happens.
If you visited a website that uses Spurn and have a question about your data, see section 13.
3. Data we collect as a controller#
| Category | What it includes | Source |
|---|---|---|
| Account | Name, email address, password (stored only as a hash), profile picture if you sign in with Google or GitHub, time zone, your workspaces and your role in each | You, or Google or GitHub when you sign in with them |
| Sessions and security | IP address and browser details of your signed-in sessions, and an audit log of changes made in your workspace | Your use of the dashboard |
| Workspace | Site names and domains, settings and rules, allowlists, API key records, alert destinations such as Slack or webhook URLs | You |
| Ad connections | Name or email of the person who granted access on the ad platform, ad account names and ids, encrypted access tokens, campaign and cost data | Google, Microsoft and Meta, when you connect them |
| Shopify | Your shop's domain, name, contact email, currency and time zone, and encrypted access tokens | Shopify, when you install the app |
| Billing | Billing name, email and address, tax id, plan and invoices. Stripe holds your card details; we never see the full card number | You and Stripe |
| Lifetime licences | Licence key, tier and status | AppSumo |
| Support | Messages, files and contact details you send by email or chat | You |
| How you found us | Campaign tags, ad click id, landing page and referring site from the spurn_touch cookie, saved to your account when you sign up | Your browser |
| Website visits | IP address, browser details and the pages requested on spurn.io | Your browser, through Cloudflare and our servers |
We do not use advertising cookies or third-party analytics on spurn.io. Our cookie policy lists everything we store in your browser.
4. How we use it and our lawful bases#
| Purpose | GDPR and UK GDPR | POPIA |
|---|---|---|
| Create and run your account and workspaces, connect your ad accounts and provide the service | Contract (Art. 6(1)(b)); legitimate interests for team members a customer invites (Art. 6(1)(f)) | s 11(1)(b) and (f) |
| Take payments, issue invoices and keep tax records | Contract and legal obligation (Art. 6(1)(b) and (c)) | s 11(1)(b) and (c) |
| Send service emails: sign-in links, alerts, weekly digests and billing notices | Contract (Art. 6(1)(b)) | s 11(1)(b) |
| Answer support requests | Contract or legitimate interests (Art. 6(1)(b) or (f)) | s 11(1)(b) or (f) |
| Keep Spurn secure, prevent abuse and fix errors | Legitimate interests (Art. 6(1)(f)) | s 11(1)(f) |
| Learn which of our own campaigns bring signups | Legitimate interests (Art. 6(1)(f)) | s 11(1)(f) |
| Improve Spurn using aggregated usage statistics | Legitimate interests (Art. 6(1)(f)) | s 11(1)(f) |
| Send news about Spurn | Consent, or our legitimate interests for existing customers, with an opt-out in every message | s 69 |
| Comply with the law and deal with legal claims | Legal obligation and legitimate interests (Art. 6(1)(c) and (f)) | s 11(1)(c) and (f) |
Where we rely on legitimate interests, our interests are running a secure, working service and understanding our own marketing. We have weighed them against your rights, and you can object at any time (section 12).
5. Data we process for our customers#
When Spurn runs#
Spurn only looks at visits that come from a paid ad: a landing whose URL carries an ad click id or paid UTM tags, and the later pages of that same paid session. Click ids include gclid, gbraid, wbraid and gad_source (Google), msclkid (Microsoft), fbclid together with Meta's paid parameters, ttclid (TikTok), li_fat_id (LinkedIn), twclid (X), epik (Pinterest), ScCid (Snapchat) and rdt_cid (Reddit). Paid UTM tags are a utm_medium such as cpc, ppc, paid_social or display.
On every other visit the tag does nothing and nothing is sent to us. Organic visits are never stored.
What is collected#
| Category | Details |
|---|---|
| Network | IP address |
| Browser and device | User agent, time zone, language, screen and hardware characteristics, a device fingerprint hash built from them, and signals showing whether automation software is driving the browser or whether the device's signals contradict each other |
| Landing | Landing URL, referrer, ad click id, UTM tags and campaign parameters such as campaign, ad group, keyword, network and placement |
| Engagement | Time on page, scroll depth, counts of pointer, touch and keyboard interactions, and pages viewed in the paid session |
| Identifiers | A random pageview id, a random visitor id, and Meta's _fbp and _fbc values when present |
| Conversions | Order id, order value and currency |
| From the ad platform | Google Ads click records (click_view) imported from the customer's own account |
From the IP address we derive the country and the network (its ASN and owner, and whether it belongs to a hosting provider, VPN or Tor) using databases stored on our own servers. No lookup leaves our servers. We do not derive a city or street-level location. IP address data powered by IPinfo. VPN data from IPLocate.io.
We do not collect the names, email addresses, postal addresses or payment details of shoppers.
Server integrations (the WordPress and WooCommerce plugin, the Next.js package, the Cloudflare Worker and custom server calls) and the tracking template send the IP address, user agent, URL, referrer, language and time, for paid landings only.
What is stored on visitors' devices#
| Name | Type | Contents | Lasts |
|---|---|---|---|
_spc | First-party cookie, SameSite=Lax | Pageview id and ad click id, so an order can be matched to the click | 30 days |
_sp_v | localStorage | Random visitor id | Until cleared |
_sp_s | sessionStorage | Marks the paid session | Ends after 30 minutes without activity or when the tab closes |
This storage is used only for fraud prevention. Some laws, such as the EU and UK ePrivacy rules, may still require consent for it. The website owner decides whether its visitors must consent and sets Spurn up to match, for example by loading the tag through its consent tool or using a server integration alone, which stores nothing on the device.
Why it is processed#
The data is used to detect invalid clicks, such as bots, click farms, competitors and repeated or accidental clicks, and to keep fraudulent and invalid traffic away from the customer's ads. Spurn scores each paid click, records the reasons, reports to the customer and builds evidence for refund claims. It also passes the verdict back to the page, so the site's own tags can stop remarketing to bots or counting them as conversions.
The lawful basis is the customer's legitimate interest in preventing fraud and wasted ad spend: GDPR Article 6(1)(f), with Recital 47 naming fraud prevention as a legitimate interest, and POPIA section 11(1)(f). Customers must tell their visitors about Spurn in their own privacy notice.
6. What we send to ad platforms#
When a customer connects its ad accounts and turns blocking on, Spurn sends the following on the customer's instruction:
- Google Ads: IP addresses and /24 ranges behind invalid clicks, as IP exclusions, and placement exclusions for websites and apps that sent invalid clicks.
- Meta Ads: Conversions API custom events named
InvalidTraffic, with the IP address, user agent and_fbpand_fbcvalues of flagged visitors, used to build an exclusion audience. Where the customer's Meta pixel is on the page, the tag also sends aSpurnInvalidTrafficevent through it. - Microsoft Ads: a UET custom event named
spurn_invalid, fired in the flagged visitor's browser through the customer's own UET tag and used to build an exclusion audience.
Spurn also imports click_view data from the customer's Google Ads account. These platforms act under their own terms with the customer, not as our subprocessors.
7. Automated decisions#
Spurn scores clicks automatically. A verdict only decides whether a customer's ads keep being shown to a network, device or audience. It does not stop anyone visiting a website, buying anything or using a service, so it has no legal or similarly significant effect under GDPR Article 22 or POPIA section 71. Customers can review every verdict and its reasons, change their rules and undo exclusions.
8. Who we share data with#
- Subprocessors that host, deliver and support Spurn, listed with their locations on our subprocessors page. Each is bound by a written contract.
- Ad platforms, on our customers' instructions, as section 6 describes.
- Independent services you choose: Google or GitHub when you sign in with them, Shopify when you install our app, and AppSumo, which shares licence details for lifetime buyers.
- Professional advisers, such as lawyers and accountants, under a duty of confidentiality.
- Authorities, when the law requires it.
- A buyer or successor of the Spurn business, who must keep to this policy.
We do not sell personal data.
9. International transfers#
MASDE Agency is in South Africa. Our servers and database are in Helsinki, Finland, in the EU. Our staff in South Africa access data to run the service, and some subprocessors are in the US or operate worldwide.
- From the EEA, UK and Switzerland: South Africa has no EU adequacy decision, so transfers to us rely on the Standard Contractual Clauses and, for the UK, the UK Addendum. For customer data these are part of our DPA. Transfers to subprocessors rely on an adequacy decision, including the EU-US Data Privacy Framework where the recipient is certified, or on the Standard Contractual Clauses.
- From South Africa: under POPIA section 72, we only transfer personal information to recipients bound by a law, binding corporate rules or a binding agreement that gives adequate protection, or where another ground in that section applies. Data hosted in the EU is protected by the GDPR.
Ask legal@spurn.io for a copy of the safeguards we use.
10. How long we keep data#
| Data | How long |
|---|---|
| Click data about visitors | The plan's retention period, then deleted: Free 30 days, Starter 90, Growth 180, Pro 365, Agency 730. Lifetime tiers: tier 1 180 days, tiers 2 and 3 365 days, tiers 4 and 5 730 days |
| Exclusions | Until the customer removes them, Spurn rotates them out to make room, or the site is deleted |
| Daily totals with no personal data | For as long as the site exists |
| Account, workspace and support data | While the account exists, then up to 90 days to deal with questions and disputes |
| Billing records | 5 years, as South African tax law requires |
| Backups | Roll off within 30 days |
When a customer closes its account, visitor data is deleted within 30 days.
11. Security#
All traffic to Spurn is encrypted with TLS. Ad platform OAuth tokens are encrypted at rest with AES-256-GCM. Access to data is limited to staff who need it, on a least-privilege basis, and backups are encrypted. Our security page has more detail. To report a vulnerability, email security@spurn.io.
12. Your rights#
Depending on where you live, the GDPR, the UK GDPR or POPIA give you the right to:
- access the personal data we hold about you and get a copy;
- correct data that is wrong or incomplete;
- have data deleted;
- restrict or object to processing, including processing based on legitimate interests;
- receive data you gave us in a portable format;
- withdraw consent at any time, where we rely on it;
- refuse direct marketing;
- complain to a supervisory authority.
To use these rights, email legal@spurn.io. We reply within one month, and may ask you to confirm your identity first. There is no charge.
You can complain to the Information Regulator in South Africa, the Information Commissioner's Office in the UK, or your local supervisory authority in the EU. We would like the chance to resolve your concern first.
13. If you visited a site that uses Spurn#
The website you visited controls the data Spurn collected about your visit. Contact its owner to use your rights, and we help them find, export or delete the data. If you contact us instead, we pass your request to the website owner and tell you we have done so.
14. Children#
Spurn is for businesses and is not meant for anyone under 18. We do not knowingly collect personal data from children.
15. Changes to this policy#
When we make a material change, we update this page and email account owners before it takes effect.
16. Contact#
MASDE Agency, Cape Town, South Africa. Email legal@spurn.io for privacy questions, or use our contact page.