Cookie policy & Similar Technologies Policy

Please read this cookie policy carefully as it contains important information on who we are and how we use cookies on our website. This policy should be read together with our Privacy Policy which sets out how and why we collect ,store, use and share personal information generally, as well as your rights in relation to your personal information and details of how to contact us and supervisory authorities if you have a complaint.

Who we are. This site/app is operated by Layer Flow Gateway FZCO (“LFG”, “we”, “us”). Contact: [email protected].

Scope. This Policy explains how we use cookies on our website and similar technologies in our app (e.g., SDKs, pixels, device identifiers). For how we handle personal data generally, see our Privacy Policy.

UAE-only. Our Services are offered exclusively in the UAE. We apply UAE data-protection law.

1) What are cookies & similar technologies?

  • Cookies are small text files placed on your browser/device.

  • Similar technologies include SDKs in mobile apps, web beacons, pixels, local storage and device IDs. These help us run the site/app, keep it secure, remember preferences, and understand usage.

2) How we use them (categories)

We use technologies in the following categories:

  • Strictly necessary (essential) – required to operate the site/app, provide security, load pages, keep you signed in, or remember consent choices. Consent not required.

  • Performance/analytics – to understand usage, improve reliability, and measure feature performance. Consent required.

  • Functionality – to remember your settings (e.g., language) and improve your experience. Consent required.

  • Marketing/advertising – to measure campaigns or show relevant content. Consent required.

3) Your choices (consent & withdrawal)

  • On first visit, we ask for your consent for non-essential categories.

  • You can change your choices at any time via Cookie Settings (link in the footer / in-app menu).

  • You can also control cookies in your browser settings. Blocking essential cookies may break parts of the site/app.

4) What we don’t set or store

We do not store your private keys, seed phrases/backup words, or your wallet passcodes/biometrics.

5) What we set / third parties

We use first-party and selected third-party technologies. Each entry lists: Name, Provider, Purpose, Category, Duration, Type (first/third-party or SDK).

Name
Provider
Purpose
Category
Duration
Type

(example) __cf_bm

Cloudflare

Bot management & site security

Strictly necessary

30 mins

3P cookie

(example) _ga

Google Analytics

Usage analytics

Performance/analytics

13 months

3P cookie

(example) amplitude_id_*

Amplitude

Product analytics

Performance/analytics

13 months

3P cookie

(example) intercom-id-*

Intercom

Support messaging

Functionality

9 months

3P cookie

(example) meta_pixel

Meta

Campaign measurement

Marketing

up to 3 months

3P pixel

(example) Mobile SDK (e.g., Firebase Analytics)

Google

App analytics/crash diagnostics

Performance/analytics

per SDK

App SDK

Your actual list may be longer. We maintain this table and update it when we add/remove vendors or purposes.

6) Aggregated Data

We may create Aggregated Data (statistical or demographic) from usage. Aggregated Data is not considered personal data if it doesn’t identify you. If we combine it with personal data so that you can be identified, we treat it as personal data and apply our Privacy Policy.

7) How to manage technologies

  • Cookie Settings: adjust per category at any time (footer link / in-app).

  • Browser controls: most browsers let you block/delete cookies (see their help pages).

  • Mobile app permissions: use your device settings to reset advertising IDs or limit tracking.

  • Do Not Track: our site currently doesn’t respond to DNT signals.

8) Retention

  • Session technologies expire when you close your browser/app session.

  • Persistent technologies last for a defined period (see table) unless you delete them or withdraw consent. We review and refresh this schedule periodically.

9) Updates & contact

We may update this Policy to reflect changes in law, our Services, or our vendors. We’ll post the new effective date. Questions? [email protected]

This policy was published on 4th September 2025. We may change this policy from time to time.

Last updated