Plain-language data practices

Privacy policy

Generator choices and results stay in your browser. This policy separately explains the technical, measurement, advertising and consent data used by the current service.

Last reviewed:

Since 2026-09-03, the tool_success event measures completed tool actions. Only fixed tool and action labels are added to Google Analytics; no input, output, settings, file names or content-derived identifiers are included. Collection follows the existing Google tag and consent settings.

Generator data stays local

The chosen letters, exclusions, custom sets and generated results are processed in the browser. The generator does not send them to the application server, and it does not place them in the URL.

Chosen letters, exclusions, custom sets, results and the optional tool history are not sent to Analytics and are not used as event content, URL content, parameters or custom dimensions. Standard page measurement remains separate from these tool values.

Optional browser storage

If history is enabled, up to 300 recent draws may be kept in local browser storage. It contains generated letters, pool size, the repeat rule and a time marker, not the custom set or exclusions. It stays on the device and is not synchronized.

Clear History removes that tool record. Browser site-data controls can remove all storage for this site, including both tool history and any Google storage described below.

Google Analytics 4

Google Analytics 4 is active to understand page visits and engagement and to improve the service. Depending on consent and configuration, Google may process a cookie or device identifier, IP-derived network and approximate-location information, browser and device details, page URL and title, referring source, approximate region and engagement signals.

The integration uses standard page-view and automatically collected engagement measurement. It deliberately adds none of the generator values listed above to Analytics events, URLs or dimensions. No session-replay service is used.

Technical delivery logs

Ordinary delivery and security logs may contain an IP address, user agent, requested path, timestamp, response status and technical error information. Generator values are separate: they are not part of application requests or deliberately written to those logs.

Nginx access and error logs rotate daily and retain up to 14 rotations. Other operational system logs may follow different technical lifecycles, so no single overall retention period is promised for every system log.

Choices, questions and limits

After making a Google choice, use the “Privacy and cookie settings” control when it is displayed to reopen the message and change or withdraw that choice. Clearing this site’s cookies and storage in the browser is a factual fallback and may also remove local tool history.

Publisher identity and the contact channel are listed in the Terms of use. This policy is factual product information, not legal advice or a certification, and it does not waive mandatory rights.

Read the cookie policy