§ 01 · Definitions

Service: the certificate validation, Gatekeeper and register services provided under the name TPP Validation, reached through api.tppvalidation.com, tppv.app and the names a customer registers there.

Customer: an institution that holds an account on the Service, on a trial or a paid plan, identified by its account and the bearer tokens and keys minted in it.

Submitted data: what a customer or its systems send to the Service to be judged: certificates and their chains, the names and settings the customer saves in the account, and the requests that carry them.

§ 02 · What the Service does

The Service validates qualified certificates against the EU and EEA trusted lists, checks revocation with the issuing trust service provider, applies the qualification rules of ETSI TS 119 615, and looks the holder up in the registers of the European Banking Authority. It answers with a verdict: as an API response, as headers and a signed assertion on the Gatekeeper, or through the CLI, MCP, Slack and Teams tools. All reference data comes from public, non-classified sources. The Service is a second opinion or, when the customer switches it on, a gate: it never replaces the customer's own obligations under the regulation that applies to it.

§ 03 · Accuracy

We make every effort to keep the verdict right, and the sources behind each verdict are named in it. The Service is nonetheless provided as is: it aggregates data from third parties, the trusted lists, the registers and the trust service providers, and we are not liable for inaccuracies that originate there. A customer who believes a verdict is wrong can report it through the contact form and we review it.

§ 04 · Availability

The Service runs on third-party infrastructure at the network edge. We work for the highest possible availability and publish the state of the trusted lists and the registers on the start page, but we do not guarantee uninterrupted service and we are not liable for disruptions outside our control. In observe mode the Gatekeeper never blocks: a disruption on our side costs a header, not a transaction.

§ 05 · The customer's responsibilities

The customer is responsible for its own compliance with the laws and regulations that apply to it. Using the Service does not by itself establish compliance with any regulatory requirement. The customer keeps its bearer tokens, sideband credentials and account access confidential, and is responsible for what is done with them. Nothing in the Service asks for a private key, and the customer must never send one.

§ 06 · Limitation of liability

We are not liable for indirect, incidental, special, consequential or punitive damages, including loss of data, service interruptions or financial loss from reliance on a verdict. Our liability for direct damages is limited to the amount the customer paid for the Service in the three months before the claim.

§ 07 · Traceability

Every verdict can be traced to its sources: the trusted list and its sequence number, the revocation answer, the register record and its hash. We log requests for this purpose and so that a customer can audit what was asked and answered. Logs and records are kept with integrity hashes; we do not guarantee perfect traceability beyond our control.

§ 08 · Submitted certificates and settings

A certificate submitted to the Service is public key material and is treated as such: it is validated, and its verdict is kept by issuer and serial so that re-checks, webhooks and the Gatekeeper can answer again without a second validation. Account settings, hostnames, signing keys and sideband credentials are kept in storage located in the European Union, one record per account, with no shared keys or tables between customers.

§ 09 · No artificial intelligence on customer data

Submitted certificates, verdicts, logs, settings and any other customer data are never sent to, processed by or used to train any artificial intelligence or machine learning system, ours or a third party's. The verdict is the output of a deterministic validation engine and of the public registers, nothing else. Our MCP server and the Slack and Teams tools are interfaces to that same engine: a certificate passed through them goes to the validation API and nowhere else, and the conversation around it is not stored by us beyond the request itself.

§ 10 · Retention and termination

When a subscription ends and is not renewed, the account's logs, settings and stored verdicts are erased at the end of the paid period. Personal information we hold is limited to what the subscription and the invoicing need, and is not linked to the use of any bearer or key. A customer can ask for its data before the end of the period.

§ 11 · Payment and termination

A subscription is paid monthly or yearly by card, yearly by invoice, or through the Microsoft Marketplace on the customer's own Microsoft agreement. A yearly subscription is paid in advance and is not refundable: the discount is tied to the commitment, and the Service stays available until the end of the paid period if the customer terminates early. Terminating a yearly subscription requires written notice at least 30 days before the next period begins; without it the next period is invoiced. A monthly subscription is charged each month; a failed charge or a cancelled card ends the subscription at once, with no refund for the remainder of the month. Invoices are due within 30 days.

§ 12 · Disputes and governing law

Disputes are first addressed in good-faith negotiation. If no agreement is reached within 90 days, the matter is brought before the District Court of Stockholm, Sweden. Swedish substantive law governs these terms.

§ 13 · Changes to these terms

We may change these terms. Current subscribers get at least 30 days' notice before new terms take effect, and continued use after that date is acceptance. A customer who objects in writing within the 30 days may terminate without penalty and receives a prorated refund of any unused prepaid period. A material change to the customer's rights or obligations may, at the customer's choice, be treated as a material breach with the same consequence.

§ 14 · Assignment

If the Service or the entity providing it changes hands, these terms and running subscriptions may be assigned to the new owner. Customers are notified; a customer who objects in writing within 30 days may terminate and receives a prorated refund of any unused prepaid period.

Contact

Questions about these terms go through the contact form. The privacy policy describes the data side in more detail.