Native clients
Future iOS and Android repositories are expected to handle recording,
encrypted local staging, upload, local account flows, and platform
lifecycle behavior.
Planned work
Roadmap
These areas are planned or under design. They are not current product behavior unless the status page says they are implemented.
Experimental · Not an emergency service
Proofline is experimental and does not contact emergency services. Read the safety boundaries.
Location and context
Future clients may capture GPS/location, timestamps, check-ins, notes,
photos, and supporting context where platform permissions and user choices
allow.
Near-live encrypted upload
Future upload flows may improve retry, resumability, partial/live access,
and regional ingest while preserving ciphertext-only backend boundaries.
Notifications
Future SMS, email, push, or other trusted-contact notifications need a
separate delivery design. They do not include emergency-services contact.
Hosted accounts and subscriptions
Future hosted accounts may include paid subscriptions for cost recovery
after billing, abuse controls, public API exposure review, and operations
work exists.
Trusted-contact workflows
Future trusted-contact access may combine grants, wrapped keys,
client-side decryption, and separate urgent or non-urgent review
experiences.
Browser decryption
Browser decryption is documented as future design work. It is not
implemented in the current backend or web client.
Key custody changes
Any key custody, escrow, browser decryption, backend decryption, or
break-glass work would require explicit design, documentation, testing,
and threat modeling.
How to read this roadmap
Planned items are not active features. They do not provide access grants, notifications, decryption, retention changes, public links, or emergency response today.
Sources
These project documents provide more detail about the current implementation, planned work, and security limits.