Security, in full
Your customers' calls, messages, and bookings run through this system. This page shows every vendor in the chain, where the data lives, how long it is kept, how access is controlled, and what Belmont Motion has not built yet.
Last reviewed: November 16, 2026
Some buyers are required to check. If you are a law firm vetting Belmont Motion under ABA Model Rule 1.6(c), start at the section written for you. It gathers the same facts in one place.
Who else sees your callers’ data
When someone calls your business, their words pass through several vendors. You should know each one before you sign anything.
The call itself
| Who | What reaches them |
|---|---|
| Retell AI | The call audio, the recording, and the transcript. Retell runs the voice platform. |
| OpenAI (via Azure) | The transcript text: what your caller said, in words. Retell's model provider generates the responses. |
| Deepgram / Soniox / AssemblyAI | The audio, for speech-to-text. |
| ElevenLabs / Cartesia | The text of what the AI says back, for the voice. Your caller's words do not reach them. |
| Twilio | Call routing and telephony. |
Everything after the call
| Who | What reaches them |
|---|---|
| Supabase | Your database: transcripts, bookings, messages, contacts. AWS us-east-2, Ohio. |
| Vercel | Your portal and the website. iad1, Virginia. |
| Resend | Confirmation and reminder emails: recipient name, email, appointment details. |
| Google Calendar / Apple iCloud | Your calendar, if you connect one. Booking details only. |
| Stripe | Billing. Your business's payment details. Never your callers'. |
Every vendor above operates in the United States for Belmont Motion’s account. There is no offshore processing.
Where this stands with Retell: Belmont Motion has a signed data processing agreement with Retell, including EU standard contractual clauses. What is still being confirmed in writing is Retell’s onward retention terms with the model providers above. Retell’s formal subprocessor documentation has been requested, and this page changes when it arrives. If your practice requires a specific arrangement, ask before you sign and you will get the answer in writing.
Where your data lives, and how long
Location. Database and application in the United States, in Ohio and Virginia. Automation server in Virginia. Nothing offshore.
Recordings and transcripts at Retell: 90 days, then deleted automatically. That setting is deliberate: long enough to investigate a disputed call inside your guarantee window, short enough that there is no permanent archive of your callers’ calls.
Transcripts in Belmont Motion’s database: kept while you are a client. Deleted on request.
When you leave: your data is deleted on request. Today that is a manual process, not an automated one. Retell’s copy ages out on its own 90-day clock.
Who can touch what
Row-level security on every table. Every table in the database (156 as of November 16, 2026) has row-level security switched on. The database itself decides which rows a logged-in user can read, so the rules hold even if the application code has a bug.
Internal tables are closed to users. 25 of those tables hold internal records, such as rate-limit counters and scrape logs. They have row-level security on and no access rules at all, so a logged-in user or a website visitor gets nothing from them. Only Belmont Motion’s server-side code and the database owner account can read them.
Checked on every change. An automatic check runs on every code change to the main branch. It reads the database catalog and fails if any table has row-level security switched off, or if a table has no access rules and is not on the reviewed list of internal tables. On November 16, 2026 it found one internal table, the scrape logs, with row-level security off. It was locked the same day, and the check passed on its next run.
Role tests. Separate scripted tests act as each kind of user: a client, a second client, the owner, an operator, a logged-in user with no role, and a visitor who is not logged in. Each check that a user is refused something is paired with a check that the same user can still see its own records, so a rule that blocks everyone cannot pass. Three test files hold 81 written checks. They are run by hand against the database, not automatically on every change.
What the role tests do not cover yet: the tables that hold the AI receptionist’s call records, bookings, and messages. Those tables are covered by the automatic check above, which confirms row-level security is on and that access rules exist, but does not test what the rules allow.
Endpoints that need a login check the caller’s role, not only that someone is logged in. Endpoints that are public by design, such as the booking page, are listed in an endpoint inventory, and the automatic checks fail if a server endpoint is missing from it.
Belmont Motion’s operator tools are owner-only. The operator dashboard requires a login and opens only for the owner account, and the server checks for the owner role again before returning data.
Multi-factor authentication was confirmed on July 16, 2026 for source control, the database, hosting, payments, the domain registrar, the automation server host, the email outreach platform, and Google Workspace. The domain is transfer-locked.
One exception: the voice platform account uses email sign-in with no multi-factor option. Google sign-in exists on that platform but cannot be linked to an existing account. The account is reachable only through a Google Workspace inbox that has multi-factor authentication, on a registrar-locked domain. When the account can be linked or the platform adds multi-factor authentication, it will be turned on and this paragraph will change.
What’s encrypted, and by whom
In transit: TLS on every connection. Belmont Motion’s code makes no unencrypted (plain http) requests.
At rest: Supabase and Vercel state in their documentation that they encrypt stored data at the disk level (AES-256).
Belmont Motion also encrypts specific things itself:
- Calendar credentials: AES-256-GCM at the application layer, before they reach the database, with the key held only in server-side secrets. A copy of the database alone would show your calendar tokens only as ciphertext.
- Booking links: the token in your confirmation email is stored only as a SHA-256 hash. The link itself is not stored and cannot be read back.
What is stored in plaintext: call transcripts, caller names and numbers, message bodies, adverse-party names. They are protected by row-level security and the providers’ disk encryption, not by field-level encryption.
No secret reaches the browser. The browser receives only keys designed to be public, such as the database’s public key and Stripe’s publishable key. Every other key is kept in the hosting providers’ server-side secret settings, not in the source code.
What the intake does, and doesn’t
The intake captures the adverse party’s name, verbatim, on every call, and puts it in front of you for review before the consultation.
Belmont Motion does not run a conflict check. It has no access to your matter records. The system collects the name and shows it to you. You check it.
The AI is an AI
Your callers are told plainly, if they ask. The intake agent never implies it is a lawyer, never suggests that speaking with it creates a relationship with your firm, never gives legal advice, never estimates case value, and never comments on deadlines. Those are hard rules in the agent’s instructions.
It captures facts and books consultations. Everything else is yours.
For law firms
Attorneys have their own duty under ABA Model Rule 1.6(c): reasonable efforts to prevent disclosure, which includes vetting the vendors that touch client information. The four answers you need, in one place:
- Who hears your callers. The full vendor chain, including the AI model providers, is listed above: Who else sees your callers’ data. Every vendor is named.
- How long recordings and transcripts live. 90 days at the voice platform, deleted automatically; database copies deleted on request: Where your data lives, and how long.
- Conflicts. The intake captures the adverse party’s name verbatim and puts it in front of you for review. Belmont Motion does not run a conflict check: What the intake does, and doesn’t.
- What the AI will never say. It discloses that it is an AI, never gives legal advice, never implies representation, never estimates case value, and never comments on deadlines: The AI is an AI.
Each line above links to the section that carries it. This summary makes no claim of its own.
How Belmont Motion builds
Secret scanning. Gitleaks scans for keys and passwords at three points: a pre-commit hook on the development machine (it warns and allows the commit if the scanner is not installed), a scan of the full code history on every change to the main branch, and push protection at GitHub.
Automatic checks on every change to the main branch and on every pull request into it: type checking of the site, a production build, type checking of the server functions, a dependency audit, the secret scan, the row-level security check, and two checks that fail if a server endpoint or a holder of the internal access key is added without being documented. These checks report failures; they do not stop the hosting provider from deploying a change.
Dependency audit. The audit fails on any high or critical advisory in the packages the site ships, with two exceptions held by advisory ID until December 16, 2026: one in the build tool (Vite) that affects only the local development server, and one in the form-validation library (Zod) whose fix requires a major version upgrade. Each exception is tied to one install location, so the same advisory anywhere else still fails the audit.
Automated alerts when a vulnerability is disclosed in a dependency.
Rate limits fail closed where a request costs money. Any request that spends money or starts a call is denied if the rate limiter itself fails. Public pages fail open by design, so a broken limiter does not take your booking page down.
Bot check on the public AI demo. The Plan Assistant demo checks each typed question with Cloudflare Turnstile on the server, and refuses the question if the check fails or cannot be completed. Cloudflare receives the visitor’s IP address for that check.
A gate before any outreach is sent. No outreach is released to the sending platform until every email’s copy is approved at its current version, with the approver’s name recorded; every email contains the business’s postal address and an opt-out notice; and an operator has confirmed a real test send. Recipients who don’t meet the conditions are held, with the reason recorded.
Secrets for scheduled jobs live in Vault. The scheduled jobs that call Belmont Motion’s own functions read their shared secret from Supabase Vault, not from code.
What Belmont Motion doesn’t have
These are the gaps, listed so you can weigh them before you sign.
- No third-party penetration test. No outside firm has tested the system. Belmont Motion plans to commission one.
- No security certification. Belmont Motion holds no SOC 2 report and no ISO 27001 certificate.
- The incident response plan has been run once, not rehearsed. A vendor in the chain disclosed a breach, and the plan was run on it end to end: timestamp, scope, severity, containment decision, written incident file. It found Belmont Motion was not affected, verified from records rather than memory. It also found a real gap: vendor security bulletins were not reaching Belmont Motion. That is closed. One run is not a rehearsed program, and the plan has never been run on an incident of Belmont Motion's own with the 24-hour notification clock live. That clock stands: you will hear from Belmont Motion within 24 hours of confirming any exposure of your data, before the investigation is finished.
- No automated data deletion. Deletion is manual and done on request.
- No standard data processing agreement for clients. If your firm requires one, ask, and Belmont Motion will work through yours.
- No cyber liability insurance. It is being evaluated.
- One person. Belmont Motion is one person with no employees, so there is no personnel security program. One person is accountable to you.
Reporting a vulnerability
Found something? Email support@belmontmotion.com with the details. Belmont Motion will confirm receipt within one business day and tell you what is being done about it, and will not threaten anyone who reports in good faith.
Why this page is shaped like this
This page lists its gaps, its vendors, and the one account without multi-factor authentication because a firm vetting a vendor needs to see them. Each statement on it is tied to a code file, a test result, or a dated account check in Belmont Motion’s records. Last reviewed November 16, 2026.