1.8 KiB
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 2–8 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.