Privacy notice
What the QuantLayer website, application and API process, written from what the software actually stores. This is a draft and is not yet a legal notice.
Status
Controller: legal entity to be published. Privacy contact: contact address to be published.
What is processed
- Website
- No analytics, no advertising trackers and no third-party fonts or scripts. Server logs record requests for operation and security.
- Wallet sign-in
- Your account address (CAIP-10) and the sign-in signature, to create a session. The session token lives in an httpOnly cookie.
- Projects and API keys
- Project names, key names, scopes, creation and last-use times. Key secrets are shown once and never stored in plain form.
- Audit trail
- Security-relevant actions per project: who, what, when, outcome and request id.
- Identities
- Public keys, verification-method metadata and status. Linked accounts are stored encrypted and indexed blindly.
- Credentials
- Issuers keep the credential record and status history. Claim values are not kept by the platform; they go to the holder only.
- Proofs
- Proof requests and results. A witness sent for delegated proving is sealed before it is queued and never persisted.
What is not processed
- Private keys
- Never accepted, stored or logged. Identity keys in the web application are non-extractable keys in your browser.
- Claim values
- Not retained by the issuer service after issuance.
- Browser storage
- The application keeps no secrets in local storage; identity keys are held as non-extractable Web Crypto keys.
Public blockchains
Data written to Arbitrum or Robinhood Chain (roots, nullifiers, key versions, verification results, transactions) is public and permanent. It cannot be corrected or erased by QuantLayer or anyone else.