Weavoa
Legal

Privacy Policy

Last updated November 11, 2026

Weavoa (“we”) lets you build, publish and host websites, alone or with an organization. This policy explains what we collect when you use weavoa.com, the builder and console, and sites published on weavoa.com or on custom domains, and what you can do about it. We don’t sell your data or use it for advertising.

If you sign in with Google

When you choose “Sign in with Google”, Google shares your name, email address, profile picture and a Google account ID with us. We use them to create your account, sign you in, and show who’s signed in. We don’t get your Google password or access to anything else in your Google account.

Organizations and collaborators

We store your organization’s name, what it does, its plan, and who is in it. Everyone in an organization can see each member’s name, email address, profile picture and role.

When an owner adds someone by email, we store that email address as a pending invitation, so the person sees the invitation when they sign in with it and can accept or decline it. We don’t email them. The invitation is deleted when they accept or decline it, when the owner cancels it, or when the organization is deleted.

Your apps

We store the apps you save (text, settings, images and any files or code you upload) so you and the people in your organization can open them on any device and publish them. Everyone in the organization can see and edit its apps. Apps are only stored in your own browser until you sign in.

Anything you publish is public: anyone with the address can see it.

Editing together

While you have an app open, the other people in your organization who have it open see your name, profile picture and which section or file you’re working on, and your edits reach them as you make them. This live connection runs through Cloudflare and only passes changes along; your edits are kept the same way as the rest of the app.

GitHub

If you connect GitHub, we store your GitHub username and an access token, encrypted. We use them only to list and read the repositories you’ve chosen and to deploy them, including when you push. You can disconnect from the console’s Home page, or revoke access on GitHub.

Custom domains

If you connect a domain, we store the domain name and where its setup is. To verify it we look up its DNS records through Cloudflare’s public DNS, and we register the domain with Cloudflare so it can issue the HTTPS certificate.

Plans and billing

We record your organization’s plan, the prices you agreed to, and when billing for a plan or domain starts. Stripe processes payments for plans and domains. You enter your card on Stripe’s pages, so we never see or store your full card number. We keep the Stripe customer and subscription IDs for your organization, and show the card’s brand, last four digits and expiry date, your invoices and your payment status, which we get from Stripe.

Visitors to published sites

To show the people in a site’s organization their traffic and to enforce hosting limits, we count page views, bandwidth, the page visited, the visitor’s country (from their IP address) and the referring website. To count unique visitors we store a shortened, one-way hash of the visitor’s IP address and browser, which changes every day and can’t be turned back into an IP address. These per-visitor records are deleted after 40 days. Published sites don’t set cookies.

Cookies and browser storage

These are essential, so they don’t need your consent; our cookie notice tells you about them and remembers that you’ve seen it. We don’t use advertising or tracking cookies. The builder also uses your browser’s local storage for a copy of your apps, the organization you last picked, and your editor settings.

Who processes data for us

Keeping and deleting your data

We keep your account, organizations and apps until you delete them.

Stripe may keep its own payment records as the law requires.

Security

All traffic uses HTTPS. Sign-in sessions are stored only as one-way hashes, and GitHub tokens are encrypted. Code that users publish runs in a sandbox, separate from your account.

Children

Weavoa isn’t intended for children under 13, and we don’t knowingly collect their data.

Changes and contact

If we change this policy we’ll update the date above. Questions or requests: ztzickmann@mail.lipscomb.edu.