Cookie Policy

oiva.dev · Effective date: 30 July 2026

1. What This Policy Covers

This policy explains how oiva.dev uses cookies and similar browser storage technologies on our platform and marketing website.

2. Storage Technologies We Use

localStorage — Authentication token

After you log in, your JWT authentication token is stored in localStorage under the key auth_token. This is essential for keeping you signed in between page loads. It is cleared when you log out or clear your browser storage.

sessionStorage — Active workspace

Your currently selected company and domain IDs are stored in sessionStorage. This data persists only for the duration of your browser session and is cleared automatically when you close the tab.

Third-party cookies — Google OAuth

If you choose to sign in with Google, the Google OAuth flow sets cookies managed by Google LLC. These are governed by Google's Privacy Policy. We do not control these cookies.

localStorage — Cookie consent preference

Your choice in the cookie consent banner (accept all, necessary only, or a custom selection) is stored in localStorage under the key cookie_consent_v2 so we don't ask again on every visit. This is not a cookie — nothing is sent to a server when it is set. You can change your choice at any time via the Cookie Settings link in the footer.

Google Tag Manager — Usage analytics (optional, consent-based)

If you accept analytics in the cookie consent banner, we use Google Tag Manager to load analytics tags — currently Google Analytics — to understand how visitors use our marketing website (e.g. page views, referral source, approximate location). These tags only run and set cookies (such as _ga) on your device after you consent, and stop the moment you withdraw consent via Cookie Settings in the footer. See Google's Privacy Policy for how Google processes this data.

localStorage — Performance monitoring (optional, consent-based)

If you accept performance monitoring in the cookie consent banner, we collect aggregate, non-identifying data about page load times, API response times, and client-side errors to find and fix bugs and slow pages. Events never include free-text error messages, page content, or anything that could identify you — only normalised page routes, numeric durations, and status codes. This data is never combined with analytics or shared with third parties. A randomly generated session identifier and a short-lived signing token are stored in localStorage (under metrics_token) to attribute events to one browsing session without using cookies; both are cleared immediately if you withdraw consent. You can change your choice at any time via the Cookie Settings link in the footer.

3. What We Do Not Use

  • No advertising or retargeting cookies.
  • No cross-site tracking.
  • Analytics cookies and performance monitoring are only active after you explicitly consent to each — see above, and you can withdraw consent at any time.

4. Embedded Widget

The oiva.dev feedback widget embedded on your website does not set any cookies or use localStorage by default. Survey responses are submitted directly to the oiva.dev API over HTTPS.

5. Managing Storage

You can change your analytics consent at any time using the Cookie Settings link in the site footer. You can also clear localStorage and sessionStorage via your browser's developer tools or privacy settings. Clearing the authentication token will sign you out of oiva.dev; clearing the consent token will show the consent banner again on your next visit. Most browsers also allow you to block or delete cookies; note that blocking essential storage may impair functionality.

6. Changes

We will update this policy if we introduce new storage technologies. Changes will be communicated with at least 14 days' notice.