Summary
Local-first by design.
TAHAI Web Services does not intentionally collect, sell, or transfer user browsing history, credentials, browser-storage contents, Mission files, or personal telemetry from TAHAI Browser. The browser may store normal application and browsing data locally on the user’s device as needed to provide the features the user chooses to use.
Normal browser data
Profiles, preferences, cache, cookies, history, downloads, permissions, session state, and site storage may be retained locally in the same manner expected of a desktop browser.
Mission data
Mission names, pane roles, layouts, notes, runbook state, evidence metadata, and local exports may be stored on the user’s device when those features are used.
Network activity
The browser connects to websites and services requested by the user or configured by the operator. Third-party destinations are governed by their own policies and account controls.
No secret harvesting
TAHAI is not designed to scrape cookies, authorization headers, credentials, tokens, browser-storage dumps, or form contents into Mission evidence or support output.
Operational features
Evidence should be useful without becoming a leak.
Mission Control and evidence workflows are designed around explicit capture, metadata-first records, redaction awareness, and deliberate export. Users remain responsible for reviewing any content they choose to capture or share.
Explicit actions
Capture, export, synchronization, and handoff actions should occur only after a clear user request. TAHAI does not silently publish Mission data to third-party services.
Redaction posture
Secret-like values, credentials, private keys, authorization material, and other sensitive classes should be warned on or removed before a sanitized export.
Integrations
Future IT Docs or PSA connections remain authorization-bound integrations. The browser is not a secret vault and does not store third-party integration credentials in Mission files.
User control
Users can remove the application and local data using normal operating-system controls. Managed environments may apply separate retention or policy requirements.
Contact
Questions or concerns?
Privacy and security questions may be sent to [email protected]. Security reports should avoid including live credentials, private keys, customer secrets, or unnecessary personal data.
Release truth: The current Microsoft Store edition and the next-generation native Windows build are separate release lanes. This policy page does not represent unfinished native functionality as already shipped.
