Explicit consent at install
Adding a co-signer requires the protected user's deliberate confirmation. There is no remote-add path, no surprise enrollment, and no “suggested partner” from anywhere except the protected user.
Safety
Lockdown cannot become a weapon.
A blocker that locks the wrong person, or that an abusive partner can hold over someone, is not a useful safety product. SentryPact is being designed against coercive control from day one, with explicit consent, persistent visibility, and documented release paths for abuse, medical, and legal emergencies.
Coercive control
The primary abuse case we design against.
Adult co-signer mode is optional and powerful. Power without protection is a weapon. SentryPact's partner features only ship after the safeguards underneath them work.
Persistent visibility
The protected user can always see who the co-signer is, what they can do, what they have done, and when they last accessed anything. This visibility cannot be hidden by the co-signer.
Audited access
Every co-signer view, approval, and decision is logged. The audit trail is visible to the protected user and survives reinstall.
Reversibility
Removing a co-signer follows the same friction as creating a pact, never more. Safety release paths cannot be blocked by the co-signer.
Emergency release paths
Documented escapes for documented reasons.
A pact must end when staying locked is the unsafe option. Each release path is explicit, auditable, and never silent. None of them require the co-signer's permission.
Recognized release reasons
- Abuse, harassment, or coercive control by a co-signer
- Medical or mental-health emergencies
- Legal compulsion or law-enforcement need
- Device safety, including loss, theft, or compromise
How a release works
- The protected user requests release with a reason category
- A cooling-off window applies for non-co-signed pacts (default 24 hours)
- Filtering remains active during the cooling-off window
- The release decision and reason category are recorded in the audit trail
- The co-signer is notified that a release happened, never asked to approve it
No stealth, no surveillance
The protected user owns the visibility.
SentryPact is not a stalking tool. The features below are guardrails, not options.
The app announces itself
No disguised icons, no hidden background processes, no “parent mode” that turns the app invisible. The protected user can always see what is enforcing.
No raw browsing history by default
Co-signers see category counts and tamper events. Page contents and URL-level data are not in the default reports and are not in any report a co-signer can request unilaterally.
Every safety-sensitive action is logged
Pact creation, release decisions, co-signer additions, co-signer access, and emergency releases are all in the audit trail.
Safety paths are not paywalled
Emergency release does not depend on subscription status, billing health, or co-signer approval. Safety is the floor, not a feature.
No claims of unbreakable
SentryPact is tamper-resistant and bypass-detecting. We do not promise impossibility. We do not market addiction treatment, guaranteed prevention, or medical outcomes.
Real human contact for safety reports
If something feels wrong, contact us. Safety reports do not get queued behind feature requests.