FormRelay
Where Does Your Collected Lead Data Go?
📬 What happens when someone submits a form
- Webflow handles the submission exactly as it normally would — email notifications, Webflow's own submission list, anything else you have configured. FormRelay does not change or replace Webflow's behaviour.
- Webflow also sends the submission to FormRelay through a
form_submissionwebhook registered on your site. - FormRelay records the submission and forwards it to each destination you have mapped that form to.
🗄️ What we store, and for how long
We do store submission data. Being precise about it:
| What | Stored | Kept for |
|---|---|---|
| Submission values, for forms you have mapped to a destination | Yes | 90 days, then erased |
| Delivery history — which destination, when, success or failure | Yes | 395 days |
| Submissions for forms with no mapping | Metadata only, no values | 395 days |
| Your connection credentials (API keys, tokens, webhook URLs) | Yes, encrypted at rest | Until you delete the connection |
Keeping the values for 90 days is what makes the delivery log useful: you can see what was sent, confirm a lead arrived, and replay a failed delivery. After 90 days the values are erased automatically and only the delivery history remains.
🔑 Fields we deliberately drop
Before a submission is stored or sent anywhere, FormRelay removes fields whose names look like credentials — password, confirm password, one-time codes, card numbers and similar. Those values are never written to our database and never reach your destinations.
This is a name-based check, because Webflow's webhook does not tell us which input was a password field — a password arrives indistinguishable from ordinary text. Field names that merely resemble credentials, such as "Passport Number", are left alone. The delivery log records which field names were dropped, never their values.
🔑 Your destination credentials
The API keys, tokens and webhook URLs you paste into FormRelay are encrypted at rest and are used for one thing: reaching that destination when a submission is delivered. They are not sent anywhere else. API keys and tokens are not shown back to you once saved. A destination URL for the Webhook, Zapier and Make integrations stays visible to you, because it is your own endpoint and you need to be able to check it.
To remove one, delete the connection under Integrations. That erases our copy immediately. Revoking access at the destination itself is separate and worth doing too — in Notion, Slack, HubSpot and the rest, remove or revoke the integration in that provider's own settings, since a key stays valid there until you do.
🧹 Deleting and exporting your data
You are in control of what we hold:
- Delete submission data — on a site's Logs page. By default this erases the submission values and keeps the delivery history; you can also delete the history.
- Export — download your logs as CSV from the same page.
- Delete your account — from Account settings. This removes your sites, connections and logs, and deletes the FormRelay webhooks from your Webflow sites.
👤 Who can see it
The account owner. Faizatech staff can see delivery metadata for support purposes — which destination, when, and whether it worked — but not submission values.
🌍 Where it goes next
Whatever you map a form to. Each destination receives the submission under its own privacy policy and terms, which are between you and that provider. The full list of destinations FormRelay can send to is on the Integrations pages.
✅ Webflow's own form behaviour is unchanged
FormRelay reads submissions through Webflow's official webhook. It does not modify your forms, inject scripts into your published site, or interfere with Webflow's native handling — email notifications and Webflow's submission list keep working as before.