FormRelay Privacy Policy

About this policy

FormRelay is published by Faizatech. This App specific policy sits alongside the general Faizatech Privacy Policy, which covers the Faizatech website and our company wide practices. Where the general policy speaks in broad terms, the sections below state what FormRelay does in practice.

FormRelay was previously called Form Integrations. Some listings and older links may still show the former name. It is the same App.

What FormRelay does

FormRelay sends Webflow form submissions to another tool. After you authorize a Webflow site and map a form to a destination, Webflow sends submissions of that form to FormRelay through a form_submission webhook, FormRelay records that the submission arrived and forwards it to the one destination you mapped that form to. FormRelay is a data client only: there is no Designer Extension, no bundle, no code added to your published site, and no use of the Webflow Custom Code API. Webflow keeps handling the form as it normally would, including email notifications and its own submission list.

Who controls the data

Form submission contents belong to you, the FormRelay customer. Faizatech handles them as a processor, acting on your instruction, for two purposes: delivering each submission to the destination you selected, and showing you the delivery log for that site.

For the people who fill in your forms, you are the controller. You decide what your forms ask for, which destination receives the answers, and what notice or consent you give the people submitting them. Faizatech does not sell submission contents and does not use them for any purpose other than operating the App for you.

Webflow access we request

When you connect a site, Webflow asks you to approve four scopes. Each one is used for a specific part of the App:

• authorized_user:read, to identify the Webflow user who approved the App so the connection is tied to the right account. We store the Webflow user id, email address and name from this.
• sites:read, to list the sites you can choose from and to read the site name and preview URL shown in the FormRelay dashboard.
• sites:write, to register the form_submission webhook on the site you authorized, and to delete that webhook when you delete your account or when you remove the site with webhook removal left selected. FormRelay does not publish your site, edit its content, or add code to it.
• forms:read, to read the forms on the site so you can map a form to a destination, and to read the submission data Webflow sends for those forms.

Authorization is per site. The Webflow consent screen asks you to select a single site, and the token FormRelay receives covers only that site. Connecting another site means authorizing again and selecting it.

What we store

FormRelay stores four categories of data in a Postgres database hosted on Railway.

Account data

Your email address, your name if you provide one, and either a password hash or the Google account id if you sign in with Google. We do not receive or store your Google password.

Webflow data

Your Webflow user id, email address, first name and last name, and the Webflow access token for the site you authorized. For each connected site we store the site id, workspace id, display name, preview URL, subscription status, and the signing secret used to verify webhooks coming from that site.

Destination credentials

The name you give a connection, plus the credential that destination needs: an API key, an access token and refresh token, or a destination URL, depending on the provider. Every one of these is encrypted at rest with AES-256-GCM envelope encryption, destination URLs included, because a Zapier or Make hook address is itself the thing that authorises posting into your automation. API keys, access tokens and refresh tokens are not shown back to you once saved. A destination URL does stay visible in the dashboard, so you can see where a form is pointing. Credentials are used to authenticate to that destination when a submission is delivered, and for nothing else.

Form submission contents

When a submission arrives for a mapped form we write a log row recording that it was received, and one further row per delivery attempt. A delivery row holds the site id, the form id, the destination type, the status of the attempt, the error message the destination returned if it failed, and the submission payload itself. These rows also record the names of any fields that were stripped before storage, described in the next section.

Fields FormRelay drops

Before a submission is written to our database, and before anything is delivered to a destination, FormRelay removes fields whose names look like credentials, for example password, confirm password, one time codes and card numbers. The values of those fields are not stored by us and are not passed on to your destination. The log records which field names were removed, not their values.

This is a name based check. The Webflow webhook does not indicate which input was a password field, so a password arrives as ordinary text alongside everything else. Field names are tokenized before matching, so names that merely resemble a credential, such as "Passport Number" or "Passenger name", are left in place. Because the check reads names, a credential field named in a way the list does not cover can still pass through. Treat this as a filter that removes common credential field names, not as a guarantee about every password field on your site.

Forms with no destination mapped

If a submission arrives for a form you have not mapped to a destination, FormRelay records metadata only: that a submission arrived for that form, and when. The values are not stored and nothing is delivered. The same applies before a site is subscribed. A site delivers nothing until it has an active subscription, and until then only the fact of a submission is recorded.

How long we keep it

• Submission payloads: 90 days. After that the payload is erased from the log row and the delivery metadata for that attempt remains.
• Delivery metadata (site, form, destination, status, timestamps): 395 days, after which the row is deleted.
• Destination credentials: until you delete the connection, or remove the site they belong to, either of which erases our copy.
• Site records: until you remove the site or delete your account. The stored Webflow access token goes when the last site it covers is removed.
• Account records: until you delete your account.

You do not have to wait for these periods to run out. You can erase stored payloads, delete individual log rows, or delete your whole account at any point, as described under Your controls below.

Where your data goes

A submission goes to the destination you picked for that form, and each form delivers to exactly one destination. Once a submission reaches that destination it is held under that provider's own terms and privacy policy, which are an arrangement between you and that provider.

The destinations you can currently connect are:

• Connected by sign in: Notion, Slack, Discord, Airtable.
• Connected with an API key: HubSpot, Mailchimp, Klaviyo, Brevo, MailerLite, EmailOctopus, Moosend, Omnisend, Sender.
• Connected with a URL only: Webhook (an HTTP or HTTPS URL you supply), Zapier, Make.

Sub-processors

Faizatech uses these providers to run FormRelay:

• Railway, for application hosting and the Postgres database.
• Resend, for transactional email such as password reset and account email, sent from noreply@faizatech.com.
• LemonSqueezy, as merchant of record for all payments. Checkout and receipts are handled by LemonSqueezy.
• The destinations you choose to connect, listed in the section above. Data sent to a destination is then governed by that provider's own policy.

Outbound IP addresses

Deliveries and other outbound requests from FormRelay leave from three static addresses, so you can allowlist them on your own endpoint or at a destination: 208.77.244.240, 152.55.184.241 and 152.55.185.190. These are shared static egress addresses provided by Railway.

Security measures in place

• Credentials are encrypted at rest with AES-256-GCM envelope encryption: the API keys, access tokens, refresh tokens and destination URLs you give us for a destination, the Webflow access token, and the webhook signing secret held for each site. Apart from destination URLs, none of them are displayed after they are saved.
• Webhook payloads from Webflow are verified with an HMAC signature before they are processed, against the signing secret Webflow issued for that site's webhook or against the App's OAuth client secret where Webflow signs with that instead. A payload that fails the check, or that carries a timestamp outside a five minute window, is rejected and recorded as a failed connection.
• Faizatech staff can see delivery metadata for support purposes, meaning which destination, when, and whether the delivery worked. The administrative endpoint selects metadata columns only, so staff do not see submission values.
• Credential shaped fields are removed before storage and before delivery, as described above.

No system can be treated as immune from compromise. If you think your account or a connected credential has been exposed, email contact@faizatech.com and also revoke the key or token in the destination provider's own settings.

Your controls

Everything below is available inside the App, without contacting support:

• Export your data: download the delivery history for a site from the Logs page for that site. The button there produces CSV, and the same export link returns JSON when you ask for that format.
• Delete stored payloads: on the same Logs page, erase submission values while keeping the delivery history, or delete individual log rows and the history as well.
• Disconnect a destination: delete the connection under Integrations, which erases our copy of the credential. Revoking that key or token in the provider's own settings is a separate step and worth doing, because a key stays valid there until you revoke it.
• Remove a site: this deletes that site's form mappings, the connections saved against it, and its delivery logs including any stored submission values. The removal dialog also offers to delete the FormRelay webhook from the Webflow site, which is selected by default and stops Webflow sending submissions to us.
• Delete your account: from Account settings. This removes your sites, connections and logs, and deletes the FormRelay webhooks from your Webflow sites.

If you need help using any of these, or want to make a request in writing, email contact@faizatech.com.

Uninstalling or removing the App

Uninstalling FormRelay or revoking it in Webflow stops the access token from working, so the App can no longer read the site and Webflow stops sending submissions to it. Records already stored stay under the retention periods listed above. To clear them sooner, remove the site or delete your account in FormRelay first, or email contact@faizatech.com and ask for deletion.

Cancelling a subscription is separate from deleting data. Access continues to the end of the paid period, after which the site stops delivering. Cancelling by itself does not erase stored records, so use the controls above if you want them removed.

Payments

FormRelay costs 4.99 USD per site per month or 49.99 USD per site per year, and there is no free tier. Payments are handled by LemonSqueezy as merchant of record, which means your checkout details and receipts sit with LemonSqueezy. Faizatech receives the subscription status needed to enable a site, and does not receive or store your card number. Refunds are available by emailing contact@faizatech.com within 14 days of purchase. Destinations bill separately on their own plans, and FormRelay adds nothing on top.

Children

FormRelay is a tool for site owners and is not directed at children. Faizatech does not knowingly collect personal information from children through the App. If you believe information about a child reached us through the App, email contact@faizatech.com and we will delete it. What your own forms ask visitors for remains under your control, and you are responsible for whether those forms are appropriate for the people filling them in.

Changes to this policy

We may update this policy by posting a revised version on this page with a new date at the top. If a change affects how submission data is stored, delivered or retained, that change will be reflected in the sections above.

Contact

For privacy questions about FormRelay, email contact@faizatech.com or use our Contact page.

The App runs at formrelay.faizatech.com. Product documentation is in the FormRelay documentation, and there is a getting help page covering support requests.

Last updated: 18 August 2026.