1. How to read this register
This register describes the providers used to deliver the service. A provider processes your information only where used for the selected service. It is not a certification that each provider is active in production. Before activating a customer’s service, Linevio confirms the providers, products, processing locations, and data-protection terms applicable to that service. No exclusive U.S. residency or certification is implied.
Our service providers may act as subprocessors for customer call data or as independent controllers for limited functions such as their own payment compliance. Customer-controlled integrations are separately identified. Changes affecting customer personal information follow the notification and objection process in the Data Processing Addendum.
2. Supabase - application data and authentication
Purpose: database, authentication, and private application storage. Information may include customer account and business configurations, approvals, call metadata and summaries, protected transcript data where configured, uploaded source files, and audit records. Processing locations, retention, and backup settings are documented for the applicable service before activation.
3. OpenAI - AI processing
Purpose: live speech interaction and supported analysis of approved setup materials. Information may include live audio, call context, transcripts, approved business facts, and setup documents and images a customer or Voice Partner uploads, which are sent to OpenAI to propose business facts for human review. Selected products and contractual settings determine provider retention; do not assume that an application storage setting guarantees zero provider retention. Production provider terms must support the data-use restrictions in the Data Processing Addendum.
4. Twilio - phone numbers and call routing
Purpose: the Linevio phone numbers to which a customer forwards calls, and the encrypted SIP connection that carries each call to the AI voice service. If that service is unavailable, Twilio routes the call to an outage voicemail box. Information may include caller, dialed, and forwarding numbers, call timing and other call metadata, live call audio in transit, and messages callers leave in the outage voicemail. Twilio acts under Linevio’s account; the customer’s own carrier remains separate.
5. Stripe - subscriptions and payments
Purpose: secure checkout, subscriptions, invoicing, payment processing, fraud prevention, and billing compliance. Information may include business contact and billing details, payment details submitted directly to Stripe, subscription identifiers, and metered usage totals. Full call transcripts are not needed for payment processing. Stripe’s role may differ by activity and is governed by the applicable payment and privacy terms.
6. Resend - transactional email
Purpose: service, setup, billing, and support emails. Information may include recipient contact details, message content, private service links, and delivery events. Email may contain limited account or call-outcome information where that notification is enabled; it is not a reason to include unnecessary sensitive caller data.
7. Website, worker hosting, and telephone infrastructure
Vercel provides website and application hosting; Railway hosts the persistent voice worker. Hosting providers process application traffic, request and security metadata, and service data needed by the hosted components. The voice worker processes live call context and protected recovery records. Linevio’s phone numbers and SIP routing are provided by Twilio, described above.
8. Google Analytics - public website measurement
Purpose: limited audience and interaction measurement on public marketing pages. Google Analytics is a website measurement provider for Linevio's own marketing activity, not a processor for customer call service data. Information may include a sanitized page URL containing only the path and allowed utm campaign parameters, page title, approved interaction events, a pseudonymous cookie identifier, and browser, device, language, network, session, and approximate location information. It does not receive portal, admin, setup, support, approval, checkout, caller, transcript, recording, uploaded-source, or connected-system data from this implementation.
Advertising storage, advertising user data, and advertising personalization consent are denied. Google signals and advertising personalization are disabled, Global Privacy Control prevents the tag from loading, and user-level and event-level retention is set to two months. First-party _ga cookies may remain for up to two years unless the browser or user removes or limits them. Google LLC provides the service under its applicable terms and privacy controls.
9. Cal.com - calls booked with Linevio
Purpose: the booking page and meeting details for calls that prospective and current customers book with Linevio from the website. Cal.com is a provider for Linevio's own customer relationship activity, not a processor for customer call service data. Information may include the name, email address, time zone, chosen time, and notes a person enters, booking records, and, when the call uses Cal.com's video meeting, the meeting link and the information Cal.com processes to run that meeting.
The booking page loads only after a person chooses to book a call, and Linevio does not pass page addresses or query parameters to it. Cal.com provides the service under its applicable terms and privacy policy and may use its own service providers. This is separate from the customer-authorized Cal.com connection in section 10, which books appointments with a customer's own business.
10. Customer-authorized services
Cal.com: where the customer connects its account, the service checks approved availability, creates confirmed bookings, and reschedules verified future bookings. Data may include attendee name, email, booking reference, time, and appointment details. Appointment cancellation remains with the customer’s team. The service order identifies whether the account is customer-contracted or Linevio-contracted.
Compatible CRM endpoint: where approved, the customer’s chosen HTTPS endpoint receives the supported structured completed-call outcome, not a full transcript. The customer chooses and authorizes that recipient and governs its later use under its own agreement.
Customer’s existing carrier: the customer retains its public number and authorizes forwarding. The carrier handles its own network and account information under the customer’s carrier agreement. Linevio’s own numbers and call routing are provided by Twilio, described above.
11. Changes in this version
This release adds Cal.com for calls booked with Linevio from the website and updates the Privacy Notice to describe the booking information collected, how it is used, and the booking page's cookies. It does not add a provider for customer call data or change how that data is processed.