On this page
Cookies and similar technologies
Cookies are small values stored by your browser and sent with requests to a website. Local storage and session storage retain values in your browser without sending them automatically. Bioza also uses service-worker caches to deliver its installable web app. This notice covers these technologies on marketing pages, the Help Center, the product and published Bioza pages.
Essential storage
Essential storage supports services you request, account security and your privacy choices. It is not switched off by rejecting optional categories. You can block it through your browser, but some features may stop working.
- better-auth.session_token (including secure-prefixed variants): authenticates your account. Sessions are configured for up to 30 days and can refresh with use. Related authentication cookies support the sign-in flow.
- bioza.active: remembers the Bioza selected in your workspace, for up to one year.
- bioza.push-device: identifies a push subscription you enabled on this device, for up to one year. Push permission is controlled separately in your browser and Account settings.
- bioza.privacy (or bioza.shared-privacy on the named Bioza domains): an HttpOnly cookie holding a random browser credential for 180 days. Only its hash is stored in our database. bioza.consent.v2 in local storage holds a preference cache and pending-save status; cached choices alone never authorize collection.
- Product preferences, dismissed notices and install prompts: remember choices you make. Session storage lasts for the browser session; local preferences remain until replaced, expired by the feature or cleared. The installation dismissal lasts 14 days.
- Application caches: store assets needed by the installable app and are refreshed as the app updates. Clearing site data removes them.
Optional analytics and audience experiments
These are off until you allow Optional analytics. Published pages can then record aggregate views and clicks with source, device, approximate country and Space context. With analytics permission, marketing pages also record page views and calls to action using first-party measurement. These events use page categories and action codes, not query strings or form contents. Marketing pages do not currently load third-party advertising pixels.
- bioza.view:* in session storage: suppresses repeat page-view events within five minutes in the same browser tab.
- bioza.source:* in session storage: carries the referral source across a visit.
- bz_ab_* cookie: keeps a visitor in a consistent audience-rule experiment group for up to 30 days. Without analytics consent, split-test rules are skipped; ordinary page access remains available.
Optional advertising measurement
Advertising has its own permission, separate from analytics. The first-party measurement system supports campaign clicks and conversion events using non-personal campaign and action codes. No external advertising partners or pixels are currently enabled. A reported browser conversion is not independent proof of a payment or booking.
Global Privacy Control disables advertising measurement. Adding a new advertising partner or materially changing purposes requires an updated notice and renewed permission before collection.
Consent records and retention
We store policy snapshots, a pseudonymous browser record and a history of your consent choices. Each receipt records the categories, policy version, time, expiry, revision, source and Global Privacy Control status. This history is separate from measurement events. It is not linked to your account, email or raw IP address.
Accepted measurement events reference the permission receipt that authorized them. We reject events with withdrawn, expired, outdated or mismatched permission. Raw measurement events are scheduled for deletion after 90 days and consent receipts after 730 days, in bounded cleanup batches. Previously generated aggregate statistics can remain. Choices expire after 180 days.
If saving fails, optional collection stops in the current browser and a pending choice is retained where storage is available. Retry to complete the server update; a failed save does not claim to have changed the server record.
External content and provider cookies
Video and audio players, booking tools, maps, social posts and file viewers can connect to another company’s servers. Those providers can receive your IP address and browser information and may use cookies or other storage according to their own policies.
Published Bioza pages load embedded players, maps, booking tools and file viewers automatically. On Bioza marketing and product sites, third-party frames stay blocked until you enable external content or select Load this content for a particular item. The one-item choice lasts while that viewer is mounted; it does not enable every provider permanently. You can use the external link instead, which takes you to the provider’s website.
Examples include YouTube, Spotify, Calendly and Google Maps or Drive, depending on what the page owner adds. Provider cookie names and lifetimes vary by service, location and whether you are signed in there; consult that provider’s current cookie notice. Bioza cannot erase cookies held on another company’s domain.
Externally hosted images and files can still make network requests when displayed or opened. Rejecting embed cookies does not make all third-party links or assets anonymous.
Making and changing your choices
Choose Reject optional, Save choices or Accept all in the privacy panel, or use Cookie Preferences. Optional categories start disabled. Rejecting them does not prevent core account creation, page editing or visiting a Bioza.
Changing preferences stops future optional analytics and updates embedded-content permissions in open pages. Withdrawing analytics also removes the session analytics keys; server-set experiment cookies are cleared on the next request. Previously collected aggregate statistics and provider information are not automatically erased by changing a browser preference.
Choices are shared across the named Bioza marketing and product subdomains in this browser. A different device, browser, private session, preview site or creator custom domain may ask again. Clearing browser storage also resets your choice. If storage is unavailable, a choice may apply only to the current session. We ask again when the saved choice expires or our consent version changes.
Browser and device controls
Your browser’s privacy settings can block or delete cookies and site data. You can revoke notification permissions in browser or device settings. Uninstalling the web app may not remove all browser storage; use site-data controls as well.
Blocking essential cookies can sign you out and prevent account features from working. Global Privacy Control disables advertising measurement. Other browser privacy signals are not permission to enable optional tracking; optional categories remain off until you choose them.
Updates and questions
This notice describes the storage categories and uses in the current product. We will update it when those uses change. For personal-information rights and retention, see the Privacy Policy. Contact support@bioza.app with questions about a particular cookie or provider.
Contact Bioza
Email support@bioza.app for privacy, legal, billing or account questions. Include the relevant Bioza URL and a description of your request. Do not send passwords, verification codes or full payment-card details.
For product instructions, visit the Help Center. Signed-in users can open a support ticket.