This list names the providers that help Relacent run its service, what each one does, the information it handles, where it processes it and how long copies are kept. It is the Provider and Subprocessor List referred to in the Terms of Use, Privacy Policy and Data Processing Addendum.
1 Scope and roles
Relacent uses the fourteen providers below. Relacent’s primary production systems are located in the eastern United States. Each entry gives the provider’s legal name, its function, the information involved, its privacy role, its processing locations and its retention.
A subprocessor handles Customer Personal Data on Relacent’s behalf. Some providers also act as independent controllers for specific information, such as a payment processor’s fraud records or a telephone provider’s call records; the entry says so where that applies. A provider’s headquarters, server region and support-access countries are different facts, and each entry states the ones that apply.
A provider receives only the information needed for the features that use it. Listing a provider does not give it access to every workspace. Links to provider terms are for reference; Relacent’s own commitments are in the Terms of Use, the Privacy Policy and the DPA.
2 Supabase
Provider identity. Supabase, under its published Data Processing Addendum.
Function and data. Database, authentication and private file storage. Workspace records, authentication and account data, uploaded files and necessary technical metadata.
Privacy role. Subprocessor.
Processing locations. Production project region: East US (North Virginia), United States. Supabase support staff may access data from other countries under Supabase’s DPA.
Provider terms or privacy source — https://supabase.com/legal/customer-resources/data-processing-addendum
Retention. Data is kept while Relacent’s project holds it and deleted by Relacent under the deletion schedule in the Terms of Use. Supabase’s managed database backups follow Section 19.
3 Render
Provider identity. Render Services, Inc.
Function and data. Hosting for the Relacent application and its background workers. Requests and workspace information processed by the application, and technical service logs.
Privacy role. Subprocessor.
Processing locations. Production service region: Virginia (US East), United States.
Provider terms or privacy source — https://render.com/dpa
Retention. The application keeps no customer files on Render’s disks. Service logs are kept for the provider’s standard retention period for Relacent’s plan. No separate backups of Customer Content are made on Render.
4 Cloudflare
Provider identity. Cloudflare, Inc.
Function and data. Website delivery and security, and Turnstile bot protection on sign-in and public forms. IP addresses, request and connection metadata and browser security signals. Cloudflare Web Analytics on the public pages of relacent.com: the page address, the referring page, browser and device type, the country inferred from the IP address and page-load timings, with no cookies or browser storage. Web Analytics is not used on app.relacent.com or on pages that businesses send to their customers.
Privacy role. Processor for delivery and security services. For Turnstile, Cloudflare also acts as a controller for the signals it uses to improve bot detection. Web Analytics handles data about visitors to relacent.com and no Customer Personal Data, so it is not subprocessing under the DPA.
Processing locations. Cloudflare’s global network, which may process requests in the location nearest the visitor.
Provider terms or privacy source — https://www.cloudflare.com/turnstile-privacy-policy/
Retention. Web Analytics keeps full-detail page-view data for 7 days and then only aggregated totals, which can be viewed for six months. Relacent does not route private workspace content through Cloudflare logging features.
5 Stripe
Provider identity. The Stripe entity named in Relacent’s Stripe account agreement (for U.S. accounts, Stripe, Inc.).
Function and data. Stripe Billing handles Relacent subscriptions. Stripe Connect handles enabled customer payments to a service business’s own connected Stripe account, including invoice payments, deposits and balance payments. Billing contacts, account and transaction identifiers, payment status, limited payment-method details and fraud and compliance information. Card numbers are entered on Stripe’s pages and are never sent to Relacent.
Privacy role. Processor for some information and independent controller for its own payment, fraud-prevention and legal records, as Stripe’s terms describe.
Processing locations. United States and other countries where Stripe and its providers operate, under Stripe’s DPA.
Provider terms or privacy source — https://stripe.com/legal/dpa
Retention. Stripe keeps payment records it is legally required to keep under its own obligations. Relacent keeps the billing records described in its Privacy Policy.
6 Resend
Provider identity. Plus Five Five, Inc., doing business as Resend, as named in its published DPA.
Function and data. Transactional email delivery. Sender and recipient details, message content and attachments where used, delivery events and service metadata.
Privacy role. Processor for message data; controller for its own account and usage information under its DPA.
Processing locations. Relacent’s sending domains, accounts.relacent.com and updates.relacent.com, are configured in the us-east-1 (North Virginia) region. Resend describes storage in the United States.
Provider terms or privacy source — https://resend.com/legal/dpa
Provider storage source — https://resend.com/security/gdpr
Retention. Open and click tracking is turned off for both sending domains. Message data is kept for the provider’s standard retention period for Relacent’s plan and deleted under Resend’s DPA.
7 Google Maps
Provider identity. Google LLC, under the Google Maps Platform terms for Relacent’s billing account.
Function and data. Maps, address lookup (geocoding) and directions for enabled scheduling and route features. Address or coordinate queries, map requests and technical metadata.
Privacy role. Google acts as an independent controller for the Maps services Relacent uses, under the Google Maps Platform Controller-Controller Data Protection Terms.
Processing locations. Google’s global infrastructure.
Provider terms or privacy source — https://cloud.google.com/maps-platform/terms/maps-controller-terms
Required notices. The Google Maps and Google Earth Additional Terms apply at https://maps.google.com/help/terms_maps/ and Google’s Privacy Policy at https://policies.google.com/privacy. Relacent follows Google’s attribution, caching and storage restrictions.
8 Microsoft 365 email
Provider identity. The Microsoft entity in Relacent’s commercial Microsoft 365 subscription, under the Microsoft Products and Services Data Protection Addendum.
Function and data. Relacent’s business email and customer-support correspondence. Contact details, support messages and attachments people send to Relacent. Microsoft 365 has no access to workspace records.
Privacy role. Processor for hosted email content under the Microsoft DPA.
Processing locations. In the provider’s data regions for Relacent’s Microsoft 365 tenant.
Provider terms or privacy source — https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA
Retention. Support emails are kept while needed to resolve the request and meet legal duties. Deleted emails stay recoverable for up to 30 days, as stated in Section 19.
9 Backblaze
Provider identity. Backblaze, Inc.
Function and data. Encrypted offsite backups of the production database and private files. Backups are encrypted by Relacent before they leave Relacent’s systems; Backblaze stores only encrypted data and does not hold the key.
Privacy role. Processor for stored data under its DPA.
Processing locations. Production bucket region: US East, United States.
Provider terms or privacy source — https://help.backblaze.com/hc/en-us/articles/360004146953-Data-Processing-Addendum
Retention. As stated in Section 19.
10 DigitalOcean
Provider identity. DigitalOcean, LLC, as named in its published Data Processing Agreement.
Function and data. Hosting for document import and text extraction (OCR), and for converting photos and PDF files that users attach to records. Uploaded import files and the text extracted from them; attached photos, including iPhone HEIC photos, which are converted into a clean JPEG copy without location or camera data; attached PDF files, which are checked and returned unchanged; and necessary technical and service logs. Each file is processed in memory in its own isolated container and is not stored on the server.
Privacy role. Subprocessor for Customer Personal Data contained in import files, extracted text, and attached photos and PDF files.
Processing locations. Production server region: New York (US East), United States.
Provider terms or privacy source — https://www.digitalocean.com/legal/data-processing-agreement
Retention. Files are kept only for the request that processes them. Import results are kept only as long as needed for review and safe recovery, within the active-system deletion deadlines. No server backups or snapshots containing customer files are made.
11 HubSpot
Provider identity. HubSpot, Inc., Two Canal Park, Cambridge, MA 02141, United States.
Function and data. Call booking on relacent.com/book (HubSpot Meetings, shown in a frame on that page). HubSpot receives only the details of people who book a call with Relacent there: the name, email address, notes and meeting time they enter, and technical data and cookies inside the scheduler frame. It never receives businesses’ customer data or any workspace records.
Privacy role. Processor for the contact records Relacent keeps in its HubSpot account; independent controller for its own cookies and service data under its privacy policy. Because it handles no Customer Personal Data, it is not a subprocessor under the DPA, and the notice and objection process in Section 16 does not apply to it.
Processing locations. United States. Relacent’s HubSpot account is hosted in HubSpot’s North America data centers.
Provider terms or privacy source — https://legal.hubspot.com/privacy-policy
Retention. Booking contacts are kept in Relacent’s HubSpot account while needed for follow-up about Relacent and are deleted on request.
12 Sentry
Provider identity. Functional Software, Inc. d/b/a Sentry, 45 Fremont Street, 8th Floor, San Francisco, CA 94105, United States, as named in Sentry’s published DPA.
Function and data. Error monitoring for the Relacent app, the admin console and the background worker. When a page or job fails, Relacent’s servers send Sentry the error type, a shortened error message, the code location, the route pattern of the page or job (for example /organizations/:id/customers), the software release and a report reference. Before sending, Relacent removes email addresses, phone numbers, street addresses, IP addresses, card and account numbers, link tokens and query strings. Browsers never contact Sentry. No names, cookies, request contents, session replays or screen recordings are sent, and business and user identifiers are sent only as one-way codes.
Privacy role. Processor for the error reports Relacent sends. The reports are designed to contain no Customer Personal Data; because a report could still carry a fragment the filters miss, Relacent treats Sentry as a subprocessor under the DPA.
Processing locations. United States.
Provider terms or privacy source — https://sentry.io/legal/dpa/
Retention. Error reports are kept for 30 days and then deleted by Sentry.
13 Retell AI
Provider identity. Retell AI, Inc., under its published Data Processing Addendum (last updated July 8, 2026).
Function and data. AI voice agent for the AI receptionist add-on: answers calls, converts speech to text and text to speech, runs the conversation model, transfers calls, records calls, produces transcripts and post-call summaries, and writes replies to customers’ texts when the business turns that on. Call audio, recordings, transcripts, summaries, caller telephone numbers, caller-provided details, call metadata, and the text of customer messages passed for AI replies.
Privacy role. Subprocessor (service provider under the CCPA terms of its DPA). Retell’s own AI-model, speech and voice providers are its subprocessors; Retell states they are contractually barred from training on this information. Retell states it may use de-identified or aggregated information to improve its own products, including its models. Retell gives Relacent 15 days’ notice of new providers, which Relacent passes on under Section 16.
Processing locations. Amazon Web Services us-west-2 (Oregon), United States. Retell staff may access data for support from the United States and Canada. AI-model processing for the receptionist runs through Anthropic or Amazon Bedrock, and voices through Retell’s speech providers, as listed in Retell’s subprocessor list (trust.retellai.com/subprocessors).
Provider terms or privacy source — https://retellai.com/legal/data-processing-addendum
Retention. Every receptionist agent is set to keep only basic call details, with no recordings, transcripts or logs after about 10 minutes, and 1-day retention of those details. Relacent copies each recording into its own private storage and then deletes Retell’s copy of the call. Retell’s backups follow Section 19. Retell holds a SOC 2 Type II report.
14 Telnyx
Provider identity. Telnyx LLC, under its published Data Processing Addendum (version 3.0).
Function and data. Telephone numbers, call carriage to the AI receptionist, call transfer, and business texting: the receptionist number of each business that uses the AI receptionist, and the texting number and carrier registration of each business that texts through Relacent. Telephone numbers, call and message detail records, message content, delivery events, opt-out keywords, and the business details needed for carrier (10DLC) registration.
Privacy role. Processor for message content and other customer content. Independent controller for call and message detail records, account data and billing and fraud-prevention data, as its DPA states. Telephone carriers have their own separate roles.
Processing locations. Telnyx states that its primary processing facilities are in the United States.
Provider terms or privacy source — https://telnyx.com/legal/data-processing-addendum
Retention. Calls are not recorded at Telnyx. Telnyx keeps call and message detail records as an independent controller for its own billing, fraud-prevention and legal purposes. Message content is deleted under Telnyx’s DPA. Telnyx notifies Relacent of new subprocessors with a 10-day objection period, which Relacent passes on under Section 16.
15 Anthropic
Provider identity. Anthropic, PBC, under Anthropic’s Commercial Terms of Service and its Data Processing Addendum, which the Commercial Terms incorporate by reference.
Function and data. AI model for Relacent’s AI features (the assistant, quote drafting, follow-up messages, visit reports and translations): the records, notes, photos and instructions needed for each request, and the generated result. Requests are sent from Relacent’s servers through Relacent’s own Anthropic account; browsers never contact Anthropic. The AI receptionist’s model runs through Retell AI instead (Section 13).
Privacy role. Subprocessor. Anthropic’s Commercial Terms state that it may not train models on customer content from its services. Relacent does not submit content to Anthropic as feedback.
Processing locations. Data is stored in the United States. Model processing may run in other countries where Anthropic operates, which Anthropic says include the United States, Europe, Asia and Australia. Anthropic’s own subprocessors are listed at trust.anthropic.com/subprocessors.
Provider terms or privacy source — https://www.anthropic.com/legal/data-processing-addendum
Retention. Inputs and outputs are deleted within 30 days of receipt or generation, except content flagged under Anthropic’s usage policy (kept up to 2 years, with safety scores up to 7 years) or where the law requires. Relacent does not use Anthropic’s file storage. Anthropic gives notice of new subprocessors with a 15-day objection period, which Relacent passes on under Section 16.
16 Changes objections and contact
A new or replacement subprocessor engaged directly by Relacent requires at least 30 calendar days’ advance email notice and a 30-day objection period, as the DPA describes. A provider engaged by a listed subprocessor follows that subprocessor’s notice period (Retell AI: 15 days; Telnyx: 10 days; Anthropic: 15 days). Relacent emails Customers within 2 business days after receiving such a notice, and an objecting Customer may pause the affected feature or end it. The DPA sets out the resolution and termination periods and the refund of unused prepaid fees for the affected service.
Questions, retention information and objections: support@relacent.com. This list is published at https://relacent.com/subprocessors.
17 What is not on this list
Relacent does not use advertising networks, session-replay tools or third-party visitor analytics, other than Cloudflare Web Analytics on relacent.com’s public pages (Section 4). Apart from Anthropic (Section 15) and the AI-model providers named in the Retell AI entry (Section 13), Relacent uses no other AI-model provider.
Domain registration, source-code hosting, development tools and payment networks do not receive workspace content and are not subprocessors. Relacent does not put production customer data into development tools.
18 Required backup schedule
Section 19 states, for each backup that can contain Customer Personal Data, the data involved, the event that starts the period and the maximum period. Backups are kept separate from ordinary use and used only for disaster recovery. Deletion instructions are reapplied before any restored record returns to ordinary use.
The 30-day active-system deletion commitment in the Terms of Use and DPA is separate. A deletion response says when active deletion was completed and when the remaining backup copies expire.
19 Backup schedule
Relacent encrypted offsite backups (Backblaze, US East). Scope: database and private file backups. Each backup copy is deleted no later than 30 days after it is created, so a record deleted from active systems leaves all Relacent backup copies no later than 30 days after active-system deletion. Backups are encrypted, stored privately and used only for disaster recovery.
Supabase managed database backups (East US). Scope: the production database. Daily backups are kept for 7 days on Relacent’s plan, so a deleted record leaves these backups no later than 7 days after active-system deletion.
Retell AI voice-agent data. Scope: receptionist call and chat records held by Retell (recordings, transcripts, logs and call details). Retell deletes recordings, transcripts and logs about 10 minutes after each call’s post-call processing and keeps only basic call details for at most 1 day. Relacent deletes Retell’s copy of each call once Relacent’s own copy is stored. Retell states that encrypted backups are kept for up to 35 days, so residual copies leave Retell’s backups no later than 35 days after the call or after Relacent’s deletion request. If Relacent closes its Retell account, Retell states that all remaining data is erased within 60 days.
Anthropic. Relacent keeps no backup copies with Anthropic. Requests and results leave Anthropic’s systems within 30 days of the request, except as stated in Section 15.
Telnyx. Call and message detail records are Telnyx’s own records as an independent controller (Section 14) and are not part of this schedule. Relacent keeps no backup copies with Telnyx.
Microsoft 365 email. Deleted support emails remain recoverable for up to 30 days, unless a legal hold applies.
Render, Resend, DigitalOcean, Cloudflare, Sentry and HubSpot. Relacent keeps no separate backup copies of Customer Content with these providers. Their own logs and records follow the retention stated in their entries.
Overall limit. Residual backup copies expire no later than 30 days after active-system deletion, except receptionist call and chat data in Retell AI’s backups, which expire no later than 35 days after the call or after Relacent’s deletion request.