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—zero requests are made after the page loads. 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. We only use the native Web Crypto API built into modern browsers. This API is maintained by browser vendors (Google, Mozilla, Apple, Microsoft) and has undergone extensive security auditing. No external JavaScript crypto libraries are loaded.
- QCan I use these tools offline?
- Yes. Once you load the page, it works completely offline. You can even save the HTML file and open it directly from your computer (file:// protocol). No internet connection is required after the initial load.
- 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 the industry standard for symmetric encryption, used by governments and financial institutions worldwide. With a strong password, it would take billions of years to crack using current technology. The security depends entirely on your password strength—use long, random passwords.
- 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 to confirm no unexpected requests, 3) Saving the page and using it offline, 4) Using a packet sniffer to verify no data transmission.
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.
Related Documentation
Still have questions?
If you can't find the answer you're looking for, please check our detailed documentation.