Subprocessor List

Effective Date: September 28, 2026 · Version: 1.5

This is the single published list of the third-party companies ("subprocessors") that Hubabble uses to help operate its service. It is the single canonical source of subprocessors and their live, imminent, and future status. It is referenced by the Hubabble Privacy Policy and by the Hubabble Data Processing Agreement (DPA). When those documents say "our current subprocessors," they mean this page, and any inline subprocessor table in those documents must match this list. If an inline table ever drifts from this page, this page controls.

We keep this list current so you always know who helps us run your coaching practice behind the scenes.

Who we are

This list is published by Hubabble, LLC, a member-managed multi-member limited liability company organized under Oregon law.

• Principal office and notice address: 403 Portway Avenue, Suite 300, Hood River, Oregon 97031
• Privacy and legal contact: privacy@hubabble.com
• Governing law and forum: Oregon, without regard to its conflict-of-laws rules, with venue in Hood River County, Oregon.

How to read this list

We sort our subprocessors by the role they play with the personal data involved:

• Hubabble is the controller of data about you (the coach), your account, visitors to our sites, and members of the Hubabble Community (including what members post and the records we keep to run and moderate it). For that data, our subprocessors act on Hubabble's behalf. A partner training organization that sponsors Community access is a separate controller of its own enrollment and program records; the Privacy Policy, section 16, explains what its admins and moderators can see once Hubabble turns those roles on.
• You (the coach) are the controller of your clients' personal data. For that data, Hubabble is your processor, and the companies below act as our subprocessors on your behalf. Your clients interact with Hubabble surfaces directly through secure tokenized links, on your behalf, to do things like book a session, complete an intake form, sign a document, or pay an invoice.
• Stripe plays a dual role. Stripe acts as a subprocessor when it processes payments on the coach's behalf, and as an independent controller for its own fraud-prevention and legal-compliance purposes. We state this dual role the same way everywhere it appears.

"Data processed" below describes categories of personal data, not every field. The exact data depends on how you use Hubabble and what your clients share with you.

Current subprocessors

These are the companies we use today or are bringing online imminently. Rows marked FUTURE / not yet active describe capabilities we are building. The data they would process is not flowing to them yet, and we will update the status before it does.

| daily.co (Pluot Labs, Inc.) | Powers your video sessions and your video room. | Session participant connection data, technical/connection metadata to deliver the video session, and audio/video media in transit during a live session | United States; global media routing | Subprocessor (our processor for your clients' session data on your behalf) | | Google LLC | Per-coach calendar and scheduling integration via the Google Calendar API (only for coaches who connect their Google Calendar) | The connecting coach's calendar event data and basic profile/email (Google scopes: calendar.events (sensitive), calendar.readonly (sensitive), userinfo.email, userinfo.profile), used only to provide your calendar and scheduling features. | United States; Google operates globally | Subprocessor | | Zoom Communications, Inc. | Per-coach video meetings on the coach's own Zoom account: creating, moving, and deleting a Zoom meeting for each booked session (only for coaches who connect their own Zoom account) | The connecting coach's Zoom account details (Zoom user ID, account ID, and email address), and for each booked session the meeting details Hubabble sends: the start time, the length, the coach's time zone, a title made of the session type and the first word of the client's name as the coach's Hubabble account has it, and the short description "Booked through Hubabble". Never the client's email address or contact details, and no Zoom invitees. Zoom returns the meeting ID and join link, which Hubabble keeps with the session; Hubabble stores the Zoom access tokens encrypted. (Zoom scopes: meeting:write:meeting, meeting:update:meeting, meeting:delete:meeting, user:read:user.) The meeting itself runs on the coach's own Zoom account, under the coach's agreement with Zoom. | United States; Zoom operates globally | Subprocessor (our processor for your clients' meeting details on your behalf) | | Resend (Plus Five Five, Inc.) | Sending transactional and e-sign email (such as confirmations, receipts, document-signing requests), and Hubabble Community email (reply emails and announcement emails, which can include excerpts of members' posts, and unread-message emails, which say who wrote and in which community, never the message text). Our email provider can record delivery and engagement events such as opens and clicks where that is enabled. | Recipient email addresses and names, email content (which for Community email can include excerpts of members' posts, but never the text of a message), and delivery and engagement events such as opens and clicks where enabled | United States | Subprocessor (our processor for client-facing email on your behalf; our own processor for Community email) | | Amazon Web Services, Inc. (AWS S3) | Secure file storage for signed PDF documents and related files, profile photos and practice logos, and files members attach to Hubabble Community posts and Messages; malware scanning of the files and photos members attach in Messages (Amazon GuardDuty Malware Protection for S3): a file is held until the scan finds it clean, and a photo shows right away and is removed if the scan finds something | Signed agreements and document files, which may include client names, signatures, and the contents of the documents; profile and logo images; Community attachments, including the files and photos attached in Messages | AWS region us-east-1 (US East, N. Virginia) | Subprocessor (our processor for your clients' document data on your behalf; our own processor for profile images and Community attachments) | | Inngest, Inc. | Running background jobs and scheduled tasks (such as queued emails, cleanup, and reliability work) | Job payloads and references needed to run background work, which may include identifiers and limited personal data | United States | Subprocessor | | Cloudflare, Inc. | DNS for our domains and routing of inbound email | DNS query routing and inbound email metadata and content in transit | United States; global network | Subprocessor | | Anthropic, PBC (AI model inference, reached through the Vercel AI Gateway) | AI-assisted support behind your in-app feedback: drafting the reply you receive when we resolve a report, and reading a new report on arrival to gauge whether it has enough detail for us to act on. | The text you submit in a feedback report (its title, your description, and captured technical details such as the page you were on and recent browser console messages), which may include personal data you type in, including any client details you choose to mention | United States | Subprocessor (and, where a report mentions client details, our processor for that data on your behalf) | | Ably (Ably Real-time Ltd.) | Real-time delivery so our internal staff triage board updates live as we work through reports, and so Hubabble Community spaces update live while a member has one open (a new post or reply appears without a page refresh), and Messages shows a new message without a page refresh. | Limited to internal record identifiers and status signals (which item changed and its state). For the Community, that is the identifier of the space and post that changed, and, for Messages, which conversation has something new, on a channel named by an opaque key, never a user id. The member's browser then uses that to fetch the update from our own servers. It does not carry post or message bodies, the content of reports, or your clients' personal data, which stay on our own servers. | United Kingdom; global edge network | Subprocessor | | KLIPY (Kikliko, Inc.) | GIF search and display in the Community: finding a GIF to add to a post or a message, and showing the GIFs in posts and messages. | The member's browser talks to KLIPY directly: search and trending requests go from the browser to KLIPY, and GIF images load from KLIPY for every member who sees them (in search results, in posts, and in messages). So KLIPY receives the member's IP address, basic browser and device details, the search terms they type, and which GIFs are loaded. Viewing a post or a message that contains a GIF sends the viewer's IP address to KLIPY, and there is no setting to turn GIFs off yet. We do not send KLIPY a name, email address, user id, or any other account identifier, and no post or message text or client data. We do not turn on KLIPY's ads or sponsored GIFs. | United States (Kikliko, Inc., San Francisco, California, per KLIPY's privacy policy, last updated June 23, 2026). GIF images are served through a global content delivery network. KLIPY does not say where its data centers are. | Provider of the GIF service, and an independent controller of what it receives. That is our reading of KLIPY's own stated collection and use: its privacy policy (klipy.com/support/privacy-policy) says it keeps a history of search terms and of the GIFs viewed (tied to the IP address that requested them), and may use them for advertising and sponsored GIFs. We have no data processing agreement with KLIPY. | | PostHog, Inc. | Feature flags (turning a feature on for some people before everyone), error tracking, product analytics, and session replay, for the signed-in dashboard (coaches and Community members). Analytics and replay never run on the links you send your clients, on our marketing site, or on your website. | Your internal Hubabble user id (never your name or email address); whether you are Hubabble staff, your role on the account, your subscription status, and whether you are on the free Community plan; the IP address requests come from and basic browser and device details; which dashboard pages you visit and what you click (with all on-screen text and link targets masked, web addresses without their query strings, and only the website of the page you came from); masked session replays (the app's own words and the names you give things like session types and spaces show, but everything typed into forms, people's names, email addresses, phone numbers, your site address, and what members post are masked; images, video, and embedded frames blocked; the clients, sessions, documents, payments, messages, and Community messages pages are never recorded); error reports that keep the type of error and where in our code it happened but never the error message or anything typed; and a few usage events sent from our servers (signing up, finishing onboarding, a session being booked, joining a community) that carry only ids and fixed values, never anything about your clients. Our servers also send AI reliability and operational logs: the feature and model, timing, token counts and cost when available, success or failure, and internal user, account, conversation, and job ids. No prompts, answers, audio, transcripts, request contents, or raw console messages are sent. When an app you connected connects to or uses a Community tool, our servers also record which tool it called, whether it worked (and, when it didn't, a general reason such as "not found" or "not allowed"), how long it took, which app called it (and that app's software name, version, and identifier), the names of the fields it filled in (such as "query", never what it typed), how much came back (its size and how many items, never the content), a random id that groups the calls of one conversation with the app, a short reason the app gives for the call, and your user id, never what was asked or what came back. We ask the app to describe only the purpose of the call, with no names and nothing a member wrote, and we remove email addresses and phone numbers and cut that reason to 200 characters before it is sent; we can't check it for every name. When the app gives no reason, we record the tool's own title instead. When such an app tells us there was something it couldn't do for you, PostHog also receives a short label the app wrote for what was missing. We ask the app to keep that label to a few words about the missing ability, with no names and nothing a member wrote, and we remove email addresses and phone numbers and cut it to 80 characters before it is sent; we can't check it for every name. The app's full report stays in Hubabble's own feedback system. Nothing is left on your device: no cookies, and nothing kept in local or session storage. | United States (PostHog US Cloud) | Subprocessor for Hubabble's own telemetry about coach and Community member accounts only. It never processes your clients' personal data. | | Stripe, Inc. (client payments), FUTURE / not yet active | Processing your clients' payments to you, so clients can pay you through Hubabble. This is imminent but not yet live. | Client payment method and card details, payment amounts, and transaction records, processed when you start accepting client payments | United States; Stripe operates globally | Dual role: Stripe acts as a subprocessor when it processes client payments on your behalf, and as an independent controller for its own fraud-prevention and legal-compliance purposes | | Recording and transcription of video sessions, FUTURE / not yet active | Optional recording of video sessions, and (separately) transcription of recordings. Neither is built or active. The transcription provider, when chosen, will not be named to you or your clients. | Audio/video recordings of sessions and text transcripts, which can include sensitive wellbeing and mental-health content | Provider and region set when selected | Subprocessor (our processor for your clients' recording/transcript data on your behalf), once active |

A note on sensitive data

Some of the data above can be especially sensitive: your clients' wellbeing and mental-health intake answers, your free-form client and session notes, and (in the future) session recordings and transcripts. Under laws like the GDPR, this is special-category data that needs extra care and explicit, specific consent.

What we do NOT treat as subprocessors

For clarity, some companies are sometimes assumed to be subprocessors but are not. Some receive no personal data from Hubabble in the ordinary course. Others, such as an app a member connects to their own account, receive only what that member directs, under the member's own agreement with that provider, and not on Hubabble's behalf:

• Font and icon assets are self-hosted by us, so they are not loaded from a third party in a way that shares your data.
• Certain internal developer and infrastructure tools we use to build and operate Hubabble do not process your personal data as subprocessors in the ordinary course.
• Apps that a member connects to their own Hubabble account, such as an AI assistant. They receive Community content at that member's direction and under the member's own agreement with the provider, not on Hubabble's behalf; the Privacy Policy, section 5, explains this.
• A meeting link a coach saves for their own video tool. It sends nothing to a new company. (A Google Meet link created through the coach's connected Google Calendar goes through Google, and a meeting created on a coach's connected Zoom account goes through Zoom, both listed above.)

Future subprocessors (not yet in use)

The following capabilities are on our roadmap and are not active today. We will add the relevant providers to the table above, with their purpose, data, region, and role, before any of them goes live and processes data:

• Recording of video sessions, and transcription of those recordings (the transcription provider will not be surfaced to you or your clients).

We list these here only so you can see what may be coming. None of them is receiving data now.

Changes to this list and your right to object

We may add or replace a subprocessor as we improve Hubabble. When we do:

• We will update this page. This page is always the current, authoritative list.

• You can subscribe to change notifications. Coaches can sign up to be notified in advance when we plan to add or replace a subprocessor.

• You can object. We give at least 30 days' prior notice before a new or replacement subprocessor that processes client data goes live. If you reasonably object on data-protection grounds within that period, you can tell us at privacy@hubabble.com. We will work with you in good faith to find a resolution, and if we cannot offer a commercially reasonable alternative, your remedy is to stop using the affected feature or to terminate the affected service. This matches the DPA's subprocessor-change clause (Section 8).

To subscribe to changes or to raise an objection, contact us at privacy@hubabble.com.

This Subprocessor List is part of, and incorporated into, the Hubabble Privacy Policy and Data Processing Agreement. If anything here conflicts with the DPA, the DPA controls.