FAQ

Does Palladium set a third-party cookie?

No. The plm_consent cookie is first-party (set on your domain) and falls into the strictly necessary ePrivacy category: it is the consent mechanism, hence exempt from consent.

Is my visitors' IP stored?

No. On reception, the IP is used once for geolocation (country / region / city) and to compute a SHA-256 hash, then immediately forgotten. No rawIp field exists in the database.

Do my European visitors require a banner?

Yes, as soon as a non-essential cookie is set on their device. Palladium is built for this case. For non-EU visitors, the banner remains displayed by default — you can disable it via the API if you geolocate server-side.

What happens if Palladium is unavailable?

If /api/consent/{siteId} doesn't respond, the snippet bails out silently: the banner doesn't display and — importantly — scripts tagged data-palladium-category remain blocked. No implicit consent is created.

How many domains can I manage?

As many as you want: each domain has its own subscription (€8/month) and its own free trial. See /tarifs.

Can I self-host Palladium?

The code is a Blazor Server .NET 9 application. Standard deployment uses Kestrel + reverse-proxy. All /api/consent requests are protected by rate-limiter (60 req/min/IP). A MySQL 8 connection is required for persistence.