Cookie Policy
Cookie policy for floref, including how M.Y.O.C. uses cookies, local storage, session storage, IndexedDB, and optional analytics technologies.
28 April 2026
28 April 2026
This Cookie Policy explains how M.Y.O.C. uses cookies and similar browser technologies when you use floref. It covers the public website, the web app, and related login, billing, and support flows.
floref is an offline-first product, so the Service relies heavily on browser storage technologies beyond traditional cookies. That includes local storage, session storage, and IndexedDB for app functionality and local persistence.
Quick Summary
M.Y.O.C.
floref.com, app.floref.com, and related service pages
Cookies, localStorage, sessionStorage, IndexedDB, and similar identifiers
Authentication, security checks, sync, local persistence, and settings
Can be allowed or refused where applicable through the in-app consent choice
support@floref.com
1. What This Policy Covers
A cookie is a small text file stored by your browser. Similar technologies can include local storage, session storage, IndexedDB, security tokens, software development kits, and browser identifiers.
We use both first-party and third-party technologies. Some are essential to make floref work. Others help us understand performance, protect forms from abuse, or process billing and authentication flows.
2. Technologies Used by floref
Traditional cookies are not the main way floref stores your canvases, settings, or offline content. Instead, the app primarily relies on browser storage technologies.
- localStorage to help keep authentication state, user settings, and app preferences available between visits
- sessionStorage for per-tab or short-lived session state
- IndexedDB for local canvases, images, sync queues, and other offline-first app data
- security tokens and challenge technologies used by Cloudflare Turnstile during login, registration, and password reset flows
3. Strictly Necessary Technologies
Some technologies are required for floref to function. Without them, important parts of the Service may not work correctly.
- signing users in and maintaining account sessions
- saving local canvases, images, and sync state on your device
- remembering interface settings and basic app preferences
- protecting account-related forms against bots, abuse, and automated attacks
4. Analytics, Diagnostics, and Performance Monitoring
In production, floref can load an analytics script from bunseki.fengsight.workers.dev and send product usage events through an Umami-style analytics setup. We use this to understand broad usage patterns and improve the Service.
We also use Sentry for error reporting and diagnostics so we can detect crashes, broken flows, and operational issues.
Depending on browser behavior and third-party implementation details, these services can use cookies or similar identifiers to function.
Where applicable law requires consent for non-essential analytics, we aim to ask before enabling those analytics technologies. Users can also change their analytics preference later in the app settings.
5. Third-Party Services That May Use Cookies or Similar Technologies
When relevant parts of floref load, third-party providers may place or read cookies or use comparable browser technologies under their own policies.
- Cloudflare, including Turnstile, for security and anti-abuse checks
- Supabase for authentication and account-related flows
- Google, if you use Google sign-in
- Stripe for checkout, subscriptions, invoices, and payment management
- Sentry for diagnostics and error monitoring
- our analytics provider for product analytics in production
6. Your Choices and Browser Controls
You can manage cookies and site storage through your browser settings. Most browsers let you block or clear cookies, local storage, and site data.
Where we present an in-app analytics consent choice, you can use that choice to allow or refuse optional analytics technologies.
Browsers and devices can also remove or restrict local site storage on their own, including in private browsing modes, low-storage conditions, aggressive privacy settings, or device cleanup scenarios.
Because floref is offline-first, clearing browser storage can remove locally stored canvases, images, app state, and settings that are kept only on that device. If that data was not synced elsewhere, it may not be recoverable.
Blocking essential technologies can prevent you from signing in, passing security checks, syncing content, or using core app features.
7. Do Not Track
At this time, floref does not respond to browser "Do Not Track" signals in a standardized way, because there is no consistent industry standard for interpreting them across the technologies used by the Service.
8. Changes to This Policy
We may update this Cookie Policy when our technologies, providers, or product behavior changes. When we do, we will post the updated version with a new "Last updated" date.
9. Contact Us
If you have questions about this Cookie Policy or want to contact us about browser storage, cookies, or related privacy issues, email support@floref.com.