Privacy

Corevo was intentionally designed to avoid creating personal profiles. Its purpose is understanding products — which features get used, where people get stuck, what's worth improving — not tracking the people who use them.

“Collect insights, not identities” is not a policy layered on top of the platform. It is a constraint built into the shape of the data Corevo is able to receive: the event contract every connected product sends against simply has no field for a name, an email address, or any other personal identifier. There is nothing to accidentally collect.

Some events carry an anonymous session identifier, used only to group activity that happened in one visit — for example, to tell whether someone who started a calculation also finished it. That identifier is generated by the connected product itself, not by Corevo, is not a user account, and may be replaced or expire at any time. It cannot be traced back to a person.

Corevo never stores raw IP addresses or full user-agent strings. A coarse device class (desktop, mobile, tablet) and a broad locale are the most specific technical detail any event carries.

Corevo's public site (not the internal dashboard, and not any connected product's own data) optionally uses Google Analytics 4 to understand aggregate public traffic — never turned on until you explicitly accept it, and off by default. See Cookies for exactly what is and isn't sent, and how to change your decision at any time.