Files
unicode-tools/docs/PRIVACY-SECURITY.md
T
zemion 424605e61f
Verify / verify (push) Canceled after 0s
Release Unicode Tools 0.2.0
2026-09-02 07:50:37 +02:00

32 lines
1.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Privacy and security
Inputs remain in browser memory. There is no account, telemetry, analytics,
storage, or runtime network dependency. The application fetches only its own
versioned static catalog files and never sends search terms or inspected text.
Input is rendered as React text, not executable HTML.
Text inspection is limited to 1,000,000 UTF-16 code units, scalar decoding to
10,000 values, catalog results to 180, emoji results to 240, displayed
confusable mappings to 500, and each virtual code-chart worker request to 512
entries. Large static datasets are held in a worker and chart rows are
virtualized so the UI can remain responsive. Unihan data loads only on demand.
UTS #39 skeleton equivalence, pinned identifier status/type, mixed-script
detection, bidi/default-ignorable controls, repeated combining marks and the
displayed restriction-level estimate are review signals. They are not proof of
spoofing, maliciousness, safety, or identifier validity; applications still
need a context-specific identifier profile and policy. The comparison field
tests skeleton equivalence only and does not perform account or domain lookup.
Character glyphs come from the user's fonts, so a missing or surprising glyph
does not alter the underlying code point.
Emoji editing removes or inserts specific variation selectors and skin-tone
modifiers or joins 28 grapheme parts with ZWJ. It intentionally refuses
ambiguous selector editing inside an existing ZWJ sequence, and it does not
promise that constructed output is RGI, semantically appropriate, supported by
the current font, or rendered as a single glyph.
Developers can regenerate the catalog, but every upstream byte sequence must
match a hard-coded SHA-256 before parsing. The public release performs no such
download. Data source identities are inspectable and exportable from the app.