⚠️ NOTICE: Deployment Testing in Progress We have recently deployed a major platform update and are currently performing post-deployment testing and validation. Please do not use this website or submit any transactions until testing is complete. Some features may be unavailable or behave unexpectedly. Thank you for your patience as we work to ensure everything is functioning correctly.
Wallets, privacy and your proofs
Privacy and what is public
What Proof keeps, what anyone can see, and what is written to the blockchain for good.
What Proof keeps
For each proof, Proof keeps:
- its fingerprint, the account that owns it, and the date and time of each step;
- the title and description you gave it, if any;
- for a file, the file’s name, type and size; for text, the text itself only if you chose to store it;
- once it is signed, the signing address, the signature and the signed message;
- for a stamped proof, your payment’s transaction ID and amount, the batch, the Merkle root and Merkle proof, and the anchor transaction ID.
The full policy is on the Privacy Policy page.
Files
A file is sent to DigiStamp when you create the proof, so the server can compute its fingerprint. It is read in memory and not saved. Only its name, type, size and fingerprint are kept, and the file cannot be rebuilt from the fingerprint. Checking a file against a proof happens in the browser, and the file is not sent.
The file’s name is shown on the certificate once you publish. If the name itself is private, rename the file before you prove it, and keep the renamed file as your original.
Text
Text is sent to DigiStamp when you create the proof. By default only its fingerprint is kept. If you tick Also store this text, and show it on the public certificate once published, the text is saved with the proof and shown on its certificate, where anyone with the link can read it.
For anything confidential, do not store the text
Who can see a proof
- A draft
- Only you, signed in, can see it.
- The certificate
- Once published, anyone with the link or QR code can open it, without signing in. That includes the title, description, stored text or file name, fingerprint and signing address.
- The list for an address
- Every published proof signed by an address is listed on that address's public page, which is linked from each signed certificate. Anyone who knows the address can open it.
- My proofs
- Only you, signed in, see your own list there.
To stop a certificate being shown, revoke the proof. See Revoking a proof.
What is on the blockchain
Stamping writes only a batch’s Merkle root to the DigiByte blockchain, after the marker prooflink.digistamp.co:b:. The title, description, text, file name and your signing address are not written there.
Blockchain data is public and permanent. Anyone can read the transaction, and nobody can delete it, including DigiStamp. Revoking a proof does not remove it.
Signing in
Signing in with Digi-ID needs no name, email or password. You sign in once, at id.digistamp.co, for every DigiStamp product, and the site sets a session cookie so it remembers you are signed in. The Privacy Policy says what else is and is not collected.
Related articles
- Creating a proofText or a file, how the fingerprint is made, what happens to your content, drafts and publishing, and the limits.
- Revoking a proofTaking a proof's certificate down: who can, what stops working, what stays on the blockchain, and reporting someone else's.
- Wallets and Digi-IDThe DigiByte wallet you need, your one Digi-ID account, the address a proof is signed with, and paying the stamp fee.