Local workflow
Text estimates, redaction and browser timers: practical limits
Local processing avoids an upload, but does not make an estimate exact or a pattern exhaustive. Keep the original, inspect changes and choose explicitly what leaves the page through Copy or Download.
Content updated: · Maintained by Hung Chi-Hsueh · corrections
A match is a candidate, not verified personal data
Redaction patterns identify candidate emails, phones, addresses or other text shapes. They can miss real sensitive data and match harmless text. Select patterns deliberately, review the entire result and treat custom regular expressions as bounded computations. This is not identity validation, legal compliance or irreversible anonymization; context can still identify people.
Environment parsing never runs interpolation or shell commands. Values are hidden by default, with a separate deliberate reveal or secret-bearing export. A keys-only report is safer to share, but key names can still disclose infrastructure. Clearing cannot erase the clipboard or an exported file.
State what each estimate actually counts
English readability scores use heuristic words, sentences and syllables, not a comprehension test. Code-line counts depend on a selected language and a small lexical model; strings, templates and comment syntax can be ambiguous. Unicode characters, graphemes, code units and UTF-8 bytes are different quantities.
Password keyspace reports an upper bound from the actual alphabet size and length, not measured entropy or a crack-time guarantee. Requiring every character group and the generator's sampling distribution affect entropy. For byte tables, ASCII means 0–127; the separately labeled 128–255 view explicitly uses Windows-1252, not a universal extended ASCII encoding.
A browser timer is not a scheduling service
Duration timers use elapsed monotonic time; dated countdowns use an explicit UTC instant. Browser background throttling, sleep, closed tabs, clock changes and denied notifications can affect when an alert becomes visible. Settings and timers are not persisted. Notifications require a deliberate request and can be denied by the browser or operating system.
Do not use these timers for medical, industrial, legal or other safety-critical alarms. A world clock uses the browser's IANA timezone data; DST and date labels can differ with outdated platform data. Compare the actual instant and timezone rather than assuming an offset stays constant.
Data provenance