Avivise

Legal

Cookie Policy

What cookies and browser storage Avivise uses, and why.

Entity

BlockFit OÜ

Jurisdiction

Estonia · EU

Updated

12 September 2026

Sections

5

1. Who operates Avivise?

Avivise is operated by BlockFit OÜ. This policy explains cookies and browser storage used on avivise.com and related Avivise app pages.

3. Cookies and browser storage we use

  • Essential authentication/session cookies are used to keep you signed in and protect your account.
  • Session storage may be used to remember checkout consent choices during the same browser session before payment.
  • Privacy preferences: the public website and app separately store the notice version, your choices, the time of your decision, and their expiry date in your browser. This information lasts for up to 180 days and is necessary to respect either an acceptance or a refusal.
  • Optional analytics status: a local record indicates whether analytics must remain disabled or may be used. It contains no email or account ID and remains until you change the setting or clear site data so that a refusal continues to be respected.
  • Analytics data in the browser: after you consent, PostHog may store a random pseudonymous browser identifier and limited feature and session state. This information is cleared when you withdraw consent or on your first visit after the 180-day consent expires. If you do not return, it may remain in the browser until you clear the site's data.
  • When checkout opens, Creem and its payment partners may set cookies or use storage when you open checkout, receipts, or billing portal pages.

4. Optional analytics and session replay

Avivise does not use advertising cookies or third-party behavioural advertising trackers. The public website and app can load EU-hosted PostHog only after you explicitly accept analytics on that origin. Consented requests pass through an intermediary service operated by BlockFit OÜ before reaching PostHog Cloud EU; this service does not override refusal or withdrawal. If accepted, PostHog local storage holds a random pseudonymous browser identifier and session metadata needed for consented page views, reviewed conversion or product events, approximate geography, performance, heatmap, interaction, and sanitized error signals. Like any internet request, the source IP reaches PostHog while the event is delivered, but the project is configured to discard it before event storage. The identifier is not linked to your email or direct Avivise account identifier.

Session replay is always disabled on the public website. In the app, masked dashboard replay is a separate choice and remains off unless both analytics and replay are accepted. Replay may cover every eligible, consented session, is retained for no more than 30 days, and excludes assessment, authentication, checkout, profile, and admin routes. Analytics events are retained for no more than 25 months. See the Privacy Policy for the categories captured and the masking and exclusion rules.

5. Managing cookies and withdrawing consent

You can block or delete cookies in your browser settings. Blocking essential cookies may prevent sign-in, checkout, receipts, or assessment access from working properly.

Use “Privacy settings” on the public website or in the Avivise app to reject, customize, or withdraw the choices available on that origin. Rejecting optional analytics does not affect access to the service. Withdrawal stops future optional capture and clears the PostHog identity storage on that origin. You may also clear site data in your browser to remove local identifiers and saved preferences.

Marketing email is a separate server-side account preference, not an analytics cookie. It can be managed in your Avivise profile and is never inferred from analytics or replay consent.