Cookies and Analytics
Last updated: October 2026
1. The short version
We use no advertising or tracking cookies. The few cookies and storage entries we always use are strictly necessary: they sign you in and remember your cookie choice. Every one of them is listed in section 3.
With your permission, we count visits to privohub.com with our own copy of Umami, an open source analytics tool, running on our own servers in the EU. It tells us which pages are read, how people find us, and whether signup and sign in work.
Analytics runs only if you allow it. Until you choose, and if you choose Reject, the analytics code is not even loaded. You can change your mind at any time with Cookie settings at the bottom of every page; section 10 explains how.
Even when you allow it, it is built to keep as little as possible: your IP address is never stored, nothing is linked to your PrivoHub account, nothing is sent to any third party, and it never sees anything inside Photos, Drive or Vault.
2. Why we measure, and what we do with it
We want to improve our website based on evidence rather than guesses. The analytics answers questions like these:
- Which pages do people actually read, and which do they leave straight away?
- How do people find us: search engines, articles, other websites?
- Are signup and sign in working, or is something broken that nobody has reported?
- Which screen sizes, browsers and languages should we design and test for?
We look at the results as totals and trends on a dashboard that only the PrivoHub team can open. We use them to improve our pages, fix problems and decide what to build next.
We do not use them to profile anyone, make decisions about individual people, target advertising, train AI models, or combine them with account, billing or support data. We do not sell or share them with anyone.
3. Everything we store in your browser
This is the complete list. None of it is used for analytics, advertising or tracking you across websites.
privohub.consent- Type
- Local storage, privohub.com
- Purpose
- Remembers your cookie choice, so we do not ask on every page. It holds only whether you allowed analytics, the date you chose, and a version number.
- Kept for
- 6 months, after which we ask again. Also cleared when you clear your browser data.
oidc.user:…- Type
- Session storage, privohub.com
- Purpose
- Keeps you signed in to the account portal while the tab is open.
- Kept for
- Until you sign out or close the tab
oidc.…- Type
- Local storage, privohub.com
- Purpose
- A random one time value that protects the sign in against forgery. Created only when you start signing in.
- Kept for
- Deleted when the sign in finishes. An abandoned one is cleared on your next sign in.
ph_export_dl- Type
- Cookie, privohub.com, only sent to the export download address
- Purpose
- Authorises the download of your data export. Set only when you click download.
- Kept for
- 15 minutes
AUTH_SESSION_ID,KC_RESTART,KC_AUTH_SESSION_HASH- Type
- Cookies, auth.privohub.com
- Purpose
- Keep track of a sign in or signup while you are filling it in.
- Kept for
- Until you close the browser (the last one: 60 seconds)
KEYCLOAK_IDENTITY,KEYCLOAK_SESSION- Type
- Cookies, auth.privohub.com
- Purpose
- Keep you signed in across PrivoHub, so you do not have to enter your password again for each app.
- Kept for
- Until you sign out or close the browser
All of these are strictly necessary: the website or the feature you asked for cannot work without them, so they do not need your consent. Our analytics itself stores nothing in your browser, even when you allow it. It sets no cookie and writes no visitor ID.
PrivoHub Photos, Drive and Vault, on their own addresses, use their own sign in cookies and browser storage in the same strictly necessary way. They carry no analytics.
When you pay for a plan, you are sent to Stripe's checkout page. Stripe sets its own cookies there, mainly for fraud prevention, under Stripe's cookie policy. We do not control them and receive nothing from them.
4. What the analytics records
Only if you allow analytics. This is the complete list. Nothing else is collected.
Sent by your browser
| Field | Example | Why we want it |
|---|---|---|
| Page address | /pricing | To see which pages are read |
| Page title | Pricing | PrivoHub | Makes the reports readable at a glance |
| Previous page or referring site | duckduckgo.com | To know how people find us and move between our pages. Other websites normally reveal only their domain. |
| Screen size | 1920x1080 | To decide which layouts to test against |
| Browser language | en-GB | To judge whether translation is worth doing |
Page addresses are recorded without their query string and without the part after the #. We strip both deliberately, so search terms, tokens, and anything else carried in a link never reach the analytics database. The reference number in the address of a signup status page is replaced with a placeholder before it is sent, so that page view cannot be matched to an account either.
Worked out on our server
| Field | Example | How it is worked out |
|---|---|---|
| Browser, operating system, device type | Firefox, Linux, desktop | From the user agent your browser sends |
| Approximate location | Germany, Berlin | Looked up from your IP address in an offline database on our own server. The IP address is used for the lookup and then discarded, never written down. No external service is contacted. |
Two actions we count
Beyond page visits we count two events, so that we can tell whether signup and sign in are actually working:
- A sign in happened. No account, email address or user ID is attached. We learn that someone signed in, never who.
- A signup was submitted, with the plan size chosen and whether it is monthly or yearly. This is counted when the form is sent, before any payment, and again with no identity attached.
5. What we never collect
- Your IP address. It is never stored in the analytics database, which has no field for it.
- Your name, email address, account ID, or any way to link a visit back to you.
- Anything at all from inside PrivoHub Photos, Drive or Vault. Your photos, files, folder names and passwords are never touched by analytics. The measurement runs only on our public website, never inside the apps.
- Mouse movement, scroll recordings, session replays, keystrokes or form contents.
- Any behaviour on other websites. Our analytics can only ever see privohub.com.
6. How a visit is counted without identifying you
To report a number of visitors rather than a number of clicks, any analytics tool needs some way of recognising that two page views belong to the same visit. The usual method is a cookie holding an ID that follows you for months or years. We do not do that.
Instead, our server takes your IP address, your browser's user agent, the website ID, and a secret value that we rotate every day, and runs them through a one way cryptographic hash. The result is a meaningless identifier that cannot be reversed back into your IP address. The IP address itself is thrown away immediately and never written to disk.
Because the secret changes daily, that identifier changes daily too. If you come back tomorrow, our analytics has no way of telling that it is you again. This is a deliberate design choice: it is what makes the measurement audience counting rather than user tracking, and it is the reason we cannot build a profile of you even if we wanted to.
7. Who can see it, and where it goes
Only the PrivoHub team, through a password protected dashboard. We host Umami ourselves at analytics.privohub.com, on the same EU infrastructure as the rest of PrivoHub, writing to a database we control. There is no external analytics provider, so no third party ever receives the data and none of it leaves the EU.
We have also switched off the software's own usage reporting and update checks, so our installation does not phone home to its developers either.
8. Where the measurement runs
Only on privohub.com itself, which includes the marketing pages and the account portal, and only after you allow it there. The tracker is configured to refuse to run on any other address.
It therefore does not run on your Photos, Drive or Vault addresses, or on your workspace's own address. Those run different software that carries no analytics whatsoever.
Pages inside the account portal are counted like any other page. The records say that a page such as /portal/billing was viewed. They never say by whom.
9. How long we keep it
Analytics records are automatically deleted after 12 months. We keep them that long only to compare a season against the same season a year earlier. The daily identifier rotation described in section 6 means that even within those 12 months the records cannot be joined into a history of one person.
If you withdraw your consent, nothing more is recorded from that moment on. Visits counted before then stay in the totals until they expire: they contain nothing that identifies you, so we cannot pick out yours to remove them.
10. Your choice, and how to change it
When you first visit privohub.com we ask whether you allow analytics, with Accept all, Reject all and Customize offered side by side. Nothing is switched on in advance. Until you answer, analytics stays off, and you can use the whole website without answering.
Rejecting changes nothing about what you can do on our website or in your account.
You can change or withdraw your choice at any time, as easily as you gave it, with Cookie settings at the bottom of every page or the button below. Withdrawing takes effect immediately.
We ask again after 6 months, or sooner if we change what we collect.
Our legal basis for analytics is your consent, under Article 6(1)(a) GDPR and, for reading information from your browser, § 25(1) of the German TDDDG. The strictly necessary storage in section 3 relies on § 25(2) TDDDG and our legitimate interest in running a working, secure website under Article 6(1)(f) GDPR.
11. Changes to this policy
If we change what we collect or why, we will update this page and its date. If the change affects what you agreed to, we will ask for your choice again.
12. Questions
Write to privacy@privohub.com or use the contact form. If you want to check our claims rather than take them on trust, Umami is open source and our infrastructure setup is described on our security and privacy page. See also our Privacy Policy.