Last updated: February 24, 2026

Overview

BitProof creates verifiable timestamp and archive proof bundles. This policy explains what data is processed when you use the website and browser extensions.

Data Processed for Core Functionality

Website: File Timestamp Flow

For file timestamping, hashing happens in your browser. Only the SHA-256 hash and optional filename/size metadata are sent to the BitProof API to generate a proof.

Website/Extension: Web Archive Flow

For web archive requests, the submitted public URL is sent to the BitProof API so the server can capture screenshot, HTML, and PDF artifacts and generate the archive proof bundle.

Browser Extension Settings

The extension stores user settings (for example, configured API endpoint) in browser extension storage.

What BitProof Does Not Collect

Storage and Retention

BitProof is designed as a stateless service. Generated proof bundles are returned to the user for local storage. The website local Proof Library is device and browser scoped.

Temporary files used during archive processing are deleted after proof generation. Standard operational server logs may include limited request metadata for reliability and security operations.

Third-Party Services

BitProof uses OpenTimestamps and Bitcoin network data for proof anchoring and verification. Hosting and infrastructure providers may process network-level metadata as part of normal service operation.

User Controls

Contact

For support or privacy questions, use: https://www.bitproof.org/faq.html

Policy Updates

This policy may be updated as BitProof evolves. Material changes will be reflected by updating the date at the top of this page.