What the form collects
Name, work email, firm name, role, an approximate recurring-client range, and optional workflow context.
Security & privacy
Trust starts with clear boundaries.
This page explains what MonthBridge handles today, how the public inquiry form works, and what must be complete before any real client accounting documents are accepted.
Pilot inquiry data
Only the context needed for a first conversation.
How it is used
Inquiry details are stored server-side and used to review fit, prepare the conversation, and respond to the person who submitted the form.
What analytics exclude
Conversion events accept only an ephemeral session identifier, page path, event name, and allow-listed interaction context; form answers are not included.
Rate-limit privacy
MonthBridge stores keyed one-way hashes for source and email rate limiting rather than storing the submitter’s raw IP address with the inquiry.
Current Sandbox
Production-shaped infrastructure, without production claims.
Hosting and data services
Vercel serves the web application and API functions; Supabase provides Sandbox authentication, Postgres, and private object storage.
Scoped file access
Sandbox uploads and downloads use short-lived, server-issued links to private storage, and service credentials remain server-side.
Access boundaries
Staff requests are authenticated and firm-scoped, while client upload links are packet-scoped, time-limited, and revocable.
Environment safeguards
Development endpoints, plaintext access-token storage, and development-link disclosure are disabled in the deployed Sandbox.
Product boundaries
Documents are prepared for people to review.
MonthBridge does not make bookkeeping, tax, legal, compliance, or ledger-posting decisions.
01Human approval remains required before a document is accepted or a packet is marked ready.
02The current Sandbox uses development malware and AI/OCR adapters and is not approved for real client documents.
03A production AI/OCR provider and no-training terms must be approved before real-document pilot use.
Before real documents
The release gate stays closed until the evidence is complete.
MonthBridge’s runtime is configured to block real-document use while any required production control or approval is missing.
- Production authentication, session, and MFA policy
- Approved malware-scanning and AI/OCR providers
- Monitoring plus backup-and-restore evidence
- Final retention, deletion, privacy, subprocessor, and incident-response processes
- Current security and end-to-end QA evidence
Retention, deletion & providers
What is settled—and what is not yet final.
Current service providers
The public Sandbox currently relies on Vercel for hosting and functions and Supabase for authentication, database, and private storage services.
Inquiry retention
Pilot inquiries currently remain available for founder review until manually removed; a time-based retention schedule is a required pre-pilot deliverable and is not yet represented as active.
Privacy or security requests
Use the pilot inquiry form and identify the request in the optional context field; do not include client information or other sensitive data.
Incident response
A documented and approved incident-response process is required before real-document use; the Sandbox is not presented as a substitute for that approval.
Last updated September 12, 2026.
Founders Pilot