Cookie Policy
Digily Link · Cookies
Cookie Policy
This policy explains which cookies and similar technologies are used on digily.link, on the other Digily Link domains and on user profile pages, and how you can manage your preferences.
The short version: apart from strictly necessary cookies, functional, analytics and advertising cookies only run after you actively opt in. Accepting and rejecting are always equally easy.
1. Who is responsible?
For personal data processed through cookies for Digily Link's own purposes, the controller is Dijital Mekan Ltd, a company registered in England and Wales, with its registered office at 71-75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom. You can reach us at support@digily.link.
When a user adds Meta Pixel, Google Analytics, TikTok Pixel or a similar integration to their own Digily Link profile, that user is also a controller for the purposes they have chosen. Profile owners are responsible for providing their own privacy information and for managing the necessary consents.
3. Cookie categories and lawful basis
- Strictly necessary: required for signing in, security, load balancing, remembering your language and cookie choices, and delivering a feature you have explicitly requested. These fall under the PECR strictly necessary exemption and cannot be switched off.
- Functional: remember non-essential display, media and personalization preferences. They run with your consent unless another appropriate basis applies.
- Analytics and performance: measure visits, errors, traffic sources and feature usage. They run with your consent.
- Advertising and marketing: used for campaign measurement, retargeting, interest profiles and ad delivery. They never run without your consent.
- Affiliate attribution: used to identify the referring partner and the most recent referral. To the extent they process personal data and are not strictly necessary, they run subject to your choice.
5. Current cookie inventory
The table below reflects the cookies and similar technologies identified in an anonymous page and source review dated 08.09.2026. Whenever a provider or tag changes, this table and the preference panel are updated together.
| Cookie / technology | Provider and domain | Purpose | Category | Party | Duration |
|---|---|---|---|---|---|
| PHPSESSID | Digily Link · digily.link | Maintains your guest or signed-in session, form security and account operations | Strictly necessary | First party | Browser session |
| page_view_{page id} | Digily Link · digily.link | Prevents the same page view being counted twice in a short period and supports the view counter | Analytics / performance | First party | 1 day |
| set_language | Digily Link · digily.link | Remembers the interface language you selected | Functional | First party | 90 days |
| set_currency | Digily Link · digily.link | Remembers the display or payment currency you selected | Functional | First party | 90 days |
| theme_style | Digily Link · digily.link | Remembers your light or dark theme preference | Functional | First party | 90 days |
| Cookie preference record (technical key of the consent tool) | Digily Link · digily.link | Remembers your accept, reject and per-category choices and evidences them where required | Strictly necessary | First party | Shown in the preference panel; updated here if the configuration changes |
| Affiliate attribution record (referral parameter and the related application record) | Digily Link · digily.link | Identifies the most recent referring partner before a new account is created | Affiliate attribution | First party | 15 days; fixed to the account once registration completes |
| Google Tag Manager | Google · googletagmanager.com | Manages tags according to your preference state; Tag Manager itself is not a persistent-cookie purpose, and every tag it fires is disclosed separately | Technical / tag management | Third party | Page request, or the fired tag's own duration |
| Analytics tags fired through Tag Manager (for example Google Analytics: _ga, _ga_* and related identifiers) | Google · google-analytics.com / googletagmanager.com | Measures visits and usage statistics | Analytics / performance | Third party | Up to 2 years depending on configuration; the actual duration is shown in the preference panel |
| Advertising tags fired through Tag Manager, where enabled (for example Google Ads _gcl_* or Meta Pixel _fbp, _fbc) | Google · googleadservices.com / doubleclick.net · Meta · connect.facebook.net | Campaign conversion, ad measurement and, where permitted, targeting and optimisation | Advertising / marketing | Third party | According to the provider's configuration; shown in the preference panel |
Cloudflare Turnstile verification token and, where risk checks require it, Cloudflare security cookies (for example cf_clearance) | Cloudflare · challenges.cloudflare.com / cloudflare.com | Bot and fraud checks on registration, activation and contact forms; CDN and WAF security | Strictly necessary security | Third party | Session, or the period set by Cloudflare's risk and security configuration |
| Identifiers of media, form or calendar integrations chosen by profile owners | YouTube, Spotify, TikTok, Google Forms, Typeform, Calendly, map providers and similar | Displays the media, form, calendar or map content a profile owner has added | Functional; analytics or advertising depending on the provider | Third party | According to the provider's current policy |
Similar technologies that do not use cookies: tags fired through Tag Manager, pixels users add to their own profiles, the PWA service worker, Digily Link's own web push subscription token, local storage keys and the server-side record of an affiliate match after registration may be used. Even where these leave no cookie, they can transmit IP, device, page and event data, so they remain subject to the applicable preference and transparency rules.
6. Integrations on user profiles
Digily Link users can, within the limits of their plan, add their own analytics or advertising pixels to their profiles. Such tags:
- must not load or send data before the visitor consents to the relevant category;
- should appear in the preference panel with provider and purpose information;
- should be explained in the profile owner's own privacy information;
- must stop when consent is refused or withdrawn.
Digily Link may technically block an integration that breaches these requirements or suspend the feature on the account concerned.
7. How do you manage your cookie preferences?
On your first visit, "Accept all", "Reject all" and "Manage preferences" are offered with equal prominence. Every category other than strictly necessary is off by default. Changing your mind later is as easy as choosing the first time.
You can also delete or block cookies in your browser settings; however, essential functions such as sessions and security may then stop working. Browser settings do not replace the per-category information and consent mechanism on the site.
8. International transfers
Where Google, Meta, Cloudflare or an integration chosen by a profile owner (such as YouTube, Spotify, TikTok, Google Forms, Typeform or Calendly) is used, device, usage, cookie or interaction data may be transferred outside the United Kingdom, including to the European Economic Area and the United States. Such transfers rely on UK adequacy regulations, the UK International Data Transfer Agreement or Addendum, or another safeguard permitted under the UK GDPR. Details of the safeguards used are available on request via support@digily.link.
9. Push notifications and email measurement
Installing the app as a PWA and granting browser push permission are not cookies. Push notifications use Digily Link's own web push configuration and the browser's separate permission prompt. Where permission is granted, browser and device information, the subscription endpoint or token, notification content and interactions may be processed. Marketing notifications are only sent where the required marketing preference is also in place. If you withdraw permission, the related push subscription record is deleted and the channel closes. Not granting permission does not affect the core service. If open or click measurement is used in marketing emails, that technology, its purpose and its duration are disclosed separately in the inventory.
10. Updates and contact
When cookies or providers change, the inventory and the preference panel are updated. If a new purpose materially changes the scope of your choice, you are asked to choose again.
Questions: support@digily.link · Data protection requests: see the Privacy Notice.