Legal
Cookie Policy
Last updated: August 27, 2026
This policy explains how FichaFlow uses cookies, local storage, service-worker storage, analytics identifiers, and other browser-side technologies.
Storage summary
FichaFlow uses browser storage to secure sign-in, remember settings, support app performance, measure product usage, and deliver optional browser Web Push notifications.
Key points
Essential authentication cookies are required for session-based sign-in and account security.
Approved production surfaces on fichaflow.com may use cross-subdomain cookie settings so supported experiences can share sign-in state.
Google Analytics and Meta Pixel run by default on approved public marketing routes and can be turned off under Settings > Privacy.
Local storage, cache storage, and service-worker related storage may support preferences and web app behavior.
Browser push subscriptions are stored only when the user enables notifications in a supported browser.
Quick links
Related legal pages
1. What FichaFlow Uses
Cookies are only one part of FichaFlow browser storage.
FichaFlow uses cookies, local storage, cache storage, service-worker related storage, and similar browser technologies to run core account and gameplay features, remember preferences, improve reliability, measure usage, and support optional capabilities such as browser push notifications.
2. Essential Authentication and Security Cookies
These cookies are needed for the service to function properly.
Essential cookies help keep users signed in, secure authenticated sessions, support password reset and verification flows, and reduce fraud or account abuse.
When FichaFlow is running on approved production domains, some authentication cookies may be configured for cross-subdomain use on fichaflow.com so supported surfaces can maintain a consistent sign-in experience.
3. Preference Storage and App State
Browser storage can keep the app feeling consistent and responsive.
FichaFlow may store non-essential browser data to remember language choice, prompts, onboarding state, UI preferences, recently used product state, and other convenience settings associated with your browser.
This category may include local storage, cache storage, and service-worker controlled assets used to improve loading behavior, reliability, or offline-ready web app behavior where supported.
FichaFlow also stores a randomly generated, first-party browser identifier used to decide which product features or feature variations your browser sees during gradual rollouts, and to measure — in aggregate — how those rollouts perform. It is not derived from your identity or your IP address, is not shared with third parties, and is not used for advertising. If you sign in, feature decisions attach to your account instead.
4. Analytics and Measurement
Google Analytics and Meta Pixel are currently enabled on the website. The mobile app uses PostHog and no cookies.
FichaFlow currently uses Google Analytics to understand product usage, navigation patterns, session and club creation flows, authentication outcomes, and feature adoption. Analytics-related identifiers may use cookies or similar browser storage depending on the browser and implementation.
FichaFlow also currently uses Meta Pixel for page-view measurement, campaign attribution, selected registration and other bounded in-product activation events, remarketing or audience-building support, and related ad-performance analysis on Meta platforms. Depending on the browser and Meta's implementation, Meta Pixel may use cookies or similar browser-side identifiers.
The current analytics implementation is event-based and focuses on bounded product telemetry such as page views, authentication method, play mode, club or match lifecycle actions, and CTA or feature entry points rather than raw user-generated content.
This Cookie Policy describes the FichaFlow website. The FichaFlow mobile app does not use cookies for measurement; it uses PostHog with an identifier stored on the device, which the Privacy Policy describes in full.
FichaFlow provides an in-product control for optional measurement under Settings > Privacy. Turning optional measurement off does not affect gameplay. Users may also manage site storage, browser privacy controls, and applicable third-party advertising preferences.
5. Push Subscriptions and Device Storage
Browser push works only after the user opts in.
If you enable browser push notifications, FichaFlow stores a browser push subscription and related browser-side registration data so supported browsers can receive notifications. This is browser Web Push, not native mobile push.
Push-related storage may include service-worker registration state, subscription endpoint data maintained by the browser, and server-side subscription records linked to your account.
6. Managing Cookies and Storage
Users can control storage through browser and product settings.
Most browsers let you review, block, or clear cookies and site storage. You can also manage notification permissions, site permissions, analytics-blocking tools, advertising or tracking protections, and related browser privacy settings directly through your browser.
Within FichaFlow, signed-in users can also review related privacy and notification preferences from settings. Clearing browser data or blocking essential storage may prevent sign-in, reset preferences, or disable optional web app and push functionality.
7. Policy Updates and Contact
Storage practices may evolve with the product.
FichaFlow may update this Cookie Policy when product behavior, analytics configuration, browser capabilities, or legal requirements change.
Questions about this Cookie Policy can be sent to support@fichaflow.com.
A practical browser-storage disclosure.
FichaFlow uses browser-side technologies to run secure sessions, support the web app experience, and deliver the features players use today.