Cookie policy

Cookie policy.

This policy explains what cookies and similar technologies Alovia uses, why we use them, and how you can control them. It is incorporated by reference into our Terms of Service.

01

What cookies are

Cookies are small text files that a website places on your device when you visit. They let the site remember information between page loads or between visits. Session cookies disappear when you close your browser. Persistent cookies stay until they expire or you delete them. Similar technologies (local storage, session storage, device identifiers) do comparable things and are covered by this policy.

02

What we use cookies for

Alovia uses three categories of cookies. Category 01 is required for the service to work. Categories 02 and 03 are optional and can be disabled in your browser without breaking the core service.

01. Essential

  • —Authentication. Keep you securely logged in and maintain your session across page visits.
  • —Security. Protect against unauthorized access, CSRF, and session hijacking.
  • —State. Remember your current place in the product as you navigate.

The cookies we set, by name

  • —alovia_access. Essential. Keeps you signed in (an HttpOnly session token). Lasts for your session and is refreshed while you use the product.
  • —alovia_logged_in. Essential. A simple flag that a session exists, so the interface knows to send you to your dashboard. Same lifetime as your session.
  • —alovia_shield. Essential, security. Set after our bot check verifies your browser on this site. It is cryptographically signed, lasts 30 minutes, and contains one-way hashes derived from your IP address and browser user agent so the pass cannot be copied to another device. It is used only to tell verified visitors from bots, never for advertising or cross-site tracking.
  • —__Host-alovia_verified. Essential, security. The same idea at our network edge: set when you visit a site protected by Shield (including aloviaai.com itself), signed, valid for up to 24 hours, containing a verification result and hashed browser details. Used only for bot defense on that site.
  • —Analytics cookie (ph_*). Optional. A first-party cookie from our analytics provider with a random visitor ID, described in Section 03. Not set when your browser sends a Global Privacy Control or Do Not Track signal.

02. Analytics (optional)

  • —Anonymized identifier for returning visitors so we can distinguish new vs. returning traffic.
  • —Page views and feature-usage events so we can tell which parts of the product are useful.
  • —Session data so we can reconstruct typical user journeys when we investigate bugs.

Analytics cookies may persist for up to 90 days. We do not share raw analytics data with third parties for their own purposes.

03. Performance (optional)

  • —Load-time and render-time measurements so we can catch regressions.
  • —Error tracking so we can see when something crashed before you had to tell us.
  • —API latency metrics so we can keep the service responsive.
03

Third-party cookies

We name each third-party cookie-setter explicitly so you know who receives what:

  • —Product analytics (US). Our analytics provider sets a first-party cookie with a randomly generated visitor ID. We use it to tell new visitors from returning ones and to count feature usage in aggregate. It is not set when your browser sends a Global Privacy Control or Do Not Track signal (Section 06 below).
  • —Google and GitHub, only during OAuth sign-in. If you click “Sign in with Google” or “Sign in with GitHub,” those providers may set their own cookies as part of their authentication flow. Those cookies are governed by their own policies, not ours.

Third-party data is processed in the United States. We do not share raw analytics data with any third party for their own purposes. For the full list of infrastructure sub-processors, see our Privacy Policy.

04

Why we use them

  • —Security. Protect against fraud and unauthorized access.
  • —Functionality. Keep you logged in and remember your preferences.
  • —Performance. Understand how the Site performs and find issues.
  • —Analytics. Learn how users interact with features, so we can improve them.
  • —Compliance. Meet legal and regulatory requirements that apply to us.
05

How to control them

Most browsers let you control cookies through their settings. The paths below are current as of the date at the top of this policy.

Chrome
Settings → Privacy and Security → Cookies and other site data
Firefox
Settings → Privacy & Security → Cookies and Site Data
Safari
Settings → Privacy → Manage Website Data
Edge
Settings → Cookies and site permissions → Manage and delete cookies and site data

You can block cookies entirely, but doing so will affect your experience with the service:

  • —You will not be able to stay logged in between page loads.
  • —Your preferences will not be saved.
  • —Some features may not work.
  • —The site may load more slowly.
06

Global Privacy Control and Do Not Track

Alovia honors browser opt-out preference signals for non-essential cookies. This includes Global Privacy Control (GPC), the signal California recognizes under the CPRA, as well as the older Do Not Track (DNT) signal. If your browser sends either one, we treat it as an opt-out: we do not set analytics or performance cookies on your device, and we turn off analytics for you. Essential cookies remain because the service cannot function without them.

07

Mobile browsers

If you use Alovia from a mobile browser, the same categories of cookies apply. In addition, we may use browser-local storage for:

  • —Session state. Remember your place between page loads.
  • —Security signals. Distinguish your device from an attacker's using an anonymized device token. This is part of the fraud and abuse-prevention stack, not tied to your identity.

You can manage these through your mobile browser's settings or by clearing site data.

08

California residents (CCPA / CPRA)

  • —We do not sell your personal information. Never have, never will.
  • —We do not use cookies or tracking technologies for cross-context behavioral advertising.
  • —Analytics cookies are used solely to improve our own service and are not shared with third parties for their own purposes.
  • —You have the right to opt out of non-essential cookies via your browser settings (Section 05) or via a browser opt-out preference signal such as Global Privacy Control (Section 06).

For the full set of rights California residents have under CCPA/CPRA, see our Privacy Policy.

09

Updates to this policy

We may update this policy from time to time to reflect changes in our practices or for legal reasons. We will notify you of material changes by posting a notice on the Site, or by email if the change materially affects your rights.

10

More information

Questions about our use of cookies can go to privacy@aloviaai.com.

Alovia · Cookie policy