Privacy Policy

Random Generatr is the publishing name used by the project at saguiitay/randomtools3 on GitHub. See publisher information. A verified legal operator identity and private contact address have not yet been supplied on this page.

You can generate and copy individual results without an account. Signing in, saving work, submitting feedback, and allowing analytics introduce different data flows, described below. Do not use saved notes, custom-generator inputs, or feedback to store passwords, confidential records, or sensitive personal information.

Clerk handles authentication, including the sign-in information you provide and your account identifier. The application uses that identifier to load and save your work in server-side Redis storage:

• Saved values: text, source generator, subtype when available, saved-item identifier, and timestamp.
• Recently visited generators and visit timestamps.
• Custom generators: names, descriptions, input lists, patterns, formatting choices, and creation/update information.
• Revision and operation identifiers used to detect conflicts and avoid applying the same save twice.

Older saved work may also remain in Clerk user metadata after migration to Redis. Deleting a value in the current interface does not establish that legacy copies or provider backups have been erased.

These features associate work with your account; they are not a public profile or a promise of confidential document storage. Review Clerk's privacy policy for its own processing.

A save awaiting server confirmation is not yet an account backup. The browser keeps recovery data so failed operations can be retried:

• Session storage retains one selected value through sign-in in the same tab. It can be saved to the account that completes that sign-in.
• Local storage keeps account-bound pending saved-value changes, recent-history caches and pending updates, and custom-generator drafts. Older local saved values may await migration.
• Signed-out recent-generator history uses a browser cookie with a seven-day expiry. The consent-preference cookie has a one-year expiry. These are cookie settings, not server-wide retention periods.

Signing out or changing accounts hides account-bound work in the interface; it does not erase browser recovery copies. Anyone with access to the browser profile may be able to inspect local data. Clearing site data removes local copies and can lose unsynced work, but does not delete saved server data.

The generator feedback form sends your rating, optional text, generator and subtype, and a submission identifier to the server. Redis stores the submission with a timestamp and updates rating totals. This helps identify output problems. The form does not require an account and is not a private support channel. The current feedback store does not set an automatic expiry.

Generation and export requests send the selected source and options to the server. Custom-generator previews also send the lists and patterns needed to produce results. Ordinary batches are not added to an account history of every generated name. Network requests still reach the hosting and service providers, which may process IP addresses and operational logs; their logging and retention settings require owner verification.

Google Analytics loads after analytics consent and records page visits and interactions such as generation, copying, saving, downloads, and affiliate-link clicks. Google may process browser, device, referral, and approximate-location information. See Google's privacy policy. Third-party sites opened through links handle your visit under their own policies.

Use Cookie Settings at the bottom of the site to review your choices. Analytics, marketing, and personalization preferences default to off until accepted:

• Functional storage: Account sessions, preferences, recent history, and pending work support the features described above. Rejecting analytics does not erase these records.
• Analytics Cookies: Help us understand how visitors interact with our website.
• Marketing preference: Controls advertising storage and personalization consent signals. Its presence does not mean a paid subscription or ad campaign is active.
• Personalization preference: Records your personalization consent choice.

Withdrawing analytics consent stops the site's future consent-gated tracking. It does not delete data already sent. Browser cookie and site-data controls are separate; blocking storage can prevent sign-in or saving from working.

The current saved-work and feedback stores do not define a general automatic expiry. No verified schedule for provider backups, legacy Clerk metadata, operational logs, or analytics deletion is published here. The owner must establish and confirm those schedules. Neither signing out nor deleting a sign-in account should be assumed to erase all of these separate copies.

The application currently provides these controls:

• In Favorites, copy or export the shown values as TXT or CSV. Clear the search first to include the whole list. Pending values can appear in an export; downloading does not confirm server sync.
• Delete individual saved values or use Clear All, then wait for confirmation. A failed or pending removal still needs retry.
• At My Generators, copy important lists and patterns before deleting a custom generator. This page does not offer a complete account-data export.
• To discard local recovery copies, copy important work first, close other site tabs, and use your browser's site-data controls for randomgeneratr.com. This may sign you out.

Privacy rights depend on the law that applies to you. For account-history removal, legacy copies, feedback deletion, or a broader access request, use the contact instructions to ask for a private channel. The linked GitHub issue tracker is public: do not include personal data or the request details. A verified private rights-request process remains an owner/legal requirement; no response time or complete-erasure promise is made here.