Cookie Policy

Version 1.1.4 · Effective 12 October 2026

This Cookie Policy explains how Monosphere Ltd (trading as Comnly) uses cookies and similar technologies on the Comnly web application (comnly.com and related subdomains) (the "Site").

This Cookie Policy supplements the Privacy Policy and uses the same defined terms.

1. What we use

We use the minimum cookies and similar technologies necessary to operate the Site. Specifically:

(a) Strictly necessary cookies: set by Supabase Auth to keep you signed in across the dashboard, member web inbox and account pages. These cookies are essential and cannot be turned off without breaking the Site for you.

(b) Local storage: used in your browser to keep an in-progress signup or join-request draft so you do not lose your work if you refresh the page or step through email confirmation, and to remember UI preferences such as the chosen plan card. Draft information is submitted to our service when you continue registration or joining and may also be saved in authentication metadata to support email confirmation across devices. Our hosting and authentication providers process it as described in the Privacy Policy. Local and session storage also remember dismissed notices and other interface preferences.

(c) Active organisation cookie: the first-party comnly-active-org cookie remembers your selected organisation for up to one year.

(d) Front-desk kiosk cookie: when a club sets up a check-in kiosk, the first device to unlock the kiosk link receives a first-party comnly_kiosk_ cookie containing a random device secret. It ties the kiosk to that device so a copied link cannot be used elsewhere, is sent only to our kiosk service, and lasts up to 400 days or until the club revokes the kiosk. It is strictly necessary for the kiosk to work.

(e) Demo workspace cookie: if you open or join a free demo workspace, a first-party comnly-demo- cookie keeps you signed in to that demo until it expires (fourteen days after the demo was opened). It is strictly necessary to give you access to the demo.

(f) Stripe checkout cookies: set by Stripe on the Stripe-hosted checkout pages (not by us) to operate payment securely and to comply with anti-fraud requirements. These are governed by Stripe's privacy notice.

We do not currently use:

• analytics cookies that profile individual users (e.g. Google Analytics user-level tracking);
• advertising or cross-site tracking cookies;
• social-media tracking pixels;
• any cookie used to build behavioural advertising profiles.

Website analytics. We use Vercel Web Analytics on the Site, enabled from 15 September 2026, to understand which pages and free tools people find useful. It is cookieless: it sets no cookie, writes nothing to your browser storage, and reads nothing already stored on your device. Because it does not store or access information on your device, it does not require consent under the Privacy and Electronic Communications Regulations 2003.

It does not identify you and does not follow you to other websites. Vercel counts unique visitors by deriving a one-way hash from your request, rotated daily and not retained afterwards, rather than by storing an identifier on your device. What it receives, and the small set of named events we record on our free tools pages, is described in the Privacy Policy.

Tool calculations and previews are processed entirely in your own browser. If you request an emailed PDF, your email and report are shared with Comnly and our email provider to verify the address and deliver your copy; your verified email and tool name also go to the Comnly team. These details are not sent to analytics. See the Privacy Policy for this separate processing.

If we ever add analytics cookies, or any measurement that stores or reads information on your device, we will update this Policy and ask for your consent first.

2. Your choices

You can clear cookies and local storage from your browser at any time. If you do, the Site will still work but you may need to sign in again and may lose any in-progress draft.

Disabling strictly necessary cookies will prevent core features (sign-in, billing, content access) from functioning.

3. Mobile app

3.1 The Comnly mobile app does not use web cookies. It uses on-device storage to keep you signed in (Supabase auth tokens normally stored using the device secure-storage facility, with app-local storage used as a fallback if that facility fails) and to cache feed content for offline viewing. Authorised door operators may also store limited admission data and offline admission records on their device. Unsynchronised admissions can remain after sign-out until they are synchronised. These mechanisms are governed by the Privacy Policy.

4. Changes

4.1 We may update this Cookie Policy from time to time, in line with the Privacy Policy update process.

5. Contact

5.1 Questions about cookies: support@comnly.com.

Monosphere Ltd (trading as Comnly), a company registered in England and Wales under company number 16315949. Registered office: 3 Broadway East, Chester, CH2 2DW, United Kingdom.