TruePulse Privacy Policy

Last Updated: November 6, 2026 (Build 24)

1. What TruePulse Collects When You Record a Clip

By default, TruePulse initializes an anonymous device session so you can record and seal live video clips without providing personal contact information. When you seal a clip, the app uploads the raw camera MP4 bytes, the SHA-256 digest of those bytes, the single-use session code (nonce) issued when your capture session opened, the active camera lens (front or back), and the timestamps of session open, capture start, and server receipt.

2. Optional Email OTP Account Sync

You may optionally link an email address in the Profile tab using a one-time 6-digit verification code (OTP) to restore your session and clip ownership if you reinstall the app or switch devices. Your email address is stored strictly inside private authentication records (auth.users) for session recovery and is never published in public proof pages, feed responses, or cryptographic envelopes.

3. Optional Contributor Attribution & Stated Place

Before sealing a clip, you may optionally provide a @username, Display Name, Short Note / Description, and Stated City / Place. If provided, these fields are cryptographically bound into the public signed_message envelope and countersigned by an independent RFC 3161 Trusted Timestamp Authority. TruePulse does not access hardware GPS coordinates; if you tap Add City / Place, the app may pre-fill a coarse city/region suggestion via network IP lookup that you can edit or clear before sealing.

4. Public Proof Records, Withdrawal & What Survives in a Tombstone

You can withdraw any clip you sealed at any time from within the app. Withdrawing a clip immediately deletes the playable raw and derivative video files from storage and removes your @username, display name, note, and stated place from the rendered public proof UI.

What Survives Withdrawal (Cryptographic Tombstone): Because TruePulse proof URLs (/v/{sha256_hash}) serve as permanent cryptographic audit records, a withdrawn record preserves a tombstone containing the original SHA-256 hash, session/receipt/withdrawal timestamps, the Ed25519 signature, the RFC 3161 timestamp token, and the exact raw signed_message text block required to verify those signatures. If you chose to sign a @username, display name, note, or stated place into the envelope at seal time, those strings remain inside the raw signed_message text block on the tombstone so the cryptographic signature remains verifiable.

5. Full Account Deletion & Contact

Tapping Delete Account & Clear Data inside the app permanently deletes your authentication record (including any linked email address) and withdraws your active clips. For privacy inquiries or deletion requests, contact yoavnave@gmail.com.