22 lines
1.2 KiB
Markdown
22 lines
1.2 KiB
Markdown
# 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, and displayed
|
|
confusable mappings to 500. Large static datasets are held in a worker so the
|
|
UI can remain responsive. Unihan data loads only on demand.
|
|
|
|
UTS #39 skeleton equivalence and mixed-script detection are review signals.
|
|
They are not proof of spoofing, maliciousness, safety, or identifier validity;
|
|
applications still need a context-specific identifier profile and policy.
|
|
Character glyphs come from the user's fonts, so a missing or surprising glyph
|
|
does not alter the underlying code point.
|
|
|
|
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.
|