Skip to main content
Frequently Asked Questions
Find answers to common questions about ZeyroVault's client-side tools, privacy practices, and security model. If you can't find what you're looking for, check our documentation.
Quick Navigation
Privacy & Data
- QIs my data sent to servers?
- No. All processing happens locally in your browser. You can verify this by opening DevTools (F12) and checking the Network tab: you will see our own files and Cloudflare's cookie-less page-view ping, but no request carrying your input. Your data never leaves your device.
- QCan you recover my lost password?
- No. We have zero access to your inputs, passwords, or encrypted data. Our zero-knowledge architecture means we cannot see, store, or recover anything you process. PBKDF2 key derivation is mathematically irreversible. Always keep your own backups of passwords and important data.
Security & Cryptography
- QWhy is encryption slow with large files?
- Browser memory and JavaScript performance limitations. Unlike native applications, browsers have restricted memory access and single-threaded JavaScript execution for crypto operations. For files larger than 100MB, consider using native tools like OpenSSL or VeraCrypt.
- QDo you use third-party crypto libraries?
- No—with one honest exception. SHA-256 and SHA-1 come from the Web Crypto API built into your browser, which the browser vendors (Google, Mozilla, Apple, Microsoft) maintain. That API does not offer MD5, so for MD5 the hash and HMAC tools use a small JavaScript implementation shipped with this page's own bundle. There is no crypto service involved, and no request carrying your input leaves your browser.
- QCan I use these tools offline?
- Yes. Once you have opened a tool page while online it keeps working offline, and the app shell is cached so previously visited pages load from the offline cache. Pages you never opened fall back to an offline notice; opening a saved HTML file directly (file://) does not work because exported pages load their scripts from the site.
- QIs mobile browser supported?
- Partially. While our tools work on mobile browsers, we recommend using desktop browsers for critical security tasks. Mobile browsers may have different Web Crypto API implementations, memory limitations, and keyboard behaviors that could affect usability.
Usage & Compatibility
- QHow secure is AES-256-GCM encryption?
- AES-256-GCM is one of the standard authenticated ciphers for symmetric encryption: it is specified in NIST FIPS 197 and NIST SP 800-38D, and it appears among the AES-256 cipher suites of TLS 1.3. The limiting factor is your password, not the cipher. A 256-bit key puts brute force out of reach; a short or reused password does not. Use long, random passwords and never reuse them.
- QAre browser extensions a security risk?
- Yes, potentially. Extensions with broad permissions can access page content, including passwords and encrypted data. We recommend: 1) Using Incognito/Private mode which typically disables extensions, 2) Disabling unnecessary extensions, 3) Using a dedicated browser profile for sensitive tasks.
- QWhat browsers are supported?
- We support all modern browsers with Web Crypto API support: Chrome 90+, Firefox 88+, Safari 14+, Edge 90+. Internet Explorer is not supported. For best security, always use the latest version of your preferred browser.
- QHow do I verify the code hasn't been tampered with?
- You can verify our claims by: 1) Inspecting the source code directly in DevTools, 2) Monitoring the Network tab — you will see our own assets plus one cookie-less measurement script from Cloudflare (static.cloudflareinsights.com) and no request carrying your input, 3) Saving the page and using it offline, 4) Using a packet sniffer to confirm that nothing you paste, encrypt, or hash is ever transmitted.
Troubleshooting
- QWhy does the page ask for clipboard access?
- We only use clipboard access when you click 'Copy' buttons—to copy results to your clipboard. We never read from your clipboard without explicit user action. You can deny clipboard permissions and still use all features; you'll just need to manually select and copy text.
- QCan I use these tools for production data?
- While our tools use industry-standard cryptography, they are designed for development, testing, and personal use. For production systems handling sensitive data, we recommend using established libraries like OpenSSL, libsodium, or your programming language's built-in crypto modules that have undergone formal security audits.
- QHow does the zero-knowledge architecture work?
- Our zero-knowledge architecture means all processing happens locally in your browser. Your data never leaves your device, and we have no way to access, store, or process it. This is achieved through client-side JavaScript and the Web Crypto API, which run entirely within your browser environment.
Related Documentation
Still have questions?
If you can't find the answer you're looking for, please check our detailed documentation.