> For the complete documentation index, see [llms.txt](https://help.getlfg.app/p/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getlfg.app/p/agreements/cookie-policy.md). # Cookie policy ## Introduction This Cookie Policy explains how Layer Flow Gateway FZCO (“LFG”, “the Company”, “we”, “us”, or “our”), a company registered in the Dubai World Trade Centre (DWTC) free zone, UAE with licence number L-3426, uses cookies, SDKs, and similar technologies to operate, secure, and improve our website and mobile app (the “Services”). In strict alignment with our Terms of Service, our Services are purely non-custodial software tools and are **not made available** to residents, citizens, or entities within the United Kingdom, the European Union (EU), the European Economic Area (EEA), the United States, mainland China, Nigeria, or any other prohibited jurisdictions listed in our Global Availability Statement. We use only the minimum necessary cookies to make our Services function, plus optional analytics or functional cookies where you explicitly choose to enable them. This Policy should be read directly in conjunction with our Privacy Policy, which explains how we protect personal data under UAE Federal Decree-Law No. 45 of 2021 (PDPL). ## 1. What cookies are Cookies are small text files placed on your device when you visit a website or use an app. Software Development Kits (SDKs) provide similar functions in mobile applications. They help remember your preferences, maintain secure user sessions, and analyse how our SaaS tools are used. ## 2. Why We Use Cookies We use cookies and SDKs strictly to: * Operate and secure the website and app infrastructure; * Maintain login states and session validation; * Enforce geographic restrictions (geo-fencing) and prevent anti-circumvention; * Detect fraud and ensure overall platform security; * Preserve user dashboard preferences and interface layout metrics; and * Monitor application crashes or service degradation. ## 3. Categories of Cookies We classify cookies and SDKs into the following functional groupings: * **Strictly Necessary** – Required for the core Services to function (e.g., authentication tokens, security layers, load balancing, user-session identifiers). These do not require user consent and cannot be disabled without breaking the interface. * **Functional / Preference** – Remember settings such as interface language, visual layout, or selected currency parameters. We will request your choice inside the application interface. * **Analytics / Performance** – Track platform health, record crash data, and identify navigation friction points. These assist us in maintaining platform stability and optimizing software code. ## 4. Third-Party SDKs in Our App Because our platform operates as a non-custodial interface, our software environment incorporates specific technical SDK dependencies: * **Web3Auth SDK:** Utilized to facilitate non-custodial threshold cryptography (MPC) key generation directly on your local device. * **Security & Performance Trackers:** Used to report system errors, balance API node server requests, and identify network DDoS vulnerabilities. ## 5. Managing Your Choices You have full control over optional tracking data. You can manage or block cookies and SDK variables at any time by: * Selecting your choices via our in-app privacy settings panel, or * Adjusting your web browser or device permissions to block or purge historic cookies. Please note that blocking essential or strictly necessary cookies will degrade the performance of the interface and prevent your secure session from validating. ## 6. Retention Session cookies automatically expire the moment you close your web browser or shut down the application interface. Persistent cookies remain stored for a predefined duration (typically up to twelve (12) months) unless you manually purge them earlier through your device settings. ## 7. Third-Party Tools & Processing Boundaries We only engage reputable infrastructure sub-processors under strict data-processing protocols requiring high data confidentiality and adequate safeguards. Technical tools receive pseudonymised or aggregated data records and process data strictly within the UAE or global secure data centers in accordance with the cross-border provisions of the UAE Data Protection Law. ## 8. No Third-Party Advertising LFG does not use third-party behavioral targeting, marketing cookies, or tracking pixels. Your online activity, connected wallet metrics, and metadata are never shared with or sold to third-party advertising brokers or commercial profiling networks. ## 9. Updates to This Policy We may update this Cookie Policy periodically to reflect shifts in our technology architecture, feature integrations, or regional compliance requirements. We will publish the revised policy with a updated effective date and, where the changes are material, alert you via an in-app notice. ## 10. Contact If you have questions about this Cookie Policy, the SDK infrastructure integrated into the platform, or our general data-handling workflows, please reach out to our privacy team: * **Privacy Email:** * **Corporate Operational Address:** Layer Flow Gateway FZCO, Level 17, Sheikh Rashid Tower, Dubai World Trade Centre, Dubai, United Arab Emirates. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.getlfg.app/p/agreements/cookie-policy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.