TITAN security & retention
What we protect.
What we keep.
When this app talks to our servers, the connection is encrypted.
Local files you choose in the player stay on your device; the player does not upload them.
What we keep and why is stated plainly in our security policy.
We do not want in on your life; ours is full beyond earthly needs.
Enjoy — Built by T.I.T.A.N.S.
The connection
Connections to TITAN-operated servers use HTTPS/TLS. The trust notice withholds its security representation on an insecure origin.
This is a transport claim. It is not a claim of universal encryption at rest, end-to-end encryption, zero knowledge, or impossible recovery.
Local files
Local files chosen in OCTA Player are read on the device through local object URLs. The player does not upload the source file.
Sharing, provider control, and output-destination lanes are separate actions. They do not inherit local-file authority.
What TOTM keeps—and why
- Moment provenance links, so a Moment can name where the recording came from.
- Moment notes and letters, so the published Moment and its conversation persist.
- Local-open counts, so TOTM can show Moment activity without calling it playback history.
- Account association, where required for personal Moment and recent-open surfaces.
- One current Now Playing item, overwritten in place and expired by heartbeat.
TOTM does not keep server-side playback history.
MercuryServer
MercuryServer retains account and forum content to operate registration, identity, threads, posts, and community features. Its current terms are stated in the MercuryServer Privacy Policy.
Promise receipt
SHA-256 c72af92c161c46c1ce59a3cbd669680fc13311bbd8039f94d44cd1540037071d