Skip to main content
MakeMyPasswords

Privacy Policy

Last updated: April 15, 2026

The short version

MakeMyPasswords has no backend. There is no server receiving your generated passwords, dice rolls, addresses, or any other output. Everything runs in your browser using JavaScript. When you close the tab, the data is gone.

We do not create user accounts, store cookies for our own purposes, or maintain any database of user activity.

What data do we collect?

From the product itself: nothing. No form submissions, no API calls, no telemetry. The generators run entirely client-side.

Cookie consent choice: If you interact with our cookie consent banner, your choice (accept or decline) is saved in your browser's localStorage. This is not sent to any server — it stays on your device and controls whether third-party scripts load.

Analytics

We may use a third-party analytics service (such as Google Analytics or Plausible) to understand which pages are visited and how the site is used in aggregate. Analytics scripts are loaded only after you accept the cookie consent banner. If you decline, no analytics scripts run.

Analytics data is aggregated and anonymous. We do not correlate analytics with individual users, and we never track the content you generate.

Advertising

We may display ads via Google AdSense to cover hosting costs. AdSense is loaded only after you accept the cookie consent banner. Google may use cookies to serve ads based on your browsing history — this is governed by Google's Privacy Policy, not ours.

If you decline the cookie consent banner, no ad scripts load and no ad-related cookies are set.

Third-party services

The site is hosted on Vercel. Vercel may collect standard server logs (IP address, user agent, request path) as part of its infrastructure. See Vercel's Privacy Policy for details.

Your rights

Since we don't collect personal data, there is nothing to request access to, correct, or delete. If you have questions, open an issue on our GitHub.

Changes to this policy

If we change this policy, we'll update the date at the top. Fundamental changes (like adding server-side data collection) would be announced prominently on the site.