Last reviewed 9 August 2026
This site sets none. Not necessary ones, not functional ones, not analytics. There is no banner because there is nothing to consent to.
promtact.com is a handful of static files. It has no accounts, no sessions, no shopping basket, no preferences to remember and no scripts of any kind. A cookie would have nothing to do.
Most cookie notices exist because a site loads analytics, embedded video, a font service or a tag manager, each of which sets identifiers on somebody else's behalf. This site loads nothing from anywhere else. Its content security policy forbids every outbound request, which is why there is no third party here to set anything.
Open the developer tools in your browser, Application or Storage, and look at the cookie list for this domain. It is empty.
Or ask the server what it sends. Cookies would arrive as
Set-Cookie response headers:
$ curl -sI https://promtact.com | grep -i set-cookie
(nothing)
$ curl -sI https://promtact.com | grep -i content-security-policy
content-security-policy: default-src 'none'; style-src 'self'; img-src 'self';
base-uri 'none'; form-action 'none'; frame-ancestors 'none'
default-src 'none' is the part that matters: no
scripts, no fonts, no frames, no connections to anywhere. A tracker cannot run
on a page that will not execute code.
The hosting provider keeps ordinary server logs - address, user agent, referrer, time, requested path - which are technically necessary to serve the site and keep it available. That happens below the application and would happen for any website. It is not combined with anything else, not used to build a profile, and there is no identifier to combine it with.
Details are in the privacy statement.
Promtact the software runs in your environment, not here. It issues a session
cookie for its own console, which is a different thing from this website: it is
set by your deployment, on your domain, and it exists so a person can stay
signed in to a control panel. It is marked HttpOnly and
SameSite=Lax, and it carries the Secure flag whenever
the connection is over TLS.
That cookie is strictly necessary for the console to function and never leaves your infrastructure. Nothing about it reaches us, because there is nowhere for it to reach.
If this site ever needs a cookie, this page will say which, why, and for how long, before it is set. A consent mechanism would appear at the same time. The date at the top of this page says when it was last checked against reality.