Server preserves ciphertext
The current backend receives already-encrypted chunks, verifies hashes
over ciphertext, stores metadata, and can generate encrypted ZIP evidence
bundles for completed streams.
Plain-language project model
About Proofline
Proofline is intended to preserve encrypted incident, interaction, safety-check, and evidence-note records without treating capture as emergency response.
Experimental · Not an emergency service
Proofline is experimental and does not contact emergency services. Read the safety boundaries.
What Proofline is intended to do
Proofline is intended to let a person create an important record when something needs to be preserved: an emergency incident, a non-emergency interaction record, a timed safety check, or an evidence note. Future clients may capture audio, video, GPS/location, timestamps, check-ins, notes, photos, and supporting context where platform permissions and the user’s choices allow.
Proofline’s core model is encryption before upload. Client apps encrypt short chunks locally, then upload those already-encrypted chunks so the server can preserve them even if the device is lost, damaged, powered off, destroyed, or taken after some evidence has already reached the server.
Metadata review exists
The current web-client prototype reviews account, incident, stream, chunk,
contact public-key, sharing-grant, and wrapped-key metadata where its mock
or confirmed live API contracts support that view.
Authorized review
Future account-owner and trusted-contact review is planned around grants,
wrapped keys, and clear separation between metadata access, ciphertext
access, and decryption capability.
Trusted-contact access
Trusted contacts may eventually review authorized incident context and
decrypt evidence client-side when policy and key custody allow it.
No production recording client
Production iOS and Android recording clients, production GPS capture,
near-live upload, and safety-check notification behavior are not current
product behavior.
Capture is not escalation
Recording or labeling an incident does not automatically notify anyone,
contact emergency services, create public links, release keys, or change
retention policy.
Why server-side preservation matters
A phone-only encrypted recording can disappear with the phone. Proofline’s long-term model is to preserve encrypted chunks outside the device while keeping raw media keys, plaintext, and decryption behavior out of the default backend path. Future production key custody is expected to avoid relying on the phone as the only place usable keys exist.
Sources
These project documents provide more detail about the current implementation, planned work, and security limits.