Intended flow
Experimental Open source Not an emergency service
The intended future Proofline flow is simple: a user starts an incident, interaction record, safety check, or evidence note; a client records audio, video, location, timestamps, and supporting context where available; the client encrypts sensitive chunks before upload; and the server preserves the already-encrypted evidence for authorized review.
Start with about Proofline or review current status .
The active project has an experimental Go server backend and an
experimental React web-client prototype. The backend stores encrypted
chunks and metadata; the web client shows account and incident-review
surfaces in mock mode or where live API contracts are confirmed.
Not an emergency service
Proofline does not contact emergency services, guarantee real-time review,
or replace user and trusted-contact judgment.
Self-hosting is part of the model
Proofline is maintainer-led open-source work with self-hosting as part of
the model. Any future official hosted service would require paid
cost-recovery and operational hardening first.
No company or response center
There is no company, response center, charity, nonprofit status, support
team, or donation-gated account access implemented today.
Current source code
Current repositories are
server and
web-client .
Native clients and protocol work are planned separately.
Production service
Production mobile clients, hosted subscriptions, trusted-contact
notification workflows, browser decryption, key escrow, and playable media
export are not implemented.
Sources
These project documents provide more detail about the current implementation, planned work, and security limits.