Cookie Use

Cookies are small values a website stores in your browser. Blipze also uses local browser storage and a service-worker cache for limited app functions. We do not use these technologies to sell personal information or build advertising profiles.

• Authentication: Supabase session values keep you securely signed in and complete sign-in redirects.
• Security: short-lived values can protect account and request flows from abuse.
• Core operation: the app may remember an active language or interface choice needed for the next request.

When Blip view counting is enabled, eligible signed-in accounts contribute when a Blip appears on screen, including scrolls, repeats and your own views. You can stop future measurement in View privacy. Signed-out visitors do not contribute. Counting uses your existing sign-in session and short-lived in-memory event IDs; it creates no separate measurement cookie or browser identifier.

The previous optional view-counting cookies are retired. A successful signed-in view request removes them if present. They are not used to count views. See our Privacy Policy for account-linked records, retention and data rights.

Blipze may store limited preferences, draft state and install information on your device. The service worker keeps only the minimal public app shell needed to show a useful offline screen; it does not cache private account pages or form submissions.

We use Vercel Web Analytics and Speed Insights to understand aggregate usage and reliability. These tools process limited technical request and performance information; Blipze does not use third-party advertising trackers.

Browser settings can remove or block stored data, but blocking essential session storage may prevent sign-in and other core features. For related details, read our Privacy Policy or contact us.