> How Countly analytics works in self hosted and SaaS mode, what cookies it sets, when consent is required and how to set it up for GDPR and ePrivacy.
>
> Canonical: https://www.flowconsent.com/en/services/analytics/countly

Analytics

# Countly

Analytics

Countly is a product analytics platform available in two flavours: an open source self hosted Community Edition and an Enterprise Edition that can be self hosted or used as a managed SaaS. It tracks sessions, views, events, crashes and user properties for web and mobile apps, with strong support for privacy controls (no cookie mode, IP anonymisation, consent gating, automatic data deletion). For EU sites it can be deployed as a fully self hosted, GDPR friendly alternative to Google Analytics.

[Block Countly until consent](https://app.flowconsent.com/auth/sign-up?utm_source=flowconsent.com\&utm_medium=referral\&utm_campaign=analytics) · [Scan my site](https://www.flowconsent.com/en/scan)

At a glance

- Category

  [Analytics](https://www.flowconsent.com/en/services/analytics)

- Consent

  Analytics

- Prior consent

  Required

- Documented cookies

  4

- Third-party domains

  5

- Servers

  Customer controlled when self hosted (Countly Community Edition or Enterprise Edition on the customer's own infrastructure or chosen cloud); for Countly SaaS, region selected by the customer (EU data centre, US data centre or APAC)

Overview

## What does Countly do?

## **What is Countly**

Countly is an open source product analytics platform developed by Count Ly Ltd (UK) and Count Ly Inc. (USA). It collects sessions, views, custom events, crashes, performance metrics and user properties for web and mobile applications. Countly is available as an open source Community Edition (self hosted under AGPL) and as a paid Enterprise Edition (self hosted or managed SaaS). Compared to Google Analytics, Countly was designed with privacy controls in mind: consent gating, no cookie mode, automatic IP anonymisation, configurable retention and per user data deletion are all built in.

## **What data and cookies Countly collects**

By default the web SDK collects session start and end, page views, screen size, locale, referrer, custom events and crashes. It generates a device identifier stored in localStorage (cly\_id) or in a first party cookie if the developer enables it. Without explicit configuration Countly does not set third party cookies; localStorage values can be cleared by the visitor. Countly's no cookie mode disables persistent identifiers and uses a session only random ID. IP addresses can be truncated or removed on ingestion at the server level.

## **GDPR and ePrivacy implications**

In default mode, Countly stores data on the visitor's device (localStorage), which triggers Article 5(3) of the ePrivacy Directive: consent is required because the identifier is not strictly necessary for the requested service. In no cookie mode with anonymised IPs and short retention, several EU DPAs (CNIL French audience measurement exemption, BfDI guidance, Norwegian and Danish DPAs) recognise the lawful basis as legitimate interest under Article 6(1)(f) GDPR. Countly's Consent API can gate the entire SDK behind a consent decision and even remove specific feature streams (events, crashes, user properties).

## **Is consent required**

In default mode with persistent identifiers, yes. In hardened mode (no cookie, no localStorage, IP anonymisation, no shared data with third parties, short retention, self hosted in the EU), Countly can be used without consent under the audience measurement exemption that several EU DPAs publish. The Countly documentation explicitly supports both flows and exposes a Consent API to switch between them.

## **Data transfers**

In self hosted Community or Enterprise mode, no data leaves the customer's chosen infrastructure. With Countly SaaS, Count Ly Inc. (USA) and Count Ly Ltd (UK) act as processors. EU customers can ask for the EU region. Count Ly Inc. relies on the EU US Data Privacy Framework for transfers to certified entities and SCCs for any remaining flows. The DPA is publicly available.

## **Practical compliance steps**

For maximum compliance, self host Countly Community in an EU region, enable no cookie mode and IP anonymisation, configure retention to a few weeks, and either rely on legitimate interest with a clear notice or wire Countly behind a consent banner using the Consent API. Update the privacy policy with the Countly deployment details and reference the AGPL license for transparency. Document the integration in the Article 30 record.

Compliance

## Countly and the GDPR

Countly is classified as “Analytics”. On a site that targets European visitors, it must only load after the visitor consents, and it must be listed in your cookie policy.

- Legal basis

  Consent (Art. 6(1)(a) GDPR and Art. 5(3) ePrivacy) by default. Where Countly is configured in fully aggregated, first party, no cookie mode with IP anonymisation, some EU DPAs (CNIL exemption, BfDI) accept legitimate interest for strictly necessary audience measurement.

- Risk level

  low

- Applicable regulations

  GDPR, ePrivacy Directive, TTDSG, LIL, UK GDPR for UK customers, LGPD for Brazilian operations

### Impact assessment (DPIA)

A DPIA is rarely triggered by Countly itself, especially in self hosted mode where the controller fully owns the stack. For Countly SaaS with US region or for enterprise deployments combining Countly with extensive user profiling, document the integration in a DPIA covering the lawful basis, the recipients and the retention.

### Sample text for your banner

> We use Countly for product analytics. By default, no Countly cookies are set and your IP address is anonymised. You can change your preferences at any time.

Cookies and trackers

## What Countly sets and contacts

- Tracking method

  JavaScript SDK (countly.js / countly-sdk-web) loaded from the customer's Countly server, plus mobile SDKs (iOS, Android, React Native, Flutter, Unity); collects sessions, views, events, crashes, custom user properties and posts them to /i and /o endpoints on the Countly server

- Server location

  Customer controlled when self hosted (Countly Community Edition or Enterprise Edition on the customer's own infrastructure or chosen cloud); for Countly SaaS, region selected by the customer (EU data centre, US data centre or APAC)

- Cookieless mode available

  Yes

- Data transferred outside the EU

  For self hosted deployments, data flows are entirely controlled by the customer. For Countly SaaS, Count Ly Inc. (the operating company headquartered in San Francisco) and Count Ly Ltd (UK) act as processors. EU SaaS customers can pick an EU region. Count Ly Inc. is certified under the EU US Data Privacy Framework where applicable, and offers EU SCCs in its DPA.

### Cookies set (4)

| Name                                     | Type                       | Duration      | Purpose                                                                                                                                                                                                     |
| ---------------------------------------- | -------------------------- | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| cly\_id (localStorage)                   | first party (localStorage) | Until cleared | Device identifier stored in localStorage by the Countly Web SDK to recognise the same browser across sessions. Not technically a cookie but qualifies as storage on the device under Article 5(3) ePrivacy. |
| cly\_session (localStorage)              | first party (localStorage) | Session       | Marks an active Countly session in the browser; cleared when the session ends.                                                                                                                              |
| cly\_event (localStorage)                | first party (localStorage) | Until cleared | Holds queued events that have not yet been sent to the Countly server (used for batched delivery and offline reliability).                                                                                  |
| cly\_token (optional first party cookie) | first party                | 1 year        | Optional first party cookie set when the developer enables cookie based identification instead of localStorage.                                                                                             |

### Third-party domains contacted (5)

- `count.ly`
- `try.count.ly`
- `api.count.ly`
- `<your-countly-server>`
- `cdn.jsdelivr.net (when loading the SDK from a CDN)`

Questions

## Frequently asked questions about Countly

Can't find your question? Write to us, we answer fast.

[Write to us](https://www.flowconsent.com/en/demo)

### What does Countly store on the visitor's browser?

By default Countly stores a device identifier in localStorage (cly\_id) and a few preference keys (cly\_session, cly\_event). It does not set third party cookies. In no cookie mode none of this is stored; only a session ID lives in memory for the page lifetime.

### Is consent required for Countly?

In default mode yes, because localStorage values qualify as storing information on the device under Article 5(3) of the ePrivacy Directive. In hardened mode (no cookie, IP anonymisation, short retention, self hosted EU) Countly can fit the audience measurement exemption in France, Germany, Norway and other EU jurisdictions.

### What is the legal basis for Countly?

Consent under Article 6(1)(a) GDPR for default mode. Legitimate interest under Article 6(1)(f) for hardened mode when the supervisory authority recognises the audience measurement exemption.

### Are personal data transferred outside the EU?

Not in self hosted mode if the server is in the EU. In Countly SaaS, Count Ly Inc. (USA) and Count Ly Ltd (UK) are processors; transfers rely on the EU US Data Privacy Framework and SCCs in the Countly DPA.

### Do I need a DPIA for Countly?

Rarely. Self hosted hardened mode is low risk and well documented. Document the integration in the Article 30 record. Include Countly in a wider DPIA when combined with extensive A/B testing, behavioural segmentation or large scale user profiling.

### How do I deploy Countly compliantly?

Self host the Community Edition in an EU region, enable no cookie mode (Countly.add\_consent only the categories you need), anonymise IP at ingest, configure retention to the minimum, and document the deployment in your privacy policy with a reference to the AGPL license.

### What are the alternatives to Countly?

Matomo (self hosted), Plausible (self hosted or EU SaaS), Fathom Analytics (EU mode), Umami (self hosted), PostHog (self hosted), Piwik PRO (EU SaaS), and the EU based Pirsch Analytics. All can be configured for GDPR friendly audience measurement.

### How should I describe Countly in the cookie policy?

For default mode, list cly\_id and any first party cookies under Analytics with provider, purpose, retention and the legal basis (consent). For no cookie mode, mention Countly in the privacy policy under analytics with no cookie storage and rely on legitimate interest with the exemption.

Same category

## More services: Analytics

[See the whole category](https://www.flowconsent.com/en/services/analytics)

### [Detectizr](https://www.flowconsent.com/en/services/analytics/detectizr)

[Detectizr is a digital analytics solution that helps businesses measure and understand their online performance through comprehensive data collection and analysis. It provides visitor tracking, behavioral insights, and conversion metrics across websites and applications. Detectizr supports custom event tracking, audience segmentation, and automated reporting. With intuitive dashboards and visualization tools, Detectizr enables informed decisions that improve experience and drive results.](https://www.flowconsent.com/en/services/analytics/detectizr)

[Analytics](https://www.flowconsent.com/en/services/analytics/detectizr)

·

### [Avizi](https://www.flowconsent.com/en/services/analytics/avizi)

[Avizi is a digital marketing technology that helps businesses reach, engage, and convert their target audience online. It provides advanced targeting, campaign management, and performance analytics capabilities. Avizi enables marketers to deliver personalized experiences across channels, optimize campaign ROI, and gain actionable insights into customer behavior. With automation features and data-driven optimization, Avizi empowers marketing teams to achieve measurable growth.](https://www.flowconsent.com/en/services/analytics/avizi)

[Analytics](https://www.flowconsent.com/en/services/analytics/avizi)

·

### [Ringba](https://www.flowconsent.com/en/services/analytics/ringba)

[Ringba is an analytics and measurement platform providing deep insights into digital ecosystem performance. It tracks user interactions, measures campaign effectiveness, and identifies optimization opportunities across web and mobile. Ringba offers customizable dashboards, automated alerts, and data export capabilities. By transforming raw data into actionable intelligence, Ringba empowers organizations to optimize strategy and maximize return on investment.](https://www.flowconsent.com/en/services/analytics/ringba)

[Analytics](https://www.flowconsent.com/en/services/analytics/ringba)

·

### [SmartDX](https://www.flowconsent.com/en/services/analytics/smartdx)

[SmartDX is a digital analytics solution that helps businesses measure and understand their online performance through comprehensive data collection and analysis. It provides visitor tracking, behavioral insights, and conversion metrics across websites and applications. SmartDX supports custom event tracking, audience segmentation, and automated reporting. With intuitive dashboards and visualization tools, SmartDX enables informed decisions that improve experience and drive results.](https://www.flowconsent.com/en/services/analytics/smartdx)

[Analytics](https://www.flowconsent.com/en/services/analytics/smartdx)

·

### [AnalyticsConnect](https://www.flowconsent.com/en/services/analytics/analyticsconnect)

[AnalyticsConnect is an analytics and measurement platform providing deep insights into digital ecosystem performance. It tracks user interactions, measures campaign effectiveness, and identifies optimization opportunities across web and mobile. AnalyticsConnect offers customizable dashboards, automated alerts, and data export capabilities. By transforming raw data into actionable intelligence, AnalyticsConnect empowers organizations to optimize strategy and maximize return on investment.](https://www.flowconsent.com/en/services/analytics/analyticsconnect)

[Analytics](https://www.flowconsent.com/en/services/analytics/analyticsconnect)

·

### [Pingdom RUM](https://www.flowconsent.com/en/services/analytics/pingdom-rum)

[Pingdom RUM is a marketing platform that equips businesses with tools to amplify their digital presence and drive customer acquisition. It supports audience segmentation, campaign automation, and cross-channel engagement. Pingdom RUM provides real-time analytics and reporting dashboards for performance measurement and strategy optimization. By combining data intelligence with marketing execution, Pingdom RUM helps deliver the right message to the right audience at the right time.](https://www.flowconsent.com/en/services/analytics/pingdom-rum)

[Analytics](https://www.flowconsent.com/en/services/analytics/pingdom-rum)

## Make your site compliant today.

Free up to 25,000 sessions a month. No credit card, no commitment.

[Create my banner](https://app.flowconsent.com/auth/sign-up?utm_source=flowconsent.com\&utm_medium=referral\&utm_campaign=general) · [Scan my site](https://www.flowconsent.com/en/scan)
