Privacy Policy

Draft pending owner/legal review. This page describes the current technical design and still needs final business/legal facts.

Last updated: August 21, 2026

Creator Processing

When you use Creator, uploaded datasets and project files may be sent to TriniSee's Cloud Run API for validation, visualization, project packaging, export, and related Creator functions. TriniSee is designed not to permanently store user projects as a hosted project library.

Viewer Privacy

The static Viewer at view.trinisee.com opens current-format .trinisee files locally in the browser. Ordinary Viewer opening, measurement, palette changes, media viewing, and screenshots should not upload project contents or consume Project Credits.

Account and Billing Data

Firebase Authentication handles account identity. Firestore stores membership, entitlement, billing status, Project Credit ledger, Stripe event, and related operational records. Stripe processes payment details; TriniSee does not store card numbers.

Logs and Diagnostics

Cloud Run, Firebase, Cloudflare, and Stripe may store operational logs such as timestamps, route names, status codes, performance data, account identifiers, and payment event IDs. TriniSee should not log complete datasets, secrets, card details, or project media contents.

Embedded Media

.trinisee files may contain user-provided data, images, PDFs, notes, and measurements. Recipients should open only files from sources they trust.

Support and Pending Details

Contact support at support@trinisee.com. Final business identity, data-retention commitments, analytics disclosure, and legal contact information are pending Robert's confirmation.