Subprocessors
The third parties that process Customer Content on our behalf, what each one does, and where it processes data.
A subprocessor is a third party that Global Linked Affiliates LLC, which operates OrbitForms ("OrbitForms," "we"), engages to process Customer Content on our behalf so we can provide the Service. Customer Content includes the form submissions, contacts, bookings, and sequence data our customers collect and manage with OrbitForms. This is the list referenced in our Data Processing Addendum (where it serves as Annex III to the Standard Contractual Clauses) and our Privacy Policy.
How we notify you of changes. Before a new subprocessor processes Customer Content, we update this page and email the owners of every team at least 30 days in advance. To have notices sent to another address, such as a privacy or procurement mailbox, email privacy@orbitforms.ai with the subject line "Subprocessor updates." Customers may object to a new subprocessor as described in Section 7 of the DPA.
Infrastructure and core services
These providers are involved in running the Service for every customer.
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Vercel, Inc. | Application hosting, edge network, serverless compute, and request logs. | All Customer Content in transit through the application, including form submissions, booking requests, and API traffic. | United States |
| Supabase, Inc. (hosted on Amazon Web Services) | Primary PostgreSQL database, authentication, and file storage, including encrypted daily backups. | All stored Customer Content: forms, submissions and uploaded files, contacts, bookings, sequences, workflows, account and team data, and authentication identifiers. | United States (AWS us-east-1, N. Virginia) |
| Inngest, Inc. | Background job orchestration for workflows, sequences, scheduling, and integration syncs. | Event payloads, which can include submission and contact data, team and record identifiers, and workflow step inputs and outputs. | United States |
| Upstash, Inc. | Redis store for rate limiting. | Short-lived counters keyed by hashed IP address or account identifier. No submission content. | United States |
| Stripe, Inc. | Subscription billing and payment processing. | Billing contact name and email, subscription identifiers, and payment details entered on Stripe-hosted pages (card numbers never reach OrbitForms). | United States |
| Resend | Delivery of account, team, booking, and notification emails. | Recipient email addresses and message content, which can include the name, email, and meeting details of people who book through a scheduling page. | United States |
Email sequences
This provider processes Customer Content only for teams that send email sequences.
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Mailgun Technologies, Inc. (Sinch) | Sending email sequences and tracking delivery, opens, clicks, bounces, and unsubscribes. | Recipient names and email addresses, message subjects and bodies, and engagement events. | United States |
AI processing
AI features that touch submission or contact data run only when a user adds or invokes them. Requests go to the provider below under commercial API terms that do not allow it to train models on Customer Content, and OrbitForms does not train foundation models on Customer Content. See our AI Policy for details.
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Anthropic, PBC | Large language model inference for workflow AI agents, lead qualification and scoring, AI-assisted form building, and the automated safety review of form configuration at publish. | Prompts containing the data the requested feature needs (for example the submission being qualified) and the model output. The publish-time safety review sends only the form’s own configuration, never respondent submissions. | United States |
Security, monitoring, and support
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Google LLC | reCAPTCHA spam protection on published forms, and Google sign-in for accounts that choose it. | Browser and device signals from people who load a protected form; name, email address, and Google account identifier for Google sign-in. | United States |
| Functional Software, Inc. (Sentry) | Application error and performance monitoring. | Stack traces, request paths, browser and device details, and account identifiers. Personal data is redacted from error reports before they are sent. | United States |
| Datadog, Inc. | Front-end performance monitoring and session replay of the signed-in OrbitForms application (never published forms or scheduling pages). | Page views, interaction and timing data, and replays of signed-in sessions. Replays mask all on-screen text, form input, and images, so they show page layout and interactions but not Customer Content. | United States |
| HaloAgents | In-app and website support chat. | Name, email address, and team of signed-in users who open the chat, and the content of support conversations. | United States |
Integrations you connect
When a customer connects a third-party service, OrbitForms sends Customer Content to that service on the customer's instruction. These services are engaged by the customer under its own agreement with them, and they are not OrbitForms subprocessors. Examples include CRMs (Salesforce, HubSpot, Pipedrive, and others), SMS through Salesmsg, Slack, Zapier, webhooks, Google and Microsoft calendars used for scheduling, ad and attribution platforms, and AI assistants authorized through the OrbitForms MCP server.
Internal tools that may incidentally process personal data
These tools support how we run the company. They do not process Customer Content as part of delivering the Service, but they can incidentally contain personal data such as a contact's name and email address or the text of a support request.
- GitHub: source code hosting and continuous integration.
- Linear: issue tracking, which can include details from bug and support reports.
- Website analytics and advertising (Google Tag Manager, Meta Pixel, Cometly, and Vercel Analytics): process visitor data on the orbitforms.ai website as described in our Privacy Policy. They are never loaded on customers' published forms or scheduling pages and never receive form submissions.
Change log
| Date | Change |
|---|---|
| 2026-10-21 | Datadog session replay now masks all on-screen text, form input, and images, so replays no longer capture Customer Content. No new subprocessor. |
| 2026-10-21 | Initial publication of this list as a standalone page, referenced by the Data Processing Addendum. |
Questions about this list?
Email privacy@orbitforms.ai and we will get back to you.