Current subprocessors
These process customer data today. “Customer data” means the information you put into Swift Pivot: your account details, your contacts and their consent records, the content you publish, and the media you upload.
| Provider | What it does | Location |
|---|---|---|
| Vercel Inc. | Application hosting and content delivery | United States |
| Supabase, Inc. | Database, authentication and file storage | United States |
| Blotato | Social media publishing to connected accounts | United States |
| cron-job.org | Scheduled task trigger (carries no customer data) | Germany |
| Amazon Web Services (SES) | Bulk email delivery | United States |
| Twilio Inc. | SMS delivery and carrier registration (A2P 10DLC and toll-free verification) | United States |
Not yet active
These are selected for capabilities still in development. They are listed here so the disclosure is complete in advance, and each one moves into the table above when the feature that uses it is released.
| Provider | What it will do | Location |
|---|---|---|
| Anthropic, PBC | AI generation of marketing copy | United States |
How changes are announced
The list on this page is generated from a single configuration file in the application, so it cannot silently drift from what the software actually does. When a subprocessor is added or activated:
- The entry is updated in the same release that introduces the integration, not afterwards.
- The Last updated date at the top of this page changes.
- Customers with a data processing agreement receive advance notice as set out in that agreement.
To be told when this page changes, email contact@swift-pivot.com and ask to be added to the notification list.
How we choose them
Every subprocessor on this page meets the same bar:
- Contractual protection. Data protection terms are in place before any customer data reaches them.
- Least privilege. Each receives only the data its function requires. The scheduler that triggers background work, for example, receives none at all — it makes an authenticated request on a timer and nothing more.
- Replaceability. Vendors sit behind interfaces we control rather than being wired through the codebase, so replacing one is a contained change. That is a resilience property as much as an engineering one.
Related reading: Privacy Policy for what data is collected and why, and Security for how it is isolated between agencies.