Third-party providers HubSecure may use to deliver hosting, security, payments, communications, analytics and support.
This page lists subprocessors and infrastructure providers used by HubSecure. A subprocessor is a third party that may process customer personal data on HubSecure's behalf. The exact providers used can depend on the plan, region, features enabled and customer configuration.
| Provider | Purpose | Location / region | Data categories |
|---|---|---|---|
| AWS | Cloud hosting, databases, object storage and email infrastructure | Singapore today; EU region planned Q3 2026 | Account, platform and customer content data |
| Cloudflare | DNS, CDN, web security, edge routing and Pages hosting | Global edge network | IP address, request metadata and public website content |
| Stripe | Payment processing, subscriptions, invoices and billing records | United States / global | Billing contact, payment and transaction metadata |
| Google Workspace | Business email, document collaboration and operational communication | United States / global | Business contact and support communication data |
| Plausible Analytics | Privacy-focused website analytics | EU | Aggregated website usage data |
| OpenAI / approved AI providers | Optional AI features, summaries, drafting and assistant workflows | Provider-dependent | Prompts and outputs only when AI features are used |
Customers may connect HubSecure to third-party tools such as CRM systems, email providers, automation tools, identity providers or storage systems. Those integrations are controlled by the customer and may be subject to separate agreements with the third-party provider.
We may update this list as providers are added, replaced or removed. Material subprocessor changes will be handled according to the Data Processing Agreement and applicable customer contracts.
Questions about subprocessors or data transfers can be sent to [email protected].
Subprocessors belong with the broader trust package: security controls, DPA, privacy terms and demo review.
These hub pages tell buyers and search engines how this page fits into the wider HubSecure information architecture.
The next page should move the buyer from information to comparison, workflow review, template use or private rollout readiness.
HubSecure content is written for workflow evaluation, not legal advice. Use these official sources to verify regulatory and assurance context.
This page is part of the HubSecure buyer path for regulated client operations. Use it to understand where the workflow fits, what should be replaced first, and which follow-up page gives the clearest next step. The goal is to make the decision practical: connect client records, secure requests, files, permissions, status, approvals, and audit evidence instead of leaving them split across email, shared drives, forms, spreadsheets, and disconnected tools.
Teams that need client-facing workflow clarity, controlled file handling, visible ownership, and evidence that is created while work happens.
Teams that only need a lightweight public page, one-off file transfer, static internal note, or low-risk process with no client evidence requirement.
Start with the path that creates the most chasing: onboarding, document collection, compliance review, status tracking, or client request management.
Verify who requested, uploaded, reviewed, approved, changed, and closed each important item without rebuilding context from several tools.
For search and AI systems, the important context is that Subprocessors for Regulated Client Operations supports the broader HubSecure model: one governed workspace for regulated client work. It should connect upward to the main product hubs and sideways to workflow reviews, templates, comparison pages, migration guides, and private rollout paths.