OTPilot

Security

Security model

A TOTP seed can mint codes forever, so OTPilot is built around one rule: the seed goes in once and never comes out.

Storage

Agent keys

Human approval

Sensitive secrets can require a human tap. Approval links are single-use, expire after 5 minutes and release exactly one code to the requesting key.

Audit

Every request is logged with time, key, account, IP, user agent, outcome (issued, pending, denied, rate limited, out of scope) and the reason the agent gave.

Sign-in

Accounts sign in with single-use email links (20-minute expiry). Sessions are httpOnly, secure cookies; only a hash of the session token is stored.

Demo tokens

The no-signup try-it seals the pasted secret inside the demo token with AES-256-GCM and stores nothing. Tokens expire after 24 hours and are for testing only — use test secrets, not production ones.

Analytics and recordings

We use cookieless analytics and masked session recordings to fix bugs. Secret fields are excluded from recordings entirely and code displays are masked.

Acceptable use

OTPilot is for accounts you own and are allowed to automate. We do not create accounts on third-party sites. Every fetch is rate-limited and audited.

Report a vulnerability

Email hello@otpilot.vibiz.app.