Publication revision: 1.1.1-uk-20260922. Effective date: 22 September 2026. Current rollout is UK web and iOS; Android is deferred. Features described in these documents are not all enabled. Original-account and newer decision-record exports currently use separate controls. Closure and erasure requests require review across the original account, Firebase and providers; submission does not confirm completion. Your statutory rights are unchanged.
FLURZI COMMIT COOKIE & SIMILAR TECHNOLOGIES POLICY Document key: COOKIE_POLICY Version: 1.1.1-uk-20260922 Effective date: 22 September 2026 1. What this Policy covers This Policy explains how Flurzi Limited uses cookies and similar technologies on Flurzi Commit websites and, where relevant, technologies in our mobile apps that store information on or access information from your device. Similar technologies can include local storage, software-development kits (SDKs), pixels, tags, device identifiers and other technical mechanisms that perform similar functions. 2. Categories we use 2.1 Strictly necessary and security These technologies are needed to provide a service you request or to keep the service secure, for example authentication, session management, fraud/security controls, load balancing, language/session continuity and essential checkout functionality. Where an applicable exemption allows it, these are used without optional consent. 2.2 Preferences and functionality These remember choices such as language, appearance or other settings. Where applicable law allows a functionality exemption, we may use them without optional consent; otherwise we request consent. 2.3 Analytics Optional analytics help us understand how people use Flurzi, diagnose product journeys and improve performance. Where consent is required, analytics technologies do not activate until you opt in. 2.4 Marketing If Flurzi uses advertising or marketing technologies, they are optional and are not classified as necessary. Where consent is required, they do not activate until you opt in. 3. Your choices 3.1 The cookie/privacy control presents available optional categories and lets you accept, reject or change them. Optional choices are not pre-ticked. 3.2 Rejecting optional analytics or marketing does not remove core Flurzi Commit functionality. 3.3 You can change your choice later from the Privacy/Cookie settings. Browser or device controls may also allow you to block or delete stored information, although blocking strictly necessary technologies can prevent parts of the service from working. 4. Current technologies and providers Because the production provider set and individual cookie/SDK names can change, the live Cookie Settings panel is the operational register of non-essential technologies used by the version of the service you are using. It should identify the provider, purpose, category and relevant duration where applicable. Flurzi will not classify an analytics or marketing technology as strictly necessary merely to avoid obtaining consent. 5. Mobile apps The same privacy principles apply where a mobile SDK or device identifier performs a function equivalent to storing or accessing information on a device. App permissions are requested separately where the operating system requires them. 6. Changes and contact We may update this Policy when our technology or legal requirements change. The version and effective date are shown above. Privacy questions: privacy@flurzicommit.com Flurzi Limited, company number 16640198, Suite G04 1 Quality Court, Chancery Lane, London, England, WC2A 1HR.