1. What Technologies We Use (and What We Avoid)
This Cookie and LocalStorage Policy explains how encbyt.in, operated by Encbyt Technologies ("Encbyt", "we", "us", or "our"), utilizes local browser storage technologies.
Traditional websites use third-party cookies to profile user habits, compile advertising dossiers, and monitor web navigation across external domains. Encbyt rejects this model entirely. We utilize zero advertising cookies, zero third-party marketing beacons, and zero cross-domain tracking scripts.
To operate a zero-knowledge cryptographic vault in a modern browser, we rely strictly on isolated, client-side browser containers:
- HTML5 LocalStorage: A secure local key-value store that allows technical state to persist across page reloads without transmitting payload data automatically in HTTP request headers.
- SessionStorage: Ephemeral browser memory that exists strictly for the lifespan of an active browser tab.
- First-Party Secure Cookies: Minimal, first-party HTTP cookies used solely for state protection and cryptographic session integrity.
2. Comprehensive Inventory of Stored Items
Every single item stored by Encbyt on your machine is strictly technical, functional, and necessary to maintain your encrypted session and enable resilient file transfers:
| Storage Medium | Key / Identifier | Category | Technical Purpose & Lifespan |
|---|---|---|---|
| LocalStorage | encbyt_session_token |
Strictly Necessary | Stores an ephemeral, cryptographically signed token to keep you authenticated across browser refreshes. Cleared upon manual sign-out. |
| LocalStorage | encbyt_transfer_state |
Functional | Preserves upload and download byte offsets and segment IDs to power the Pause & Resume transfer feature. Cleared automatically upon transfer completion. |
| LocalStorage | encbyt-theme |
Preferences | Stores your interface aesthetic preference (light or dark mode). Persists until modified or cleared. |
| SessionStorage | encbyt_crypto_context |
Strictly Necessary | Temporarily caches in-memory cryptographic salt references for the active vault session. Destroyed instantly upon closing the tab. |
| Cookie (1st Party) | __Host-encbyt_csrf |
Security | A hardened, SameSite=Strict, HttpOnly token deployed strictly to prevent Cross-Site Request Forgery (CSRF) attacks against API endpoints. |
3. What Encbyt Will NEVER Deploy
To defend your absolute digital privacy, Encbyt adheres to strict mathematical and engineering boundaries:
- No Third-Party Cookies: We do not partner with advertising networks, commercial telemetry brokers, or retargeting pixels.
- No Social Media Beacons: We do not embed Meta Pixels, Google Tag Manager scripts, LinkedIn Insight tags, or X tracking pixels.
- No Device Fingerprinting: We do not execute canvas fingerprinting, WebGL shader probes, or audio API profiling signatures to identify your hardware across other domains.
- No Plaintext Key Storage: Your master password and 24-word recovery phrase are never written to LocalStorage, SessionStorage, or cookies in plaintext.
4. User Control & Browser Management
You retain full authority over the storage items housed within your local browser environment. You can audit, inspect, or wipe all Encbyt storage keys at any time via your browser's native developer tools:
F12 → Application → Local Storage / Cookies → encbyt.in
5. Policy Inquiries & Corporate Information
For questions or verification regarding our client storage architecture, contact our compliance desk:
Operating Entity: Encbyt Technologies
Headquarters & Operations: Dist- Pali, Rajasthan, India
Data Protection Desk: [email protected]
General Inquiries: [email protected]