Privacy Policy
Privacy terms written around the real product workflow
This Privacy Policy explains how We0.ai handles information when you use account login, project creation, page generation, article workflows, CMS management, domain setup, deployment, and related website delivery functions.
The goal is not to make broad statements detached from the product. The goal is to explain, in practical terms, what information may enter the workflow, why it is used, when third-party providers are involved, and what users remain responsible for inside the current service scope.
- Covers accounts, projects, generated output, and launch records
- Organized around the current website delivery workflow
- Clarifies third-party boundaries in login, payments, and deployment
- Focused on practical handling rather than abstract claims
Scope and core definitions
This policy applies to the information processed through We0.ai's current website-building and website-delivery workflows. That includes the website, account system, project-related product surfaces, article and CMS capabilities, deployment flow, and related support or billing steps when enabled in the running environment.
In this context, information may include account identifiers, project instructions, generated pages, article drafts, CMS-managed content, deployment and domain records, operational logs, and any other materials a user actively submits or triggers through the product.
What information may be collected
Depending on which features you use, We0.ai may process several categories of information:
Account and authentication information
Information used to create, identify, verify, and maintain an account, such as email-based login details, session-related information, or linked third-party authentication data.
Project, content, and generation data
Project descriptions, page instructions, generated website output, article drafts, CMS-managed content, media references, and similar materials that users submit, edit, or publish through the platform.
Deployment, domain, and delivery records
Records needed to publish websites, such as deployment status, launch URLs, default-domain usage, custom-domain setup details, and related workflow feedback.
Operational and support data
Basic usage signals, logs, service events, support-related context, and error records used to keep the product available, diagnose failures, and improve workflow reliability.
How the information is used
Data in We0.ai is used to operate the current website delivery system rather than for unrelated collection purposes.
- Authenticate users, maintain sessions, and restrict access to account-level functions.
- Generate, store, edit, organize, and publish website pages, articles, and CMS-managed materials.
- Support deployment, domain configuration, release tracking, and related launch steps.
- Operate billing and payment-related workflows when payment capabilities are enabled in the current environment.
- Monitor service health, investigate failures, prevent abuse, and improve product stability over time.
Third-party providers and sharing boundaries
Some parts of the workflow rely on third-party infrastructure, including providers for authentication, email delivery, hosting, deployment, storage, payments, or analytics. When you use those functions, the corresponding data may be processed within that provider's service boundary to complete the workflow.
We0.ai does not describe broad data-sharing rights detached from the current product path. In practice, information is shared only when it is necessary to deliver the feature you are using, maintain service availability, support payment or deployment steps, or comply with a legal requirement connected to that workflow.
- Authentication and email providers may receive the minimum information needed to complete login and verification steps.
- Hosting, storage, or deployment providers may receive site output, configuration data, or domain-related records needed to publish and operate a website.
- Payment providers may process transaction-related information needed to complete billing workflows when billing is enabled.
Retention, user responsibilities, and policy updates
Retention periods may vary depending on account status, project lifecycle, operational needs, legal obligations, and the type of workflow involved. Users remain responsible for the materials they upload, generate, edit, and publish, and should avoid placing unnecessary sensitive information into public-facing website or article content.
As the product evolves, this Privacy Policy may be updated to reflect changes in the real workflow, third-party integrations, or legal requirements. Continued use of the service after an updated policy takes effect indicates acceptance of the revised terms within the scope permitted by applicable law.
Summary
A useful privacy policy should explain the real workflow, not just list generic promises.
For We0.ai, that means clearly mapping account information, project data, generated website materials, deployment records, and third-party delivery steps to the actual product architecture users interact with today.