Overview
Bisonflow uses essential cookies and similar storage technologies such as localStorage and sessionStorage to run core product features, maintain sign-in state, and remember basic preferences.
We do not currently use non-essential analytics or marketing cookies at launch. If that changes, we plan to update this page and add any consent controls that may be required before those technologies are activated.
What We Use
- Authentication and session cookies: used by our authentication stack to sign users in, keep sessions active, and protect account access.
- Preference storage: used to remember settings such as theme choice, sidebar state, and selected workspace or project context.
- Flow and continuity storage: used to preserve temporary in-product state such as checkout continuation or landing-page navigation behavior during a session.
Why We Use Them
- Sign-in and security: to authenticate users, maintain sessions, and protect access to workspaces.
- Core functionality: to preserve preferences and keep product navigation and workflow state working as expected.
- Operational continuity: to complete flows such as onboarding, checkout recovery, and similar short-lived product states.
No Non-Essential Tracking at Launch
Based on the current application behavior, we are not intentionally deploying third-party marketing trackers, advertising pixels, or optional analytics cookies on the public site or inside the app at launch.
If we later introduce optional analytics, advertising, or similar technologies that are not strictly necessary for the service to function, we expect to provide updated disclosures and any appropriate user controls before enabling them.
Managing Cookies and Similar Storage
Most browsers allow you to control cookies through browser settings. You can also clear localStorage and sessionStorage through your browser tools. Blocking essential cookies or storage may prevent the service from working correctly.
For more information about how we process personal data generally, see our Privacy Policy.
Readership measurement
We count views of public blog articles and release notes to understand which content is useful. A view is recorded after an article stays visible for five seconds. We store only article identifiers, language, daily counts and aggregate timestamps. Reloads may count again; these are page views, not unique readers.
These counters use no cookies, browser storage, visitor identifiers, IP addresses or device fingerprints. We do not link them to accounts or workspace activity. Daily counts are kept for up to 400 days, and aggregate totals for the life of the content. Only authorized internal administrators can access the detailed dashboard.
We skip recording when the browser sends Do Not Track (DNT: 1) or Global Privacy Control (Sec-GPC: 1). Known automated agents and prefetch requests are excluded. We do not sell readership data or use it for advertising profiles.
Contact
If you have a question about cookies or similar storage used by the service, contact contact@bisonflow.com.
Questions about this document?
Contact Bisonflow