Sub-processors
The third-party providers we rely on to run dplooy, what each one handles, and where your data lives.
What a sub-processor is
When you use dplooy features that collect personal data from your own website visitors — dplooy Forms, the email gate, lead capture — you are the data controller and dplooy is your processor. The companies we use to deliver that service are our sub-processors.
Engaging them is authorised under the Data Processing Addendum in our Terms. Each is bound by data protection obligations no less protective than the ones we owe you.
Providers that handle your visitors' data
Google Cloud / Firebase
United States- Purpose
- Database, file storage and authentication
- What it processes
- Form submissions, uploaded site files, account records
Railway
United States- Purpose
- Application and API hosting
- What it processes
- Requests in transit, including form submissions being written
Vercel
Global edge network- Purpose
- Frontend hosting and content delivery
- What it processes
- Requests in transit to the dashboard and marketing site
ip-api.com
Germany- Purpose
- Geographic lookup for site analytics
- What it processes
- Visitor IP addresses, sent to resolve country, region and city. Results cached for 24 hours; the IP is hashed and discarded, never stored
Providers for our own operations
These handle dplooy's own business data. They do not receive the personal data your website visitors submit through your forms.
Stripe
United States and global- Purpose
- Subscription billing and payments
- What it processes
- Your billing details and payment method. Never your visitors' data
OpenRouter
United States- Purpose
- AI features — chatbot replies, SEO suggestions, site generation
- What it processes
- Only content you submit to an AI feature. Not used for form submissions
PostHog
United States- Purpose
- Product analytics on dplooy's own website and dashboard
- What it processes
- Usage events for dplooy visitors. Not your website visitors
Where your data is stored
Form submissions, uploaded files and account records are stored in Google Cloud infrastructure in the United States.
If you or your visitors are in the UK or EEA, this means personal data is transferred outside that area. Those transfers rely on the Standard Contractual Clauses incorporated into Google Cloud's terms.
What we deliberately don't collect
We do not store the IP addresses of people who submit your forms. An IP is held in memory only, for rate limiting, and then discarded. It is never written to storage, never returned by our API, and never appears in a CSV export.
The practical trade-off is worth stating plainly: if you receive an abusive submission, we have no IP address to give you. We think holding nothing your visitors didn't knowingly provide is the better default.
Changes to this list
We will update this page before adding or replacing a sub-processor that handles your visitors' data, and will notify account holders by a notice in the dashboard. If you object to a new sub-processor, contact us and we will discuss the options available, including ending your subscription.
Questions about this list? Get in touch.