Privacy policy

Last updated: 29 August 2026

uuidly does not collect, transmit, sell or share any data about you. This policy is short because there is very little to describe.

What is collected

Nothing. uuidly has no analytics, no telemetry, no crash reporting and no accounts. It makes no network requests of any kind, so there is no mechanism by which data could reach us or anyone else, and no server for it to reach.

What is stored on your device

Four interface preferences are saved in your browser's local extension storage (chrome.storage.local) so the popup opens the way you left it:

• the UUID version you last selected;
• your formatting choices — uppercase, hyphens, and the wrapper;
• the bulk generation count;
• your theme choice — system, light or dark.

That is the complete list. The UUIDs you generate are not stored. This data stays on your own machine, is never transmitted, and is removed when you uninstall the extension. You can clear it at any time by removing and reinstalling uuidly.

Permissions

uuidly requests a single permission, storage, which is what allows the four preferences above to persist. It requests no host permissions and runs no content scripts, so it cannot read or modify any page you visit — including this one.

Third parties

None. No third-party services, SDKs, fonts or scripts are used by the extension or by this website. Nothing you do is disclosed to anyone, because nothing is recorded.

Clipboard

uuidly writes to your clipboard when you ask it to. It never reads your clipboard.

Children

uuidly is a developer tool and is not directed at children. Since it collects no data from anyone, it collects none from children either.

Verifying this

You do not have to take any of this on trust. uuidly is MIT-licensed and the source is public. The claims above are enforced by a check that runs on every change and fails the build if the extension gains a permission, a host permission, a content script or any network API. See SECURITY.md for how each one is enforced.

Changes

If this policy ever changes, the updated version will be published here with a new date, and the change will appear in the project's changelog alongside the code change that caused it.

Contact

Questions go to GitHub issues. For anything security-related, please use a private security advisory instead of a public issue.