Overview
Xive — the platform owned and operated by Xive Inc., a Florida company — relies on a small number of service providers, often called “vendors” or “subprocessors”, to run the Services. They host our infrastructure, deliver video, move money, send messages, and help us keep the platform safe.
This page names the providers that materially process personal information today. What data we share with them, and on what legal bases, is governed by our Privacy Policy. Technical safeguards are summarised in our Data Storage & Security Overview.
Providers we use
- Google Cloud (Google LLC) — compute and managed PostgreSQL hosting for the platform and its primary database, in the United States; Cloud Text-to-Speech for reading viewers’ paid chat messages aloud on stream. Processes: everything stored by the Service, and the text of messages sent for reading aloud.
- Cloudflare, Inc. — DNS, content delivery, TLS termination, web application firewall and bot mitigation; Cloudflare Stream for live ingest, recording, and video delivery; Cloudflare R2 for stored media; Cloudflare Workers AI for automated media screening; relay servers for voice and video in Hubs when a direct connection is not possible. Processes: IP addresses and request metadata, uploaded media, live video and recordings, and encrypted call traffic it relays but cannot read.
- 2633134 Alberta Inc. — a Canadian company that holds the Google Cloud and Cloudflare accounts the Services run on and administers them on our behalf, and operates our standby servers and backups in Canada so the Services can keep running if our primary hosting fails. Google Cloud and Cloudflare provide the services described above under those accounts. Processes: everything stored by the Service, as the holder of the accounts it is hosted in, and a continuously updated standby copy and backups of that data in Canada.
- Cybera Inc. — cloud hosting in Alberta, Canada for the standby servers and backups operated by 2633134 Alberta Inc. Processes: the continuously updated standby copy and backups of the data stored by the Service.
- KLIPY — GIF and sticker search. Processes: your search terms and a one-way hashed identifier, never your account ID or name.
- OpenStreetMap Foundation (Nominatim) — converting coordinates you share when setting your profile location into a city and region. Processes: those coordinates.
- Stripe, Inc. — card payments on the web, and Stripe Connect for creator identity verification, tax collection, and payouts; and Stripe Identity for identity and age checks. Processes: payment credentials (which we never see), transaction data, creator identity and bank details, and the government ID and selfie submitted for identity checks (of which Xive receives only the result).
- Didit Identity, Inc. — the selfie age check offered in some places as an alternative to an ID check. Processes: the selfie you take, to check it shows a live person and to estimate your age; Xive receives only the result, and we ask Didit to delete the selfie as soon as we have it.
- Apple Inc. — in-app purchases through the App Store and push notification delivery to iOS devices. Processes: purchase receipts and device push tokens.
- Google LLC — in-app purchases through Google Play and push notification delivery to Android devices. Processes: purchase receipts and device push tokens.
- Expo (650 Industries, Inc.) — the push notification service that routes our notifications to Apple’s and Google’s push gateways, and delivery of app updates. Processes: device push tokens and notification payloads.
- Postmark (ActiveCampaign, LLC) — transactional and administrative email. Processes: email addresses and message content.
- Google LLC — Google Analytics and Google Ads conversion measurement on the website, only for visitors who opt in to analytics or advertising cookies. Processes: device and browser identifiers, pages viewed, and on-site events.
We run our identity provider, our realtime messaging service, and our voice and video calling service on infrastructure we operate ourselves, so no third-party SaaS provider processes your credentials, your realtime activity, or the content of your calls.
Some services exchange data with Xive only because you choose to connect them. If you connect Twitch or Kick, we keep the access you grant and your stream key so we can send your broadcast to your channel there. If you connect Twitch, Steam, or Discord to a Hub, we confirm the account is yours so the Hub can give you a role or access. Those services handle that data under their own privacy policies, and you can disconnect them at any time.
Apart from the opt-in Google tags above, we do not use third-party advertising networks, marketing platforms, product analytics services, or crash-reporting services.
How we govern vendors
Before a material vendor touches user data in production, we review its documentation, certifications where relevant, and incident history. Riskier relationships receive deeper review or are rejected.
- Confidentiality and use limitations: vendors may use our data only to provide the contracted service, not for unrelated model training or resale unless expressly allowed.
- Data processing terms: where GDPR, UK GDPR, or similar laws apply, we rely on Article 28-style processor obligations covering instructions, subprocessors, deletion or return, and cooperation with audits.
- Security and incidents: vendors commit to notify us of breaches or unauthorised access affecting our data within contractually defined windows and to assist with investigation.
- Sub-subprocessors: where vendors appoint their own subprocessors, we rely on their published change notice processes.
International processing
Our primary hosting is in the United States, with standby servers and backups in Canada operated by 2633134 Alberta Inc. and hosted by Cybera. Content delivery is global by design, so published media may be cached near the person watching it. Didit may process the selfie age check in the European Union. Where cross-border transfers require safeguards — Standard Contractual Clauses, the UK Addendum, or another approved mechanism — we rely on the mechanisms described in our Privacy Policy and in each provider’s data processing terms.
Changes
We add, replace, or retire vendors as the product, security posture, or economics change. Material changes are reflected on this page, and announced in-product or by email where our agreements or the law require it. This page is maintained by hand and reflects our production stack as of the “Last updated” date; short-lived trials and non-production tooling are not listed.
Contact
Questions about vendors, subprocessors, or data processing agreements: [email protected].