8x Sub-processor List
Last updated: 2 November 2026
1. About this list
This is the public, versioned list of third-party service providers ("sub-processors") that 8x Social, Inc., a Delaware corporation ("8x", "we") engages to help operate its platform. Each sub-processor receives or has access to personal data that 8x controls, and processes it only on 8x's documented instructions and under contract.
8x is the controller for all personal data described in its privacy notices — both the data of its sales representatives (independent contractors and applicants) and the data of the business prospects whom representatives contact. 8x does not act as a processor for the business customers of its managed service; the providers below are 8x's own sub-processors. The one exception is the 8x Dialer: for a business that runs its own reps on it, 8x processes that business's data on its behalf, under the 8x Dialer's data processing agreement, which lists the sub-processors that data reaches. See Rep & Applicant Privacy Notice (rep-facing) and Prospect Privacy Notice (prospect-facing) for the underlying processing descriptions, and DPA and transfer register / internal compliance records for the internal record this table backs.
This list supports:
- the privacy notices, which reference it for the identity of recipients;
- the internal DPA register and Record of Processing Activities (RoPA); and
- 8x's cross-border transfer documentation (see Section 5).
The "Location" column states where the relevant processing/account is configured.
2. Current sub-processors
| # | Sub-processor | Service / Purpose | Categories of personal data shared | Location (processing / data residency) | Cross-border transfer mechanism (for non-US data subjects → US) |
|---|---|---|---|---|---|
| 1 | Twilio Inc. | Outbound telephony for cold calls; carrier connectivity; call audio capture | Prospect phone numbers; call audio (rep + prospect voice); call metadata (timestamps, duration, call status); caller ID / per-rep number | United States | See Section 5. |
| 2 | OpenAI, L.L.C. | (a) Speech-to-text transcription of call audio (whisper-1); (b) AI evaluation of call transcripts (gpt-4.1) that drives meeting-qualification and rep pay | Call audio; AI-generated transcripts; rep identifiers tied to a call; prospect identifiers present in transcript content | United States. Default API endpoints are in use; no zero-data-retention (ZDR) / enterprise tier has been elected — see Section 4. | See Section 5. |
| 3 | Anthropic, PBC | AI evaluation and summarization of call transcripts (Claude models) | AI-generated transcripts; rep identifiers tied to a call; prospect identifiers present in transcript content | United States. Default API endpoints are in use; no zero-data-retention / enterprise tier has been elected — see Section 4. | See Section 5. |
| 4 | Supabase, Inc. | Primary application database (Postgres), authentication, and file storage (Storage buckets) — the system of record | All categories of rep and prospect personal data, including: account credentials, names, contact details, country, CV files, training/performance records, payout data, IP addresses; prospect names, companies, emails, phone numbers, LinkedIn, firmographics, free-text rep notes; voice recordings, AI transcripts, and AI evaluations | United States (us-east-1) | See Section 5. |
| 5 | Vercel Inc. | Application hosting, serverless compute, edge/CDN delivery | IP addresses and request metadata in server/access logs; any personal data transiting requests to the application | United States / global edge network | See Section 5. |
| 6 | Resend (Plus Five Five, Inc.) | Transactional email and rep/prospect outreach email delivery | Rep email addresses and names; prospect email addresses, names, and any personal data contained in message content | United States | See Section 5. |
| 7 | Cal.com, Inc. | Meeting scheduling for booked calls | Prospect-entered scheduling data (name, email, chosen time, any notes); rep identifier for the host | United States / EU (provider-configured) | See Section 5. |
| 8 | PostHog, Inc. | Product analytics and privacy-masked session replay to improve the Platform — under the consent rule in Cookie Notice: where consent is required, activated only after the visitor accepts the cookie banner; elsewhere on load, unless the visitor rejects or the browser sends Global Privacy Control; if the visitor declines, only a privacy-preserving, non-identifying count is kept (no cookies, no device storage) | Website-visitor / rep online identifiers, usage and event data, and masked session recordings (only the Platform's interface text is readable — navigation, tabs, column headings, labels, steps, error headings, and the text of the public website, sign-in and legal pages; all other text and every form input are masked — no readable names, emails, phone numbers, notes, or lead data). No prospect personal data | European Union — PostHog Cloud EU (eu.posthog.com); data residency in the EU | EU-hosted; no transfer to the US for this processor. For non-EU data subjects, data is processed in the EU. |
| 9 | Google LLC (Google Analytics, Google Ads, Google Workspace) | Change note: November 2026: analytics and ad measurement now load on visit outside consent regions; a decline or Global Privacy Control turns them off. Earlier declines stay declines. (a) Website analytics (Google Analytics 4) measuring site usage to improve the site — under the consent rule in Cookie Notice: where consent is required, loads only after the visitor accepts the cookie banner; elsewhere on load, unless the visitor rejects or the browser sends Global Privacy Control; (b) advertising measurement on the company pages (the home page, the /for-companies pages, and /dialer and its feature pages): the Google Ads tag records inquiries, booked calls and 8x Dialer waitlist sign-ups as conversions for 8x's Google Ads campaigns — under the same rule, and never when the browser sends Global Privacy Control; (c) a call booked on Cal.com, reported to Google Analytics by 8x's server (the event and the Google Analytics client identifier only), under the consent rule in Cookie Notice; (d) Google Workspace on 8x's own Google account (8x.social): 8x's team calendar, the meetings 8x books on it, their Google Meet rooms, and who joined them, read from Meet and from 8x's Meet audit log | Website-visitor / rep online identifiers (GA client-id cookie, IP address — GA4 does not store the full IP), device/browser metadata, and page-interaction events; on the company pages, the Google ad-click identifier and conversion events. For (a) to (c), visitor browsing data only — no prospect personal data. For (d), the email address of the person invited to a meeting on 8x's calendar and their company's name (or their name) in its title, and who joined it: each participant's name, Google account id when signed in, and join and leave times, and a signed-in participant's email address from the Meet audit log; no recordings, transcripts or chat | (a) to (c): United States. (d): wherever Google keeps data centres, the United States among them | See Section 5. (Google is EU-US Data Privacy Framework-certified; per Section 5, default to SCCs + TIA.) |
| 10 | Meta Platforms, Inc. (Meta Pixel, Conversions API) | Change note: November 2026: analytics and ad measurement now load on visit outside consent regions; a decline or Global Privacy Control turns them off. Earlier declines stay declines. Advertising measurement for 8x's ads to businesses: (a) the Meta Pixel on the company pages (the home page, the /for-companies pages, and /dialer and its feature pages) — under the consent rule in Cookie Notice (only after the visitor accepts where consent is required, on load elsewhere), and never when the browser sends Global Privacy Control; (b) inquiries, booked calls and 8x Dialer waitlist sign-ups reported by 8x's server through Meta's Conversions API — opt-in where consent is required (the regions listed in Cookie Notice, Section 4); elsewhere on unless the visitor rejects or the browser sends Global Privacy Control | Company-page visitors' online identifiers (Meta browser and click identifiers), IP address and browser user agent, page views and conversion events, and the email address entered in an inquiry, a booking or a waitlist sign-up, hashed with SHA-256 before it is sent. No prospect personal data from prospecting | United States (Meta Platforms Ireland Limited for visitors in the EU/EEA, the UK and Switzerland) | See Section 5. |
| 11 | Slack Technologies, LLC (a Salesforce company) | 8x's own Slack workspace, where 8x's staff work: alerts about new bookings on 8x's own and managed campaigns, calendar connections, company inquiries and intro calls, the 8x Dialer waitlist, dialing health, lead supply and daily calling reports; reps' support chat, mirrored from the app with staff replies; and, for the 8x Dialer, 8x's copy of a client's chat with 8x and 8x's alerts about a client (its application, calling signals, complaints and payments). A client's own Slack, which the client connects to the 8x Dialer, is the client's provider, not 8x's sub-processor | Rep names, email addresses and support-chat messages; for a booking on 8x's own or a managed campaign, the prospect's name, company, job title, industry, country, phone number, email address, and profile and company website links, the meeting's time and link, the rep's and account manager's notes about the call, the AI booking check with up to two of its reasons, and the rep's name and email address; company contacts' names and work email addresses from inquiries, intro calls and the waitlist; calendar owners' names and email addresses; the names and chat messages of people at 8x Dialer clients | United States (Slack's default storage; 8x has chosen no data residency region) | See Section 5. |
| 12 | Deepgram, Inc. | Speech-to-text transcription of calls (Nova-3 models): (a) live, for the call's live transcript: the rep's browser streams the rep's microphone and the prospect's audio to Deepgram as two separate streams, from when the prospect is connected until the call ends, never while the recording notice plays; (b) after the call, each channel of the call recording (the prospect's and the rep's), sent separately for the call's transcript, which the AI evaluation reads; (c) practice calls: the rep's voice, live and from the practice call's recording | Call audio (rep + prospect voice); practice-call audio (the rep's voice); recognition hints sent with a call: the prospect's first and last name, their company's name, the rep's calling name, and the name in the prospect's email or website domain (never a full email address); the transcripts Deepgram returns | United States. Processes under its own terms. | See Section 5. |
3. Intended sub-processors (not yet live)
These providers receive no personal data yet. Each moves to Section 2, with the notice Section 6 describes, before the processing begins.
| Sub-processor | Service / Purpose | Categories of personal data shared | Location (processing / data residency) | Cross-border transfer mechanism (for non-US data subjects → US) |
|---|---|---|---|---|
| LiveKit Incorporated | Real-time audio, video and screen sharing for team rooms inside the Platform, where a team trains and syncs (never a meeting with a prospect); later, audio-only room recordings, each speaker's microphone recorded as its own track and written to 8x's own storage | The voice, camera video and shared screen of the people in a room, relayed and not stored by LiveKit (they may include any personal data a participant shows on a shared screen); each participant's 8x identifier, never a name or email; IP addresses and connection metadata. No prospect call audio: a call never enters a room | Media: LiveKit Cloud's global network, each participant connecting to the nearest server. Project analytics, telemetry and logs: United States (LiveKit Cloud's US data region) | See Section 5. (LiveKit is EU-US Data Privacy Framework-certified; per Section 5, default to SCCs + TIA.) |
4. AI provider data-retention posture
OpenAI (#2) and Anthropic (#3) are currently used through their default API endpoints, with no zero-data-retention (ZDR) or enterprise tier elected. Under default API terms these providers may retain submitted content for a limited period (e.g. for abuse monitoring) before deletion, per the provider's then-current policy.
Because the data sent to these providers includes call audio and transcripts of real prospects, 8x's default posture is to elect a zero-data-retention / enterprise arrangement (and an EU/regional endpoint where offered) to minimize provider-side retention and tighten the transfer posture. 8x is evaluating electing such an arrangement for OpenAI and Anthropic and will update this Section and the transfer documentation accordingly.
5. Cross-border transfers
All current sub-processors except PostHog (#8, hosted in the EU) process data in, or transfer data to, the United States. Personal data of prospects and representatives in Brazil, Mexico, India, and the EU/UK (EU/UK is in scope — see DPA and transfer register) therefore flows from those jurisdictions to US-based processors, which engages cross-border transfer obligations:
- Brazil (LGPD): International transfers to US processors require ANPD Standard Contractual Clauses (Resolution CD/ANPD No. 19/2024). 8x is putting the ANPD Standard Contractual Clauses in place with its US sub-processors for these transfers.
- Mexico (Federal Law on Protection of Personal Data Held by Private Parties, in force 21 March 2025): Transfers to US sub-processors must be disclosed in the Spanish
aviso de privacidadunder Art. 35 (transfer disclosure is still required even though Art. 15's express enumeration changed). Contractual transfer safeguards with each recipient are recommended. - India (DPDP Act 2023 + DPDP Rules 2025): Transfers are permitted except to countries restricted by the Central Government. Separately, under the DPDP Act cold outreach generally requires consent and a notice is not a substitute for consent; 8x is aligning its India outreach to a consent-first approach, honors all opt-out and do-not-contact requests, and treats India activity as subject to Indian-counsel review before scaling. See Prospect Privacy Notice and DPA and transfer register.
- EU/UK (in scope): EU/UK IS in scope — GDPR and the ePrivacy Directive apply (no EU-exclusion gate). Chapter V transfers to US sub-processors require SCCs (Module 2) plus a documented Transfer Impact Assessment (TIA); treat the EU-US Data Privacy Framework as unstable (pending the Latombe appeal) and default to SCCs + TIA. ePrivacy Art. 13 prior consent also applies to electronic/automated direct marketing to EU prospects (outreach email via Resend, automated calls). See DPA and transfer register.
For each sub-processor above, 8x maintains the applicable provider DPA and transfer instrument (SCCs / regional equivalent) in the DPA register (DPA and transfer register).
6. Changes to this list and advance notice
8x maintains this list as the authoritative, versioned record of its sub-processors. When 8x intends to add a new sub-processor, change the purpose for which an existing one is used, or bring an intended sub-processor (Section 3) live, 8x will:
- update this list and increment the document version (Section header), and
- provide advance notice of the change before the new processing begins.
8x will provide at least 30 days' advance notice before the change takes effect, except where a faster change is required to maintain security or service continuity, in which case notice will be given as soon as reasonably practicable.
Questions or updates: to ask about this list or 8x's use of any sub-processor, or to request notice of changes, contact our Privacy Team at privacy@8x.social.
7. Document control
| Field | Value |
|---|---|
| Controller | 8x Social, Inc., a Delaware corporation |
| Registered address | 1111B S Governors Ave STE 47647, Dover, DE 19904, United States |
| Privacy contact | our Privacy Team, privacy@8x.social |
| Governing law | Delaware, United States |
| Version | 1.7 — 2 November 2026 |
| Related documents | Rep & Applicant Privacy Notice, Prospect Privacy Notice, DPA and transfer register, internal compliance records |