Corrections Policy
Report tool, translation or content errors and understand how ClockTools reviews, tests and discloses corrections.
Last updated: September 14, 2026
This policy covers every ClockTools tool, language, guide and supported export. We assess reports against evidence and reproducible behavior. A preference or an unexpected random outcome alone does not establish a defect.
API keys and random secrets
For generator reports, share the format, size, quantity and a synthetic example, never a real secret. Encoding, length, entropy or export defects receive regression tests; a material correction should explain whether affected keys must be regenerated and replaced in the consuming application.
What We Review
Report incorrect calculations, misleading results, broken workflows, translation errors, accessibility barriers, inaccurate exports, outdated sources or privacy disclosures. Include missing limitations when they could change how someone uses a result.
Send A Useful, Safe Report
Email [email protected] with the URL, language, selected mode, steps, expected result and actual result. Include units, timezone, browser, device and observation time when relevant. A small non-sensitive example, redacted screenshot or authoritative source helps us investigate.
Do not send passwords, API keys, private documents, precise personal location or confidential links. Replace real names and account details with safe examples. We do not need access to your account to receive a report.
How We Handle Corrections
The publisher reviews the evidence and tries to reproduce the issue. When a defect is confirmed, the correction process includes a fix, a regression check and review of affected guidance, related tools, translations and exports. Incomplete reports may need clarification; not every requested change is a correction.
Priority And Interim Warnings
Security, privacy and materially misleading results take priority, followed by broken workflows, accessibility and factual errors. Minor wording and styling follow. A serious unresolved defect may require a warning or temporary removal of the affected feature. We do not promise a fixed response or resolution time.
External Data Or A Tool Defect?
A provider can change a record, delay an update or stop responding. That is different from ClockTools misreading the record or presenting stale data as current. Reports should identify the source and observation time. We can correct our handling and wording, but cannot alter a registry or a provider's status report.
What We Disclose
Material corrections should identify what changed and which result or guidance was affected, with a correction note where needed and a meaningful update date. Relevant product changes belong in What's New. When earlier outputs may be wrong, the notice should explain whether users need to recalculate or regenerate them.
Minor spelling, formatting or non-substantive clarity edits may be made without a separate notice. We do not change evidence merely to preserve an earlier conclusion. Previously downloaded files, shared screenshots and third-party caches do not update automatically.
Security And Privacy Reports
Send security concerns privately to [email protected]. Describe the affected page and impact without sending credentials or another person's data. Avoid public exploit details while a report is being assessed. Any public correction notice should explain the user impact without exposing sensitive operational information.
Rights And Follow-Up
For privacy or rights requests, identify the material and your relationship to it without unnecessary personal data. If a problem persists after a change, send the earlier report context and new reproduction steps. Guidance and fixes remain open to revision when better evidence becomes available.