Editorial Policy

This policy explains how LetsRandomize publishes and maintains tool instructions, method guides, examples, and safety notes.

Page purpose and ownership

Every page should help a person complete a specific randomization task or understand the method behind it. Tool pages describe controls that exist on the page. Guides explain methods, comparisons, and use cases without claiming features the linked tool does not provide.

Sam Parker maintains the public explanations, checks them against the current interface and code, and records material operational changes.

Research and sources

Technical claims are checked against the implementation and, where useful, primary documentation such as browser API or programming-language references. Search results and user questions may identify missing explanations, but competing pages are not copied and are not treated as proof by themselves.

Testing and review

Interactive pages are checked for their relevant generate, copy, reset, input-boundary, mode, and result flows. Automated checks look for missing authorship, repeated boilerplate, thin pages, unsupported privacy language, and problems in built-in prompt or word data.

Dates are updated only when a page or its underlying behavior has been meaningfully reviewed. A published test describes its environment, sample size, method, and limitations.

Assisted drafting

Automated systems may help organize research, identify repeated passages, or produce a first draft. A draft is not published solely because it was generated. Claims, formulas, examples, links, and product behavior are checked against the actual page and relevant source material before release.

Claims we avoid

LetsRandomize does not describe its tools as certified, independently audited, suitable for regulated drawings, or guaranteed to produce a desired kind of fairness. Browser-side processing is described separately from technical data handled by hosting, analytics, advertising, and security providers.

Corrections

To report a factual error, broken control, unsuitable prompt, or accessibility problem, email [email protected] with the page address and enough detail to reproduce the issue. Confirmed errors are corrected in the page and reviewed before redeployment.