Subprocessors

Loray (loray.ai)
Last updated: April 25, 2026 · Version 3

Loray uses the following third-party subprocessors to deliver its services. Each subprocessor is bound by a written Data Processing Agreement (DPA) or equivalent contractual data protection terms and is only permitted to process data for the specific purposes listed below.

All subprocessors currently operate via US-based endpoints or are used for data stored and processed in the United States.


Telephony & Messaging

Telnyx

Purpose
SMS delivery, A2P 10DLC messaging, inbound and outbound voice calls, phone number provisioning, carrier campaign management, call routing, and related telephony infrastructure.

Data processed
Phone numbers in E.164 format, SMS message content, voice call audio streams, call metadata, delivery status, timestamps, call duration, caller ID, and related routing data.

Location
USA

DPA
telnyx.com/legal/dpa


TCR (The Campaign Registry)

Purpose
A2P 10DLC brand and campaign registration required by major US carriers.

Data processed
Client business identifiers, such as EIN, legal business name, business address, brand metadata, campaign description, sample messages, and related compliance information.

TCR processes Client business data only. Loray does not intentionally send end-user contact data to TCR.

Location
USA

DPA / Terms
Per TCR standard terms.


AI & Language Processing

Deepgram

Purpose
Speech-to-text transcription of voice calls, including real-time or near-real-time transcription used to operate Loray's AI voice assistant.

Data processed
Voice call audio and resulting transcripts. Loray does not intentionally send raw phone numbers to Deepgram as separate identifiers; however, call audio may contain personal information if spoken by a call participant.

Location
USA

DPA
deepgram.com/legal/dpa


Google Cloud Text-to-Speech

Purpose
Voice synthesis for AI assistant responses during calls, including generation of spoken audio from AI-generated text using Google Cloud Text-to-Speech, including Chirp 3 HD or similar Google Cloud voice models.

Data processed
Text strings sent for speech synthesis, such as AI-generated responses. Loray does not intentionally send phone numbers or direct contact identifiers for text-to-speech generation.

Location
USA, currently using US-based Google Cloud endpoints where available, including us-west1 Oregon.

DPA
cloud.google.com/terms/data-processing-addendum


Anthropic (Claude)

Purpose
Primary AI language model provider for generating AI assistant responses to customer inquiries through the Claude API.

Data processed
Conversation context, messages, transcripts, service details, appointment-related information, and inquiry content provided by the contact or Client.

Loray removes direct phone-number identifiers before sending conversation context to AI language models where technically feasible. Conversation content may still contain personal information, such as name, service address, service request details, or other information voluntarily provided during the conversation.

Location
USA

DPA / Terms
anthropic.com/legal/commercial-terms, including applicable data processing terms.


OpenAI (API)

Purpose
Fallback AI language model provider for specialized processing, redundancy, and service continuity.

Data processed
Conversation context, messages, transcripts, service details, appointment-related information, and inquiry content provided by the contact or Client.

Loray removes direct phone-number identifiers before sending conversation context to AI language models where technically feasible. Conversation content may still contain personal information, such as name, service address, service request details, or other information voluntarily provided during the conversation.

Location
USA

DPA
openai.com/policies/data-processing-addendum


Note on AI Data Handling

Loray does not permit AI subprocessors to use Client data or end-user contact data to train their general-purpose AI models.

Loray removes direct identifiers, such as phone numbers, before sending conversation context to AI language models where technically feasible. However, conversation content may still include personal information provided by the caller or message sender, such as a name, address, service issue, appointment request, or other details needed to provide the service.

Zero-data-retention or reduced-retention configurations are used where available and commercially supported.


Billing & Payments

Stripe

Purpose
Subscription billing, payment processing, invoices, receipts, payment method management, tax-related payment records, and automatic top-up billing.

Data processed
Client billing data, such as name, email address, billing address, payment method metadata, subscription status, invoice history, transaction metadata, and tax-related billing information.

Stripe does not receive end-user contact conversation data from Loray.

Location
USA

DPA
stripe.com/legal/dpa


Communications

Resend

Purpose
Transactional email delivery to Clients, including platform notifications, billing receipts, account notices, onboarding messages, security notices, and support-related emails.

Data processed
Client name, email address, email subject, email body, delivery metadata, and engagement events such as delivery, bounce, or open status where available.

Resend does not receive end-user contact conversation data from Loray.

Location
USA

DPA
resend.com/legal/dpa


Infrastructure

OVHcloud (US, LLC)

Purpose
Application hosting, database storage, MySQL hosting, Redis cache, server infrastructure, networking, backups, and related infrastructure services.

Data processed
All categories of data processed by Loray may be stored or processed on Loray-controlled infrastructure hosted by OVHcloud, including Client data, contact data, SMS content, voice transcripts, call metadata, configuration data, audit logs, and operational records.

Location
USA — Oregon, region us-west-or-2, Hillsboro, OR.

DPA
us.ovhcloud.com/legal/data-processing-agreement


Changes to This List

Loray updates this page when subprocessors are added, removed, or materially changed.

Clients are notified by email at least 30 days in advance of additions or changes that may materially affect data processing.

Clients may object in writing to a new subprocessor within 15 days of notice by emailing [email protected]. If the objection cannot be resolved, the Client may terminate the affected service without penalty.


Change Log

April 25, 2026

Change
N/A


Contact

For questions about Loray's subprocessors, DPAs, or data processing practices:

Email: [email protected]
Website: loray.ai