Privacy
What we collect, and when
This site and its blog send nothing about your visit unless you allow it. If you do, they count the pages you read and how long you read them. The console counts what signed-in users do in it, and never what is in their projects.
Your choice
Counting on this site and the blog
If you allow it, usercurrent.com and blog.usercurrent.com send the pages you read to our own UserCurrent project, so we learn which pages help. We use it for nothing else: no advertising, and it is not sold or shared.
- Each page you open
- Its address without query parameters (campaign tags excepted), its title, and the page you came from. The first page of a visit also marks when the visit started.
- Reading time
- How long you read the page: time it was on screen with a scroll, key press or pointer move in the last 15 seconds. Sent when you leave the page.
- About your browser
- Its language and time zone, and the country and region your connection comes from, as the network reports them.
- An id for this browser
- A random id, kept in localStorage under keys starting with uc:, so visits from this browser count as one reader. It holds no name or email address.
- uc_consent
- A cookie that keeps your choice, Allow or Don't allow, for 180 days, set when you choose and shared by usercurrent.com and its subdomains so you are asked once.
- uc_visitor
- Only after Allow: a cookie with the same random id, for 180 days, so usercurrent.com, the blog and the console count you as one reader. Don't allow, or Global Privacy Control, removes it.
You have not chosen yet. Nothing is sent until you allow it.
Don't allow stops sending from then on, on both sites. If your browser sends Global Privacy Control, we treat it as Don't allow, whatever you chose before, and do not ask. If you allowed counting and later sign up or sign in to the console, the pages you read here are joined to your account through uc_visitor. Without Allow, nothing you read here is joined.
In the console
What the console sends about signed-in users
When you sign in to the UserCurrent console, it counts what you use, so we can see where setting up gets stuck. This is part of using the console.
- Screens you open
- Which console screen you are on, as a page view.
- Who you are to us
- Your account id, with your organization and its plan. No email address.
- Milestones
- Project created, key created, first event received, slot published, experiment started and catalog uploaded.
It sends nothing from your projects: no events, profiles, catalog rows, copy or settings you wrote. The console does not personalize itself for you.
In your browser
A reading profile that never leaves it
The site runs UserCurrent's affinity engine in your browser to pick the second button at the bottom of most pages, and to run the live demo. It keeps one entry in localStorage, whatever you choose above.
- uc-site-profile
- Scores for what you seem drawn to: who the pages you read are for and what they are about, weighted by reading time, and the style, material, features and color of the shoes you looked at on the live demo. It also keeps what the site learned from the suggestions you took or passed over. It holds no name, address or identifier, and nothing reads it but this site in your browser.
To remove it, open "Why this button?" at the bottom of a page and choose Forget me, use Forget me on the live demo, or clear this site's data in your browser.
Everything else
What else there is to know
The server
The pages are static files, served as they are. The host receives each request, as every web host does.
Email
If you write to support@usercurrent.com, your address and message are used to reply, and nothing else.
The product
UserCurrent itself has its own promise for the data customers send it: never used for advertising or to train shared models. The product page covers it.
Read the product's data promise. Last changed 13 November 2026.