Skip to content
Privacy tools

Privacy policy generator for Webflow

Policy generation is paused. Check your existing policy against your website.

Build a privacy draft around your Webflow forms, analytics and integrations. Scan your site free and turn the findings into a publication checklist.

Updated 1 Oct 2026 against Webflow Help Center

Start with your website

I have the link to my privacy policy

Optional. If you paste the direct link, we read that page instead of looking for it, so the check is more exact.

By scanning, you confirm that you own this website or are authorized to test it, and you agree to our Terms.

No account needed.

What to account for

  1. Map each form destination

    Webflow forms can store submissions in Webflow, send notification emails, or connect to webhooks and apps. A custom action changes that route. Document the destinations you actually enabled.

  2. Include stored submissions

    Manage stored form submissions in Site settings → Forms. Include this storage in your retention and deletion process, alongside copies held in your inbox or connected tools.

  3. Choose how tracking gets consent

    Webflow provides tracking-consent settings for Analyze and Optimize. Match your chosen tracking behavior to the visitor choices on the published site.

Common mistakes to check

  1. Describing the form as email-only

    The default flow can include Webflow storage as well as notification emails. Inspect the form’s settings before saying that submissions only reach your inbox.

  2. Ignoring uploaded files

    Deleting a Webflow submission also deletes its uploaded files. Include files in your retention workflow and check whether separate copies exist in downstream services.

Your review checklist

Our suggested review process. The linked requirements above explain the platform or legal basis.

  1. List forms and integrations

    Scan the published site, then inspect each form’s destination settings, notification recipients, uploaded-file options and connected CRM or automation. Record purposes and data fields.

  2. Draft the complete data journey

    Confirm the controller, retention periods, service providers and request contact. Explain analytics separately from form processing so visitors can understand each purpose.

  3. Test a visitor’s choices

    Publish the policy link near forms and in the footer. Test a fresh visit, refusal and acceptance; compare observed requests with the behavior described in the draft.

Example

  1. A lead form connected to a CRM

    A fictional agency sends enquiries to Webflow, a shared inbox and a CRM. Its owner records the fields, recipients and deletion process for all three destinations.

  2. A policy that matches the setup

    The agency reviews the draft against a test submission and its analytics settings. It publishes the policy, then adds privacy review to its checklist for future form changes.

Questions before publishing

  1. Does a custom action keep Webflow’s normal delivery?

    A custom action cannot be combined with Webflow storage or its email notifications for that form. Check the configured endpoint and its own processing.

  2. Where can I delete saved submissions?

    Use the Forms area in site settings to manage and delete submissions. Check external destinations separately.

  3. Should I review Analyze or Optimize settings?

    Yes, when enabled. Their tracking-consent settings are part of the published site’s data collection behavior.

Source review and changes

First edition: platform requirements, implementation checks and fictional worked example. Sources reviewed on the date above; verify changes before relying on them.