Privacy policy

TRIUMPH is operated for its owner's personal use. This policy describes how the application processes information from accounts the owner chooses to connect.

Information accessed

Google authorization is account-specific and read-only. Gmail access includes message headers, recipients, subjects, message bodies, labels and available attachments. Google Drive access includes file metadata and readable file or document content. Google Calendar access includes calendars, event descriptions, participants, schedules and updates. Some unsupported formats, oversized files or scanned documents may be retained as original files without searchable text; coverage limits are recorded.

The owner may also authorize other sources, including Microsoft mail, files, calendars and contacts, device activity, browsing observations, goals and imported bank statements. Connecting one source does not authorize access to another source.

Purposes

Information is used to maintain a private searchable archive, show where records came from, reconcile supported financial evidence, and generate provisional personal context with source citations. A received message does not prove that an action occurred; a calendar event does not prove attendance. Generated interpretations can be incomplete or wrong.

Storage and access

Collected payloads, retained original files and generated reconstructions are encrypted by the application in the owner's private infrastructure. Operational metadata, such as source identifiers and timestamps, is not all encrypted. OAuth credentials are held in separate protected files and are not included in model prompts. The dashboard is protected by private-network restrictions and application authentication. Application and infrastructure administrators with sufficient privileges can access data; encryption does not remove that access.

AI inference and sharing

For enabled reconstruction features, the application sends bounded selected eligible source excerpts and controlled derived context to the managed inference provider configured by the owner. This processing takes place outside the application's private storage. Provider handling and retention depend on that provider's applicable account settings and terms. The application does not claim that model processing is entirely local or that the provider retains no data.

Raw bank statement events and records explicitly marked for deterministic-only processing are excluded from model evidence. Deterministically derived financial summaries may be supplied instead. Where supported, collectors filter recognized authentication messages and credential content before upload. The server excludes recognized authentication content from evidence eligible for model processing. Historical raw records and original files may remain encrypted in private storage until the owner carries out the applicable retention or purge procedure. These filters cannot guarantee detection of every secret in every format.

The application does not sell Google user data, use it for advertising, or make personal records publicly accessible through this site. Google user data is used only for the disclosed personal functionality, including the applicable Google API Services User Data Policy and Limited Use requirements.

Controls and retention

The owner can revoke account access through the account provider and can disable a source in the application. Revocation stops future authorized collection after existing access expires or is rejected; it does not erase records already stored. Source evidence remains until the owner requests and executes its supported purge or retention procedures. Purging source event records does not automatically erase orphaned content-addressed files, prior reconstructions or backup copies; those require separate retention review. Local encrypted backups are rotated separately.

The owner can inspect retained source records, original retained files, source status and generated reconstructions through authenticated application access. Source exclusions can prevent selected sources from entering future reconstruction context without deleting their history.

Contact

The application operator is the account owner. Questions or requests should be directed to the operator through the existing private contact channel. This site does not accept uploads, private records or account credentials.