Security

• All traffic is served over HTTPS with HSTS (max-age=63072000, two years).
• X-Content-Type-Options: nosniff — no MIME sniffing.
• X-Frame-Options: SAMEORIGIN — the site cannot be framed by another origin (clickjacking).
• Referrer-Policy: strict-origin-when-cross-origin — full URLs are not leaked to third-party sites.
• Permissions-Policy: camera, microphone, geolocation and the payment API are all denied.
• Content-Security-Policy is not set today. It is planned; we list it here as missing rather than implying coverage we do not have.

• The database is Supabase (PostgreSQL) in the Tokyo region, ap-northeast-1; hosting is Vercel (US).
• Row Level Security is enabled on every table.
• The waitlist table accepts INSERT from the anonymous key and nothing else — it cannot be read back with that key.
• Door tables are reachable only with the service-role key, which exists only on the server; the browser cannot query them directly. The one exception is read access to already-published doors.
• Accounts use Supabase Auth with httpOnly cookie sessions. Tokens are never placed in localStorage, so an XSS bug cannot walk off with a session.

• Disclosure gate: a vendor's agent answers only from sources that vendor explicitly approved. Revoking a source immediately invalidates cached answers derived from it, not just future ones.
• Every answer carries its citations, and a question the approved sources cannot answer returns a refusal rather than a guess.
• The site-ingestion crawler is SSRF-guarded: https/http only, standard ports only, IP literals and localhost / .local / .internal rejected, every hostname resolved before connecting and refused when it points at a private, loopback or link-local address (cloud metadata included), and redirects followed one hop at a time with the same checks on each hop.
• Page count, payload size and request timeouts are all capped during ingestion.

The processors that handle personal data on our behalf:

• Changes reach production through an automated pipeline; only commits that pass type-checking and a full build are promoted.
• Dependency vulnerabilities are picked up by automated scanning and scheduled updates.
• The database (Supabase) runs on the Pro plan, which takes automatic daily backups; the last 7 days of them are retrievable (Supabase's published spec, checked 2026-08-25).
• We hold no third-party security certification (SOC 2, ISO 27001 or equivalent).
• No third-party penetration test has been performed.
• There is no 24/7 monitoring rota and no formal incident-response SLA yet.
• Point-in-Time Recovery — the paid add-on that restores to any chosen second — is not enabled. Recovery granularity is therefore one day, not one transaction.
• No restore drill has been performed. Backups being taken and a restore actually working are two different facts, and only the first is established.

Please report vulnerabilities to contact@agent-door.com, with reproduction steps if you have them. There is no bug bounty at this stage, but every report gets a reply and a status update on the fix, and we are glad to agree a disclosure timeline with you.