PRIVACY · UPDATED SEPTEMBER 26, 2026
RNGdle Tool privacy: what we store and what we do not
This RNGdle Tool privacy notice covers the whole toolkit. The application does not require an account. Number analysis is sent to the project server for calculation and submitted numbers are not stored in the application database.
Local history and preferences
Recent analyzed numbers and your analytics preference are stored in your browser on this device. Clear history from a tool page or clear this site’s browser data. Clearing browser data also resets your analytics choice.
Optional analytics
With your permission, we use Google Analytics 4 to understand visits and Microsoft Clarity for heatmaps and session recordings, helping us improve navigation and usability. These services can process page URLs, browser and device information, interactions, online identifiers and connection information, and can use cookies after you accept.
The Google Analytics and Microsoft Clarity scripts do not load until you choose “Allow analytics”. You can decline and keep using every tool, or withdraw permission using “Analytics preferences” in the footer. Withdrawing stops tracking by reloading the page and removes accessible first-party analytics cookies. We honor supported Global Privacy Control and Do Not Track signals. Development, preview and visits opened with URL query parameters do not start analytics.
Tool content, including inputs, results and local history, is marked for masking in Clarity recordings. After consent, Google Analytics may also receive limited event categories: which tool was used, whether an action started, succeeded or failed, the action category, and clicks to related tools or copy-link actions. We do not send submitted numbers, pasted text, share text, full URLs or free-form error details as custom events. Advertising consent is denied and Google advertising personalization signals are disabled. Microsoft and Google operate their own systems; see the Microsoft Privacy Statement and Google Privacy Policy for their processing and retention practices.
The daily game
The play page runs the daily number game built by this site inside a frame served from this same domain, so no third party is involved and loading it requests nothing from anyone else. The game keeps a random seed and your roll history in local storage on this device, so today's roll survives a refresh; pressing reset inside the game, or clearing this site's browser data, removes both.
When you roll the daily number, that number and its score are sent to the project server so the page can show the best roll counted for the day, a short board of the day's best rolls, how many rolls have been counted and how many claps the day received. Only those aggregates are stored — numbers with scores, a count and a clap count, per day — with no identifier of any kind: no account, no cookie, no address and no per-visitor row, and the number is not linked to anything else you did. The game's settings panel turns that contribution off, after which nothing is sent. Practice rolls are never sent, and the analysis tools keep sending only the number you type in.
External images
Some directory badges in the footer are images hosted by other websites. When your browser loads those images, the image providers receive your IP address and standard request information, including that the request came from rngdletool.com. These image requests are separate from the optional analytics choice.
Operational data
Cloudflare serves this site and automatically adds a measurement beacon to its pages (Cloudflare Web Analytics). It reports aggregate page views, referrers, load timing and coarse device and country information to this site’s own measurement endpoint, sets no cookies and no browser storage, and, per Cloudflare, does not log query strings. It runs whether or not you allow optional analytics.
Hosting services may also process connection and security logs. The application API logs endpoint name, response status and processing time; these application logs do not include submitted numbers or share text. Analytics choices do not disable essential service or security processing.
Contact
For privacy questions or requests, email [email protected]. Mail is forwarded through Cloudflare to our support inbox. We use your message and reply address to handle your request. Please do not include sensitive information that is not needed for your request.
What this RNGdle Tool privacy notice does not cover
This RNGdle Tool privacy notice covers this website only. It does not describe what RNGdle itself collects when you play the game, because that happens on the game's own site under the game's own policies — including when the game is loaded in the frame described above. It also does not cover third-party sites we link to, such as directory listings or the sources cited in our guide; each of those has its own notice.
Two practical points follow from that boundary. First, clearing this site's browser data removes your stored history, favorites and analytics preference, but it does not touch anything held by the game. Second, if you email us, your message is handled by our support inbox and the forwarding provider described above; we keep it only as long as needed to answer you and to keep a record of the request.
Changes to this notice
When this notice changes materially, the date at the top of the page advances and the sitemap entry for this URL is updated at the same time. If a change affects what optional analytics can collect, the consent choice is re-presented rather than assumed.
What is stored on the server
Analysis requests send the number you typed to the project server so it can be computed. The number is not written to the application database, and the server log line for a request records only the endpoint name, the response status and the processing time in milliseconds. It does not record the submitted number, the text you pasted into the share decoder, your user agent, your IP address or the full request URL.
The API does keep a short-lived request count per client address so that a flood cannot exhaust the service. That address is used only as a counter key inside the running process, it is never written to the log or the database, its counters expire as they age out, and they disappear when the process restarts. No request is stored, profiled or shared; the count exists so that one abusive caller cannot slow the site down for everyone else.
Local history, favorites and your analytics preference are different: those live in your browser on this device and are never sent anywhere. Clearing them is described above, and clearing them has no effect on the game.
Cookies in practice
Before you make a choice, this site sets no analytics cookies of its own and loads no analytics vendor script. If you choose “Allow analytics”, Google Analytics may set its first-party cookies and Microsoft Clarity may set its own, which is what allows a returning visit to be recognised in their reports; advertising consent stays denied in the same request. If you withdraw, the withdrawal stops tracking, removes the first-party analytics cookies this site can access, and reloads the page so no vendor script keeps running.
The Cloudflare measurement beacon described under operational data is cookieless and writes nothing to browser storage, so it behaves the same way whether you allow optional analytics or not. Nothing else on the site sets a cookie.
Your choices
There are four things you can do, and all of them are available without contacting anyone. Decline optional analytics and keep using every tool. Accept and later withdraw using “Analytics preferences” in the footer. Clear this site's browser data to remove local history, favorites and the stored preference. Or write to the support address above for a question about data handling.
Supported Global Privacy Control and Do Not Track signals are honoured: when a browser sends one, analytics stays off regardless of any stored preference, and the preferences panel explains why rather than silently doing nothing.
Common questions
Do you store the numbers I analyse?
No. A number is sent for calculation and is not written to the application database. Recent numbers and favorites are kept by your own browser so you can reuse them, and they are cleared whenever you clear this site's data.
What exactly does the API log contain?
Endpoint name, response status and processing time. That is enough to notice errors and slow responses and not enough to reconstruct what anyone analysed, which is the point of keeping the fields that narrow.
Can I use the tools with analytics blocked?
Yes. Every tool works with analytics declined, blocked by an extension, or disabled by a privacy signal. There is no feature that depends on accepting analytics.
Does declining affect the game?
No. This site has no connection to your game account, so nothing here — including an analytics choice — can change what the game does.