Webflow security: custom code, forms and the connections behind your site
Webflow runs the platform and the hosting.
This guide covers the parts a site owner sets on top of it: custom code and embeds, the forms that collect visitors' details, and the apps, API tokens, webhooks and people with access. Each statement about Webflow is credited to the Webflow page that makes it, and the inventory at the end lists every script and form on your site, the forms each script shares a page with, and every place each form's data goes.
In this guide
Webflow custom-code and form data-flow inventory
Copy this into a document or spreadsheet and fill in one inventory per site. Part 1 is a worked example for an invented business and Part 2 is the blank form.
How to use itHide the instructions
Parts A to D map people and roles, custom code and embeds, forms and their destinations, and apps, tokens and webhooks, by reading your own account and published pages and asking the owner of each connected system. Part E is a staged removal plan with its limits written in. Each location and plan condition it gives was taken from Webflow's pages on 14 November 2026.
webflow.txt
Introduction10 lines
Part 1. Worked example97 lines
Part 2. Blank inventory55 lines
Whole template169 lines
WEBFLOW CUSTOM-CODE AND FORM DATA-FLOW INVENTORY
One inventory per Webflow site. Parts A to D are readings: of the Webflow dashboard and Designer, of your published pages as a visitor's browser receives them, and of what the owner of each connected system confirms. Part E is the only part that changes anything, and it keeps each change off the live domain: in preview, on the staging domain or on a duplicate site, within the limits written there.
RULES FOR FILLING IT IN
1. Names, never values. Never write an API token, client secret, webhook signing key, password, or a full webhook or form destination address into this inventory. Webflow's site token page says a site token acts as a unique identifier and password. For an address, write the receiving service and who owns it.
2. Where code or a setting might hold a key or token, record only whether one is present (yes, no or unsure) and which service it belongs to. Never its value, and never paste the code itself here.
3. Field names, not submissions. Do not open, export or copy real submissions for this review.
4. Read your published pages in an ordinary browser visit to your own site. No scanners and no repeated requests: Webflow's Acceptable Use Policy lists automated security scanning among actions that place, or may place, an unreasonable or disproportionate load on Webflow's infrastructure or its third-party providers.
5. A location in brackets is the one a Webflow page gives, and the page is named. Where no Webflow page used for this inventory names a screen, the row says what to read and leaves the location to you.
6. "Second platform plan" means the platform plan Webflow's pricing page lists after Team. Where a row depends on it and your site is not on it, write "not on plan".
==================================================
PART 1. WORKED EXAMPLE
Everything in Part 1 is invented: the business, the people, the addresses, the apps and the records. Nothing was run against any real site to produce it.
Site: Kestrel Bay Kitchens, an invented cabinetry business
Live domain: kestrelbay.example Staging: kestrel-bay.webflow.io
Plan: the Premium site plan, on the Team platform plan
Reviewed by: the business owner, with the operations manager, on 14 November 2026
Test marker for Part E: KBTEST-1114
A. PEOPLE AND ACCESS (Workspace role checks)
Where to look: the Workspace member list and each site's list of people with access. For which roles can publish, edit custom code, or manage forms and apps, read Webflow's role documentation for your plan on the review date and copy the answer in.
Record per person: who | user type (member, guest, reviewer or client, the user types Webflow's audit log reference lists) | role as Webflow shows it | can publish | can change custom code, forms or apps | still needs this access | finding
A1. Business owner | member | as shown | yes | yes | yes | holds the Primary Email Address of the account the site was created under
A2. Operations manager | member | as shown | yes | no | yes | none
A3. Designer at the agency that built the site, contract ended in June | guest | as shown | yes | yes | no | finding: the owner decides on removing this access once the agency has confirmed what its code and token (B3, D1) were for
A4. Copywriter | reviewer | as shown | no | no | yes | none
Ownership note: among the factors section 2.6 of Webflow's Terms of Service lists for ownership disputes, section 2.6.2 says Webflow will consider the owner of Website Content to be whoever has access to the Primary Email Address of the account it was created under. Here that is the business owner, not the agency.
Second platform plan only (Webflow's Get Workspace Audit Logs reference): does anyone already collect the Workspace audit log? Not on plan.
B. CUSTOM CODE, EMBEDS AND THIRD-PARTY SCRIPTS
Where to look: (1) each kind of published page in your own browser, such as the home page, a page with a form and a CMS page: view the page source and list every script and iframe with the host it loads from; (2) the site-wide custom code and each page's custom code (Webflow's custom code guide shows a script an app applied to a page in the Custom Code section of that page's settings in the Designer); (3) custom code embeds on each page (Webflow's pricing page names custom code embeds); (4) the apps in D3 that hold custom code scopes.
Record per item: item | host it loads from, or inline | where it was added (site-wide, page, embed, app or unknown) | pages it runs on | shares a page with a form | integrity attribute, for a script from another host | key or token present (yes, no or unsure, and whose; never the value) | owner who can say what it does | still needed | Part E candidate
B1. Analytics tag | the analytics vendor's host | site-wide, in the head | every page | yes, C1 and C2 | no | yes, the analytics account identifier | business owner | yes | no
B2. Chat widget | the chat vendor's host | applied site-wide by the chat vendor's app (D3) | every page | yes, C1 and C2 | yes | yes, the chat vendor's widget key | operations manager | yes | no
B3. Heatmap script from an agency trial | the heatmap vendor's host | page custom code, in the head of Home and Contact | 2 pages | yes, C1 | no | unsure | nobody | unknown | yes, E1
B4. Booking iframe | the booking service's host | custom code embed on the Book page | 1 page | no | not a script | no | operations manager | yes | no
B5. Reviews widget | the reviews app's host | applied by the invented app ReviewRail, still shown in the Custom Code section of the Products page settings | 1 page | no | yes | no | nobody: the app was uninstalled in August | no | yes, E2
B6. The same chat widget as B2, pasted into the Contact page's custom code by the agency | the chat vendor's host | page custom code | 1 page | yes, C1 | no | yes, the same widget key | operations manager | no: duplicate | yes, E1
Findings: B5 should have gone with the app. Webflow's Marketplace Guidelines ask an app to remove the custom code it registered and applied through the API, at site and page level, when a user uninstalls it, or to give clear removal instructions where it cannot remove it automatically. B6 duplicates B2. The same guidelines say pasted code sits outside an app's lifecycle and can run twice when the app also applies the same script through the API.
Response headers on the home page, read in your own browser's developer tools: Strict-Transport-Security present; Content-Security-Policy absent; X-Frame-Options absent. Webflow's security page describes custom security headers as a setting for the second platform plan: not on plan.
C. FORMS AND WHERE EACH SUBMISSION GOES
Where to look: each form's settings, the destinations in Part D, and the inboxes that receive notification emails. Webflow's pricing page describes form submissions as collecting submissions, customising notification emails and downloading submissions as a CSV, and form file upload as accepting file uploads from site visitors through forms.
Record per form: form | page | fields (names only) | fields that ask for health, identity, payment or password details, and free-text fields where a visitor could type them | file upload | destinations | for each destination: fields received, who can read them there, owner | scripts sharing the page (from B) | privacy notice names this form's data and who it is shared with
C1. Quote request | Contact
Fields: name, email, phone, suburb, project description, plan drawing (file upload)
Sensitive fields asked for: none. Project description is free text, so a visitor can type anything into it.
Destinations:
a. Webflow's stored submissions | all fields | people whose role reaches form submissions, per the role documentation | business owner
b. Notification email to the shared quotes inbox | all fields | the 3 people on that inbox | operations manager
c. CSV downloads | all fields | whoever downloaded one: the agency in May | finding: ask the agency to delete its copy
d. Webhook, form_submission trigger, to the invented quoting tool QuoteDesk | all fields | QuoteDesk users | QuoteDesk's developer
e. Site API token "Agency automation" with forms:read (D1) | every submission from every form on the site, going by Webflow's API reference | the agency | finding, see E3
f. The invented MailNest app, authorised with forms:read (D3) | every submission from every form on the site, going by Webflow's API reference | MailNest | business owner
Scripts sharing the page: B1, B2, B3, B6
Privacy notice: names contact form data; does not name QuoteDesk. Finding.
C2. Newsletter | Blog
Fields: email
Sensitive fields asked for: none
Destinations: a. Webflow's stored submissions; b. the MailNest app (f above); c. token e above
Scripts sharing the page: every site-wide script, so B1 and B2
Privacy notice: names the newsletter and MailNest
D. APPS, API TOKENS AND WEBHOOKS
D1. Site API tokens (site settings, Apps & integrations, API access section: Webflow's site token page, which also says only site administrators can create one, a site can hold up to 5, and a token stays valid until it is revoked or goes 365 consecutive days unused)
Record per token: name | scopes | created by, and for which system | still used, and who confirmed it
"Agency automation" | forms:read, sites:read | the agency, for a reporting script | unknown, agency to confirm | E3
D2. Workspace API tokens (second platform plan; Workspace sidebar, Apps & integrations, Manage, Workspace API access section: Webflow's workspace token page) | not on plan
D3. Apps
Where to look: the apps installed or authorised for the Workspace and for this site. Webflow's OAuth guide says the authorisation screen shows the permissions an app requests and lets the user authorise it for specific sites or a Workspace.
Record per app: app | sites or Workspace authorised | scopes approved, from the authorisation record or the app's listing | holds forms:read | holds custom code scopes | owner | still needed
MailNest | this site | forms:read, sites:read | yes | no | business owner | yes
Chat vendor's app | this site | custom_code:read, custom_code:write, sites:write | no | yes: Webflow's Marketplace Guidelines treat these as elevated-risk scopes | operations manager | yes
D4. Webhooks
Where to look: the webhooks set up for the site. Webflow's webhooks guide says webhooks can be configured through the dashboard as well as created through the API.
Record per webhook: trigger | filter (one named form, or all) | receiving system and its owner, never the address | made in the dashboard, with a site token, or by an app | receiving system checks x-webflow-signature and x-webflow-timestamp (ask its owner) | still needed
form_submission | Quote request | QuoteDesk, its developer | made in the dashboard, and Webflow's webhooks guide says dashboard webhooks do not include the headers needed to validate signatures | no: finding for QuoteDesk's developer | yes
E. STAGED REMOVAL PLAN
Part E keeps every change off the live domain: a change is checked in preview and on the staging domain, or made on a duplicate site. Removing anything from the live site, revoking a token, uninstalling an app or deleting a webhook is a separate decision the site owner makes, recorded on the last line of each entry.
Limits for every test in this part:
- Preview, a publish to the staging domain alone, or a duplicate site; never a publish to the live domain.
- A publishing freeze agreed with everyone who can publish, from the removal until the test is undone or approved. Webflow's custom code guide says a change an app makes to custom code through the API takes effect only when the site is published, and that publishing pushes all staged site changes live.
- One test submission per affected form, using the invented test record below and no real person's details.
- Every email address in the test goes to an inbox the business controls.
- Before the submission, list every destination it could reach (Part C) and treat each one as live.
- No scanners, no load and no repeated requests.
Test record: name Test Enquiry KBTEST-1114; email test.enquiry@kestrelbay.example; phone left blank; project description "KBTEST-1114 staged removal test, please ignore".
E1. Remove B3 (heatmap) and B6 (duplicate chat widget)
Evidence they are unused: the agency confirmed in writing that the heatmap trial ended in March; B6 duplicates B2
Rollback point: the version in the site's history from just before the removal. Webflow's security page says previous versions of a site can be restored.
Freeze agreed with: A1, A2 and A3, the three people who can publish
Where tried: preview mode, then kestrel-bay.webflow.io
Checks: Home and Contact load; the chat widget appears once; C1 sends one test submission
Where the test record should land: Webflow's stored submissions, the quotes inbox, QuoteDesk; token e and MailNest could also read it
Result: ______ Decision, and who made it: ______ Live change made by, and date: ______
E2. Remove B5 (reviews widget left after uninstall)
Evidence it is unused: ReviewRail uninstalled in August; any removal instructions from its developer attached
Rollback point, freeze and where tried: as E1
Checks: Products page loads in preview mode and on staging; no form on the page, so no test submission
Result: ______ Decision, and who made it: ______ Live change made by, and date: ______
E3. Token "Agency automation" (D1)
Cannot be tried on a copy: the token belongs to the live site.
Evidence it is unused: the agency's written confirmation that no system still calls it
What revoking does: Webflow's site token page describes revoking from the API access section and says revoking disables the token. A system that still needed it would then need a new token.
Decision, and who made it: ______ Revoked by, and date: ______
E4. Webhook to QuoteDesk: not a removal candidate, because it is in use. The signature finding goes to QuoteDesk's developer.
Test record cleanup: KBTEST-1114 lands in Webflow's stored submissions, the quotes inbox and QuoteDesk. Removing it is a change each system's owner makes. Owner and date for each: ______
==================================================
PART 2. BLANK INVENTORY
Site: ______________ Live domain: ______________ Staging: ______________
Plan: ______________ Reviewed by: ______________ Date: ______________
Screens I could not open: ______________
Test marker for Part E: ______________
A. PEOPLE AND ACCESS (one line per person)
Who | user type | role as shown | can publish | can change custom code, forms or apps | still needs access | finding
1. ______________________________
2. ______________________________
3. ______________________________
Who holds the Primary Email Address of the account the site was created under: ______
Second platform plan only (Webflow's Get Workspace Audit Logs reference): who collects the Workspace audit log, and where: ______
B. CUSTOM CODE, EMBEDS AND THIRD-PARTY SCRIPTS (one line per item)
Item | host or inline | where added | pages | shares a page with a form | integrity attribute | key or token present, and whose | owner | still needed | Part E
1. ______________________________
2. ______________________________
3. ______________________________
Response headers on the home page: Strict-Transport-Security ______ Content-Security-Policy ______ X-Frame-Options ______
C. FORMS (one block per form)
Form: ______ Page: ______
Fields (names only): ______
Fields asking for health, identity, payment or password details: ______
Free-text fields where a visitor could type such details: ______
File upload: yes / no
Destinations (fields received | who can read them there | owner):
a. ______________________________
b. ______________________________
c. ______________________________
Scripts sharing the page: ______
Privacy notice names this data and who it is shared with: yes / no
D. APPS, API TOKENS AND WEBHOOKS
D1. Site API tokens: name | scopes | created by, for which system | still used, confirmed by
1. ______________________________
D2. Workspace API tokens (second platform plan, per Webflow's workspace token page): name | scopes | created by | still used
1. ______________________________
D3. Apps: app | sites or Workspace | scopes | forms:read | custom code scopes | owner | still needed
1. ______________________________
D4. Webhooks: trigger | filter | receiving system and owner | how it was made | checks signature and timestamp | still needed
1. ______________________________
E. STAGED REMOVAL PLAN (one block per candidate)
Limits for every test in this part, as in Part 1: preview, a publish to the staging domain alone, or a duplicate site, never a publish to the live domain; a publishing freeze agreed with everyone who can publish; one test submission per affected form, using an invented record and no real person's details; every email address in the test goes to an inbox the business controls; before the submission, list every destination it could reach and treat each one as live; no scanners, no load and no repeated requests.
Candidate (from B or D): ______
Evidence it is unused, and who confirmed it: ______
Rollback point: ______
Publishing freeze agreed with: ______
Where tried (preview, staging or duplicate; never the live domain): ______
Checks, with one test submission per affected form: ______
Where the test record should land: ______
Result: ______ Decision, and who made it: ______ Live change made by, and date: ______
Test record cleanup (system | owner | date removed): ______
Next review date: ______Where Webflow sits in your website
Webflow security covers the platform Webflow runs and the layer you configure on top of it.
Webflow's security page describes Webflow as centralising design, CMS and hosting, among other things. On top of that, the site owner and whoever built the site add code, forms and connections: scripts pasted into the site, embeds on individual pages, apps installed from Webflow's Marketplace, API tokens made for integrations, and webhooks that send form data to other systems.
That layer decides which scripts run in your visitors' browsers and where the details they type end up, and it is what this guide and its inventory cover.
On the platform, Webflow's security page describes Webflow in its own terms. It lists TLS 1.2 or later for all sites and data encrypted at rest, HSTS enforced by default, a global CDN with DDoS protection and built-in rate limiting for all sites, and automated patches and updates with no customer maintenance.
It says Webflow maintains SOC 2 Type II compliance and is ISO 27001 certified. Those are Webflow's statements about its own controls, not about the code and settings a site owner adds, and this guide does not assess them.
Several controls depend on the plan. Webflow's pricing page lists site plans and, separately, platform plans, starting with Team. This guide calls the platform plan listed after Team the second platform plan, and where a Webflow page limits a feature to it, the page is named beside the statement.
What Webflow's terms leave to the site owner
Webflow's Terms of Service, the version effective 15 November 2023, fill in more of the picture.
Several passages put specific duties with the customer, and a plain-English note, which the Terms say is not legally binding, adds a recommendation. Each maps onto a part of the inventory:
- Section 4.4, under security safeguards: the customer will use all reasonable efforts to protect information it collects through the platform, and is solely responsible for configuring and implementing security controls for its website cookies, website headers, DNS configurations, subdomains and similar web attributes. If it discovers that information it collected has been breached, compromised or inadvertently exposed to unauthorised third parties, it is to notify Webflow promptly, with the root cause, remediation steps and compensating controls.
- Section 4.4, under privacy: the customer, as data controller, is directly responsible for the personal information it collects from its site's visitors, and Webflow, as processor, is not responsible for responding to those visitors on the customer's behalf.
- Section 4.4, under notice: the customer's privacy policy is to describe what information it collects, such as login information, contact form data and cookies, and how it uses and shares that information with Webflow and other third parties, including for marketing and advertising.
- Section 2.4: the customer is solely responsible for any third parties it invites into workspaces or sites it owns or administers, and anyone else who gets into an account may perform any actions available to the account holder.
- Section 3.3: the customer alone is responsible for any of its site content that may be lost or unrecoverable through its use of the platform, and Webflow has no obligation to archive or back it up.
- The plain-English summary printed under section 5.1: anyone who integrates Webflow services with a third-party service should review that service's terms, because they might need to agree to additional or different terms.
Reading those clauses for this guide
What those passages mean for your business is a question for your own adviser. For this guide they mark out the ground. Headers, the data your forms collect, the people you invite in and the third-party services you connect are each named in one of the passages above, and each has a row in the inventory.
Webflow custom code security: scripts, embeds and apps
Webflow's pricing page describes custom code as adding custom code and scripts to your entire site or to individual pages, and describes dynamic custom code as using CMS data inside custom code embeds.
Webflow's developer guide to working with custom code describes where a script an app registers lands: in the head of the page, or just before the closing body tag, applied to the whole site or to one page.
This guide's reading follows from that. Whoever can edit a site's custom code decides what every visitor's browser runs on the pages it covers, and a script loaded from another company's server runs whatever that server sends on the day.
The supply chain attacks guide covers third-party scripts in general and the XSS guide covers how untrusted text becomes script, so this section stays with where Webflow puts the code and what you can see of it.
Code that Marketplace apps add
Apps can add code too. Webflow's Marketplace Guidelines say the custom_code:read and custom_code:write scopes allow an app to inject site-wide JavaScript and are treated as elevated-risk scopes. They ask apps to deliver code through the Custom Code API so users can see, manage and remove what an app applies, and they require an app's listing to state what code it applies, what it does, where it runs and why.
When a user uninstalls an app, the app is to remove the code it registered and applied through the API at both site and page level, or to give clear removal instructions where it cannot remove it automatically.
The custom code guide says a script an app applies to a page can be seen in the Custom Code section of that page's settings in the Designer.
The same guidelines set out the limits of review. App review is not a testing service, a security audit or a complete list of defects, approval does not certify an app's overall security, and how an app's features behave on a published customer site is generally outside the scope of review.
Code an app delivers runs under the app developer's responsibility, as part of the service relationship between that developer and you.
Pasted code has a problem of its own. Both the guidelines and the custom code guide say code pasted into a site directly sits outside an app's lifecycle, so the app cannot version, update or remove it, and it can run twice when the app also applies the same script through the API.
A widget installed once by an app and once by a developer following the vendor's instructions is the case the inventory looks for.
Integrity attributes and security headers
For a hosted script, one registered by the address where it is hosted, the custom code guide says the API requires that address together with an integrity hash to verify the script's contents, and says inline scripts that apps register are uploaded to Webflow's CDN and served from there.
The Marketplace Guidelines recommend, without making it a review gate, that injected scripts sit at immutable, versioned HTTPS addresses with a subresource integrity attribute and `crossorigin="anonymous"`. Code you paste in yourself carries whatever attributes you gave it, so the inventory records whether each script from another host has one.
Response headers are the other place a site's rules for scripts can sit. Webflow's security page says customers on the second platform plan can configure custom security headers, including Content Security Policy and X-Frame-Options, through site settings, and that HSTS is switched on automatically for sites outside that plan.
The page does not describe a custom header setting for other plans. Read the headers your own published pages send, in your browser's developer tools, and write them into the inventory as they are.
Webflow form security: where each submission goes
Webflow's pricing page describes its form submissions feature as collecting submissions, customising notification emails and downloading submissions as a CSV, and its form file upload feature as accepting file uploads from site visitors through forms, up to 10 MB a file.
On that description alone, one enquiry form can leave copies in Webflow, in every inbox that receives a notification and in every CSV someone has downloaded.
Webflow's developer reference adds further routes out. Its List Form Submissions by Site endpoint lists all form submissions for a given site and needs the forms:read scope, and its scopes page lists forms:read among the site-level scopes that apply to both site tokens and Data Client apps. On that reading, each token or app holding the scope can list the submissions of every form on the site, not only the form it was made for.
Webflow's webhooks guide says that when an event occurs Webflow sends a POST request to a specified address, that a form_submission event carries details of the submission, including the form name, site ID, data submitted, submission timestamp and form ID, and that the trigger can be filtered to one named form.
The inventory therefore lists, for each form, every place its data goes and who can read it there.
Whether the receiving system can trust a webhook
Webflow's webhooks guide says webhook requests carry an x-webflow-timestamp header and an x-webflow-signature header, the signature being a SHA-256 HMAC. For webhooks created through site settings with a site token after 14 April 2025, it says each webhook has its own secret key, and for webhooks created by an OAuth app the app's client secret is the signing key.
It also says webhooks created through the dashboard will not include the request headers needed to validate request signatures. Read those statements against how each of your webhooks was made.
The guide describes the check on the receiving side as recomputing the HMAC from the timestamp and the body, comparing it with the signature, and treating a request older than 5 minutes as a possible replay. Whether your receiving system does that is a property of that system, so the inventory asks its owner rather than testing it.
The guide also counts any response other than HTTP 200, redirects, certificate problems and timeouts as failures, and says Webflow deactivates a webhook that keeps failing and notifies you by email, which is worth knowing before a receiving system is switched off.
Details Webflow's own documents say to keep out
Section 3.6 of the Terms says the platform may not be compliant with the Health Insurance Portability and Accountability Act, and that the customer agrees not to provide, or enable visitors to provide, Protected Health Information as that Act defines it.
The Acceptable Use Policy, effective 6 October 2026, says not to use the platform to collect, store or process protected health information subject to HIPAA or any other applicable health-privacy or data-protection laws, and not to post site content that includes non-public personally identifiable information, sensitive personal information or confidential data, such as Social Security numbers, passwords or credit card information. Webflow's security page says Webflow is not designed to store or process protected health information.
How those clauses apply to an Australian business's forms is for your adviser. The inventory flags any field that asks for health, identity, payment or password details, and any free-text field where a visitor could type them, so the question gets asked. Choosing which fields a form needs in the first place is the subject of the sensitive data exposure guide.
Scripts that share a page with a form
Every script in the custom code inventory that runs on a form's page runs where visitors type their details. Webflow's Marketplace Guidelines say apps must not read, collect, modify, transmit or act on password, login, authentication or other credential fields, and recommend that injected code avoid reading, writing or listening on payment form elements and never collect visitor-entered data beyond what the app's listing discloses.
Those rules are written for app developers. Webflow's Acceptable Use Policy says Webflow does not review or approve site content.
Code that you or a developer paste in has no app review behind it, which is why the inventory joins the two lists and records, for each form, the scripts that share its page.
Apps, API tokens and webhooks: connections that outlast a project
A site API token is made in the site's settings, under "Apps & integrations", in the "API access" section, and Webflow's site token page says only site administrators can create one.
The creator chooses its scopes. A site can hold up to five tokens, each acts as a unique identifier and password, and a token stays valid until it is revoked or goes 365 consecutive days without an API call.
The same page recommends a separate token for each use case with the minimal scopes it needs, and says to consider revoking an administrator's token when they leave or their role changes and to regularly review and revoke tokens that are no longer needed.
Revoking is a change to the site's access, so the inventory records each token by name, scopes and the system that uses it, and leaves the decision to the owner.
A site token cannot change custom code through the API. Webflow's site token page says site tokens do not reach the custom code endpoints, and its custom code guide says only apps with OAuth tokens can call them. On the second platform plan there are workspace tokens as well: Webflow's workspace token page says only workspace administrators can create them, from "Apps & integrations", then "Manage", in the "Workspace API access" section, and that they reach workspace resources such as the audit log rather than site data.
Apps connect through OAuth. Webflow's OAuth guide says the authorisation screen shows the permissions an app is requesting and lets the user authorise access to specific sites or a Workspace, and its scopes page says users see and approve those permissions when connecting an app.
Among the site-level scopes that page lists are forms:read and the custom code scopes, custom_code:read and custom_code:write, which it says are available only to Data Client apps. The Marketplace Guidelines require that users can fully revoke an app's access to their data.
An app's reach is set when someone approves it, which may have been during the build and by whoever was doing it, so the inventory asks what each app was authorised for and which scopes it holds.
Workspace roles and the people who can change the site
Anyone who can edit custom code, change a form's settings or connect an app can change what visitors' browsers run and where their details go.
Which Workspace and site roles carry those rights is a question for Webflow's role documentation, so the inventory asks you to read it on the review date and copy the answer in rather than rely on a summary here.
Webflow's developer pages settle a few points. Only site administrators can create site API tokens, and only workspace administrators can create workspace tokens. Webflow's audit log reference lists the user types member, guest, reviewer and client.
Its pricing page lists granular permissions and custom roles among the features of the second platform plan, and its security page lists two-factor authentication among its access controls, with single sign-on and SCIM on that plan.
For a business whose site was built by an agency or freelancer, sections 2.6.2 and 2.7 of the Terms are worth reading before anyone leaves. Among the factors section 2.6 lists for ownership disputes, section 2.6.2 says Webflow will consider the owner of site content to be whoever has access to the Primary Email Address of the account it was created under.
Section 2.7 says that if a client's website designer passes away or becomes otherwise unreachable, Webflow will be unable to transfer that designer's account or export the site content in their workspace to the client, and can only let the client update the billing information to keep the site running. The inventory asks who holds that address.
A record of who changed access
Webflow's audit log reference describes events for logins and logouts, with the login method and IP address; for people added to or removed from the Workspace or a site and changes to their roles; for invitations, including guest access requests; and for custom roles.
Each event names its actor, and an actor of type token means an API token made the change without a signed-in user. Webflow's reference for getting Workspace audit logs says the endpoint needs a workspace on the second platform plan and a workspace token with the workspace_activity:read scope. Without it, a dated inventory is your own record of who had access and when.
How to fill in the data-flow inventory
Make one inventory per site and work through it in order: people first, because they decide everything else, then custom code, forms and connections, then the removal plan.
Part 1 is a worked example for an invented cabinetry business with invented people, apps and records. Part 2 is the blank form.
- Parts A to D are readings. Nothing in them changes a setting, connects an account or submits a form. They read the Webflow dashboard and Designer, ask each system's owner, and send nothing to your published site beyond ordinary visits to your own pages.
- Names, never values. Write that a token, key or signing secret exists, its scopes and who holds it. Never copy a token, client secret, password, or a full webhook or form destination address into the inventory.
- For code that might hold a key, record only whether one is present and whose it is. For forms, record field names, never submissions.
- Read your published pages in an ordinary browser visit to your own site, using the page source and the developer tools. Webflow's Acceptable Use Policy lists automated security scanning among actions that place, or may place, an unreasonable or disproportionate load on Webflow's infrastructure or its third-party providers, so leave scanners out of a self-review.
- Where a Webflow page names the screen, the inventory gives the location and credits the page. Elsewhere it says what to read and leaves the location to you, because screens move.
- Date the inventory and redo it after a new app, a new form, a redesign or a person with access leaving. Webflow's pages were read for plan conditions on 14 November 2026.
Removing unused code and connections in stages
An inventory can turn up code nobody can explain: a tracking script from a trial that ended, a widget left behind by an uninstalled app, a token made for an integration that was replaced.
Removing it is the right end point, but removing the wrong thing can cut a form off from the system that receives it, and nobody may notice until enquiries stop. Part E of the inventory turns removal into a staged test with written limits. It is the only part that changes anything, and it keeps each change off the live domain.
- Record a rollback point first. Webflow's security page says Webflow keeps a history of changes to a site and that a previous version can be restored. Write down the version you would restore.
- Agree a publishing freeze with everyone who can publish. Webflow's custom code guide, written for app developers, says a change an app makes to a site's custom code through the API takes effect only when the site is published, and that publishing pushes all staged site changes live. On that reading, a removal made in the project for a test can wait there, and the next person to publish would take it live with everything else.
- Check the result in preview, then on the staging domain. Webflow's preview guide says preview and comment mode render the site on a canvas.webflow.com subdomain where custom code scripts can execute, and that scripts enforcing a Content Security Policy, domain restrictions or origin checks may need changes to work there. Webflow's Marketplace Guidelines refer to the .webflow.io domain as a staging domain. Webflow's Publish Site API reference describes publishing to one or more domains, with a choice of whether to include the default Webflow subdomain and which custom domains to include. Publish the test to the staging domain alone and leave the live domain out.
- A duplicate site is the other option, with a caution. The custom code guide says an app registering a script sets whether it can be copied on site duplication and transfer. A duplicate may therefore lack app scripts the live site runs.
- Send one test submission per affected form, using an invented record with a marker and an email address in an inbox the business controls. Before sending it, list every destination a submission could reach and treat each one as live.
- No scanners, no load and no repeated requests. Afterwards, list where the test record landed and who removes it from each system.
Connections cannot be staged
This guide's reading: a site token, a webhook and an app's authorisation, which Webflow's OAuth guide says covers specific sites or a Workspace, are attached to the real site or Workspace, so there is no copy to try their removal on. For those, Part E records the evidence that each one is unused and the person who confirmed it, such as the owner of the receiving system.
Webflow's site token page describes revoking a token from the API access section and says revoking disables it. A system that still relied on it would then need a new token.
Revoking a token, uninstalling an app and deleting a webhook are changes the site owner decides on and makes, and the inventory records the decision, who made it and the date.
What a review of your own Webflow account cannot show
The inventory records your settings, your code and the routes your data takes.
Several things sit outside it:
- Webflow's own systems: its hosting, infrastructure, staff access and audits. For those you have what Webflow publishes, starting with its security page.
- What a third-party script does from one visit to the next. The inventory records the host that serves it, and that host decides what the file contains each time it loads.
- What each receiving system does with the data: the inbox, the CRM, the automation tool or the app. That is for each system's own settings and terms, and the summary under section 5.1 of Webflow's Terms says to review a third-party service's terms when you integrate it.
- Copies already made: CSV downloads, forwarded notification emails and exports from the systems that received your form data.
- Whether a token, client secret or signing key has already been copied somewhere. The inventory shows where each one is meant to be.
- How your own receiving application handles a forged, replayed or malformed request. That takes testing of the application itself.
- Changes after the review date. A setting can change the day after you read it.
Webflow's Acceptable Use Policy on security testing
Read Webflow's Acceptable Use Policy, as it stands on the day, before anyone points a testing tool at a site Webflow hosts.
The version effective 6 October 2026 says, under the heading Probing or Testing Security, not to probe, scan or test the vulnerability of the platform, Webflow IP or any connected system or network, including penetration testing, without explicit written authorisation from Webflow.
Under Excessive Load or Interference, it says not to take actions that place, or may place, an unreasonable or disproportionate load on Webflow's infrastructure or its third-party providers, and says this includes brute-force attempts, denial-of-service attacks, automated security scanning and performance testing.
Webflow's security page separately describes a Vulnerability Disclosure Program: anyone who has identified a potential vulnerability is asked to review the program policy for what is in scope and submit a report through Webflow's bug bounty portal. This guide does not summarise that program's terms.
This guide's own reading is plain. Parts A to D of the inventory read settings and load your own pages in a browser, and Part E sends one ordinary submission per affected form to check that it still reaches its destinations. Anything more active against a site Webflow hosts, such as a scan or a penetration test, waits for Webflow's written answer, recorded with its date.
Where Clever Ops fits around a Webflow site
Nothing on this page describes a Clever Ops service for Webflow, and Clever Ops does not test Webflow's platform.
The Clever Ops methodology puts a host's platform outside the method, and services run by other businesses stay out of scope unless their owner agrees.
Where a Webflow site hands data to a web application you own that customers or staff sign in to, active testing of that application, including the route that receives Webflow's webhooks, sits within a scoped web application and API penetration test. It is a signed-in test of what each role can see and change, with the API called directly and not only through the screens.
A secure code review lists webhooks among the ways into the code it traces from the request to the query.
Before any request is sent, the methodology checks each target's hosting provider testing policy, because some hosts ask for notice or written approval first. For anything on Webflow's hosting, that check includes the Acceptable Use Policy quoted above. Where Clever Ops built or hosts the application under review, the work is a security review rather than an independent test, and the report names who built it and who hosts it.
Round-the-clock monitoring and emergency incident response are outside what Clever Ops offers. If you think a token, an app or a Workspace account is being misused now, contact Webflow and an incident response specialist first.
Frequently asked questions
Webflow's security page answers that question itself, listing, among other measures, SSL certificates for all hosted sites, DDoS protection and regular security updates managed by its team, along with two-factor authentication, single sign-on on the second platform plan and access controls for accounts. This guide gives no verdict. Webflow's Terms of Service put duties on the customer: section 4.4 says the customer is solely responsible for configuring and implementing security controls for its website cookies, website headers, DNS configurations and subdomains, and that the customer, as data controller, is directly responsible for the personal information it collects from its site's visitors.
Webflow's security page says customers on its second platform plan can configure custom security headers, including Content Security Policy and X-Frame-Options, through site settings. It says HSTS is switched on automatically for sites outside that plan, where customers on the plan can configure it. The page does not describe a custom header setting for other plans. Read the headers your published pages send and record them, with the date, before deciding anything.
Possibly more than the people in your Workspace. Webflow's List Form Submissions by Site endpoint lists all form submissions for a site and needs the forms:read scope. On that reading, any site API token or authorised app holding the scope can list them. Webflow's webhooks guide says a form_submission event carries the data submitted to the address the webhook was set up with, and its pricing page describes notification emails and CSV downloads. Which Workspace roles can see submissions is a question for Webflow's role documentation, read on the day you check.
Webflow's webhooks guide says requests carry x-webflow-timestamp and x-webflow-signature headers, the signature being a SHA-256 HMAC, and that a request older than 5 minutes may indicate a replay. It says webhooks created through site settings with a site token after 14 April 2025 each get their own secret key, that webhooks an OAuth app creates use the app's client secret as the signing key, and that webhooks created through the dashboard will not include the headers needed to validate signatures.
Read Webflow's Acceptable Use Policy first. The version effective 6 October 2026 says not to probe, scan or test the vulnerability of the platform, Webflow IP or any connected system or network, including penetration testing, without explicit written authorisation from Webflow, and lists automated security scanning among actions that place, or may place, an unreasonable or disproportionate load on its infrastructure or its third-party providers. Webflow's security page describes a separate Vulnerability Disclosure Program for reporting a potential vulnerability.
Webflow's own documents set limits. Section 3.6 of its Terms says the customer agrees not to provide, or enable visitors to provide, Protected Health Information as the Health Insurance Portability and Accountability Act defines it. Its Acceptable Use Policy says not to use the platform to collect, store or process protected health information subject to HIPAA or any other applicable health-privacy or data-protection laws, and not to post site content that includes non-public personally identifiable information, sensitive personal information or confidential data, such as Social Security numbers, passwords or credit card information. Its security page says Webflow is not designed to store or process protected health information. How these apply to your forms is a question for your adviser.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.