What Proofline is for

About Proofline

Proofline is being built for moments when losing the record could matter. It helps preserve end-to-end encrypted evidence as events unfold, while giving trusted contacts controlled access when it matters.

Why it exists

Some moments are hard to reconstruct later: an unsafe situation, an important interaction, a missed check-in, damage, harassment, threats, or a dispute. Proofline is meant to help preserve a private record while events are still unfolding.

The goal is not to turn every record into an emergency. The goal is to help a person keep evidence protected, decide who should see it, and avoid depending on a single phone as the only copy.

Use cases

More than emergencies

Proofline is being designed for incident capture, safety checks, interaction records, and evidence notes. Those labels should help explain why a record exists; they should not silently trigger escalation or sharing.

Evidence

Context where available

Future clients may capture and preserve audio, video, location, timestamps, notes, check-ins, photos, and supporting context where platform permissions and user choices allow.

Privacy

Encrypted by design

Sensitive material should be encrypted before Proofline receives it. Proofline itself should not be able to read the private contents of a record.

Access

Controlled sharing

Trusted contacts may be given controlled access when it matters. That access should be explicit, bounded, and separate from emergency dispatch or automatic response.

What it is not

Proofline is experimental, not an emergency service, and not a guaranteed real-time response system.

Production mobile capture, trusted-contact notifications, official hosted accounts, cost-recovery billing, live context sharing, and decryption workflows are not production features today.

Sources

These project documents provide more detail about the current implementation, planned work, and security limits.