Cookie Policy
Last Updated:
1. About this policy
This policy explains how Fynd S.à r.l. uses cookies, browser storage, pixels, SDKs, and similar technologies on Fynd.lu and related web application surfaces. Mobile applications may use SDK or device storage rather than browser cookies; those mobile data practices are covered below and in our Privacy Policy.
2. Your choice
Necessary technologies operate because the service cannot function securely without them. Analytics and advertising technologies require the applicable consent. Using Fynd does not itself mean you consent to non-essential technologies. On public website pages, use the consent banner to accept all, reject non-essential technologies, or choose categories. You may change your browser settings or clear site data at any time.
3. Technologies in use
| Category / provider | Purpose and typical data | When it operates |
|---|---|---|
| Necessary Fynd storage | Authentication/session state, security, language, location/session state requested by you, and the record of your consent choice. | Without optional consent where necessary to provide the requested service. |
| PostHog analytics | Product analytics, page and app interactions, feature use, device/browser information, and analytics identifiers. PostHog may use cookies or local persistence. | After analytics consent. Revoking analytics consent stops new PostHog capture and resets the browser analytics identity. |
| Google Ads | Conversion measurement and advertising, including page/event, browser, IP, and advertising-related identifiers. Google consent mode defaults analytics and advertising storage to denied. | The Google tag is loaded after analytics or advertising consent is signalled. |
| Meta Pixel | Advertising measurement for page views, searches, leads, registration, contact, and other configured interactions; this may involve browser, IP, and Meta identifiers. | After advertising consent; revocation signals the pixel to stop collection. |
| Sentry | Error, performance, and diagnostic monitoring. Data may include IP/device data, URLs, stack traces, request context, and user context if attached. Session replay is configuration-dependent. | Error monitoring is initialized when configured as a security and reliability control. The current web configuration does not enable Sentry Session Replay. |
Stripe may set technologies when you enter a hosted payment flow, and Cloudflare may process request and security information when delivering the service. Their technology and retention are controlled by the relevant service configuration.
4. Duration
Session storage may end when the tab or browser session ends. Persistent cookies and local storage remain until their configured expiry or until removed. Duration varies by provider, consent choice, and configuration. Current browser values can be inspected through browser developer tools, and provider-specific retention information can be requested at [email protected].
5. Mobile applications
Mobile apps may store authentication, security, consent, language, and feature state locally and may use PostHog or Sentry SDKs when configured. A persistent device or installation identifier may be used for rate limiting, abuse prevention, session integrity, and security. It is not described as an advertising ID. User-entered city or approximate location is distinct from precise GPS latitude/longitude, which is used only for a foreground, user-initiated location feature with device permission.
6. Managing and withdrawing consent
- Use the website consent controls on a public page to reject or select non-essential categories.
- Clear cookies and site data through your browser to remove stored identifiers and preferences.
- Use browser controls to block third-party cookies or tracking protection. Necessary functions may be affected if all storage is blocked.
- On mobile, use operating-system permissions for precise location and app storage controls where available.
Withdrawing consent does not affect processing that occurred lawfully before withdrawal. A Global Privacy Control or Do Not Track signal is not a substitute for the consent categories unless the application explicitly confirms that it has applied the signal.
7. International processing and deletion
Technology providers may process data outside the EEA depending on configuration and subprocessors. See the Privacy Policy for transfer information. Deleting browser cookies removes local identifiers but does not by itself erase server-side account or analytics records. Use our account and data deletion page to request deletion without signing in.
8. Contact and changes
We may update this policy when technologies or legal requirements change. Contact Fynd S.à r.l. at [email protected]. You may also complain to the CNPD at cnpd.public.lu.