Privacy Policy
1. Introduction
Welcome to the AES-256 Encryptor/Decrypter, a free, open-source, client-side web utility hosted as a static site. This Privacy Policy explains our practices regarding any information related to your use of the tool. Because the application runs entirely in your browser using only the Web Crypto API, we collect, store, transmit, or process no personal data, usage data, or content whatsoever. This policy exists to provide full transparency and to confirm our strict zero-data-collection commitment.
2. Information We Do Not Collect
We do not collect or have access to:
- Personal Identifiable Information (names, email addresses, IP addresses, device identifiers)
- Passphrases or plaintext — these never leave your device
- Ciphertext or any input/output — all encryption/decryption is local
- Usage analytics (page views, session duration, click events)
- Browser fingerprinting data or any telemetry
No server exists to receive data. The site is deployed statically on GitHub Pages with no backend, no database, and no logging.
3. How the Tool Operates
All functionality — key derivation via PBKDF2, AES-256-GCM encryption/decryption, random salt/IV generation, and base64 encoding — occurs exclusively client-side. Your browser’s memory holds the data temporarily during use. Closing the tab or refreshing the page clears everything. We do not use localStorage, sessionStorage, IndexedDB, or any persistent mechanism.
4. Cookies and Tracking Technologies
The AES-256 Encryptor/Decrypter does not use cookies, tracking pixels, web beacons, fingerprinting scripts, or any form of user tracking. No third-party scripts are loaded that could monitor behavior.
5. Third-Party Services
We do not integrate analytics (Google Analytics, Plausible, etc.), advertising, CDNs with tracking, or any external API calls. The only external resource is Bootstrap CSS/JS from a public CDN, which does not collect user data when used as static assets.
6. Security Considerations
Because we collect nothing, there is no risk of data breach on our side. However, security depends on:
- Choosing a strong, unique passphrase
- Safely transmitting ciphertext and passphrase separately
- Using an up-to-date, secure browser
We are not responsible for loss or compromise of data due to weak passphrases, insecure devices, or user actions after encryption.
7. Children’s Privacy
The tool is not directed to children under 13. We do not knowingly collect data from children. If you believe a child has used the service, please contact us.
8. Changes to This Policy
We may revise this Privacy Policy. Updates will appear here with a new effective date. Continued use after changes constitutes acceptance.
9. Contact
For questions about this policy, open an issue on the GitHub repository.
By using this tool you acknowledge that no data is collected or shared. Your privacy is protected by design.