Data processing agreement
Between the Customer (controller), who accepts this DPA by using Countnest, and IDCPH ApS, CVR 40009175, Lindgreens Allé 7A, 2300 København S, Denmark, operating Countnest (processor).
1. Subject matter and duration
The processor provides website analytics to the controller under the Countnest Terms of Service. This DPA applies for as long as the processor processes personal data on the controller's behalf, and ends when all such data has been deleted or returned (section 9).
2. Nature and purpose
Collecting, storing, aggregating and displaying website usage statistics for the controller's own websites, including traffic sources, AI-referral classification, AI crawler logs, custom events and e-commerce events, and imported search-console data.
3. Categories of data subjects and data
Data subjects: visitors to the controller's websites.
Data processed:
- Transiently, in memory only, never stored: IP address and full user-agent string, used to compute the visitor hash and to filter bots. Country, region and city are derived from IP geolocation headers set by our hosting/CDN provider.
- Stored: a pseudonymous visitor hash = SHA-256(daily random salt | site | IP | user agent), truncated; the salt is generated per day and deleted after at most 2 days, so hashes cannot be linked across days or reversed.
- Stored per session/pageview: page path (no query string except UTM parameters), referrer domain and path, UTM parameters, channel and AI engine, country, region, city, device type, browser and OS (with version), screen class, language, engaged time, scroll depth, 404 flag, timestamps. Form submission events carry only the form's id or name attribute; field contents are never read or sent.
- Stored unless the controller switches it off for a website: the on-site search phrase, read from the page address (q, s, search and similar parameters). Before storage the processor removes email addresses, web addresses, every word containing a digit and other text that looks like personal data, and caps the phrase at 100 characters. The query string itself is not stored. Sessions end after 30 minutes of inactivity.
- Stored if the controller sends them: custom event names, properties (max 4 KB), values and currency, and e-commerce order IDs and item names/quantities/prices.
- AI crawler log (server-side): bot name, path, HTTP status, time. Not personal data of visitors.
Visitors sending Do Not Track or Global Privacy Control signals are not recorded. Known bots are excluded.
The controller must not send directly identifying data (names, emails, phone numbers, customer IDs that it can resolve to a person) in event properties or URLs. Order IDs are pseudonymous data for the controller and are processed only for de-duplication and revenue reports.
Special categories of data (Art. 9) are not intended to be processed.
3a. No tracking of individuals
The processor processes visitor data only to produce aggregate website statistics for the controller. The processor shall not: store IP addresses; set tracking cookies or store information on visitors' devices; fingerprint visitors beyond the daily-rotating, site-specific pseudonymous hash in section 3; link visitors across days or across websites or customers; build user or advertising profiles; sell, rent or share visitor data; or use it for its own purposes. The controller shall not use Countnest to identify, track or profile individual visitors, nor combine Countnest data with other data to do so.
3b. Optional ads features (off by default)
The following applies only if the controller turns it on for a website. (a) Consent mode: when the controller's consent banner signals a visitor's consent through the tracker, the processor stores the ad click ID found in the landing page address (gclid, gbraid, wbraid, fbclid or msclkid) with that visit, deletes it after 90 days, on withdrawal signalled through the tracker, or when the controller turns consent mode off, and otherwise records only the type of click ID. (b) Conversion forwarding (Growth and Agency): on the controller's documented instruction (the destination, pixel or account ID and the event names it configures), the processor transmits, for consented visits only, a conversion record (event name, time, page address, value, currency, the platform's click ID and the browser user agent, never IP addresses or contact details) to the advertising platform the controller selects, using credentials the controller provides. The advertising platform is not a sub-processor of the processor: it receives the data under the controller's own agreement with that platform. The controller is responsible for obtaining and recording any consent required and for informing visitors. Section 3a does not prevent processing the controller instructs under this section.
3c. Team access, stats API and MCP
(a) Team access: the controller's account owner may invite users (editors and view-only users, including the controller's own clients) to its account. Invited users act for the controller and see the controller's websites in the dashboard. The controller decides who to invite and is responsible for removing access. The processor sends each invited person one transactional email containing a one-time link and stores only their email address, role and a hash of the link. (b) Stats API and MCP: on the controller's instruction (creating an API key), the processor returns aggregate statistics for one website to whoever presents that key, through the read-only API or MCP endpoint. Responses contain only aggregates, never IP addresses, visitor codes, session identifiers or single visits. Tools the controller connects with a key (for example an AI assistant) are the controller's own recipients, not sub-processors of the processor. The processor stores only a hash of each key and per-minute request counts for rate limiting.
3d. Site audit, SEO and GEO tools
On the controller's instruction (adding a website), the processor fetches the controller's public web pages, robots.txt and llms.txt with the CountnestBot crawler, obeying robots.txt, and stores facts about those pages to show the controller its site audit, schema suggestions, AI answer readiness and AI crawler access history. Public pages may contain personal data such as an author's name or a business contact detail; the processor uses it only for these features, keeps page facts only for the latest two audits and access checks for 120 days, and deletes both with the website. If the controller connects Google Search Console, the processor also stores query and page pairs (the last 28 days, replaced daily) and URL Inspection results (kept up to 7 days per page). None of these features uses visitor-level data or IP addresses.
3e. AEO question finder
On the controller's instruction (a signed-in user typing a topic into the AEO question finder), the processor sends only that topic (never visitor data or IP addresses) to Google and DuckDuckGo autocomplete services (US providers) to fetch suggested questions, and caches the results for 7 days.
4. Processor obligations
The processor shall: process only on documented instructions (these Terms, this DPA and the controller's configuration); ensure staff confidentiality; implement the measures in Annex 2; assist with data-subject requests and with Art. 32–36 obligations; notify the controller if an instruction appears to infringe GDPR; make available information necessary to demonstrate compliance.
5. Sub-processors
The controller gives general authorisation to the sub-processors in Annex 1. The processor will notify the controller of intended changes at least 30 days in advance by email or in the dashboard; the controller may object on reasonable grounds and, if unresolved, terminate. The processor imposes equivalent data-protection obligations on each sub-processor and remains liable for them.
6. International transfers
Analytics data is stored in the EU (Supabase, AWS eu-central-1 Frankfurt; Vercel functions in fra1 Frankfurt). Several sub-processors are US-headquartered companies and may access data from outside the EEA for support or operations. Such transfers rely on the EU-US Data Privacy Framework (adequacy decision of 10 July 2023) where the sub-processor is certified, otherwise on the Commission's Standard Contractual Clauses (Decision (EU) 2021/914, Module 3 processor-to-processor) plus supplementary measures. For UK data the UK Addendum applies, and for Swiss data the Swiss adaptations (section 10). EU data stays stored in eu-central-1 regardless of where the controller is located.
7. Security breach notification
The processor notifies the controller without undue delay and where feasible within 48 hours after becoming aware of a personal data breach affecting controller data, with the information in Art. 33(3) GDPR as available (nature of the breach, categories and approximate numbers of data subjects and records, likely consequences, and measures taken or proposed), so the controller can meet its 72-hour supervisory-authority obligation. The processor follows an internal breach procedure covering detection, containment, Datatilsynet notification (when IDCPH ApS is controller), customer notice, and a written incident log.
8. Audits
The processor provides, on request and at most once a year, a written description of its measures and its sub-processors' certifications (e.g. SOC 2 / ISO 27001 reports where available). On-site audits by an independent auditor bound by confidentiality are possible with 30 days' notice at the controller's cost, unless a breach makes them necessary.
9. Retention, deletion and export
- Raw analytics (sessions, hits, events, crawl logs): kept for up to 25 months, then deleted automatically by a daily job. Deleted earlier if the site or account is deleted.
- Daily salts: deleted after at most 2 days.
- On site deletion or account deletion: all analytics for those sites is deleted from the live database immediately; database backups roll off within about 7 days (Supabase Pro retention).
- Export: the controller can export its account configuration from Account. Analytics data (daily statistics and raw events) can be exported as JSON or CSV from Account. On termination, the controller may export for 30 days, after which data is deleted.
10. UK, Swiss, US and other country addenda
- UK: where UK GDPR applies, the ICO International Data Transfer Addendum to the EU SCCs (in force 21 March 2022) is incorporated; the UK Extension to the DPF (UK-US data bridge, from 12 October 2023) may be relied on for certified US recipients.
- Switzerland: where the revised FADP applies (in force 1 September 2023), references to GDPR include the FADP, the FDPIC is a competent authority, and SCCs are used with the Swiss adaptations; the Swiss-US DPF applies to certified recipients from 15 September 2024.
- US (CCPA/CPRA): Countnest acts as a "service provider". It will not sell or share personal information, will use it only for the business purpose of providing website analytics to the customer, will not retain, use or disclose it outside the direct business relationship or combine it with other data except as permitted, will comply with the CCPA, allows reasonable compliance checks (at least yearly), will notify the customer if it can no longer comply, and will help with consumer requests (11 CCR § 7051). The same commitments apply as "processor" terms under other US state privacy laws (for example Virginia, Colorado, Connecticut, Utah and Texas). Countnest does no cross-context behavioural advertising and offers no targeted-advertising features.
- Canada (PIPEDA), Australia (Privacy Act 1988) and Brazil (LGPD): the processor acts only on the controller's instructions, protects the data with the measures in Annex 2, notifies breaches as in section 7 so the controller can meet local notification duties, and helps with access and correction requests. For Brazil, the processor is an "operador" under LGPD Art. 39, and international transfers rely on contractual clauses under LGPD Art. 33.
11. Liability and law
Liability as in the Terms of Service. Governing law and venue: Danish law. For business customers, the exclusive venue is Copenhagen City Court (Københavns Byret).
Annex 1: Sub-processors
| Sub-processor | Service | Data location | Transfer basis |
|---|---|---|---|
| Supabase, Inc. | Database, authentication | EU, AWS eu-central-1 (Frankfurt) | DPA + SCCs |
| Vercel Inc. | Hosting, serverless functions, edge network, IP geolocation headers | Functions in fra1 Frankfurt; edge network global | DPF/SCCs |
| Stripe Payments Europe Ltd. / Stripe, Inc. | Billing of the Customer (account data only, not visitor data) | EU/US | DPF/SCCs |
| Cloudflare, Inc. | DNS for countnest.com | Global | DPF/SCCs |
| Google LLC / Microsoft Corp. | Only if the Customer connects Search Console / Bing Webmaster (read-only); aggregated search stats imported; OAuth tokens encrypted and deleted on disconnect | US/EU | Customer's own relationship with them; DPF/SCCs for any incidental US access |
| Google PageSpeed Insights API (URLs of customer pages only) | Core Web Vitals / Lighthouse via PageSpeed Insights; only public page URLs | US | DPF/SCCs |
| Open PageRank (Keywords Everywhere; domain name only) | Domain authority score; only the Customer's domain name is sent | Outside EU | Provider terms / SCCs as applicable |
| Scaleway SAS (Scaleway SAS (France, EU)) | Transactional email to Customer users (account emails only, not visitor analytics) | EU (France) | EU processing; no third-country transfer required |
Annex 2: Technical and organisational measures
- No visitor IP addresses stored; visitor hash with daily salt deleted within 2 days; no tracking cookies or device storage.
- TLS for all traffic; integration tokens and API keys encrypted at rest with AES-256-GCM.
- Postgres row-level security isolating customer data; service role keys only server-side; database grants hardened.
- Origin checks per site; bot, spam, DNT and GPC filtering; ingest keys for server-to-server endpoints compared in constant time.
- Admin access limited to the owner account, enforced server-side. Multi-factor authentication on provider admin accounts (Vercel, Supabase, Stripe, Google Cloud, Scaleway, Cloudflare, domain registrar).
- Provider-level encryption at rest and backups (Supabase Pro, about 7-day backup retention).
- Access logging and an internal personal-data breach procedure (detection, containment, 72-hour Datatilsynet notice when we are controller, customer notice within 48 hours when we are processor, written incident log).
- Optional ads features: click IDs only with a consent signal and only when the controller turns consent mode on; deleted after 90 days, on withdrawal or when consent mode is off; ad platform access tokens encrypted at rest (AES-256-GCM) and not readable through the dashboard.