1. What GlinFi does not use
GlinFi does not use Google Analytics, advertising pixels, cross-site advertising cookies, social-media tracking plugins, session replay, device fingerprinting or a persistent analytics visitor ID. Planner values and article filters are not written to cookies, localStorage or sessionStorage.
2. Cloudflare security cookie
When the public website was checked on 30 October 2026, Cloudflare set a __cf_bm cookie. Cloudflare documents this as a security cookie used by its bot-management services. It is separate for each site, is not a GlinFi application user ID and expires after 30 minutes of continuous inactivity. Cloudflare controls the cookie’s encrypted bot-management information.
This security technology is used to protect and deliver the website, not for GlinFi advertising or visitor profiling. Other Cloudflare challenge cookies may appear if the service needs to verify a request.
3. Aggregate website statistics
GlinFi sends a first-party request to its own analytics endpoint for a page view and for a small set of completed actions: a launch-list registration, a contact submission or a weekly-plan download. The analytics table keeps only daily totals by page and event. It does not keep individual browsing histories, analytics IP addresses, full referrers or device identifiers.
Under the current UK PECR statistical-purposes exception, consent is not required when qualifying storage or access technology is used solely to create aggregate statistics for improving the service, provided clear information and a simple, free objection are available. UK GDPR duties still apply where personal data is processed.
4. Your analytics choice
You can object at any time on the Analytics choices page. Selecting “off” stores glinfi_analytics_optout=1 in localStorage. This value exists only to remember your privacy choice in that browser. GlinFi also respects Global Privacy Control and Do Not Track for the aggregate counter.
5. Forms and downloaded plans
Launch registrations and contact messages are sent to the website server when you submit them and are stored in the website database, not in an advertising cookie. A downloaded weekly plan is created on your device at your request and is not a tracking technology.
6. Managing storage
You can clear website storage and cookies in your browser settings. Blocking a security cookie can cause Cloudflare to challenge or restrict a request. Clearing localStorage removes the saved analytics objection, so revisit Analytics choices if needed. For questions, email contact@glinfi.com.