Vercel
Infrastructure
Hosts the website, API, dashboard and MCP server.
Receives All web and API traffic, including request logs with IP address and browser.
- SOC 2 Type II
- ISO 27001
- PCI DSS
- TISAX
Trust center · mailbox.bot
mailbox.bot Trust & Security
Subprocessors, security controls and mail custody
This page lists every company that receives mailbox.bot customer data, what each one receives and the security reports each holds, with the controls around postal mail, identity documents, agent access and payments. Reviewed against the code on .
Compliance
StatusUSPS Form 1583
Two IDs and a notarized form for every mailbox holder.
RequiredUSPS CMRA registration
Form 1583 details and both ID copies filed in the USPS CMRA database.
FiledCalifornia CMRA records
Form 1583 and both IDs kept through service plus two years.
KeptPCI DSS
Cards are handled by Stripe, a PCI DSS Level 1 service provider.
Via StripeSOC 2
mailbox.bot has no SOC 2 report of its own. Its hosting, database and payment vendors hold SOC 2 Type II.
No reportMail facility
Location #12100 N SEPULVEDA BLVD · STE 28
MANHATTAN BEACH CA 90266
MANHATTAN BEACH CA 90266
Mail is received, photographed, scanned, printed and handed to USPS and FedEx here. Scans, forwards and discards wait for the mailbox owner's approval.
22
Subprocessors
34
Controls
7
Policies
20 Oct
Last reviewed
7
Policies
Published documents that govern how mailbox.bot handles mail, accounts and data.
34
Controls
Safeguards in the product and at the mail facility.
- Photo proof of every outbound piece
- Match check before dispatch
- Owner approval for inbound actions
- Agents propose, people approve
- No mail images for agents
- Letters encrypted at rest
- Every document read logged
- Originals purged after mailing
22
Subprocessors
Companies that receive customer data on our behalf, each bound by a contract or published data processing terms.
VercelHosts the website, API, dashboard and MCP server.
SupabaseDatabase, file storage and account sign-in.
RailwayRuns the background workers: letter photo checks, mail text recognition, support drafts, retention and tracking.
UpstashRate limits and the queue for background jobs.Google CloudCloud KMS holds the keys that seal ID documents. Document AI reads the text of forwarded mail.34
Controls
Safeguards in the product and at the mail facility, reviewed against the code on 20 Oct 2026.
Mail custody
- Photo proof of every outbound pieceStaff photograph each envelope with its pages before it is mailed.
- Match check before dispatchA photo of each prepared letter must match the order's own first page and postage label before the letter is marked ready.
- Owner approval for inbound actionsScans, forwards and discards wait for the mailbox owner to approve them at the price shown.
- Agents propose, people approveAgent keys can only propose inbound actions. They never open, forward, discard or spend on their own.
- No mail images for agentsAgents read status and recognized text, never image links.
Letters and proof photos
- Letters encrypted at restEvery uploaded letter is sealed with AES-256-GCM under its own key, wrapped by Google Cloud KMS. Storage holds only ciphertext, and the dashboard and facility read it through the app.
- Every document read loggedEach time a letter is opened, the read is recorded in an access log.
- Originals purged after mailingOnce a letter is mailed or delivered, the file you submitted is deleted. A rasterized first-page preview is kept, readable only in its top 30%.
- Blurred proof photosProof photos of the pages, envelope and receipt are kept as previews with the lower half blurred, and the full photos are deleted.
- No document links in webhooksWebhook payloads never carry a readable link to your letter.
Identity documents
- Sealed Form 1583 and IDsEach file is encrypted with AES-256-GCM under its own key, wrapped by Google Cloud KMS. Storage holds only ciphertext.
- Approved networks onlyID documents open only for signed-in facility staff on approved networks.
- Every access loggedEach ID document view is recorded in the audit log.
- Online notarizationForm 1583 is notarized in a live online session with a commissioned notary.
- California retentionForm 1583 and both ID copies are kept through service and for at least two years after, as California CMRA rules require.
Accounts and API keys
- Verified accountsEvery account verifies its email address and phone number at signup.
- Scoped keysMember, agent, sandbox and facility keys carry only the scopes they need. An agent key cannot read or act on another agent.
- Sandbox keysTest keys use the same API with no charges and no physical mail.
- Spend limitsDry runs, per-request cost caps, daily piece limits and account spend caps stop a send before any charge.
- Approval queueA key can require a person to approve every letter before it prints.
- Signed webhooksEach webhook carries an HMAC-SHA256 signature with a timestamp, and signing keys can be rotated.
- Duplicate protectionIdempotency keys and version checks stop repeat letters and double charges.
- Request budgetsPer-person, per-key and per-network limits slow abuse and repeated failed sign-ins.
Payments
- No card numbers storedCard details go straight to Stripe. mailbox.bot keeps a token and the last four digits.
- Prepaid creditsLive mail spends prepaid credits, and daily caps are checked again when a letter is approved.
Data handling
- Row-level securityDatabase access is governed by Postgres row-level security.
- Zero-retention AIMail recognition, letter photo checks and support drafts go only to AI providers that keep no data and never train on it.
- No training on customer dataForm 1583 records, ID copies and identifiable mail contents are never used to train AI models.
- People send support repliesAI support drafts stay internal. A person sends every reply.
- Audit logAdmin and system changes are recorded in an audit log.
Monitoring and disclosure
- Private error reportsError monitoring runs with default personal data off. Replays mask all text and block media.
- No session recordingProduct analytics has session recording off, and web analytics anonymizes IP addresses.
- Bot checksCloudflare Turnstile screens the signup and contact forms.
- Vulnerability reportsSend reports to support@mailbox.bot. A security.txt file lists the same contact.
7
Policies
Published documents that govern how mailbox.bot handles mail, accounts and data.
22
Subprocessors
Every company that receives mailbox.bot customer data, what it receives, and the reports it holds.
Supabase
Infrastructure
Database, file storage and account sign-in.
Receives Account and mail records, encrypted letters until they are mailed, mail scans and the sealed Form 1583 files.
- SOC 2 Type II
- ISO 27001
- HIPAA
Railway
Infrastructure
Runs the background workers: letter photo checks, mail text recognition, support drafts, retention and tracking.
Receives Letters and their proof photos, to check them before dispatch and to make the blurred previews after mailing, plus forwarded mail files and support tickets.
- SOC 2 Type II
- SOC 3
- HIPAA
Upstash
Infrastructure
Rate limits and the queue for background jobs.
Receives IP addresses and account and key IDs as rate-limit counters, and queued job messages. Never document contents.
Google Cloud
Infrastructure
Cloud KMS holds the keys that seal ID documents. Document AI reads the text of forwarded mail.
Receives File keys to wrap and unwrap, never the documents themselves, and forwarded mail files for text recognition.
- SOC 2
- ISO 27001
- ISO 27017
- ISO 27018
- PCI DSS
Cloudflare
Infrastructure
Turnstile bot checks on the signup and contact forms.
Receives IP address and browser signals during the check.
- SOC 2 Type II
- ISO 27001
- ISO 27701
- PCI DSS
GitHub
Infrastructure
Hosts our source code and engineering notes in a private repository.
Receives Code, plus the account email addresses and IDs that appear in some engineering notes and database scripts.
- SOC 3
- ISO 27001
OpenRouter
AI processing
Routes AI requests to model providers for mail text recognition, letter photo checks, tracking-number reads and support drafts.
Receives Mail scans and label images, letter photos and support ticket text. Mail, photo and support requests go only to providers that keep no data and never train on it. Mail reading and photo checks run on Claude, OpenAI, and Google models.
- SOC 2 Type II
OneNotary
Identity and payments
Online notarization of USPS Form 1583 for mailbox holders.
Receives Name, email, phone and the filled Form 1583. The live notary session checks ID and is recorded.
- SOC 2 Type II
- ISO 27001
Stripe
Identity and payments
Card payments, prepaid credits and the billing portal, Stripe Identity checks when an account needs one, and payouts to facility operators.
Receives Card details, entered directly with Stripe, and billing name and address. An ID photo and selfie when Stripe Identity runs. Facility operators' payout details through Stripe Connect.
- PCI DSS Level 1
- SOC 1
- SOC 2 Type II
- SOC 3
Twilio
Identity and payments
Phone verification at signup, carrier lookup and text messages.
Receives Phone numbers and message text.
- SOC 2 Type II
- ISO 27001
- ISO 27017
- ISO 27018
USPS
Mail and carriers
Carries mail and keeps the CMRA customer registration records for mailbox holders.
Receives Form 1583 details and both ID copies for each mailbox holder, through the USPS CMRA registration database, and the addresses on every piece.
EasyPost
Mail and carriers
Buys USPS First-Class and Certified Mail postage and labels.
Receives Sender and recipient addresses, weight and service class.
- SOC 2 Type II
Shippo
Mail and carriers
Quotes and labels for FedEx and USPS Priority Mail.
Receives Sender and recipient addresses, package size and weight, and service class.
- SOC 2 Type II
- PCI DSS
FedEx
Mail and carriers
Carries FedEx shipments. Tracking updates come back from the FedEx API.
Receives Sender and recipient addresses and package details on each FedEx label.
Resend
Communications
Sends account, security and mail notification emails.
Receives Email addresses and message content.
- SOC 2 Type II
Slack
Communications
Our team's support inbox: new support chats arrive in a private channel.
Receives The sender's email address and message.
- SOC 2 Type II
- SOC 3
- ISO 27001
- ISO 27018
Fastmail
Communications
Hosts support@mailbox.bot, the one address for email to mailbox.bot.
Receives Emails you send to support@mailbox.bot.
Amazon Web Services
Communications
Amazon SES receives email sent to agent addresses at agent.mailbox.bot.
Receives Emails sent to agent addresses, with their attachments.
- SOC 2
- ISO 27001
Sentry
Monitoring and analytics
Error monitoring for the website, dashboard and API.
Receives Error reports with default personal data off, and session replays with all text masked and media blocked.
- SOC 2 Type II
PostHog
Monitoring and analytics
Product analytics.
Receives Page views and feature use, tied to the account when signed in. Session recording is off.
- SOC 2 Type II
Google Analytics
Monitoring and analytics
Website traffic statistics.
Receives Page views, traffic source and approximate location from IP, with IP anonymization and no advertising features.
- ISO 27001