Files
log-tools/public/docs/PRIVACY-SECURITY.md
T
2026-09-01 14:43:03 +02:00

10 lines
2.0 KiB
Markdown

# Privacy and security
Log files, pasted text, normalized records, filters, redaction previews, and exports stay in browser memory. There are no accounts, analytics, telemetry, persistence, uploads, remote parsers, or runtime third-party assets. Explicit source navigation is outside the processing flow. Clearing or closing the workspace releases application references but cannot promise forensic erasure from browser or operating-system memory.
Files are streamed rather than buffered whole. The file byte gate is eight GiB, scans stop at five million physical lines, and one framed line retains at most 256 KiB. A normalized raw/message string retains at most 32 KiB, one flattened field at most 4 KiB, and the preview stops at 10,000 nonblank records or 32 MiB of retained characters. Pasted input is limited to 2 MiB. JSONL parsing limits text, depth, values, dangerous keys, flattened fields, and field lengths. Unique aggregation keys, hourly buckets, fields, rendered rows, export rows, and export text are separately bounded and truncation is surfaced.
ANSI escape sequences are stripped; other control characters are replaced; HTML and URLs render only as text. No `dangerouslySetInnerHTML`, script evaluation, regex input field, or network enrichment exists. Auto-detection and parser results are syntactic interpretations, not authenticity checks. A malicious value can still be misleading when copied into another system.
Redaction is a previewable convenience, not a data-loss-prevention guarantee. Built-in patterns can miss unusual representations and can redact false positives. Stable pseudonyms use a non-cryptographic hash and user-selected salt and may be reversible by guessing. Redacted values retain the same per-value caps as parsed values; expansion past a cap is truncated and reported. CSV export mitigates common formula injection by apostrophe-prefixing cells whose trimmed value begins with `=`, `+`, `-`, or `@`; consumers should retain that defence when transforming the file.