Privacy Policy
Effective Date: October 19, 2026 · Version 1.0
At 0Stamp (0stamp.com), your privacy is not a policy setting or an afterthought—it is the foundational constraint of our system architecture. We have deliberately engineered our software so that we cannot inspect, collect, or store your documents, even if requested or subpoenaed.
The Zero-Upload Guarantee
0Stamp operates with a strict zero-upload architecture. We do not own, operate, or maintain any backend file processing or storage servers. When you drop an invoice, receipt, or agreement into 0Stamp:
- ✓ All PDF parsing, text extraction, and page rendering execute in your browser using
pdfjs-distWebAssembly. - ✓ Stamp composition, custom vectors, dates, and circular seals are rendered via client-side HTML5 Canvas.
- ✓ Document compilation into final downloadable PDFs runs purely in browser memory using
pdf-lib.
1. Zero Document Telemetry
We transmit zero bytes of document data across the internet. When you process a document with 0Stamp:
- We never receive or read invoice totals, bank account numbers, SWIFT/IBAN codes, tax IDs, or company names.
- We never read client addresses, employee names, or itemized line items.
- We never extract or upload camera EXIF metadata, GPS locations, or image timestamps from receipt scans.
- We never create temporary server caches or cloud copies.
2. Local Storage Disclosures
To provide a seamless workflow between browser refreshes, 0Stamp saves non-sensitive interface preferences directly to your browser's local sandbox (localStorage):
| Key Name | Purpose | Storage Location |
|---|---|---|
| 0stamp_sig_mode | Stores preferred signature mode ('type' or 'draw') | Local browser only |
| 0stamp_sig_text | Optional custom signer name for stamp metadata | Local browser only |
| 0stamp_sig_font | Selected cursive typography style | Local browser only |
| 0stamp_sound_muted | Haptic sound mute toggle state | Local browser only |
You can clear these preferences at any time by clicking "Clear Signature" inside the workbench, or by clearing your browser storage for 0stamp.com.
3. Hosting & Network Edge Infrastructure
The static assets (HTML, CSS, JavaScript, and fonts) for 0Stamp are served via Cloudflare edge infrastructure. When your browser requests web assets from Cloudflare, standard ephemeral routing metadata (such as your public IP address and browser User-Agent) is processed to fulfill the HTTPS connection and defend against automated DDoS attacks.
Cloudflare operates as a content delivery network (CDN) only; it does not receive, intercept, or handle any document data processed inside the web application island.
4. GDPR, CCPA & Enterprise Audit Compliance
Under the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA), processing personal data requires lawful grounds and rigorous protection measures.
Because 0Stamp employs a zero-knowledge, zero-retention model:
- No Data Controller / Processor Burden: We never act as a data controller or data processor for your documents because your files never reach our servers.
- Immune to Server Breaches: In the impossible event of a server compromise, no document data can be exposed because no document data was ever stored.
- Right to Erasure (RTBF): No deletion requests are required. Simply clearing your local browser cache completely deletes any locally stored preferences.
5. Contact Our Privacy Team
If you have questions about our zero-upload architecture, security audits, or compliance policies, reach out to our team: