Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
How Analytick handles cookies and personal data, and what European websites must do to use it in a GDPR and ePrivacy compliant way.
Analytick is a web analytics service. It is a web analytics service that measures traffic and visitor behaviour and reports it to website owners. When it runs on a website it operates as a third party processor whose scripts, cookies and network requests are loaded into the browsers of your European visitors.
In a typical deployment Analytick processes page views, device and browser data, approximate location and persistent or session identifiers used to recognise visitors. Most of this information qualifies as personal data under the GDPR because it can be linked to an identifiable person, directly or through online identifiers stored on the device.
Any storage of or access to information on a visitor device is governed by Article 5(3) of the ePrivacy Directive, transposed into national law across the EU. The GDPR then governs the subsequent processing, so Analytick must have a valid legal basis, a clear retention period and transparent information for the data subject.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Because Analytick sets cookies or identifiers that are not strictly necessary to deliver a service the visitor explicitly requested, prior, freely given, specific and informed consent is required before it loads. Scripts must stay blocked until the visitor accepts, and refusal must be as easy as acceptance.
Analytick does not publicly disclose its hosting region, so a transfer outside the European Economic Area cannot be excluded and must be verified. Transfers of personal data outside the European Economic Area need an appropriate safeguard such as an adequacy decision or Standard Contractual Clauses, together with a transfer impact assessment where required.
List Analytick in your records of processing and your cookie policy, load it only through a consent management platform, document the consent you collect and review the vendor data processing agreement at least once a year. Test the site with consent refused to make sure no identifier is set before a choice is made.
Websites using Analytick must obtain user consent under GDPR regulations.
DPIA considerations
Assess the volume and sensitivity of data processed through Analytick, whether visitors are profiled or tracked across sites, and any transfer outside the EEA. A formal DPIA is advisable where Analytick enables large scale monitoring or combines data from several sources.
Sample consent text
We use Analytick to power parts of this site. It may store cookies and identifiers on your device and process related data. With your consent we activate Analytick. You can withdraw your consent at any time from the cookie settings.
Third-party domains contacted
analytick.comanalytick.netCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| _ank_id | analytics | 1 year | Identifies a returning visitor for analytics |
| _ank_ses | analytics | Session | Distinguishes a single analytics session |
Analytick collects user analytics data — you legally need a consent banner. Try FlowConsent free.
Analytick typically stores session identifiers and, depending on configuration, analytics or marketing cookies. The exact names and lifetimes appear in the cookie table on this page, and you should scan your own site because deployments differ.
Yes. Analytick sets cookies or identifiers that are not strictly necessary, so under Article 5(3) ePrivacy you must obtain prior consent before it loads.
The non essential cookies rely on consent under Article 6(1)(a) GDPR combined with Article 5(3) ePrivacy. Strictly necessary processing can rely on contract under Article 6(1)(b) or legitimate interest under Article 6(1)(f).
Analytick does not publicly disclose its hosting region, so a transfer outside the European Economic Area cannot be excluded and must be verified. Any such transfer needs Standard Contractual Clauses or an adequacy decision and a transfer impact assessment.
A DPIA is required when processing is likely to result in a high risk, for example large scale tracking or profiling. Where Analytick monitors behaviour at scale or combines data sources, run a DPIA before going live.
Load Analytick only after consent through a consent management platform, keep it blocked by default, document each consent, list it in your records and cookie policy, and sign a data processing agreement with the vendor.
Yes. Depending on your goal you can choose privacy first or cookieless tools, or self hosted options that keep data in the EEA. Whichever you pick, the same consent and transparency duties apply.
Add Analytick to the cookie policy with its purpose, the cookies it sets, their duration and the recipient, note any third country transfer and the safeguard used, and refresh the entry whenever you change configuration or after a new cookie scan.