Authentication and agent access
Website sessions and MCP authorization use Clerk. Remote agents connect through OAuth 2.1; the gateway derives caller identity from the verified token, replaces caller-supplied identity, and dispatches only to internal Convex handlers. Agent functions repeat workspace ownership checks.
OAuth access can be revoked from the authorization provider. A revoked or invalid token is denied before an AWB tool runs; reconnecting requires a new approval.
Private media
File metadata lookup, download signing, and B2 retrieval require an authenticated owner path. Signed-out and foreign-workspace requests are rejected before storage egress. Agent image tools strip metadata and bound output dimensions.
A deliberately shared dossier uses a separate capability path. The server hashes the supplied long-random token, verifies the share is active and unexpired, and confirms the requested file is in that share's exact media manifest before signing any B2 download. Revocation closes both page and media access immediately, and responses are private no-store.
Research capability links
Raw share tokens are returned to the owner once and are never stored in the database. AWB keeps only their SHA-256 digest. Recipient pages are server-rendered from live allowed fields, marked noindex, and use a generic unavailable state for unknown, expired, replaced, or revoked links.
The lightweight view counter stores only a bounded total and last-counted time on the share row. It does not create a visitor record or store visitor identity in the application database.
Audit and retention
AWB keeps compact application events and gateway tool metadata for operational history. Content-heavy MCP arguments are disabled. Gateway audit and idle protocol sessions are pruned in bounded scheduled batches.
The repository includes daily offsite backup automation and a restore runbook, but the operator-scoped production key and current Convex-native retention still require dashboard confirmation. AWB does not claim a currently proven disaster-recovery SLA.
Report a security problem
Please use the security reporting route. Do not include passwords, OAuth tokens, private photos, or unnecessary personal data in the first message.
Last reviewed: July 16, 2026. No unsupported certification or compliance claim is made here.