Privacy Policy
Effective November 12, 2026
What we collect, why, who sees it and how long we keep it, written against what the platform actually does today.
1. Who we are
Pywa Cloud (pywa.cloud, with studio.pywa.cloud, dashboard.pywa.cloud,
docs.pywa.cloud and status.pywa.cloud) is operated by David Lev, an individual based in
Israel, who is the data controller for the personal data described here.
Privacy questions and requests: privacy@pywa.cloud.
2. What we collect
Waitlist
When you join the waitlist we store your email address, the answers you give (what you want to deploy, how many bots, your role, where your bot runs today, whether you have a WhatsApp Business Account), the optional company, company size and "what are you building" text, an optional campaign tag from the link you arrived by, and the time. Entries live in the Pywa Cloud database. Spam protection is a hidden form field, a per-address rate limit and Cloudflare Turnstile.
Account and team data
Your email address, name and, if you use a password, a salted hash of it (never the password). If you sign in with Google or GitHub we receive your email, name and an account identifier from them, never your password there. If you turn on two-factor authentication we store the secret and hashed recovery codes. We store your team's name, its members and their roles, and pending invitations (the invited email address).
We keep sign-in sessions (a cookie, valid for up to 30 days) and, if you use the CLI, a login token (up to 90 days). We keep an audit trail of account actions such as deploys, member changes and settings, so a team can see who did what.
Bots, code and environment variables
A bot's name and settings, the code you deploy, deployment history and build logs, and the environment variables you set. Variables marked secret are encrypted before storage and never returned by our API. Every successful deploy also stores a copy of your bot's source archive so a lost server cannot lose your running code (see retention). Your bot's own output can end up in logs; if your code prints personal data, it will be in them.
Webhook traffic and message content
WhatsApp sends your bot's messages to Pywa Cloud, which checks them and forwards them to your container. We do not store message content in our database. We record technical facts about requests (time, bot, result, duration). Your bot, which you control, decides what to keep.
WhatsApp Business Account connection
The WhatsApp Business Account ID, the phone numbers you assign, and an access token for the account, obtained through Meta's Embedded Signup (where Pywa Cloud acts as your Meta Tech Provider) or provided by you. We encrypt these at rest and use them only to run your bot's connection to WhatsApp. We also read your account's phone number details, quality rating and, where you use Studio's publishing, your Flows and message templates.
Pywa Studio
Studio runs in your browser. Without an account, what you build stays in your browser. If you sign in and use sync, your Studio projects (bots, Flows, templates and their media) are stored with your team so every member can open them. Publishing to WhatsApp uses the connection above. Pushing to GitHub is done by the control plane through the GitHub App you installed; Studio itself never holds a GitHub token.
GitHub and integrations
If you install the Pywa Cloud GitHub App, we store the installation, which repository and branch each bot deploys from, and we read your code from those repositories to deploy it and post commit statuses. If you connect Supabase or Neon, we store your team's read-only access tokens, encrypted, and the connection string for a linked project as an encrypted secret variable. The database password you type for Supabase is used for that connection string and stored only inside it.
Server and security logs
Our servers log request metadata (IP address, time, path, result) for security, abuse prevention and debugging. Container logs are size-capped and rotated. Live resource metrics (CPU, memory, requests) are kept in memory for about six hours. We do not use this data for advertising or tracking.
We send transactional email (verification, sign-in and password links, invitations, important notices about your bots) through Resend. We do not send marketing email. If we ever do, it will be opt-in with an unsubscribe.
3. How we use it
- To run the waitlist and reach out about early access.
- To provide the service: building and running your bot, keeping its WhatsApp connection, showing status, logs and deployments.
- To keep the platform safe: verifying that webhook traffic really comes from Meta, isolating tenants, limiting per-bot resources and outbound traffic, and detecting abuse.
- To tell you about your account, bots and changes to the service.
- To understand what is used and what is broken, as described under cookies and analytics.
- To comply with the law.
Where the GDPR applies, our bases are performing the service you asked for, our legitimate interest in running a secure service, consent where we ask for it (analytics cookies), and legal obligation.
4. Who we share it with
We do not sell your data. We share it only as needed to run the service:
- Meta Platforms, Inc.: the WhatsApp Business Platform is the core of the product. Meta processes your WhatsApp activity under its own terms, independent of us.
- Hetzner Online GmbH: hosts the control plane, its database and the containers that run your bots, on a server in Helsinki, Finland (EU).
- Cloudflare: this website, Pywa Studio and the dashboard hosting, DNS, the network proxy in front of our servers, Turnstile, inbound email forwarding, and R2 object storage for encrypted database backups and bot source archives.
- Resend: delivers our transactional email.
- PostHog, Inc.: product analytics (Cloud, EU region), described below.
- GitHub, Google, Supabase, Neon: only if you sign in with or connect them. They share data with us under their own consent screens.
We may disclose information if the law requires it, or to protect the service and its users from abuse.
5. Cookies and analytics
We use PostHog (Cloud, EU region), reached through our own domain, to count visits and see which features of this site, the documentation, the status page, the dashboard and Pywa Studio get used, so we can fix what is broken and improve what matters. We record the pages and tabs you open, the buttons you press, whether an action succeeded or failed, and technical errors. We do not record what you type or what is on your screen: bot names, environment variable names and values, logs, phone numbers, flow contents and email addresses are never sent, and the waitlist form reports only whether it was submitted.
We also record on our servers that an action on your account happened, so we can run and improve the service and see problems the browser cannot: that a deploy finished and whether it succeeded, how long it took and roughly how large it was, that a bot was created, started, stopped or restarted, and, once a day per bot, whether it received traffic and whether it answered with errors. These records hold your account's opaque ID, counts, outcomes and timings, never your code, environment variables, logs, message content or email, and they do not depend on the cookie choice below, because they describe operating your account rather than your browsing. In the documentation we also record what is typed into the search box, once you stop typing, so we can see what the docs fail to answer.
A short bar asks for your choice. If you decline (or ignore it), visits are still counted but anonymously and without cookies or any stored identifier. If you accept, PostHog sets a first-party cookie so your visits to this site, the documentation, the status page, the dashboard and Studio belong to one anonymous visitor (and, once you sign in, to your account's opaque ID, never your email or name). In Pywa Studio only, accepting also lets us watch anonymised session recordings, to see where the builder gets in your way: everything you type and the contents of your flows and templates are hidden in them. We do not record sessions on this website, the documentation, the status page or the dashboard. You can change your choice any time with Cookie preferences. Your choice is remembered in one small cookie shared by our sites (it holds only "accepted" or "declined").
Besides analytics, the dashboard and Studio use a strictly necessary sign-in cookie and a CSRF token, and this site remembers your light or dark theme in your browser's local storage. We do not use advertising cookies.
6. Retention
| Data | How long |
|---|---|
| Waitlist entries | Until you ask us to delete them, or you sign up |
| Account, team, bots, deployments | While your account is active |
| Secrets and tokens | Deleted when you remove them, unlink the integration, or delete the bot |
| Sign-in sessions and CLI tokens | Up to 30 and 90 days; revoked on password change |
| Bot source archives | The latest archive while the bot exists (deleted with the bot); earlier deploys' archives for 30 days |
| Database backups | Encrypted daily dumps kept for 14 days |
| Container logs, live metrics | Size-capped rotation; metrics about six hours in memory |
You can delete your account in the dashboard. That removes your account and, if you were its only member, your default team once it has no bots. Data in backups disappears as they expire, within 14 days. We do not yet have an automated expiry schedule for every log type; until then, deletion on request removes what remains.
7. Your rights
Wherever you are, you can ask us to tell you what we hold about you, correct it, delete it, export it, or withdraw consent for anything based on consent. Write to privacy@pywa.cloud. If you are in the EU/EEA, the UK or a US state with its own privacy law you may have further rights and may complain to your local data protection authority.
8. Security
Secrets, WhatsApp tokens and integration tokens are encrypted at rest; database backups are encrypted before they leave the server. Traffic to your bot is validated against an HMAC signature before it reaches your code. Each bot runs in its own non-root container with no route to another tenant's container, and per-bot resource and outbound-traffic limits. Accounts can use two-factor authentication. Full detail on the security and isolation page. This is container isolation on shared infrastructure, not VM-level isolation, and it has not had an independent audit. No system is perfectly secure; if we learn of a breach affecting you, we will tell you.
9. International transfers
Our infrastructure is in the EU (Helsinki). Meta, Cloudflare, Resend, PostHog (EU region) and others operate globally, so data may be processed outside the EU/EEA. Where required we rely on the safeguards those providers offer, such as standard contractual clauses.
10. Children
Pywa Cloud is a developer and business tool, not directed at children. We do not knowingly collect personal data from anyone under 16.
11. Changes
When we make material changes we update the date above and, for significant ones, notify account holders by email or a notice on this site.
12. Contact
Privacy: privacy@pywa.cloud. Abuse reports: abuse@pywa.cloud.