A current overview of the sub-processors Senly engages to deliver the service, with the purpose, location and transfer basis for each.
This is a courtesy translation. The Dutch version is the legally binding original. View the Dutch version →
Senly uses a limited number of sub-processors to deliver the service. Below you'll find, for each sub-processor, the purpose, the location and the basis for transfers outside the EU. For transfers outside the EU we rely on the EU-US Data Privacy Framework and/or the EU Standard Contractual Clauses (SCCs). Data of agencies and their clients only goes to AI services in this list that are covered by the EU-US Data Privacy Framework or a data processing agreement with SCCs; we use Cerebras and OpenRouter only for Senly's own internal content. We keep this list up to date.
| Processor | Purpose | Location | Transfer basis |
|---|---|---|---|
| Railway | Platform hosting and database | United States (Google Cloud) | EU-US Data Privacy Framework + SCCs |
| Google (Gemini, Drive) | AI features: text and content generation, image analysis, meeting reports and draft replies; storage of client files in Senly's Drive for agencies without their own cloud storage | US / EU | EU-US Data Privacy Framework |
| Microsoft | Outlook calendar and mail (Graph API) | US / EU | EU-US Data Privacy Framework + SCCs |
| Anthropic | AI features: captions, content generation, support assistant, Advisory Board and help with automations; fallback when other AI services are unavailable | United States | DPA with SCCs |
| Cloudflare | CDN, AI edge inference and a proxy for public Instagram profile data | United States | EU-US Data Privacy Framework |
| Groq | AI features (supplementary) | United States | DPA with SCCs |
| xAI | AI features (supplementary) | United States | Own DPA |
| OpenAI | AI features (supplementary / fallback) | United States | EU-US Data Privacy Framework |
| Cerebras | AI for internal content (AI team, blog); no customer data in prompts | United States | Internal content only (no customer personal data) |
| OpenRouter | AI gateway for internal content (AI team, blog); no customer data in prompts | United States (+ upstream providers) | Internal content only (no customer personal data) |
| Resend | Sending transactional email | United States | EU-US Data Privacy Framework |
| Stripe | Payment processing (incl. affiliate payouts) | United States | EU-US Data Privacy Framework + SCCs |
| Mollie | Online payment of an agency's invoices to its clients, when the agency connects its Mollie account | Netherlands (EU) | Within the EU |
| KVK | Company data (lead enrichment) | Netherlands (EU) | Within the EU |
| Moneybird | Accounting and invoicing integration | Netherlands (EU) | Within the EU |
| Enable Banking | Bank connection: fetching payments to match them to invoices | Finland (EU) | Within the EU |
| Metricool | Social media analytics | Spain (EU) | Within the EU |
| Canva | Design integration | United States | EU-US Data Privacy Framework |
| GoHighLevel | Task and CRM sync (optional, when enabled) | United States | DPA with SCCs |
You also connect your own social accounts in Senly. When you publish, your content goes to the platform you connect:
In addition, you optionally connect your own external services in Senly — e-mail (Gmail/Outlook/IMAP), cloud storage (Google Drive, OneDrive, SharePoint, Dropbox), meeting recordings (Fireflies, tl;dv), AI services for which you set your own key, CRM, accounting and invoicing, e-mail marketing, analytics, helpdesk, webshop and automation (over 100 integrations in total). For those services you choose and control the recipient: you enable the connection and Senly only sends data on your instruction. As the controller you therefore determine whether and where that data goes — they are not Senly sub-processors. You can always see which integrations you have enabled in the portal under Integrations.
Questions about our sub-processors or data transfers? Contact us via the details in our privacy statement.