Sub‑processors
Last updated: 11 August 2026
Lifted Work, Inc. engages the vendors below to deliver the Service. This page is referenced by our Terms of Service and Privacy Policy. We keep it current as vendors are added or removed.
1 Service sub‑processors
These vendors process Customer Data on our behalf so that the Service can run.
| Sub‑processor | Purpose | Data involved |
|---|---|---|
| Fly.io | Application hosting and application logs | All Customer Data in transit, plus anything written to logs |
| Neon | Managed PostgreSQL database hosting | All Customer Data at rest |
| Cloudflare (R2 and CDN) | File and asset storage, content delivery | Uploaded files, images, brand assets, and rendered reports |
| Anthropic | AI features (Claude) | Content you or your team send to an AI feature, and the client context attached to it |
| OpenAI | AI features, including image generation | Content you or your team send to an AI feature |
| Cloudmersive | Malware scanning of uploaded files | Files uploaded to your workspace, sent for scanning as they arrive |
| Stripe | Payment processing and subscription billing | Billing contact details and payment method data, handled by Stripe |
| Postmark | Transactional and notification email delivery | Recipient addresses and the content of emails we send on your behalf |
Vendors are listed by the name you would recognize. The legal entity for each one is named in the addendum we send if you request a signed DPA. We do not train models on your content, and we reach the AI providers above on commercial API terms we select for processing your content to return your result.
2 Integrations you connect
These are not our sub‑processors. They are services you choose to connect to your workspace, using your own account and under your own agreement with that provider. Data moves between them and Lifted Work only because you authorised it, and you can revoke that access at any time.
- Google — Google Analytics (GA4), Search Console, Google Ads, Business Profile, and Gmail sync, each connected per client.
- Meta — Meta Ads and Meta social publishing.
- Zapier, an API, and an MCP server — optional connections you configure. Only what your own automation sends or requests moves through them.
3 Website analytics
Our public marketing site uses Google Analytics, Google Tag Manager, the Meta pixel, Cloudflare analytics, and a Calendly booking embed. These run on liftedwork.com only. They do not have access to Customer Data inside the application.
4 Changes and objections
We keep this page current as sub‑processors change. If you want notice of changes, or you object to a particular sub‑processor, email support@liftedwork.com and we will work through it with you.