01We set no cookies
regescore.pro does not set cookies, first-party or third-party. There are no advertising, social-media or session-replay tools, and no embedded content from other sites. We do use Umami, a self-hosted, cookieless analytics tool that runs on our own server: it has no cookie, no persistent identifier and no third party involved. That is why you do not see a cookie banner: there is nothing to consent to.
02Exactly what the site stores
| Where | What | Why |
|---|---|---|
| Cookies | Nothing | — |
| Local storage, session storage, IndexedDB | Nothing | — |
| Our analytics server (analytics.regescore.pro) | An anonymous pageview count (page, referrer, browser/OS type, country from IP) — no cookie, no persistent ID | To see how many people visit and which pages they read. Self-hosted; no third party receives this data. |
| Your browser’s HTTP cache | The site’s own files: scripts, styles, fonts and images | So pages load faster on your next visit. Your browser manages this cache and you can clear it at any time. |
| Our server’s memory | A counter per IP address for form submissions | To stop spam. Held for up to 10 minutes and never written to disk. |
| Our server’s disk | Only what you submit in the contact or early-access form | To reply to you. See the Privacy Policy. |
03Links to other sites
Links to other sites, such as GitHub, take you to services that have their own cookie policies. Nothing from those sites loads on regescore.pro until you follow a link.
04Cookies in the Reges software
The Reges software runs on your own machine. On a network installation (Reges for Business), the Reges server sets one strictly necessary cookie, reges_sid, when a remote user signs in. It is HttpOnly and SameSite=Strict, lasts at most 12 hours, is set by your own server and is never sent to us.
05Changes
If we ever add a cookie or similar technology, we will update this page first and, where the law requires it, ask for your consent before setting it.
Last updated 2026-10-25