Privacy Policy

Last updated: November 2025

1. Information We Do Not Collect

StrongPass is designed so that your data stays on your device. We do not collect, store, or share:

2. How the Generator Works

All password generation and strength checking are performed locally in your browser using client-side code. Randomness is sourced from the browser’s crypto.getRandomValues() where available. Nothing is uploaded or stored on our servers.

The on-page “History” feature exists only in memory while the tab is open; closing or refreshing the page clears it.

3. Cookies & Local Storage

We use only functional storage (e.g., theme preference for dark/light mode). We do not use marketing or behavioral cookies.

4. Third-Party Services

We currently do not use third-party analytics or tracking. If we later add optional services (e.g., privacy-friendly analytics or ads), we will update this policy and present a clear notice with opt-out options for non-essential cookies.

5. Advertising

We may display clearly labeled ads in the future to support hosting. Advertising scripts will run separately from the generator and will never access your inputs or generated passwords.

6. External Links

Our blog may link to other sites. We are not responsible for the content or privacy practices of third-party websites. Review their policies before providing information.

7. Security

We use HTTPS (SSL/TLS) to protect connections to our site. Because StrongPass is entirely client-side, your generated passwords never leave your device.

8. Children’s Privacy

We do not knowingly collect information from children. The site is safe for general audiences and requires no account or personal data.

9. Changes to This Policy

We may update this page as the site evolves. Material changes (e.g., adding analytics) will be announced via a banner or notice, and this page will show a new “Last updated” date.

10. Contact Us

Questions about this policy? Email us at info@strongpass.tech.

Tip: For the strongest protection, use long, random passwords and store them in a reputable password manager. See our blog for guides.