Countnest

Privacy policy

What we collect and what we never do

We count visits. We never follow people.

Countnest tells website owners how their site is doing: how many visits, which pages people read, where they came from, and which countries and devices they use. You see totals and trends. You never see a person.

How we count visitors without knowing who they are

  • When a page loads, our server mixes the visitor's network address and browser type with a secret key and the website's ID, and turns it into a one-way code.
  • The network address (IP) is never saved.
  • The secret key changes every day and is deleted within about two days. After that, nobody can rebuild or reverse the code, not even us.
  • Tomorrow the same person gets a new code. On another website they get a different code too.
  • So we can say "about 120 people visited today", but we can't follow anyone from one day to the next, or from one site to another.

What we keep

  • Visits and page views: page address, where the visitor came from, campaign tags, time on page and how far they scrolled.
  • Rough location (country, region, city) and device, browser, system and language.
  • Form submissions: only that a form was sent and the form's id or name. Never what people typed into it.
  • Site search: the words typed into the website's own search box, read from the search results address. Emails, numbers and anything that looks like personal data are removed before saving, and website owners can turn this off.
  • A visit ends after 30 minutes without activity.
  • Raw visit records are kept for up to 25 months and then deleted automatically.

To be straight with you: these records are pseudonymous, not "anonymous" in the strict legal sense. On the same day, visits from the same browser and network to one site can be grouped together. That's how we count unique visitors. We only ever show this as statistics, never as a visitor profile.

What we never do

  • We never save IP addresses.
  • We never put tracking files on anyone's device.
  • We never fingerprint people beyond that daily-changing code.
  • We never follow people across days or across websites.
  • We never build ad profiles or user profiles.
  • We never sell or share visitor data, and we never use it for ourselves. (The only exception is the optional ad conversion feature in section 3c, which a customer has to turn on and which only covers visitors who agreed on that customer's website.)
  • We never try to find out who a visitor is, and we don't let our customers do it either.
  • If a browser says "Do Not Track" or sends Global Privacy Control, we don't count that visit at all.

Honest limits

  • People on the same network with the same browser may count as one visitor on a given day.
  • Someone who switches from Wi-Fi to mobile data may count twice.
  • If a site owner sends extra details through custom events (like an order number), that's their data and their responsibility.

1. Who we are

Countnest (countnest.com) is operated by IDCPH ApS, CVR 40009175, Lindgreens Allé 7A, 2300 København S, Denmark ("we", "us"). Contact: privacy@countnest.com. Data Protection Officer: No DPO appointed.

This policy covers personal data we process as data controller: visitors to countnest.com, people who create a Countnest account, and our paying customers. When a customer installs Countnest on their own website, we process that website's visitor data on the customer's behalf as a processor; that is governed by our Data Processing Agreement (DPA), and the customer's own privacy policy applies to their visitors.

2. What we collect and why

DataPurposeLegal basis (GDPR)Retention
Account data: email, display name, password (stored hashed by our authentication provider), account and team membershipProvide the service, log you in, securityArt. 6(1)(b) contractLife of account; deleted when you delete the account
Site settings: domains, site IDs, goals, funnels, alert rules, ingest keysProvide the serviceArt. 6(1)(b)Life of account; deleted together with all analytics for those sites 30 days after a free trial ends without a plan or a paid plan ends (we email 7 days before)
Team invites: the invited person's email address, the role offered, who invited them and when, and a fingerprint (hash) of the one-time invite link. We send the invited person one email with the linkLet account owners add teammatesArt. 6(1)(b) for the account owner; Art. 6(1)(f) for the invited person (the owner's interest in giving a colleague or client access)Deleted 30 days after the invite expires (invites expire after 7 days), or straight away when the owner cancels it
API keys: key name, the first characters of the key, a one-way fingerprint (SHA-256 hash) of the key, who created it, when it was created, last used and revoked; per-minute request counts for rate limiting. We never store the full keyProvide the read-only stats API and MCP access, security, abuse preventionArt. 6(1)(b)Keys until revoked or the site is deleted; revoked keys deleted after 90 days; request counts after 1 day
Billing data: plan, subscription status, trial and period dates, Stripe customer ID, billing name and address (required at checkout). Card details are handled by Stripe, we never see full card numbersBilling, accounting, fraud prevention, taxArt. 6(1)(b); Art. 6(1)(c) Danish Bookkeeping Act (bogføringsloven)Accounting records 5 years from end of financial year
Search integrations: encrypted Google Search Console OAuth refresh tokens and Bing Webmaster OAuth tokens or API keys you provide; imported aggregated search data (queries, pages, query and page pairs, clicks, impressions, positions, countries, devices, inbound links); Google URL Inspection results for your pages (indexed or not, last crawl, Google's chosen canonical); keywords you choose to follow in the rank tracker; Open PageRank score for your domainShow search performance in your dashboardArt. 6(1)(b)Tokens revoked/deleted when you disconnect or delete the account; imported history deleted with the site or account
Site audit and AI crawler access checks: facts from the public pages of the websites you add, read by our crawler CountnestBot (address, status code, title, description, headings, links, image alt text, dates, structured data, and any author name, phone number, address or price shown on the page); your robots.txt and llms.txt status and which crawlers they allowSite audit, SEO and GEO tools in your dashboard, and alert emails you can turn offArt. 6(1)(b)Page facts for the latest two audits only; access checks 120 days; all deleted with the website
Support and emails you send usAnswer youArt. 6(1)(b) / 6(1)(f)24 months after case closed
Technical logs on our hosting (may include IP address, user agent, timestamps)Security, abuse prevention, debuggingArt. 6(1)(f) legitimate interestTypically a few days to a few weeks on Vercel; we do not export these logs into analytics
Usage of our own website countnest.comAggregate statistics with Countnest itself (nothing stored on your device, see section 5)Art. 6(1)(f)Raw records kept for up to 25 months, then deleted automatically

We do not sell personal data and do not use it for advertising profiling.

Legitimate interests (Art. 6(1)(f))

Where we rely on legitimate interests (security and abuse logs; aggregate statistics on countnest.com itself), our interest is running a secure analytics product and understanding our own marketing site. We balance this against visitors' rights by: never storing IP addresses in analytics, storing nothing on the device, rotating the visitor code daily, honouring DNT/GPC, keeping raw records for at most 25 months, and never selling or profiling. You can object by writing to privacy@countnest.com.

3. Service providers (recipients)

  • Supabase (database, authentication), hosted in AWS eu-central-1 (Frankfurt).
  • Vercel (application hosting, functions run in the Frankfurt fra1 region).
  • Stripe (payments, subscriptions).
  • Cloudflare (DNS for countnest.com).
  • Google LLC, only when you connect Google Search Console (read-only OAuth) or when we call the PageSpeed Insights API for public page URLs you choose.
  • Microsoft Corporation (Bing), only when you connect Bing Webmaster Tools (OAuth or API key), to fetch your search data.
  • Open PageRank (Keywords Everywhere; domain name only), only the customer's domain name, for an authority score.
  • Google PageSpeed Insights API (URLs of customer pages only), only public page URLs, for speed scores.
  • Scaleway SAS (France, EU), for transactional email (sign-up, password reset, team invites, trial ending, weekly reports, breach notices).

Some providers are US companies. Where personal data may be accessed from or transferred outside the EU/EEA, we rely on the EU-US Data Privacy Framework where the provider is certified, and/or the European Commission's Standard Contractual Clauses (2021/914) included in the provider's DPA. For data from the UK we use the UK International Data Transfer Addendum to the SCCs or the UK-US data bridge (UK Extension to the DPF); for data from Switzerland, the SCCs with Swiss adaptations or the Swiss-US DPF. Customer and analytics data is stored in the EU (AWS eu-central-1, Frankfurt), whichever country you are in. For other countries (for example Canada, Australia and Brazil) we rely on these same contractual safeguards and on transfer mechanisms recognised by local law, such as contractual clauses under LGPD Art. 33.

3a. Google user data (Limited Use)

Countnest's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In plain terms:

  • We only request Google Search Console read-only access (webmasters.readonly) so we can show your search performance (queries, pages, clicks, impressions, position, country and device) in your Countnest dashboard.
  • We use that Google user data only to provide or improve that user-facing Search engine data feature. We do not use it for advertising, retargeting, credit scoring, or to build profiles of people.
  • We do not sell Google user data, and we do not transfer it to third parties except as needed to run Countnest (our EU database and hosting), for security, to comply with law, or as part of a merger or sale of the business with your prior consent.
  • OAuth refresh tokens are encrypted at rest (AES-256-GCM). We revoke the token at Google and delete it from our database when you disconnect Search Console or delete your account. Humans at Countnest do not read your Google Search Console data except if you ask us to for support, for security investigations, or where the law requires it.
  • With the same read-only access we call Google's URL Inspection API to show whether your pages are indexed. We check a few pages at a time, stay well under Google's daily limit, and keep each result for up to 7 days before checking again.
  • PageSpeed Insights is called with public page URLs only; it does not use your Google account.
  • If you create a stats API key, you can read your own search data through the API or MCP endpoint into tools you choose. We only send it in answer to a request made with your key.

3b. Bing Webmaster data

When you connect Bing Webmaster Tools, we store an encrypted OAuth refresh token or API key and import aggregated search and inbound-link statistics for your site. We use that data only to show Bing performance in your dashboard. Disconnecting Bing deletes the token or key from our database.

3c. Optional ads features (off by default)

Customers can import their own advertising costs (dates, campaign names, spend, clicks, impressions) to compare with their traffic. That is the customer's business data, not visitor data.

By default Countnest records only which type of ad click ID a visit arrived with (Google, Meta or Microsoft), never the ID itself. Our tracker removes the ID's value before sending the page address.

A customer can turn on an optional consent mode for a website. When it is on, and the customer's own consent banner tells Countnest that a visitor agreed, Countnest keeps the click ID from the landing page address (gclid, gbraid, wbraid, fbclid or msclkid) with that visit. Kept click IDs are deleted after 90 days, when the visitor withdraws consent on that website, or when the customer turns consent mode off.

On the Growth and Agency plans a customer can also ask Countnest to send conversions from consented visits to the Meta Conversions API, using the customer's own Meta pixel and access token. Countnest then sends the event name, time, page address, value and currency, the Meta click ID and the browser's user agent. We never send IP addresses, email addresses or names. The customer decides whether to use these features, is responsible for the legal basis (normally consent) and must name the ad platform in its own privacy notice. For these features we act as the customer's processor, and the ad platform handles the data under its own terms with the customer. Access tokens are stored encrypted and are never shown again in the dashboard.

3d. Site audit, SEO and GEO tools

  • Site audit: once a week our crawler, CountnestBot, reads the public pages of each website you add (up to 500, 2,000 or 10,000 pages depending on your plan). It follows robots.txt, including Crawl-delay, sends no more than two requests at a time, only reads pages on your own domain and never logs in. It stores page facts (address, status, title, description, headings, internal links, image alt text, dates, structured data types). If a page shows an author name, a business phone number or an address, we store that too, only to build the structured data suggestions for you. We keep page facts for your latest two audits.
  • AI crawler access monitor: once a day we read your robots.txt and llms.txt and store their status, a one-way fingerprint (hash) of robots.txt and which crawlers it allows. We email the site's owners and admins, and send your webhook if you set one up, when a change blocks a major search or AI crawler. You can turn these emails off per site, and every email has an unsubscribe link. Content refresh emails are off until you turn them on. We keep access checks for 120 days.
  • No visitor data: these tools use public pages, your own Search Console data and the aggregate counts already in your dashboard. They store no IP addresses and identify no visitors. AI citation clues are estimates from that same data; we use no paid or third-party AI monitoring services.

3e. AEO question finder

The AEO question finder sends only the topic a signed-in user types (never visitor data or IP addresses) to Google and DuckDuckGo autocomplete services (US providers) to fetch suggested questions. Results are cached for 7 days.

4. Your rights

You can request access, rectification, erasure, restriction, portability and object to processing based on legitimate interest. Many actions are self-serve in Account: change email and password, export your data, delete your account. Contact privacy@countnest.com. You can complain to the Danish Data Protection Agency (Datatilsynet), www.datatilsynet.dk, or your local authority.

4a. Where you live: rights outside the EU

Countnest serves customers worldwide. We apply the same privacy-friendly design everywhere, and we honour the rights your local law gives you. Write to privacy@countnest.com; we answer within the time your law requires (usually one month, 45 days under US state laws).

  • United Kingdom (UK GDPR, Data Protection Act 2018, PECR): the same rights as above. You can complain to the Information Commissioner's Office (ICO), ico.org.uk.
  • Switzerland (revised FADP): rights of access, correction and deletion. Supervisory authority: the Federal Data Protection and Information Commissioner (FDPIC), edoeb.admin.ch.
  • United States (California CCPA/CPRA and other state privacy laws): rights to know, access, correct and delete, and to opt out of sale, sharing and targeted advertising. We do not sell or share personal information, and we do no cross-context behavioural advertising or targeted advertising. We do not use or disclose sensitive personal information for inferring characteristics. We will not treat you differently for using your rights. You may use an authorised agent. Global Privacy Control signals are honoured: our tracker does not count those visits.
  • Canada (PIPEDA): rights of access and correction; complaints to the Office of the Privacy Commissioner of Canada, priv.gc.ca.
  • Australia (Privacy Act 1988, Australian Privacy Principles): rights of access and correction; complaints to the Office of the Australian Information Commissioner (OAIC), oaic.gov.au.
  • Brazil (LGPD): rights of confirmation, access, correction, anonymisation or deletion, portability and information about sharing; complaints to the ANPD, gov.br/anpd.

Categories (for US state law notices): identifiers (email, account ID), commercial information (plan and billing status), internet activity on countnest.com (aggregate statistics only). Sources: you, and your use of the service. Purposes and recipients: as in sections 2 and 3. We have not sold or shared personal information in the past 12 months.

5. Countnest's own website, dashboard and the tracker (ePrivacy)

  • countnest.com measures visits to its own public pages with Countnest itself, in the same cookie-free way and without storing IP addresses; the login, signup and dashboard pages are not measured.
  • Our public pages and the Countnest tracking script store nothing on your device: no cookies, no local storage, no fingerprinting beyond the daily server-side code described above.
  • The tracker sends a page-view request to our servers so we can count visits. Whether a website that uses Countnest needs visitor consent under ePrivacy / cookie rules depends on the site owner's country and setup. We never claim that consent is never needed; see our disclaimer and browser storage page.
  • When you log in, we set one strictly necessary login cookie. During a password reset, our authentication provider briefly keeps the reset session in your browser's local storage. Neither is used for marketing or analytics.
  • Stripe sets its own cookies on its checkout pages (on stripe.com), for payment and fraud prevention.

The full list is on our browser storage page.

6. Security

Encryption in transit (HTTPS), encryption of integration tokens at rest (AES-256-GCM), database row-level security, least-privilege access. See the DPA for details. If you believe there has been a personal-data incident affecting Countnest, write to privacy@countnest.com.

7. Changes

We will post updates here and notify account holders of material changes by email.