Subprocessors
This page identifies service providers Fluencify may engage to process Customer Personal Data on documented instructions when delivering the Platform. The applicable Data Processing Agreement controls role, authorisation and objection rights.
- Version
- SUBPROCESSORS-2026-10-17
- Effective and last updated
- 17 October 2026
To subscribe to subprocessor-change notices, email contact@fluencify.io with the subject “Subprocessor change notices” and identify the customer legal entity and contract contact.
1. Scope and terminology
“Customer Personal Data” means personal data processed by Fluencify solely on a customer's documented instructions under the applicable DPA. A provider is a subprocessor only for the function in which it processes that data for Fluencify. The same provider may have a different role for another service or dataset; actual conduct and contract terms control.
The list below describes services that may be used by the Platform. A provider marked “where enabled” receives Customer Personal Data only if the relevant feature and approved account route are enabled for the service.
2. Current Platform subprocessors
| Provider | Processing purpose | Main location information |
|---|---|---|
| Convex | Primary backend, database and server functions | Selected account/deployment region; authorised support may be global |
| Cloudflare | Web hosting and request transit; file, image and video storage, processing and delivery | Global edge network with account/service-specific storage locations |
| Google Cloud / Gemini | Video or image analysis where enabled | Selected project/service region; authorised support may be global |
| Anthropic | Support, moderation or structured extraction where enabled | Service/account-specific; may include United States processing |
| Clerk | Authentication and user-account management | Global service; locations follow the contracted account and subprocessor chain |
| ClickHouse Cloud | Operational and product analytics mirror | Selected cloud and service region |
| Railway (hosting self-managed Typesense) | Search indexing | Selected Railway service region |
| Resend | Transactional email | Global email delivery and service infrastructure |
| BoldSign | E-signature and contract storage | EU API endpoint for the reviewed integration; support/subprocessor access may be broader |
| OpenAI | Text embeddings and approved AI functions where enabled | Business/API service locations; may include United States processing |
| Braintrust | LLM tracing and evaluation where enabled | Selected Data Plane/account region; authorised support may be global |
| Expo Push | Mobile push-notification delivery | Global notification-delivery infrastructure |
| OpenPhone | SMS on the creator support line: message text and the phone numbers that sent and received it | Service/account-specific; may include United States processing |
| Meta (WhatsApp Business Platform) | WhatsApp on the creator support line: message text, the phone numbers that sent and received it, and the creator's name in a conversation-reopening message | Meta's global infrastructure; may include United States processing |
| Photon | The iMessage sign-in line, including messages forwarded to creator support: message text and the phone number or Apple ID email address that sent it | Service/account-specific; may include United States processing |
| Linear | Support issue tracking, including the reporter's email address and the text of their support message | Service/account-specific; may include United States processing |
| Slack | Internal operational alerts, which may quote a drafted support reply, and shared channels with business customers, including their contacts' email addresses and channel messages | Service/account-specific; may include United States processing |
| Composio | Access to the support inbox for reading and sending support email, and storage of customer-supplied analytics credentials | Service/account-specific; may include United States processing |
| PostHog | Backend application and error logs, which can contain personal data the Platform processes | Selected PostHog project region; authorised support may be global |
3. International transfers
A provider's product region does not necessarily prevent remote support, security access or onward processing elsewhere. Where Customer Personal Data is transferred outside the EEA or another protected origin, Fluencify uses the mechanism required by the applicable DPA and GDPR Chapter V, such as an adequacy decision or the European Commission's Standard Contractual Clauses, and assesses supplementary protections where required.
A customer may request account- and route-specific location and safeguard information. The response may include confidential contract evidence under appropriate access controls.
4. New or replacement subprocessors
We update the version and date above when this list changes and provide advance notice in the manner and period stated in the applicable DPA. A customer may raise a reasonable, documented data-protection objection during that period. We will work in good faith on a commercially reasonable alternative; the DPA explains the outcome if the objection cannot be resolved.
5. Services not listed as customer subprocessors
Stripe and Grade may act as independent controllers for payment, payout, identity, tax, fraud and regulatory functions. Apple/Google sign-in, Google Places, YouTube Data API and social platforms may likewise act under separate controller terms. They are not made customer subprocessors merely because a user chooses their service.
PostHog, AppsFlyer and Google Ads process analytics, attribution or ad-measurement data for Fluencify's own controller purposes rather than ordinarily on a customer's instructions. PostHog is listed in section 2 only for the Platform's backend logs. Public-creator data-source providers and their role are described in the Public Creator Notice. The broader recipient information is in the Privacy Policy.