1. Scope and roles
This Privacy Policy applies to orvius.im, related marketing pages, account signup, and the Orvius Service operated by Solution Development LLC.
Business users (controllers for their shop data). For information about shop owners, staff accounts, and billing contacts, Solution Development LLC is generally the controller (or "business" under U.S. state privacy laws).
Caller / end-customer data (customer is controller). When a business customer connects phone lines or messaging to Orvius, that business is generally the controller of caller and end-customer personal information. Solution Development LLC acts as a processor / service provider — we process that data only to provide, secure, and support the Service on the customer's instructions, and as otherwise described in this policy and our Terms of Service.
Contact for privacy requests: support@orvius.im.
2. Categories of information we collect
A. Business account and profile data. Name, email, phone, business name, trade, service area, hours, services offered, escalation contacts, plan/billing status, and numbers you connect or provision.
B. Authentication data. Sign-in identifiers via Google OAuth (name, email, provider subject id) and session/security cookies as described in our Cookie Policy.
C. Call, SMS, and messaging data. Call and SMS metadata (timestamps, duration, direction, status), phone numbers, message content, recordings or transcripts where enabled, AI summaries, urgency labels, and lead fields (name, address, urgency, service type, notes).
D. Workspace / operations data. Customers, jobs, dispatch assignments, estimates, invoices, payment records you enter, technician contacts, and related audit history created in the product.
E. Website and support data. Forms, waitlist or pilot applications, support emails, and standard technical logs (IP address, user agent, pages, approximate timestamps, error diagnostics).
F. Payment data. Processed by Stripe. We receive billing contact details and payment status tokens. We do not store full card numbers on our application servers.
Sensitive / special categories. We do not intentionally collect government ID numbers, precise geolocation for advertising, biometric templates for identification, or health information regulated as protected health information (PHI) under HIPAA. Callers may volunteer sensitive details in free-form speech or text; if that happens, it is processed as Customer Content to operate the Service for the shop, not to build consumer profiles for sale. Orvius is not a HIPAA-covered product and is not intended for covered entities needing a BAA unless we expressly agree in a signed writing.
3. Sources of information
- Directly from you (signup, settings, forms, support)
- From your connected lines and messaging (callers, SMS, voice AI stack)
- From your authorized users and technicians
- From payment and identity providers (Stripe, Google)
- Automatically from browsers and devices (logs, essential cookies)
4. How we use information
We use information to:
- Operate the night-shift line, workspace, owner alerts, and related product features
- Display calls, customers, jobs, money tools, and history in your dashboard
- Authenticate users, secure accounts, prevent abuse, and debug reliability issues
- Onboard, support, and communicate about the Service (transactional email/SMS)
- Process subscriptions and comply with law, lawful requests, and enforcement of Terms
- Improve Service reliability and quality for your account (for example, fixing failures, tuning prompts under your configuration) — not to sell data
No sale / no ads sharing. We do not sell personal information. We do not share personal information for cross-context behavioral advertising. The one time a caller's details go to another business is the Orvius Network, described in §5, and only when the caller asks for it. We do not use Customer Content to train unrelated third-party foundation models outside what is required to operate the Service through our subprocessors under their terms and our configuration.
Automated processing. The Service uses automated systems (including voice AI and summarization) to handle calls/texts and generate workspace records. These outputs can be wrong or incomplete. Business customers must review material outputs before high-risk decisions. See Terms §9.
5. How we disclose information
We disclose personal information only as needed for:
- Service providers / subprocessors who process data for us under contract (hosting, database, telephony, voice AI, payments, auth) — see §6
- Your organization — account admins and authorized users see Customer Content for their shop
- Legal and safety — to comply with law, lawful process, or to protect rights, safety, and integrity of the Service, users, or the public
- Business transfers — in connection with a merger, financing, acquisition, or asset sale, subject to appropriate confidentiality
- With your direction — integrations or exports you initiate
- Orvius Network, at the caller's request — when a business that uses the Service is fully booked and has the Network turned on, the receptionist (or a text) asks the caller whether their name, phone number, address and the problem they described may be shared with another nearby business on the Network so it can call them. Their details are shared with that one business only if they say yes, and are never shared if they say no or have replied STOP. The business that passed the request may receive a referral credit from that business; the caller is not charged for it.
We do not disclose personal information to data brokers for their independent marketing use.
6. Subprocessors
We use infrastructure and communications providers to run Orvius. Current named processors include:
- Vercel. Application hosting and edge delivery. Data: Account, application, and log data.
- Turso. Managed database (application and shop records). Data: Account, call/lead/job records, and related operational data as stored by the Service.
- Twilio. Telephony, SMS, and related communications. Data: Phone numbers, call/SMS metadata and content.
- Vapi. Voice AI orchestration (may engage nested speech/model providers). Data: Call audio/transcripts and related metadata as configured.
- Stripe. Subscription billing and payment processing. Data: Billing contact and payment tokens (card data on Stripe).
- Google. OAuth sign-in. Data: Account identity (name, email) for authentication.
Voice AI stacks may include additional speech-to-text, text-to-speech, and model providers engaged through our voice platform. Those nested providers process call audio/transcripts as needed to complete a session. We update this list as primary providers change. See also Security.
7. Processor terms (Customer Content)
When we process caller/end-customer personal information as a processor / service provider for a business customer, we will:
- Process Customer Content only to provide and secure the Service and as instructed by the customer (including configuration in-product)
- Require subprocessors to protect Customer Content with appropriate contractual and technical measures
- Assist with reasonable deletion, access, and correction requests the customer must fulfill as controller
- Notify the customer of a confirmed personal-data breach affecting their Customer Content without undue delay where legally required
- Upon account termination, cease active processing and delete or return Customer Content within a commercially reasonable period, except for backups, legal holds, security logs, or records we must retain by law
Business customers are responsible for providing legally required notices to callers and texters, obtaining SMS/consent where required, and configuring recording/AI disclosures for jurisdictions they serve. See SMS Terms and Terms.
8. Retention
We retain business and call-related data while your account is active and for a reasonable period afterward for backups, disputes, security, fraud prevention, and legal compliance. Retention windows vary by data type (for example, security logs may outlast marketing waitlist entries).
Call recordings, call transcripts, and voicemail recordings are deleted 24 months after the call, both in Orvius and at the voice and telephony providers that hold copies. The call's summary and the resulting lead and job history stay with the shop's account. Appointment confirmation links stop working a day after the visit or once the job is closed, and technician job links a week after the visit.
Request deletion of account data at support@orvius.im. We will verify the request and delete or de-identify where feasible. Some records may be retained where required by law, for legitimate security purposes, or until backup cycles rotate.
9. Security
We use industry-standard measures including TLS in transit, access controls, secrets hygiene, and vendor controls appropriate to our stage. No method of transmission or storage is 100% secure. See our Security page. We do not claim SOC 2, ISO 27001, HIPAA, PCI DSS Level 1, FedRAMP, or similar certifications at this time.
10. Your rights and requests
Depending on your location and role (business user vs. caller), you may have rights to access, correct, delete, or export personal information; to appeal a denial; and to opt out of certain processing where applicable law provides that right.
How to submit. Email support@orvius.im with enough detail to locate your data. We may verify identity (and authority, for agents). We respond within timelines required by applicable law (including up to 45 days where required, with permitted extensions).
Callers. If you are a caller seeking deletion or access to data collected by a shop using Orvius, contact that business first as controller. We will assist that business as processor when they instruct us or when law requires. The shop's owner can delete a caller's data from the customer's page in Orvius: their name, number, email, addresses, notes, texts, call recordings and transcripts (including the copies at our voice and telephony providers), and job photos and signatures. The shop keeps that the calls and jobs happened, without those details, and keeps the caller's opt-out from texts so they are never texted again. From the same page the owner can download a copy of everything the shop holds about a caller, to answer an access request.
We will not discriminate against you for exercising privacy rights available under applicable law.
11. California and other U.S. state privacy notices
If you are a resident of California or another U.S. state with a comprehensive consumer privacy law (for example, Virginia, Colorado, Connecticut, Utah, and similar statutes as they apply), this section supplements the rest of this policy.
Categories collected (in the last 12 months, as applicable to our Service): identifiers (name, email, phone, IP); commercial information (plan, billing status); internet/network activity (logs, pages); audio/electronic content (calls, SMS, transcripts where enabled); professional/employment-related information you provide about your shop; and inferences limited to product operation (for example, urgency labels on a lead). We do not collect biometric identifiers for unique identification or precise geolocation for advertising.
Business / commercial purposes of collection and disclosure match §§4–5 (provide Service, security, payments, legal compliance). We disclose categories to service providers listed in §6 and as otherwise described in §5.
Sale and sharing. We do not sell personal information and do not share it for cross-context behavioral advertising as those terms are defined under the CCPA/CPRA and similar laws. We do not have actual knowledge of selling or sharing personal information of consumers under 16.
Sensitive personal information. We do not use or disclose sensitive personal information to infer characteristics about consumers for purposes that require a "Limit the Use of My Sensitive Personal Information" link under CPRA. Account credentials and contents of communications are used to provide the Service you request.
Rights. Subject to verification and exceptions, residents may request know/access, delete, correct, and (where applicable) opt-out of sale/sharing or targeted advertising. Because we do not sell or share for targeted advertising, an opt-out of sale/ sharing is generally not applicable; you may still email support@orvius.im to confirm. Authorized agents may submit requests with proof of authority.
Shine the Light. California Civil Code §1798.83 requests may be sent to support@orvius.im. We do not disclose personal information to third parties for their direct marketing in the manner that statute addresses.
Appeals. If we deny a request, you may appeal by replying to our decision email. If your appeal is denied, you may contact your state attorney general where that remedy is available.
12. Call recording, AI disclosure, and SMS
Business customers are solely responsible for legally required notices to callers and texters about AI handling, recording, monitoring, and messaging consent (including TCPA and state analogues). Availability of product features does not guarantee compliance in every jurisdiction you serve. See SMS Terms and Terms of Service.
13. Bookings made through AI assistants
When someone uses an AI assistant (such as ChatGPT or Claude) with the Orvius connector, the assistant sends us a trade and ZIP code to find shops, and, only to book or request a visit, the person's name, mobile number, service address and description of the problem. We pass those details only to the shop they chose, or for a request where no shop is listed, to the first Orvius shop of that trade nearby, so it can schedule, confirm and carry out the visit. The confirmation is a text from that shop.
We do not receive the person's conversation with the assistant, only what the assistant sends to our tools. The assistant's own provider handles that conversation under its own privacy policy. Once a visit is booked, the shop controls the record as described in section 1. Requests can be sent to support@orvius.im. See AI assistants.
14. International processing
The Service is designed and operated primarily for customers in the United States. Information is processed in the United States (and may transit through subprocessor regions they operate). If you access the Service from outside the United States, you understand information may be processed in the U.S.
We do not currently market Orvius as a GDPR/UK GDPR-ready product with a standard contractual clauses package for EEA/UK controllers. If you require a signed Data Processing Agreement for a specific jurisdiction, contact support@orvius.im before sending regulated personal data.
15. Children
The Service is for businesses and is not directed to individuals under 18. We do not knowingly collect personal information from children. If you believe a child provided data, contact support@orvius.im and we will take appropriate steps.
16. Do Not Track
Some browsers offer a "Do Not Track" signal. Because there is no consistent industry standard for responding to DNT, we do not alter practices solely based on DNT signals. Our default is essential cookies only; see the Cookie Policy.
17. Changes
We may update this policy by posting a revised version with an updated date. Material changes will be posted on this page. Continued use after the effective date constitutes acceptance where permitted by law. If you disagree, stop using the Service and request account closure.
18. Contact
Solution Development LLC
Privacy / legal: support@orvius.im
orvius.im
This Privacy Policy is a protective template for Solution Development LLC. Have qualified counsel review and localize it (including state-law mappings and any EU/UK packaging) before relying on it in a dispute or regulatory response.