ATTESTRAS
Trust and limits

What we claim, and what we do not.

A receipt is evidence about a record. This page says exactly how far that goes.

The boundary

A successful verification means the supplied proof ID and exact receipt hash match an intact stored record under the receipt profile described in the docs. It does not certify truth, legality, safety, regulatory compliance, quality or any future outcome. ATTESTRAS gives no advice, makes no predictions and scores nothing.

Shipped and not shipped

CapabilityStatus
HMAC-SHA256 request signing over exact bytes, timestamp, request ID, source and keyShipped
Tenant bound from the signing key, not the requestShipped
Per-tenant actor pseudonymisationShipped
Deterministic canonical JSON and SHA-256 receipt hash, recomputed on every readShipped
Append-only storage with UPDATE, DELETE and TRUNCATE guards; separate migration and runtime database rolesShipped
Account-free, privacy-minimised verifier with no-store and noindexShipped
RFC 3161 timestamp-authority anchoringNot shipped
Optional OpenTimestamps (Bitcoin) anchoring of receipt hashesBuilt, off
Owner record export: the key holder can recompute any of their own receipt hashes from the stored recordShipped
Published protocol spec and test vectors, so the hash and signature rules can be re-implemented and checkedShipped
Plain, dependency-free client files you can read before you run them, with their SHA-256 on the protocol pageShipped
Per-receipt digital signatures from a managed key service (KMS/HSM)Not shipped
WORM (write-once) object storageNot shipped
SOC 2, ISO 27001 or any other certificationNot held
A service-level agreement on self-serve plansNot offered

Where we are weaker than public-ledger tools

Tools such as Sigstore Rekor and OpenTimestamps let a stranger check a timestamp without trusting the operator. Today ATTESTRAS cannot do that for you: verification depends on our service, and the recorded time is our server clock. We have built optional OpenTimestamps anchoring, but it is off until it has been run against the live calendars. If independent time evidence is a hard requirement for you, use a public-anchoring tool alongside us, or tell us. What we offer is a simple, private, tenant-bound API with append-only storage and a verifier that reveals almost nothing.

Check it yourself

You do not have to take our word for the mechanics. The protocol page has the spec to download, published test vectors, and a short walkthrough that recomputes a receipt hash and a request signature on your own machine with python3 and openssl. It also lists the SHA-256 of each client file so you can confirm what you downloaded. If you hold a key you can also export one of your own records and recompute its hash. What a third party cannot reproduce is a live receipt's hash, because the public verifier does not return the full record: the protocol page says so.

Data handling in one paragraph

Receipts hold your tenant ID, a pseudonymised actor hash, the artifact hash and link, and the claim text you send. Sign-up data (your email) is kept for 12 months after your last sign-in, or deleted immediately when you close the account. Receipts follow your contract. Details: privacy.

Report a vulnerability

Email hello@3dcoded.com with details. Please give us reasonable time to fix before you disclose, and do not access other customers' data. See also security.txt.