Randomly

Privacy

This page is the honest version. Randomly runs generators in your browser. We also load Google Analytics on public pages. Those two facts used to sit next to a footer line that said “no tracking.” That line was wrong. This page replaces it.

What stays in the browser

When you generate a UUID, hash a string, or check an IBAN, the work happens in JavaScript on your machine. We do not receive the prompt, the output, or a copy of the clipboard. You can confirm that in the network panel: generating data does not POST your input to randomlydata.com.

Admin CMS sessions are a different story. If you log into the editor, that is authenticated traffic to our Worker and D1. Public visitors do not get that surface.

Analytics

We load Google Analytics with measurement ID G-L14E2E0T46. Google may set cookies or use similar storage to collect page views, approximate location, device type, and referral information. We use that to see which tools and articles people open. We do not sell that data.

If you block analytics scripts or use a browser that strips them, the generators still work. They do not depend on Google.

Cookies

The public generators do not need a cookie to function. Analytics may set cookies according to Google’s own policies. Cloudflare may set cookies needed to run the Worker and cache. We do not run a marketing pixel farm on these pages.

Datasets and logs

Catalog endpoints can return a random sample from published datasets (for example names or cities). Those requests hit our Worker. We may see standard request metadata (time, path, status, Cloudflare edge data). We do not treat that as a profile of you.

Contact

Questions about this page: contact.