Sendivent Subprocessors
Last updated: 21 December 2025
This page lists the third-party subprocessors Appitude AB ("Sendivent", "we", "us") uses to process Customer Content on behalf of customers under our Data Processing Addendum (DPA).
- This list applies to Customer Content only.
- For website analytics, see our Privacy Policy (Plausible Analytics).
- EEA means the European Economic Area.
- Customers may connect customer-connected integrations (such as Slack) to Sendivent. When enabled, we transmit the information reasonably necessary to deliver the message to that provider (for example: workspace and channel identifiers, message content, and delivery-related metadata). These providers are selected and configured by the customer and are not listed as Sendivent subprocessors; they process data under the customer’s relationship and terms with the provider.
For questions or objections, contact legal@sendivent.com.
1) Subprocessor changes (notice and objection)
We follow the notice and objection process set out in the DPA (see DPA Section 5).
In summary:
- We provide 30 days' prior notice of material changes by updating this page and, where appropriate, notifying account owners in-product or by email.
- If you reasonably object to a new subprocessor on data protection grounds, contact legal@sendivent.com within the notice period.
- Remedies (including termination of the affected feature/portion where applicable) are described in the DPA.
A change is considered material if it involves:
- adding a new subprocessor that will process Customer Content;
- changing the primary processing location of Customer Content to a location outside the EEA;
- adding a new category of processing of Customer Content performed by an existing subprocessor; or
- materially expanding the scope of processing performed by an existing subprocessor.
2) Current subprocessors
| Subprocessor | Purpose | Customer Content processed | Primary processing location |
|---|---|---|---|
| Amazon Web Services (AWS) | Hosting and core infrastructure (compute, storage, networking, managed databases, backups) | Customer Content stored and processed by the Service; operational logs and system metadata (excluding message content and identifiers to the extent feasible) | Sweden (AWS eu-north-1 / Stockholm) |
| Cellsynt AB | SMS delivery (when SMS is enabled) | Phone numbers; SMS message content and metadata necessary to deliver messages | As applicable to SMS delivery (may vary based on delivery routing and telecom networks) |
3) Notes
- We do not currently use third-party support ticketing, observability, or error monitoring tools that process Customer Content (e.g., Intercom/Zendesk/Sentry/Datadog).
- We do not use Customer Content to train AI models and we do not send Customer Content to LLM providers.
- Subprocessors that process Customer Content on our behalf are listed above.
- Transfers outside the EEA may occur in limited cases due to (i) customer-connected integrations (such as Slack) that process data under the customer’s relationship with that provider, (ii) SMS delivery routing depending on recipient destination and telecom networks, and/or (iii) limited support/admin access from outside the EEA.
- Where required for Processor-initiated transfers, appropriate safeguards are applied as described in the DPA.
4) Changelog
- 21 December 2025: Initial publication (including clarifications on EEA definition, customer-connected integrations wording, and Cellsynt routing-based location phrasing).