Subprocessors
The principal providers that support OrbitPage managed hosting and the purposes for which they receive data.
Effective and last updated: October 22, 20261. How to read this list
This directory distinguishes providers appointed for hosted-service processing, providers used for OrbitPage own controller purposes, customer-contracted services and links or embedded content chosen by users. The DPA authorises only the subprocessors involved in customer-controlled processing. A service name is not evidence of commercial partnership or joint controllership. Official provider terms identify the contracting entity, onward subprocessors and safeguards for the relevant account and service.
2. Current providers
Google Firebase and Google Cloud
Google services provide Authentication and Identity Platform (including MFA), Firestore, App Check and reCAPTCHA Enterprise; Cloud Run, Cloud Scheduler, Cloud Storage and related restricted infrastructure support backups and maintenance. Data includes account and authentication records, workspace content, subscribers, Shop and support records, network/attestation signals and encrypted or restricted recovery copies, as applicable to each service. Google is a processor or subprocessor for contracted customer-data services, with independent purposes governed by the applicable service terms. Firebase Authentication operates in US data centres. The configured provider-backup destination is European Cloud Storage; other service, support and onward-processing locations follow the service configuration and Google disclosures. No blanket EU-only residency is promised.
Firebase privacy and service locations · Cloud DPA · Subprocessors · Google privacy
Vercel
Vercel Inc. hosts the public website, login, dashboard, APIs and scheduled control-plane operations. Its functions process submitted account, workspace, Shop, subscriber and support data as required by each request; hosting logs contain request and technical metadata. Vercel is a processor for OrbitPage controller activities and a subprocessor for customer-controlled features. Processing can involve US and global infrastructure, edge delivery and support, subject to the configured region and Vercel onward-provider terms; a function region is not a general residency guarantee.
Cloudflare
Cloudflare, Inc. and applicable contracting affiliates provide Workers, R2 object storage, KV domain routing, Analytics Engine, cache, DNS, TLS/custom hostnames, Access security and the PostHog managed proxy infrastructure. Data includes published content/media, private revisions and Shop delivery files, domain routing, aggregate page-view/click events and network/security metadata. Cloudflare acts as processor or subprocessor for the relevant service; its own account/security processing follows its terms. Edge processing is global; storage placement and regional options do not establish that all support or network operations remain in the EEA. Transfer safeguards and onward providers are described in its DPA.
Privacy · DPA · Subprocessors
Stripe
The relevant Stripe contracting entities provide Billing, subscriptions, Checkout, Customer Portal, Connect onboarding, direct-charge Shop payments, identity/business verification, fraud checks, invoices, refunds, disputes and payouts. Stripe receives billing contacts, payment and transaction data and seller verification details directly where its flow requires them. Stripe acts as an independent controller for regulated payment, identity, fraud and compliance purposes and as a processor for specified services; it is not categorised as a subprocessor for every payment purpose. Card numbers and identity documents entered on Stripe are not intentionally stored by OrbitPage. Processing is international and follows the Stripe entity/service agreements and transfer terms.
Privacy and roles · DPA · Service providers · Connected Account Agreement
OpenAI
The relevant OpenAI contracting entity provides the Responses API for the public product guide, authenticated page assistance, Launch Kit and, where invoked, moderation review, plus the Moderations API for bounded safety classification. Data sent depends on the request: visitor question and bounded history/public excerpts; account-holder instruction, recent conversation and page context; a re-encoded user screenshot; or bounded publication text. OrbitPage requests store: false for Responses calls; this does not mean zero retention. Standard Responses abuse-monitoring logs may retain content for up to 30 days, subject to legal or safety exceptions. OpenAI documents separate endpoint-specific controls for the Moderations API. Zero-data-retention settings require separate provider approval and are not presumed. API data is not used for model training by default under OpenAI business terms. OpenAI is a processor for OrbitPage requests and a subprocessor where customer-controlled data is sent on customer instructions; business-contract locations, onward providers and transfer safeguards apply, without an unverified EU-only commitment. For automated image-safety checks, OrbitPage sends newly uploaded images to OpenAI before storing them for publication. Video uploads are not checked this way.
Google Analytics 4
Used solely for optional OrbitPage platform analytics after consent, with advertising features disabled. Data includes pseudonymous browser/session identifiers, page/product events and technical metadata. This is OrbitPage controller processing, separate from customer-page reporting. Google processing and transfers follow the Analytics terms; the customer-selected Analytics property on a hosted page belongs to that customer own processing arrangement.
3. Transactional email services
The configured services below transmit account, platform, support, withdrawal or Shop email for the stated channel. Where Purelymail (Add Rabbit LLC) is the configured transport, it handles recipient/sender addresses, message bodies, attachments and delivery/security metadata. Its public privacy notice does not specify an exclusive EEA processing location. Relevant processing terms, location and transfer safeguards depend on the contracted email service and can be requested through the OrbitPage privacy contact. Purelymail privacy.
Resend
Sends account verification and password-reset email. Processes recipient addresses, message content and delivery metadata. Processing locations and transfer safeguards follow the provider terms.
4. PostHog
PostHog, Inc. provides consent-gated platform product analytics, redacted browser error tracking and masked recordings of selected editor sections through PostHog Cloud EU. It receives pseudonymous browser, account and session identifiers, product and device metadata, limited technical error frames and masked interactions. Customer text and inputs are masked; layout, bundled styles, standard icons and static navigation remain visible. It does not receive OrbitPage's customer-page traffic or intentional copies of page content, prompts, credentials or payment details. This processing is separate from tenant Analytics Engine reporting: PostHog processes data for OrbitPage's own controller purposes, rather than acting as a subprocessor for customer-page analytics.
Requests use t.orbitpage.com and PostHog's Cloudflare-based managed reverse proxy. Cloudflare handles network and request information for that delivery; the proxy removes the Cookie header before forwarding to PostHog. The EU ingestion configuration does not imply that every network, support or provider operation occurs exclusively in the EU. PostHog's DPA and subprocessor disclosures describe applicable locations and transfer safeguards.
Privacy policy · Data processing agreement and subprocessors · Managed proxy processing
5. Optional OrbitPage marketing email
Resend (Plus Five Five, Inc.) sends optional OrbitPage welcome, tips and reminder email to consenting accounts and may also supply the dedicated account-email transport when configured. It processes email addresses, language, message content, delivery events and suppression status. It is a processor for OrbitPage controller activities and, if used for customer-controlled Shop messages, a subprocessor for that purpose. It has US-based operations and onward providers; location and transfer safeguards follow the contracted service, not the language of an email.
Privacy · DPA · Subprocessors
6. Operator-managed workflow automation
Where configured, an operator-managed n8n deployment routes contact submissions and related support notifications. n8n is workflow software in that configuration; its licence alone does not make n8n GmbH a recipient of every message. The workflow host and any downstream mail or infrastructure provider must be included in the actual processing arrangement. The public AI guide uses the OrbitPage server and OpenAI directly and does not send chat conversations to n8n. RankBench supplies selected public blog content to a separate ingestion workflow and is not a recipient of customer workspace data merely because its content is published.
7. Customer-selected SMTP providers
When a workspace enables newsletters, its owner supplies and controls the SMTP account. OrbitPage submits recipient addresses and campaign content to that provider on the owner's instructions. Because OrbitPage does not select or contract with one shared newsletter provider for this feature, the customer's SMTP provider is not listed as an OrbitPage platform subprocessor; the customer must assess its terms, processing locations and safeguards.
8. Page-owner selected partner services
A page owner can add external links and consent-gated content from services such as Instagram, Facebook, YouTube, Spotify, Apple Music, Deezer, SoundCloud, Mixcloud, Vimeo, Loom, TikTok, Giphy, Google Maps, Google Calendar, Calendly, Cal.com, Typeform and Google Forms. A Shop seller can connect Cal.com for booking lifecycle updates. A page owner can also choose iubenda, Cookiebot, CookieYes, OneTrust or an approved custom consent manager. These providers are selected by the page owner or visitor, not appointed by OrbitPage to process the platform's own data, so they are not OrbitPage subprocessors for that use.
When a visitor opens a link or consents to load an embed, the selected provider can independently receive network and browser information and use its own identifiers. The page owner must assess the provider, configure the correct consent category and explain the integration in their own privacy and cookie notices. Compatibility with a partner block does not mean that the provider sponsors, endorses or has a commercial partnership with OrbitPage.
For a connected Cal.com account, OrbitPage sends order-linked booking data such as buyer email, booking identifier, status and scheduled times on the seller's instructions. Official policy: Cal.com privacy.
9. Customer-selected destinations and official notices
External services can act as independent controllers or as processors appointed by a customer under a separate agreement. Their actual role depends on the enabled feature. A link does not load its destination until activated; an embedded resource or externally hosted media can disclose network and referrer information when loaded. The directory covers named integrations; custom URLs, images, video, scripts or consent managers introduce the additional providers selected by the page owner.
Social, messaging and source destinations: Meta: Instagram and Facebook; WhatsApp; TikTok; X; LinkedIn; Telegram; Discord; GitHub. GitHub also hosts the public source, issue and private vulnerability-reporting flows; information submitted there follows that service privacy terms.
Video, audio and animated media: Google/YouTube; Vimeo; Loom; Spotify; Apple Music; Deezer; SoundCloud; Mixcloud; Giphy.
Maps, calendars, forms and booking: Google Maps, Calendar and Forms; Calendly; Cal.com; Typeform. A seller-selected Cal.com connection can receive buyer contact data, intake answers, order-linked booking references, times, status and meeting URLs according to the seller instructions.
Consent management: iubenda; Cookiebot/Usercentrics; CookieYes; OneTrust; or the customer selected custom provider. A customer choosing SMTP, a registrar, external media or a custom service must supply that provider identity, notice and relevant safeguards in its own disclosures.
10. Local libraries and provider supply chains
The installed FingerprintJS open-source library computes the returning-browser signal locally after consent; its optional monitoring is disabled. Its inclusion does not make FingerprintJS a recipient of that signal. React, Next.js and other software packages likewise are not automatically external recipients merely because their code is used. Vercel, Google, Cloudflare, OpenAI, PostHog, Resend and other contracted providers may rely on their own infrastructure suppliers; their linked subprocessor lists govern that onward chain. OrbitPage does not represent every library author or downstream infrastructure supplier as a commercial partner.
11. Transfers and safeguards
Providers may operate from the EEA, United States and other service locations. OrbitPage uses provider data-processing agreements, Standard Contractual Clauses, adequacy decisions or other lawful transfer mechanisms where required. Provider links above contain the latest location and transfer details.
12. Changes
OrbitPage may add or replace a provider as the service evolves. The directory is updated for material provider or purpose changes. For customer-controlled processing, the DPA requires active advance notice of intended additions or replacements and an opportunity to object on documented data-protection grounds. Organisations that need notice of subprocessor changes can request it at contact@orbitpage.com.