Webflow

There is no clear product-wide public promise that customer site or account data is excluded from all AI-model training uses.

Webflow's policy allows de-identified platform data to be used for business purposes, which leaves room for broad internal improvement uses.

Webflow publishes a global privacy policy and supporting legal materials instead of leaving platform data handling undocumented.

Webflow distinguishes ordinary platform data from de-identified data that can be used for broader business purposes.

Site owners retain meaningful control over what website content and integrations they put into Webflow.

Third-party apps, embeds, hosted sites, forms, and app credentials can create additional data flows beyond Webflow itself.

Webflow may disclose data for legal demands, business transfers, and affiliate or third-party operational purposes.

Webflow openly lists service providers such as payment processors and hosting partners involved in operating the platform.

The privacy policy is clear that third-party apps and services have their own policies and that users choose when to authorize them.

Webflow distinguishes the platform's disclosures from customer-controlled website behavior and connected app behavior.

Webflow combines personal information with third-party analytics, including session replay, to build broader customer profiles.

Webflow sites, websites, and marketing surfaces still use cookies and traffic monitoring outside any customer-site privacy notice.

Webflow is direct about using analytics and session replay technologies rather than hiding them behind vague wording.

The policy distinguishes de-identified data from personal information, which is clearer than many generic marketing policies.

Users still have some account and communication preference controls around how Webflow contacts them.

The policy does not provide one simple deletion timetable for platform, site, and account data.

Messages, uploaded website content, and public community posts may still be retained or remain visible depending on context.

Webflow documents privacy-rights paths and removal requests for some public community content.

Site owners and workspace collaborators can remove or change content through normal product controls.

Webflow describes what kinds of content and messages may be retained, which is more transparent than offering no retention explanation at all.

Financial data is mostly handled through processors rather than being fully stored by Webflow itself.

Workspace owners can manage sites, collaborators, forms, and integrations.

Users can choose whether to authorize third-party apps and what content those apps can access.

The platform provides privacy-rights paths and content-removal requests for some public-facing surfaces.

Site owners decide much of the end-user data collection and notice behavior on Webflow-hosted sites.

End-user privacy still depends heavily on the site owner and on third-party apps that the customer connects.

Some security and privacy limitations are shifted back to the user through general disclaimers about third-party services and internet transmission.