This Cookie Policy explains how Lyberty Labs FZCO d/b/a Lyberty ("Lyberty," "we," "us," or "our") uses cookies and similar technologies on our websites and Services. Read it together with our Privacy Policy.
What cookies and similar technologies are
Cookies are small files stored on a browser or device. Similar technologies include pixels, tags, SDKs, scripts, local storage, session storage, IndexedDB, device identifiers, fingerprinting signals, and other mechanisms that store or access information on a device.
Categories we use
- Necessary — required for security, session continuity, consent state, load balancing, fraud and abuse prevention, and core site functionality. These cannot be disabled because the site cannot function without them.
- Functional — remember preferences and improve optional features.
- Analytics and performance — help us understand usage, diagnose issues, measure performance, and improve the Services.
- Marketing — measure campaigns, conversions, and advertising where permitted, including cross-context behavioral advertising in jurisdictions that allow it.
Non-essential technologies are loaded only when consent is granted in jurisdictions that require consent (EEA/UK/Switzerland under ePrivacy/PECR, opt-out US states, and others).
Technologies on Lyberty-controlled sites
The exact technologies present may vary by region, page, feature set, and consent choices. We maintain a periodically updated cookie and similar-technology inventory identifying the provider, technology name, purpose, category, typical duration, and whether the technology is first-party or third-party. Actual technologies may vary by region, consent choice, page, and feature.
| Source | Cookie / storage key examples | Typical lifetime | Category | Purpose |
|---|---|---|---|---|
| Lyberty | lyb_consent, lyberty_s, _al, _ae, localStorage consent keys | Session to 13 months | Necessary / Functional | Consent state, session continuity, first-party linker, experiment assignment, fraud prevention, preferences. |
| Lyberty telemetry | first-party event IDs, pseudo/session IDs, page-instance IDs | Session to 13 months or customer-configured | Analytics | Product/site analytics, performance, reliability, event measurement, experiment analysis. |
| Microsoft Clarity | _clck, _clsk, CLID, MUID or related identifiers | Session to 13 months | Analytics | Session replay, interaction analytics, heatmaps, usability diagnostics. See Microsoft privacy. |
| Google Analytics or Google Ads, if enabled | _ga, _ga_*, _gcl_au | Up to 13 months | Analytics / Marketing | Usage analytics, conversion measurement, attribution. See Google privacy. |
| Meta, if enabled | _fbp, _fbc | About 3 months | Marketing | Ad measurement, conversion tracking, retargeting. See Meta privacy. |
| TikTok, Reddit, Microsoft Ads, or other customer/marketing pixels, if enabled | Provider-specific identifiers | Varies by provider | Marketing / Analytics | Campaign measurement, attribution, retargeting where permitted. |
| Cloudflare | __cf_bm and similar | Up to 30 minutes | Necessary | Bot mitigation, security, traffic protection. |
We do not seek or knowingly store special-category data, payment-card numbers, or full government identifiers in cookies.
Microsoft Clarity
Our marketing site uses Microsoft Clarity when analytics consent is granted and no applicable browser opt-out signal blocks analytics loading. Clarity may collect page interaction data such as clicks, scrolling, session-replay signals, device/browser information, approximate location, and visited URLs to help us understand website use and improve the site. Where consent is required, Clarity does not load until analytics consent is granted.
Session-replay and interaction-analytics tools are configured, where available, to mask or suppress sensitive fields, passwords, payment information, authentication credentials, and other Restricted Data. We do not intentionally use session-replay tools to collect the contents of private messages, payment-card numbers, passwords, government identifiers, or health information.
Customer-configured tracking
Customers may configure Lyberty first-party tracking, SDKs, pixels, session-replay, experiments, feature flags, destinations, or analytics on their own properties. Customers are responsible for legally sufficient notices, consents, opt-outs, preference-signal handling, platform compliance, and lawful configuration on those properties. Customer-configured technologies may differ from those used on lyberty.ai and are governed by the customer's own privacy notices.
For customer-configured technologies, Lyberty acts only as instructed by the customer unless otherwise stated in a written agreement. Customers are responsible for determining whether Lyberty's technologies constitute cookies, tracking technologies, sales, sharing, targeted advertising, profiling, or similar activities under applicable law, and for configuring consent and opt-out controls accordingly.
Managing choices
- Preference center: /privacy/choices
- Cookie inventory: the table above, updated as technologies, providers, regions, and consent choices change
- Browser controls: Most browsers let you block or delete cookies in their settings — see Chrome, Safari, Firefox, and Edge.
- Global Privacy Control (GPC): Where applicable, we honor GPC as an opt-out signal for Sale/Share and targeted advertising under US state privacy laws.
Your choices are browser- and device-specific. Disabling non-essential technologies may reduce analytics, personalization, or measurement features, but necessary technologies remain active so the site continues to function.
US "Do Not Sell or Share"
If marketing cookies or similar technologies on lyberty.ai constitute a "Sale" or "Sharing" for cross-context behavioral advertising under California, Colorado, Connecticut, Texas, Virginia, Utah, or comparable US state law, residents of those states may opt out at /privacy/choices. Where applicable, GPC is honored as an opt-out request.
Third-party providers
Common providers may include Microsoft Clarity, Google, Meta, TikTok, Reddit, Microsoft Advertising, Cloudflare, and Lyberty's other subprocessors. Core subprocessors are listed at /trust/sub-processors. Provider use may change as features, consent choices, or customer configurations change.
Updates
We may update this Cookie Policy as technologies, providers, features, or laws change. We will update the date above and seek renewed consent where required.
Contact
privacy@lyberty.ai Lyberty Labs FZCO Premises Number 23201, IFZA Business Park, Dubai, UAE