PrivacyPolicy

The short version

You sign in with Google. WEB4 stores the sites you build, the conversation that shaped them, and the files you upload. If you pay, charges go through a secure payment gateway. On public marketing pages WEB4 uses Meta Pixel for advertising measurement and Microsoft Clarity for analytics; neither runs in the editor, your projects, or checkout.

Account and sign-in

Sign-in uses Google. WEB4 does not ask you to create a password. The sign-in page also shows GitHub; that button does not start a login.

From Google, WEB4 receives the profile details needed to recognize you:

• your name
• your email address
• your profile picture, kept as a link inside the sign-in session
• a Google account identifier, stored as the subject of your WEB4 session

That session lives in an encrypted cookie. WEB4 does not keep a copy of your Google access token or refresh token. A billing account row — email, display name, and the sign-in subject — is created when you pay, open settings that read your credit balance, or use a metered AI action. Checkout can replace the email and display name with the billing email and the cardholder name you enter.

Projects and website content

Projects are stored for the account that created them, in Cloudflare R2. A project can include the page HTML, the words and links you edit, the design you started from, and a saved editor conversation.

That conversation is editor metadata. It is not printed onto the public site. WEB4 keeps up to the newest 100 settled lines, and each line is limited in length. Undo and redo stay in the editing session and are not saved as their own record.

When you publish, WEB4 copies the site into a separate public bucket and serves it at a name.getweb4.com address, and at a custom domain if you connect one. Published pages are public on purpose.

AI prompts, voice, and usage

When you ask WEB4 to change a page or generate one, the prompt, a short view of the selection, nearby page context, and a portion of the site CSS are used to produce the edit. Those prompts are not written into a separate database row. They can remain in the saved project conversation.

Voice input sends audio from your browser for transcription. WEB4 stores a billing record for that session and does not store the audio file. If you save the project, text that came from voice can sit in the editor conversation like any other line.

Free accounts have a count of applied AI edits. Paid voice use is recorded on a credit ledger: token or time figures, the model name, and the credit change. That ledger does not store the prompt text.

Uploads

Images and video you add to a project are stored with that project. WEB4 keeps the file type and a generated file name. It does not keep the original file name as its own field. Image uploads are limited to common image types and a size cap; saved video is limited to mp4 and webm with its own size cap.

Billing

Founding Access, AI credit packs, and WEB4 Cloud are charged through secure gateways using SSL encryption. If WEB4 cannot reach the processor, no billing occurs at the processor's end.

When a charge succeeds, WEB4 stores:

• any email, phone, and postal code you provided, encrypted with AES-256-GCM
• the amount, currency, and description of the purchase

A declined Founding Access charge is recorded as a failed payment.

The IP address on the checkout request is sent to our secure payment gateway with the charge.

Domains and hosting

If you connect a domain you already own, WEB4 stores the hostname, a verification token, and the connection status. Ownership is checked with a DNS TXT lookup. When Cloudflare custom hostnames are configured, the hostname is also sent to Cloudflare so the domain can route to your published site.

Cookies and technical data

WEB4 uses cookies to keep you signed in and, during credit checkout, to remember the pack you chose. Your light or dark theme is stored in this browser, not in a cookie. The details are on the Cookie Policy.

On public pages, Meta Pixel sends Meta page views, browser and device details, your IP address, and cookie identifiers so we can measure advertising and traffic. Meta may combine this with its own data. It is not used in the editor, account, checkout, or on published customer sites, and project content is not shared. Opt-out options are on the Cookie Policy page.

Why this information is used

• to sign you in and keep projects on the right account
• to save, edit, export, and publish the sites you build
• to run AI edits and voice transcription
• to connect and disconnect a custom domain
• to protect sign-in and avoid charging the same purchase twice

Service providers

• Google, for sign-in
• Cloudflare R2, for private projects and published sites
• Cloudflare, for custom hostnames when that connection is configured
• Meta Platforms, for advertising measurement (Meta Pixel)
• Microsoft, for Clarity analytics

Fonts are compiled with the site and are not an analytics tag.

Security

Sign-in cookies are httpOnly. Payment details kept by WEB4 are encrypted as described above. Project files are stored for your account, and another account cannot open them. These are the controls in the product. They are not a promise that data cannot be lost, intercepted, or misused.

How long we keep information

We retain personal information only for as long as reasonably necessary to provide WEB4, maintain your account, operate our services, prevent abuse, resolve disputes, and meet applicable legal or accounting obligations.

Projects generally remain in your account until you delete them. If a project has been published, its published website may remain available until it is separately unpublished.

Certain records may be retained after other account content is deleted. These can include payment transaction records, WEB4 AI credit records, and usage records needed to maintain account balances, enforce service limits, prevent fraud or abuse, and preserve the integrity of our billing systems.

Retention periods vary depending on the type of information and why it is needed. When information is no longer reasonably necessary for these purposes, we remove or anonymize it where appropriate.

Your choices

You can sign out, delete a project from My Projects, unpublish a live site, and disconnect a custom domain. Those are separate actions. Deleting a project does not take the live site down. Theme storage can be cleared in the browser. Blocking essential cookies will stop sign-in and credit checkout.

Access, correction, and deletion requests are described on Data & Privacy Requests and Data Deletion. WEB4 does not offer an automated privacy portal.

Changes

When this policy changes, the date at the top of the page changes with it. Continued use of WEB4 after that date is use of the revised policy.

Contact

Privacy questions go through the Contact page.