Security & compliance

Human help without handing over the keys.

BatonPass is built for sensitive workflows. The agent pauses, the operator clears only the blocked step, and automation resumes only after explicit approval. Below — nine deep sections covering every question a security team will ask.

No password storage

BatonPass never sees, requests, or stores user credentials. Operators only see what the agent already had access to.

Encrypted handoff session

Browser snapshot + control channel are end-to-end encrypted between agent-host and operator phone. WebRTC DTLS-SRTP.

User-authorized control

Each handoff requires explicit operator action — no autonomous credential entry. Session expires after solve.

Sensitive fields redacted

Pre-configured patterns (SSN, card numbers, banking PII) auto-masked in audit log + replay.

Expiring handoff links

Mobile PWA URLs are single-use, signed, and expire in 60s by default. No replay possible.

We never store credentials

BatonPass operates downstream of your agent's authenticated session. Operators see what your agent saw — they never receive, type, or store passwords. The browser snapshot captures DOM + cookies for state restoration, with cookie values encrypted at rest with per-tenant keys.

End-to-end encrypted handoff

Browser state replay + operator control channel run over WebRTC with DTLS-SRTP. The BatonPass relay never sees decrypted screen content — it only routes signaling between agent-host and operator's phone.

Explicit human authorization

Every handoff requires the operator to: (1) open the signed mobile URL, (2) tap a physical action on screen, (3) confirm submit. No background or autonomous actions. The agent only resumes after the operator explicitly hits Resume.

Audit logs you can ship to compliance

Every state transition (created → detected → frozen → notified → opened → solving → solved → resumed → completed) is timestamped, tamper-evident (hash chain), and exportable as SOC 2 / HIPAA / GDPR-formatted JSONL or CSV. Retention configurable up to 7 years on Enterprise.

Sensitive field redaction

Configure per-domain redaction rules: SSN, credit card numbers, bank account numbers, healthcare identifiers. Redaction happens at snapshot time — operators and audit log never see the raw value, only the masked one.

Data retention you control

Default: handoff snapshots deleted 24 hours after resume. Audit log retained per tier (7 days Free → 7 years Enterprise). Custom retention windows + per-tenant deletion API on Enterprise.

Allowed domains

Each agent declares its domain allowlist. BatonPass refuses handoffs from any other domain. Prevents agent compromise from triggering handoffs on attacker-controlled pages.

Compliance posture

SOC 2 Type II in audit (target Q3 2026). HIPAA-ready architecture (BAA available on Enterprise). GDPR Article 17 deletion API. CCPA-compliant data subject access.

Incident response

Public status page at status.batonpass.dev. Incident severity matrix + customer notification SLAs. Security disclosures via security@batonpass.dev with PGP key. Bug bounty program (target Q4 2026).

Early access

Security questions? I'll send the architecture summary.

12-page PDF: every interruption type, mitigation strategy, and code sample. Plus early access.

By submitting you agree to receive BatonPass product updates from @SidraMiconi. Unsubscribe any time.