Last updated October 7, 2026
VOpilot holds the financial and contact details of your voiceover business, so protecting that data is core to the product. This page is a plain-English summary of how we do that, including the parts that are not done yet. It complements our Privacy Policy.
Every account is walled off from every other account at the database level using row-level security. The isolation is enforced by the database itself, not just by application code, so one customer can never read another's jobs, clients, invoices, or income. The public demo site you can publish only ever shows what you explicitly put on it, never your private account data.
In transit: all traffic to and from VOpilot is encrypted with TLS (HTTPS).
At rest: the database and file storage are encrypted at rest by our database provider, Supabase.
Field level: mailbox access tokens are additionally encrypted by the app, so they aren't readable even in a raw database export.
Our backups: our own backup copies are encrypted before they are written, and the key is kept apart from them.
VOpilot signs you in with your email address and password. Two-step login is optional for members: turn it on in Settings → Privacy & security, and after your password VOpilot asks for the 6-digit code from an authenticator app (Google Authenticator, Microsoft Authenticator, 1Password, Authy and others). It works with authenticator apps only, not text messages. With it on, your password alone does not open your account: the app and the database itself both refuse a sign-in that has not entered its code.
Two-step login is required for VOpilot staff to open the admin area. Staff use the same sign-in as members, and the admin area is open only to staff accounts on an approved list that have entered their code. The staff accounts that run VOpilot's hosting (Vercel) and database (Supabase) do require two-step login.
What it does not do: it protects signing in, so a browser that is already signed in stays signed in until you sign out there. Sign out on shared computers. If you lose your phone and have no backup authenticator, support checks it's you against your own records and gives you 24 hours' notice by email before removing two-step login.
Access to production systems is limited to the people who run VOpilot. We don't read your business content in the ordinary course of operating it. We look only when we need to: to answer a support request you raised, to investigate a problem or a security issue, or to comply with the law.
Settings → Privacy & security has an access log you can check any time. It shows changes we make to your plan access, and our maintenance scripts that record when they read or repair records in your account, with who, when, and what. It is not a complete record yet. Our reading of a support conversation you started, our work directly in the database, and most maintenance scripts are not listed there. We would rather tell you that than let an empty log suggest more than it shows.
Any cloud product that actually does something useful with your information (organizes it, reads the emails you forward, builds your invoices, totals your income) has to be technically able to read that information to do its job. The same is true of nearly every tool you already trust: your email provider, your accounting software, your bank's app.
So the question worth asking isn't whether a provider could access your data, but whether that access is kept minimal and controlled. That is the standard we hold ourselves to, and this page says where we fall short of it today.
Forwarded emails: we save a copy of each forwarded email as it arrives, so an outage costs a delay rather than the email. Its body and attachments are deleted 30 days after the email is filed, skipped, or given up on; the sender, subject, and outcome are kept for 180 days. The record an email becomes keeps its text and files for as long as you keep the record.
Backups: our database provider keeps daily backups for 7 days. We also keep our own encrypted backup copies, outside our database provider, for 30 days, so we can recover even if we lost that provider. Copies made before October 7, 2026 can also remain, encrypted, in the backups of the computer that makes ours until they age out.
Deleting your account deletes your data from VOpilot’s database and file storage straight away, apart from the few items listed on our Delete your account page; the copies in backups are gone within 30 days, apart from the older computer backups described above. You can delete it even after your trial or plan has ended, from the plan screen you see when you sign in.
When you get paid through VOpilot, Stripe and PayPal handle your clients' card and bank details directly. VOpilot never sees or stores your clients' card or bank-account numbers. You are the merchant of record, and funds settle directly to your own connected account. Payment instructions you type into your business profile (bank details for a transfer, say) are stored and printed on your invoices like the rest of your profile.
If you reconcile deposits by importing a bank statement CSV, that file is parsed and matched entirely in your browser and is never uploaded. Only when you confirm a match does VOpilot record that one payment's amount and date against the record; the rest of the statement, including account numbers and every unmatched line, never leaves your device.
Two different things often get bundled together: AI helping to write the code, and AI being the thing the app runs on. The first is true of VOpilot and matters about as much as which text editor a developer uses. The second is not true.
Your records are rows in an ordinary database. Jobs, auditions, invoices, contacts, expenses, agreements, and the reports built from them are data. They do not live inside an AI model, and they do not need one to exist or open.
AI does specific jobs here: reading the emails you forward and turning them into draft records, transcribing your takes and your voice input, the Monday brief, the in-app assistant, Ask your business, filling in contacts from a connected mailbox, Find the spot, contract questions, receipt scanning, the tax review, and drafting text when you ask for it. Those are features sitting on top of your data, not the thing holding it. What each provider keeps is in our Privacy Policy.
Filing forwarded email already runs on two providers. Every forward is saved the moment it arrives, before anything tries to read it, so an outage costs you a delay rather than an email. If Anthropic’s own service is down or overloaded, the same request is retried against Claude on Amazon Bedrock, which is separate infrastructure run by AWS (for some features with an earlier Claude version, since not every current model is available to us there yet). If both are unavailable, the email waits and is retried automatically.
If a provider disappeared for good, those features would move to another provider or go quiet for a while. Your records would sit there untouched, your invoices would still send, your reminders would still fire, and you would type a booking in by hand until it was back.
On every plan you can export your contacts and expenses to CSV, most reports’ totals to CSV, your transactions as a file for QuickBooks, and your customers and invoices for Wave, and you can download invoice PDFs and stored files one at a time. There is no single “download everything” yet, and auditions and agreements have no export. If your trial or plan has ended, the export tools are behind the plan screen; email support@vopilot.co and we will send you a copy. If VOpilot ever shuts down, our Terms promise at least 60 days’ notice and the chance to get your data out first.
These are the outside services that handle your data for us, each under its own terms limiting what it may do with it:
Microsoft and Google come in only if you choose to connect an Outlook mailbox or your Google contacts under Contacts → Add from email. We then read from your account with the permission you grant, and you can disconnect at any time. Likewise, a calendar you add on the Planner (from Google, Outlook, iCloud, or elsewhere) is fetched from the private address you paste in, until you remove it.
If we become aware of a security breach affecting your personal data, we will notify affected users and any required authorities without undue delay, consistent with applicable law.
If you believe you've found a security issue, please email support@vopilot.co with the details. We welcome responsible disclosure and will work with you to confirm and address it.
If your organization requires a signed Data Processing Addendum (DPA), see our DPA template and email support@vopilot.co to put one in place.
VOpilot is a focused product from a small company, not a large enterprise with formal third-party certifications (such as SOC 2 or ISO 27001). Our database provider, Supabase, reports SOC 2 Type 2 compliance; VOpilot itself has no certification. What we can show you is the list above, including what isn't done yet, and we'll keep strengthening it as we grow.