Normal Chromium profile data such as history, cookies, cache, site permissions, and session state stays within the relevant profile boundary.
Privacy and local data
Local data is classified before release.
NATIVE038 inventories browser-profile, cache, Mission, evidence, diagnostic, download, policy, and support data. The goal is to define what exists, where it belongs, how it is retained, and what must never enter evidence or support output.
Local-data classes
Different data requires different handling.
Final behavior remains subject to native runtime and packaging proof. This page describes current source-level privacy rules, not a released binary’s final retention controls.
Mission structure, recipes, pane roles, timeline metadata, notes, and user-created operational context require profile-scoped handling.
Evidence output must be deliberate, reviewable, and redaction-aware. It must not silently absorb browser secrets.
Support output is planned to be metadata-only and to include redaction reporting rather than private browsing payloads.
Downloaded files remain user-controlled files and must not be silently included in support or evidence bundles.
Active policy truth may be reported without exposing credentials or unrelated private content.
Absolute exclusions
Secrets do not belong in evidence or support output.
The source rules explicitly prevent the following categories from entering evidence or support bundles.
CookiesSession tokensPasswordsCredentialsAuthorization headersRefresh tokensAPI secretsRaw browser storageCopied authentication data
TAHAI services
The browser is not the authority.
Safe references and authorized links may connect users to TAHAI Portal, IT Docs, PSA, or other services. The browser does not become an authentication authority, credential vault, or provider-connector host.
Authorization boundary: IT Docs and PSA operations remain server-authorized. Local IDs and Mission references never grant access by themselves.
Status
Final privacy controls require runtime proof.
Retention choices, deletion behavior, profile migration, support-bundle generation, and installed-package behavior will be finalized and documented through the remaining passes.