Legal
Cookie Notice
Last updated: 21 July 2026
Draft — not for publication
This page is a working draft and has not received professional legal review.
Guidr currently uses browser local storage needed for secure account sign-in. Google Analytics is planned for basic measurement but is not installed and must not run until a visitor actively consents. Guidr does not use advertising, remarketing or Google Signals.
1. What this notice covers
This notice covers cookies, local storage and similar technologies that store information on, or access information from, your browser or device. Some are essential for a feature you request. Others, such as analytics, require a choice before they can be used.
2. Technologies used or planned
| Technology / provider | Purpose | Category | Duration |
|---|---|---|---|
| Technology / providersb-[project-reference]-auth-tokenSupabase | PurposeKeeps a signed-in account authenticated and stores the access and refresh session needed for protected features. | CategoryStrictly necessary | DurationPersists until sign-out, session removal or expiry; the session may refresh automatically while valid. |
| Technology / providersb-[project-reference]-auth-token-code-verifierSupabase | PurposeProtects OAuth, email-link or account-recovery flows using PKCE and related security checks. | CategoryStrictly necessary | DurationTemporary; removed after the authentication flow completes or is cleared. |
| Technology / providerProvider-controlled sign-in technologiesGoogle, if selected | PurposeAllows a visitor who chooses Google sign-in to authenticate on Google's service and return to Guidr. | CategoryAuthentication / functional | DurationControlled by Google on its own pages; check Google's current notices when using this option. |
| Technology / providerNames to be confirmed during implementationGoogle Analytics — planned, not active | PurposeBasic audience and service measurement only. No advertising, remarketing or Google Signals. | CategoryAnalytics — consent required | DurationTo be confirmed and documented before Analytics is enabled. |
3. Necessary authentication storage
Supabase stores authentication tokens in browser local storage so that Guidr can keep you signed in, refresh a valid session and authenticate requests to protected account features. Temporary PKCE or security values help prevent interception during Google sign-in, email-link or recovery flows.
This storage is strictly necessary when you ask Guidr to create or operate a signed-in account. Blocking or deleting it may sign you out or prevent those features from working.
4. Google sign-in
If you choose Google sign-in, you leave Guidr temporarily and interact with Google. Google may use provider-controlled cookies or similar technologies under its own notices. Guidr does not activate Google sign-in technologies merely because you visit a public Guidr page.
5. Fonts
At launch, Guidr's fonts will be self-hosted, so loading the site's typography will not contact Google Fonts. This change must be completed before these drafts are published.
6. Planned Google Analytics
Google Analytics is planned for basic measurement only and is not currently installed. Before it is enabled, Guidr will confirm and document the exact technologies and durations, configure the service without advertising features, remarketing or Google Signals, and provide consent controls.
When Analytics is implemented:
- it must not load until you actively choose to accept analytics;
- rejecting analytics must be as easy as accepting it;
- you must be able to change or withdraw your choice later; and
- withdrawing consent must stop future analytics use without affecting earlier lawful processing.
No consent banner or analytics preference control has been implemented yet, because Analytics has not been installed.
7. Your browser controls
You can remove local storage and cookies through your browser settings, but removing necessary authentication storage may sign you out. Future Guidr analytics controls will be the intended way to accept, reject or withdraw analytics consent without disabling account functionality.
8. Contact and related information
Questions about this notice can be sent to ben@guidrdiy.com. For more information about personal data, see the Privacy Policy.