INBOX TRIAGE PRIVACY AND LOCAL DATA — VERSION 1.0.0

Inbox Triage does not send your Gmail data, OAuth credentials, or application
data to CzerTek servers. It communicates directly with Google services and
stores application data locally.

Inbox Triage is a proprietary, free, unsupported, self-service CzerTek utility.
You own and manage your Google Cloud project, Desktop OAuth client and account.
There is no shared CzerTek OAuth client, OAuth/token backend, hosted sync,
analytics, advertising, telemetry, crash reporting or update service. Technical
support is not promised. Google receives OAuth credentials and Gmail requests
needed for the features you authorize; Google's own terms and policies apply.

Google access
The app requests openid, email, profile and
https://www.googleapis.com/auth/gmail.modify. It reads Google subject ID and
email to identify and validate the connected account. Gmail requests list
matching message IDs and read metadata (From, Subject, Date, labels, snippet,
thread ID and size estimate) for previews. Snippets can contain message content.
Full message bodies and attachment contents are not downloaded. The app can
create/apply/remove labels, archive, change read state and move messages to Trash.
It does not permanently delete Gmail messages, send mail or download attachments.
Gmail modify permission authorizes more capabilities than this app implements.

Authorization and credential protection
Sign-in opens Google in your default browser. A temporary listener on a random
127.0.0.1 port receives the callback using state and PKCE. Connection times out
after two minutes and can be cancelled. Google Cloud setup links open only the
Google Cloud Console in the default browser. Gmail HTML and remote images are
not rendered. The client secret exists in the local form while you enter it and
is sent to Google during OAuth. Client ID is stored locally in plaintext.
Stored client secret and refresh token use Electron safeStorage/Windows user
protection. Access tokens are held in main-process memory, with expiry and
refresh managed by Google's library; the app does not persist access tokens.
Windows protection is not a guarantee against software running as your user.

What persists
Normally %APPDATA%\Inbox Triage contains the SQLite database, settings,
encrypted credentials, account identifiers, job/rule names and Gmail queries,
schedules, selected message IDs, statuses, counters, and minimal audit events.
Preview subjects/snippets/senders are not written to message metadata tables.
Some unused schema tables may contain data from future/other versions or restored
backups. Query and rule names can contain user data. Database and files are not
encrypted as a whole. Electron also creates profile/cache files. Settings shows
the actual location, which may differ if a custom profile is selected.

Diagnostics and backups
Application diagnostic logging uses fixed lifecycle messages, not API payloads,
tokens, secrets, addresses, subjects, snippets, Gmail IDs or queries. User-visible
errors and new audit records do not contain raw Google errors or query contents.
Existing pre-v1 logs or external backups may still contain older data. Database
backups include local user data and protected credential ciphertext; they are
SQLite-consistent snapshots, not separately encrypted archives. Windows backups,
cloud-synced folders, user-selected network destinations and manual sharing can
copy data elsewhere independently of CzerTek. Protect and delete those copies
yourself. Credentials copied to a different Windows profile may not decrypt.

Disconnect Google Account
Disconnect invalidates the session, aborts tracked API requests, drains active
work, disables that account's schedules, interrupts queued work, attempts Google
revocation, and removes local active-account refresh credentials and saved OAuth
client configuration. An already-sent Google request may have completed; it
cannot be undone by disconnect. Revocation failure is shown, with instructions
to revoke access in your Google account. Jobs, rules, account history, settings,
logs and backups remain. SQL deletion is not forensic erasure of old files/WAL
or external backup copies. Reconnect and review before resuming jobs/rules.

Delete Local Data / Reset Inbox Triage
Available before connection and in Settings. Type DELETE LOCAL DATA and confirm
the Windows dialog. The app disconnects, closes SQLite, clears Electron browser
storage, cache and authentication state using session APIs, and removes its own
database/WAL/SHM, settings, logs and internal backups/exports. It then creates a
fresh database and reloads at the license and first-run setup. Empty Chromium
profile scaffolding may remain. Unknown/unrelated files in the profile are preserved.
External backups/exports, Google browser cookies and files outside that profile
are not removed. No Gmail messages are deleted. If revocation fails/offline,
revoke the project's access at Google yourself. Reset is ordinary deletion, not
secure disk wiping. If reset fails, it displays an error; close the app and
remove its application-data folder manually after checking the actual path.

Uninstall
The Windows uninstaller preserves application data. Reset before uninstalling,
or fully exit/uninstall and manually remove the actual application-data folder.
Separately delete external backups and revoke Google access as necessary.
