Green claims you can prove.
Security is demonstrated, not promised.
Your data is hosted in the European Union, each customer's space is isolated, and the evidence register is dated and chained so that any later change shows. This page states what is in production today and what is still to come, with its date.
A service whose argument is proof cannot be vague about its own. Here is what can be verified, and what is still outstanding.
Security and integrity of the register
Every ClaimTrace finding is dated, chained to the previous one and kept with no possibility of rewriting.
- Qualified timestampingEach finding will receive a timestamp token from a qualified trust service provider under the eIDAS Regulation once that provider is in service; the provider is being selected and, until then, each finding is dated and chained.
- Append-only logA register entry is never edited or deleted; a correction is added as a new entry that refers to the previous one.
- Daily sealingEach closed day is sealed with a hash that makes any later alteration detectable.
- Versioned rulesEach finding cites the rule and the version of the rulebook applied.
- Encrypted backupsKept in two separate locations in the Union, with full restoration rehearsed before opening.
The standard security questionnaire and the continuity and reversibility plan are given to every customer who signs the data processing agreement.
Isolation per organisation, tested table by table
Chained log, hashes linked from one day to the next
Audit file generated at every release
Controls at a glance
| Control | Status | What it means |
|---|---|---|
| Data hosted in the European Union | In place | Production database in Frankfurt, application functions in the same zone. |
| Isolation per organisation | In place | Row-level policies, tested table by table. |
| Chained register | In place | Each day's hash incorporates the previous day's. |
| Audit file at every release | In place | Generated with each release. |
| Daily encrypted backups, restoration-tested | Planned | A daily backup of the database at the host (Supabase Pro plan), active before the first data of any customer enter the service, kept seven days; a full restore rehearsed before subscriptions open. |
| Qualified time stamps | Planned | Within the meaning of Regulation (EU) 910/2014; the provider is being selected. |
| ISO certification, SOC report | Not held yet | Planned; announced here on the day they are obtained, not before. |
Where the data lives
Data is hosted in the European Union. The production database is located in Frankfurt and the application functions run in the same zone. The text of the public pages the scan analyses is the only exception:
| Question | Answer |
|---|---|
| What leaves the Union? | The text of the public pages the scan analyses, and nothing else. Our page analysis subprocessor, named in the list of subprocessors, processes it outside the Union, notably in the United States. |
| What is never sent to it? | Your evidence documents, the decisions in your register, the requester's email and any other personal data. |
| On what legal basis? | The standard contractual clauses of Implementing Decision (EU) 2021/914. |
| How long does it keep the text? | No more than thirty days after processing (twenty-nine days for processing in batches), except in the cases its terms provide for. Its commercial terms exclude the training of its systems on this content. |
The service is built to be portable: it is containerisable and uses no proprietary primitive without a documented substitute, so that a migration to a sovereign European host remains possible without a rewrite. That migration is the subject of a trigger-based item written into our roadmap.
Isolation and access
Each organisation is isolated at database level, through policies applied to every row carrying customer data, not through an application filter.
Role-based access control, mandatory second factor for any administrative role, with no bypass.
Other than through the actions of its users, the ClaimTrace operator accesses the data of an organisation through the service's commands, and each such access is recorded before the reading in that organisation's audit log, which the customer consults in the service. The operator accesses the data through the host's console only to handle an incident; such an access is not recorded by the service: the operator records it by hand, with its date and its reason.
Encryption in transit and at rest, immutable audit log, encrypted backups (a daily backup of the database at the host, active before the first data of any customer enter the service, kept seven days; a monthly encrypted export kept ninety days), a full restore rehearsed before subscriptions open.
Proof and time
The register is chained: each day's hash incorporates the previous day's, which makes any back-dated insertion detectable. Once the provider is in service, entries will be covered by qualified time stamps within the meaning of Regulation (EU) 910/2014, whose Article 41 attaches a presumption of accuracy of the date and integrity of the data; the provider is being selected. An exported report will carry its own qualified time stamp and the company seal. Until then, dates come from our clock, protected by the hash chain; once the provider is in service, no enforceable date will come from our own clock alone, and this requirement was confirmed against the option of a blockchain anchor, which carries no legal presumption before a European authority.
Personal data
For the content you submit and for the register, you are the controller and ClaimTrace acts as processor, under the data processing agreement attached to the terms. No append-only table contains personal data in the clear: individuals appear through an identifier whose mapping lives in an erasable table, so that the right to erasure remains enforceable without breaking the integrity of the hash chain.
- the hash of the page and of each claim
- the capture time
- the rule and the status
- the rulebook and engine versions
- the log of erasures
- the text of the pages
- the text of the claims
- the explanations and the triggers
- the salt that protects the hashes
After an erasure, the finding stays readable and dated, but can no longer be replayed.
Reversibility
The full export of the register, in dated CSV and PDF, remains available to the owner in all circumstances, including suspension for non-payment. On termination, exports remain accessible for thirty days, after which data and the evidence copies of the pages read are deleted, except for the daily global digests of the hash chain, which relate to no client and contain no personal data. Only a named and dated hold, set for a specific dispute or at the request of an authority and notified to the customer with its reason, delays this deletion; a disagreement about a finding never justifies a hold. The export includes the proofs of inclusion and, once qualified time-stamping is in service, the time-stamp tokens: it can be verified without ClaimTrace. We also keep a minimal service log for five years, with no page content, no name and no email address, and backup copies until they expire, at most ninety days after their date; they are not restored for any reason other than disaster recovery, and the deletions are replayed after any restore.
You will confirm by a link sent by email, and can unsubscribe in one click. The form is loaded from Brevo, our email provider, only when you click.