What Entropa's architecture actually does, each claim backed by real code or a public document you can check yourself — not a certification, and not marked done unless it genuinely is.
Every checkpoint is signed with ML-DSA (NIST FIPS-204), independently verified against NIST's own published test vectors — not just "should be correct."
Records are folded into a signed Merkle checkpoint. A later record can never rewrite an earlier one's proof.
Every record page runs a real inclusion-proof and signature check and shows the actual result — not a claim taken on faith.
Entropa never receives your underlying data — only a hash you compute yourself, plus an optional short label you choose to disclose.
Every customer gets their own private Merkle tree. Two customers' data can never physically occupy the same structure.
Download your complete attestation history any time, with one click — nothing is ever locked away. If you ever choose to cancel, your tree and account record are deleted in full, so there's nothing left lingering afterward either.
All API traffic is HTTPS/TLS. No plaintext submission path exists.
Every write is authenticated by a bearer key tied to your account. Identity comes from the key, never from anything the request body claims.
Deploy, runtime, and admin roles are separate GCP service accounts, each scoped to only the permissions it actually needs.
Keys and credentials live in Secret Manager, never as literals in committed code — enforced by an automated secret-scanning gate on every commit.
Every dependency is checked against known vulnerabilities on every push and on a daily schedule, not just at release time.
The signed, timestamped, tamper-evident log provides the specific recordkeeping/evidence component that BSA/FinCEN recordkeeping rules, SR 11-7 model risk management guidance, EU AI Act Article 12, NIST AI RMF, ISO/IEC 42001, and IAPP AIGP each call for — not a full compliance program or the regulation itself.
Entropa runs on Google Cloud's own HITRUST-assessed platform, and the application-layer controls Entropa owns directly (least-privilege IAM, no PII in the data path, secrets never logged) are built to that same bar as a default, not an afterthought. Stated honestly: not independently certified — adherence to the controls is the real, verifiable claim.
A real Terms of Service and Privacy Policy govern the Service today, built on well-established, industry-standard SaaS legal structures.
Entropa targets 99.95% monthly uptime — a direct pass-through of Google Cloud Run's own published SLA, not a number invented separately from it. See the full SLA.