1. Our posture
We design Orvius for small and mid-size trade businesses that handle sensitive caller and job data. We take security seriously and continuously improve controls. We do not currently claim SOC 2, ISO 27001, HIPAA, PCI DSS Level 1, FedRAMP, or similar third-party certifications. Do not interpret marketing language as an audit attestation.
2. Practices
Each of these is enforced in code, and the ones marked checked run as automated tests on every release.
- One shop never sees another's records (checked).Every signed-in request is tied to the shop it belongs to, and every record opened by id is looked up inside that shop. A release fails if any API route doesn't check who is asking.
- Roles (checked).Owner, manager and dispatcher each see only what their role allows. Technicians get a private link per person, not a sign-in, and sending a new link retires the old one.
- Credentials.Connected-app tokens and keys (Jobber, Housecall Pro, QuickBooks) are encrypted before they are stored. Passwords are stored only as salted hashes. Provider keys live outside the source code.
- Signed webhooks.Calls, texts, payments and Jobber updates are accepted only with a valid provider signature or shared secret.
- Activity log.Settings → Activity log records what Orvius did on each call and what your team changed, with who and when, and downloads as CSV.
- Retention.Call recordings, transcripts and voicemail are deleted 24 months after the call. Provider delivery logs are pruned after 90 days and alert history after 180 days.
- Recording notice.Every call opens by telling the caller it may be recorded and is answered by an automated receptionist.
- Connections.Encrypted (HTTPS/TLS) for all web and API traffic.
No system is perfectly secure. We work to reduce risk and respond to incidents.
3. Product controls you operate
Each of these is in your workspace, for you or your team to use.
- Business hours, services, and escalation contacts you configure
- Whether Orvius books callers itself or only takes the request for you to schedule
- Approvals: anything typed into Command is shown as a plan you approve, and jobs where two people fit equally wait for you. Emergencies and danger calls always come to you
- Settings → Receptionist lists what Orvius does on its own, what waits for you, and what it never does
- Audit trail of calls, transcripts, and key workspace actions
- Each person's sign-in: password, two-step codes, a list of recent sign-ins, an email when a new device signs in or a sign-in setting changes, one button that signs out every device, and a sign-in email change that only goes through once the new inbox confirms it
- Teammate roles: only the owner can manage billing or delete a customer's data, and dispatchers can't export the shop's data
- Deleting one customer's data on request, including the recording copies at our voice and phone providers
You remain responsible for how the Service is deployed on your lines, including recording notices, AI disclosure, and SMS consent. See Terms and SMS Terms.
4. Data handling
Call metadata, transcripts, lead records, and account data are stored to operate the Service (including via our database provider). See our Privacy Policy for controller/processor roles, categories, retention, state privacy rights, and deletion requests. We do not claim HIPAA readiness or offer a standard BAA unless expressly agreed in writing.
5. Subprocessors
- VercelApplication hosting and edge delivery
- TursoManaged database (application and shop records)
- TwilioTelephony, SMS, and related communications
- VapiVoice AI orchestration (may engage nested speech/model providers)
- StripeSubscription billing and payment processing
- GoogleOAuth sign-in
6. Customer compliance
Business customers are responsible for laws applicable to their operations, including TCPA and similar messaging rules, call recording/AI notice requirements, advertising rules, and trade licensing. Orvius provides tools; customers control deployment.
7. Incidents
If the voice AI can't be reached, your line doesn't go silent: it rings your handoff number, or your own mobile, then takes a message and texts you. Live provider status is on the status page.
When something on our side stops calls, texts or alerts from working, we email the affected shops with what happened, what it affected and what we changed, and we refund billing affected by an outage we caused.
For confirmed personal-data breaches affecting Customer Content, we notify affected business customers without undue delay where legally required or when we determine notification is appropriate, and we cooperate with customer notification duties as processor.
8. Reporting a vulnerability
Email support@orvius.im with what you found and how to reproduce it. We aim to reply within three business days and to tell you when it's fixed. The same address is in /.well-known/security.txt.
If you act in good faith, we won't take legal action against you for research that: uses only accounts you own or have permission to test; stops as soon as you reach someone else's data, and doesn't keep or share it; doesn't degrade the service, place real calls or send texts to people who didn't agree; and gives us a reasonable time to fix the issue before you publish.
Out of scope: denial of service, spam, social engineering of our staff or customers, and physical attacks.
9. Leaving
You can download all of your shop's records at any time, including after you cancel. If you forwarded your number, it never left your carrier: turn forwarding off and calls ring as before. If you moved your number to Orvius, email support@orvius.im and we give your new carrier what it needs to move it again. We don't hold a number back. See Leaving Orvius.
10. Contact
Solution Development LLC
support@orvius.im