Cookie Policy
Last Updated: 17 November 2026
1. Introduction
This Cookie Policy explains how Digital Loyalty (“we,” “us,” or “our”) uses cookies and similar technologies when you visit our website at https://digitalloyalty.com or use our services. This policy should be read alongside our Privacy Policy.
Company Information:
- Company Name: Carrott LTD
- Contact Email: admin@carrott.io
2. What Are Cookies?
Cookies are small text files that are stored on your device (computer, tablet, or mobile) when you visit a website. They help the website remember your preferences and actions over time.
Types of Storage Technologies We Use
- Cookies: Small text files stored by your browser
- Local Storage: Browser storage that persists until cleared
- Session Storage: Browser storage cleared when the browser closes
3. How We Use Cookies
3.1 Essential Cookies (Strictly Necessary)
These cookies are necessary for the website to function and cannot be disabled.
| Cookie/Storage | Purpose | Duration | Provider |
|---|---|---|---|
auth_session | Maintains your authenticated session | Session | Digital Loyalty |
better_auth_* | Authentication state and tokens | Session/30 days | Better Auth |
csrf_token | Prevents cross-site request forgery | Session | Digital Loyalty |
Legal Basis: Legitimate interest (essential for service operation)
3.2 Functional Cookies
These cookies enable enhanced functionality and personalization.
| Cookie/Storage | Purpose | Duration | Provider |
|---|---|---|---|
selectedWorkspace | Remembers your selected workspace | Persistent (localStorage) | Digital Loyalty |
theme | Stores your theme preference | Persistent (localStorage) | Digital Loyalty |
i18next | Stores your language preference | Persistent (localStorage) | Digital Loyalty |
mantine-color-scheme | Stores dark/light mode preference | Persistent (localStorage) | Mantine UI |
user-region | Marketing website: remembers the country, language and currency you chose or confirmed in the region selector. Set only when you pick a region or choose Keep on the suggestion; never set automatically | 1 year | Digital Loyalty |
Legal Basis: Legitimate interest (user experience) or consent where required. user-region is stored only at your request to remember a choice you made, so it does not need consent.
Region suggestion without storage: to suggest a language and currency on the marketing website, we use the approximate country that our hosting provider (Vercel) derives from your IP address. It is read on each request, kept in the page’s memory and not stored on your device. Earlier versions of the site stored it in a geo-country cookie and also set geo-redirected and region-detection-seen cookies. The site no longer sets them and deletes any left from earlier visits.
3.3 Third-Party Cookies
Our service integrates with third-party providers who may set their own cookies.
Payment Processing (Stripe)
| Cookie | Purpose | Duration | Provider |
|---|---|---|---|
__stripe_mid | Fraud prevention | 1 year | Stripe |
__stripe_sid | Fraud prevention | 30 minutes | Stripe |
Stripe cookies are used for payment processing and fraud detection. See Stripe’s Cookie Policy.
Wallet Services
When generating wallet passes, Apple and Google may set cookies on their respective domains:
- Apple Wallet: Cookies on apple.com during pass installation
- Google Wallet: Cookies on google.com during pass saving
These are subject to Apple’s and Google’s respective privacy policies.
3.4 Marketing-website statistics and optional analytics
Anonymous statistics (on by default; you can switch them off)
To measure and improve our marketing website, we run anonymous statistics for every visitor who has not objected. They do not store or read anything on your device: no cookies, local storage or session storage.
- Our servers count page requests, page views and clicks by page category, without visitor IDs, IP addresses, full URLs or form details. Counts are not unique visitors.
- PostHog (EU cloud, acting as our processor) receives page views and on-page events such as button clicks and form steps. The identifier is random, held in browser memory and discarded when you leave the page, so visits are not linked across pages or over time. No person profiles are created, and automatic capture and session recording are off. Web addresses are reduced to the page path and referring websites to their domain. Email addresses, phone numbers and advertising click IDs are removed.
These statistics are used only in aggregate to understand how the website is used. They are never used for advertising or to profile individuals. You can switch them off at any time with the Anonymous cookieless statistics toggle in Privacy settings (in the footer), or by choosing Reject optional. A Global Privacy Control signal also switches them off. When you switch them off, we remember that choice with the pp-privacy-v2 and site-statistics entries below.
Enquiries
When you send an enquiry, it includes the campaign tags (utm parameters) in the address of the page you are on, the domain of the website that linked to that page, and that page’s path. This uses nothing stored on your device. Remembering the campaign that first brought you to us across pages (lp-attrib) happens only after you accept analytics. Advertising click IDs are not sent with enquiries.
Our server also reports each enquiry to Google Analytics as a “generate lead” event, so we can count enquiries. The event contains the form type, page path, language and those campaign tags. It does not contain your name, email address, phone number, company, IP address or any click ID. Unless you accepted analytics, it uses a random one-off identifier that is not linked to your browser. If you accepted, it uses your Google Analytics browser identifier so the enquiry is counted once.
Optional analytics (only if you accept)
With your permission, we use Google Analytics and PostHog with cookies or local storage to measure visits across pages and over time. Google Analytics loads only after you choose Accept analytics or enable optional analytics in Privacy settings, and PostHog then switches from memory-only to stored mode. We disable advertising storage, Google Signals, ad personalisation, automatic PostHog capture and session recording. We do not send names, email addresses or phone numbers to these analytics services.
| Cookie/Storage | Purpose | Duration | Provider |
|---|---|---|---|
_ga, _ga_* | Distinguishes browsers and measures site use, after consent only | Up to 2 years | Google Analytics |
ph_*_posthog | Stores a pseudonymous analytics identifier, after consent only | Up to 180 days | PostHog |
pp-privacy-v2, pp_analytics | Remembers your privacy choice | 180 days | Digital Loyalty |
site-statistics | Remembers that you switched anonymous statistics off | 180 days | Digital Loyalty |
You can withdraw consent at any time through Privacy settings in the footer. Withdrawing consent removes optional analytics storage that this site can access and stops further stored browser analytics. Anonymous statistics continue unless you switch them off too.
3.5 Programme application analytics and similar technologies
The platform integrates PostHog for service analytics and diagnostics. The join application is configured in source to use memory persistence and identified profiles. It sends submitted names, email addresses, phone numbers and marketing preferences, where supplied, to person profiles and events with programme/card context. Memory persistence does not make that data anonymous. Dashboard analytics have their own configuration. Autocapture and session replay depend on the deployed SDK and PostHog project settings; this notice does not assert that every visit is recorded or that production recordings are fully masked.
Cookie rules can apply to technologies beyond cookies. Any applicable exemption depends on the actual purpose and operation of the technology. Memory-only storage, acceptance of service terms or marketing permission does not by itself establish an analytics exemption or consent. Required consent or objection controls must be appropriate to the actual Processing. See the Privacy Policy for personal-data roles and the supplier register for recipients.
4. Local Storage Usage
We use browser local storage for the following purposes:
| Key | Purpose | Data Stored |
|---|---|---|
selectedWorkspace | Remember your current workspace | Workspace ID |
tanstack-query-* | Cache API responses for performance | Query cache data |
lp-attrib | First-party attribution, only after you accept analytics: remembers which campaign brought you to our site so we can measure our own marketing (expires after 90 days; not shared with third parties) | Campaign tags from the link you arrived on (utm parameters), landing page and referring domain |
pp-privacy-v2 | Remembers your optional analytics and anonymous statistics choices on the marketing website | Consent decision and timestamp |
dl-analytics-consent-v1 | Compatibility value used by the site analytics adapter | Granted or denied |
Note: Local storage persists until manually cleared by the user or through browser settings.
5. How to Manage Cookies
5.1 Browser Settings
You can control cookies through your browser settings:
Chrome: Settings > Privacy and security > Cookies and other site data
Firefox: Settings > Privacy & Security > Cookies and Site Data
Safari: Preferences > Privacy > Manage Website Data
Edge: Settings > Cookies and site permissions > Cookies and site data
5.2 Blocking Cookies
If you block cookies:
- Essential features may not work properly
- You may need to log in repeatedly
- Your preferences won’t be saved
- Some payment features may be affected
5.3 Deleting Cookies
You can delete cookies at any time through your browser settings. Note that this will:
- Log you out of the platform
- Reset your preferences
- Clear cached data
5.4 Global Privacy Control
When your browser sends a Global Privacy Control signal, optional analytics and anonymous statistics are disabled. Browser “Do Not Track” signals are not consistently implemented across browsers; use our Privacy settings to record your choice directly.
Browser signals and marketing-website choices do not by themselves establish the settings of the separate programme join and dashboard applications. Contact admin@carrott.io for programme-data privacy requests.
6. Cookies and Mobile Apps
If you access our service through a mobile app:
- Mobile apps use device storage instead of cookies
- Session tokens are stored securely in the device keychain
- The same data privacy principles apply
7. Wallet Pass Considerations
When you install a wallet pass:
Apple Wallet:
- Apple receives device registration information
- Push notification tokens are stored
- Pass data is synced via iCloud (if enabled)
Google Wallet:
- Google receives pass data
- Linked to your Google account
- Subject to Google’s privacy policy
These wallet providers operate independently and have their own cookie and privacy policies.
8. Updates to This Policy
We may update this Cookie Policy to reflect changes in:
- Our use of cookies
- Legal requirements
- Third-party integrations
Material changes will be notified through our website.
9. Cookie Consent
9.1 EEA/UK Users
In accordance with GDPR and the ePrivacy Directive:
- Essential cookies are set without consent (strictly necessary)
- Non-essential cookies require consent where applicable
- Where Processing relies on consent, it must be possible to withdraw it as easily as giving it. Browser cookie controls can remove stored cookies, but do not by themselves stop every analytics request or erase data already sent. Contact admin@carrott.io for privacy requests.
9.2 Other Jurisdictions
We comply with applicable cookie laws in all jurisdictions where we operate.
10. Contact Us
For questions about our use of cookies:
Carrott LTD
- Email: admin@carrott.io
- Privacy contact: admin@carrott.io
- Address: Piccadilly Business Centre, Blackett Street, Manchester, M12 6AE
Revision dated 17 November 2026.