Forms Bridge is built so that the data your clients care about most never reaches us. This page explains how, in plain terms, so you can share it with your clients.
Your form submissions never pass through Forms Bridge
When someone submits a form on your Webflow site, Webflow sends it straight to a small script in your client's own Google account, which writes it into their own Google Sheet. Forms Bridge isn't in that path at all: we never receive, store or see form submissions. Once set up, the connection keeps working even if Forms Bridge goes offline.
Your client owns everything
The spreadsheet and the script are created in your client's Google account and belong to them. They can open, share, move or delete them at any time, like any of their own files. We keep no copy of the sheet's contents.
What we store, and how
- Developer accounts: name, email and sign-in, handled by our sign-in provider (Clerk). We never see or store passwords.
- Project settings: project name, the client's name and Google email, form names, and the IDs of the client's spreadsheet and script.
- Google Sheets access for developers (optional): if you connect Google Sheets, the long-lived Google key is stored encrypted with AES-256-GCM. It's used only when you add or remove a form.
- Your client's Google access: used only during setup, kept only in an encrypted cookie in their browser for about an hour, and never saved on our servers. Forms Bridge keeps no lasting access to your client's account.
- Purchases: card payments are handled by Stripe; card numbers never reach us. We keep the purchase and the billing details needed for the invoice.
Our database runs on Cloudflare in Europe and is encrypted at rest. Every connection uses HTTPS.
How each connection is protected
- A secret key per sheet. Each script only accepts submissions that carry its own random 256-bit key, checked in constant time. The key is in the webhook address you paste into Webflow, never in your website's code.
- Only your forms. A sheet that lists forms in its Forms tab takes only those; every other form is ignored.
- Minimal Google permissions. We ask only for what setup needs (Google Sheets, creating and publishing the script, and the files Forms Bridge creates), never for your client's Gmail or whole Drive.
- Guarded sheet structure. The Forms tab and header rows ask for confirmation before anyone edits them by hand.
- Abuse limits. The public setup-status check and code redemption are rate-limited.
Who helps us run Forms Bridge
These providers (sub-processors) handle data for us, each only for its part:
| Provider | What for | Location | Certifications |
|---|---|---|---|
| Cloudflare | Hosting and database | Europe (global network) | SOC 2 Type II, ISO 27001 |
| Clerk | Developer sign-in | United States | SOC 2 Type II |
| Stripe | Card payments | United States, Ireland | PCI DSS Level 1, SOC 2 |
| Sheets and Apps Script, in your client's own account | Global | ISO 27001, SOC 2 | |
| Billingo | Invoices | Hungary | |
| Purelymail | Our support email | United States |
Forms Bridge itself is a small independent product and doesn't hold its own SOC 2 or ISO 27001 certificate; we rely on these certified providers and keep the data we hold to a minimum. Agencies that need one can use our Data Processing Agreement. More detail is in our Privacy policy.
If something goes wrong
Removing Forms Bridge's access in a Google account is always safe: it was only needed during setup. If we ever had a security incident affecting your data, we'd tell you without undue delay, and within 72 hours where GDPR requires it.
Reporting a security problem
Found a vulnerability? Please email hello@forms-bridge.com with the details, and give us a reasonable time to fix it before sharing it publicly. We reply to every report. Our contact details are also in security.txt.