1. What this policy covers
This policy covers cookies, browser storage, service-worker cache, scripts, SDKs, and similar technologies used by Flare Innovation Ltd on the Flare website and web app.
Some technologies are needed for the app to work. Others, especially analytics, monitoring, replay, advertising, or cross-site tracking, may need consent before they run.
2. Current cookie and storage inventory
| Technology | Purpose | Type | Notes |
|---|---|---|---|
| Supabase auth cookies, usually starting with sb- | Keep users signed in and secure authenticated sessions. | Strictly necessary | Needed for account access. |
| flaire_onboarded | Stores signed onboarding status for one hour so the app can route users correctly without repeated checks. | Service operation | Used for service flow. |
| flare_cookie_consent_v1 in local storage | Stores your cookie choice so we do not ask on every visit. | Strictly necessary preference | Expires after the consent period. |
| pwa-dismissed in session storage | Remembers that a user dismissed the install prompt during the session. | Preference/session storage | Used for a session preference. |
| Service worker and browser cache | Stores app shell and fallback assets for performance and installability. | Functional storage | Supports the web app experience. |
| Sentry browser tracing and Session Replay | Error monitoring, performance tracing, and replay of sampled sessions or error sessions. | Monitoring / analytics-like storage | Replay and tracing only run after optional consent. |
| Stripe cookies on Stripe checkout or billing portal | Payment, checkout, fraud prevention, and billing portal operation. | Payment flow | Stripe also provides its own notices. |
| Google login cookies, if Google login is selected | Google authentication flow. | Authentication / third-party | Google controls parts of this flow. |
| Vercel Web Analytics | Anonymized page-view analytics for understanding which pages are used. | Analytics | Vercel says Web Analytics does not use cookies. |
| Vercel Speed Insights | Core Web Vitals and performance measurements for deployed pages. | Performance analytics | Used to monitor loading speed, responsiveness, and visual stability. |
| Marketing pixels | No Google Analytics, Meta Pixel, PostHog, Mixpanel, or similar marketing pixel was found in the reviewed code. | Marketing | Not used at present based on the reviewed implementation. |
3. Cookie choices
Flare uses authentication cookies, an onboarding cookie, browser storage, service-worker caching, and monitoring tools.
Necessary cookies and storage stay on because they keep login, onboarding, checkout, security, and the app experience working.
Optional monitoring, browser tracing, and session replay only run if you accept optional cookies.
4. Managing cookies and storage
You can control cookies and storage through your browser settings. Blocking strictly necessary cookies may stop the app from working, especially sign-in, onboarding, checkout, and account access.
If cookie controls are shown on the site, you can use them to manage non-essential technologies.
5. Contact
For questions about cookies or storage, email walid@flareinnovation.com.