Subprocessors
Last updated
These are the outside companies that store or handle personal data so FlowyForm can run. Each is bound by a contract that limits what it can do with the data. Our Data Processing Terms explain how we choose them and tell you about changes.
Current subprocessors
| Company | What for | Data involved | Location |
|---|---|---|---|
| DigitalOcean | Servers, database, backups and file storage | All account data, forms, responses and uploaded files | North America (uploaded files: New York, United States) |
| Twilio SendGrid | Sending email: sign-in codes, invitations, response notifications and confirmations | Email addresses and the content of each email, which can include form answers | United States |
| Stripe | Subscription payments, invoices and the billing portal | Name, email, payment card and billing details (entered on Stripe, never stored by FlowyForm) | United States |
| Sign in with Google; Google Sheets integration; website analytics and ad measurement; web fonts on forms | Google account name and email; answers sent to sheets you connect; website usage data; IP address when fonts load | United States and worldwide |
Services you choose
These are not our subprocessors. They receive data only when a form owner connects them to a form, and they work under the agreement between the form owner and that service.
| Service | What it receives |
|---|---|
| Slack | A message with the answers, posted to the channel the form owner picks |
| Google Sheets | A row with the answers, added to a spreadsheet the form owner connects |
| Webhooks | The answers, sent to any web address the form owner enters |
| YouTube and Vimeo | Videos a form owner embeds in a question load from those sites (YouTube in privacy-enhanced mode) |
Changes
We update this page before a new subprocessor starts handling customer data. To be emailed about changes, write to help@flowyform.com with the subject “Subprocessor updates”.