§ 01 · What we collect

Account data: the work email address an account is invited on, the institution, the plan and its dates, and the contact details the customer gives us for invoicing. The Gatekeeper and API are not tied to a person: the bearers and keys belong to the institution's account.

Submitted certificates: the public certificates and chains sent to the API, presented to the Gatekeeper or passed through the tools. A certificate is public key material and is treated as public, non-sensitive data.

Operational logs: the request, its time, the verdict and its sources, so that the Service can be monitored, so that we can trace a verdict to its origin, and so that a customer can review its own usage.

Contact form: name, email, institution and what the sender asked for, used only to answer.

§ 02 · How we use it

Reference data comes exclusively from the EU and EEA trusted lists, the European Banking Authority's registers and the qualified trust service providers listed there. Submitted certificates are validated and their verdicts kept by issuer and serial, so that re-checks, webhooks and the Gatekeeper can answer again quickly; the certificate is never used for anything but validation. Logs are used for monitoring, troubleshooting and audit. Account data is used to run the subscription and to invoice it.

§ 03 · Where it lives and how it is protected

Account settings, hostnames, signing keys and sideband credentials are kept in storage located in the European Union, one record per account, with nothing shared between customers. Verdicts, logs and reference data are kept at the network edge with integrity hashes so that every record can be shown to be unaltered. Sideband credentials are stored only as their hash; signing keys never leave the record they are made in; no private key of a customer or a third party is ever requested or accepted.

§ 04 · No artificial intelligence on customer data

Submitted certificates, verdicts, logs, account settings and the content of contact messages are never sent to, processed by or used to train any artificial intelligence or machine learning system, whether ours or a third party's. Every verdict comes from a deterministic validation engine and the public registers. Our MCP server and the Slack and Teams tools are interfaces to that engine: a certificate handed to them goes to the validation API and nowhere else, and the conversation around it is not kept by us beyond the request. An AI assistant a customer connects to our MCP server is the customer's own choice and runs under the customer's own agreement with its provider.

§ 05 · No selling, no profiling, no tracking

We do not sell, rent or share customer data with third parties, except the infrastructure providers that run the Service under our instructions. We do not build profiles of people. The website sets no advertising or tracking cookies; the account uses one session cookie, and the browser keeps a view preference locally.

§ 06 · Retention

Logs and stored verdicts are kept for as long as the subscription runs and for operational and audit purposes thereafter within a reasonable period, then deleted, unless a legal obligation requires longer. When a subscription ends and is not renewed, the account's logs, settings and verdicts are erased at the end of the paid period. Account and invoicing data are kept as long as bookkeeping law requires.

§ 07 · Your rights

A customer can ask for a copy of the data held about its account, ask for corrections, and ask for deletion where no legal obligation stands in the way. Requests go through the contact form from the address the account is registered on.

§ 08 · Changes

We may update this policy when the Service or the law changes. The current version is always at this address, with its date at the top; subscribers are told of material changes.

Contact

Questions about this policy go through the contact form. The terms of service cover the contractual side.