Privacy Architecture & Zero-Upload Guarantee

The Zero-Upload Invariant

Bitpeek guarantees that no user bytes, filenames, patterns, hashes, or inspection outputs are ever uploaded to any server.

When you open a file in Bitpeek:

• The browser reads the file directly from your local filesystem into client-side JavaScript memory using the standard HTML5 File and Blob APIs.
• All scalar decoding, bit toggles, transforms, structure parsing, and cryptographic hashes are calculated entirely by your device's CPU.
• Saving an edited binary triggers a standard browser download from an in-memory blob: URL.

Zero Tracking, Analytics, or Third-Party Fonts

Bitpeek deliberately excludes all third-party telemetry and tracking:

• No Google Analytics, Mixpanel, Segment, or tracking pixels.
• No remote web fonts (system monospace and sans-serif fonts are used exclusively).
• No external CDN scripts or third-party cookies.
• No artificial AI chat widgets or server-side LLM API dependencies.

Storage Isolation & Security Headers

User files and byte data are never written to localStorage or IndexedDB. The only persisted value is the user's preferred input format (e.g. hex or text), handled via a safe storage adapter that falls back to memory in private browsing mode.

Strict security headers protect the application:

• X-Content-Type-Options: nosniff
• X-Frame-Options: DENY
• Referrer-Policy: strict-origin-when-cross-origin
• Permissions-Policy: camera=(), microphone=(), geolocation=()

Local processing and privacy

The Privacy model workflow opens the same Bitpeek browser workspace. Selected file bytes, file names, pasted input, searches, edits, hashes, and comparison data are processed in local browser memory and are not sent to a Bitpeek server.

The static guide itself can be read without opening a file or creating an account.

Frequently asked questions