Privacy policy
Last updated 17 November 2026
Beep (“Beep”, “we”, “us”) runs an application platform at usebeep.dev that builds, deploys and runs software on servers our customers choose. This policy explains what personal data we collect when you use our website, dashboard and API, why we collect it, and what you can do about it.
What we collect
- Account details: your email address, name and a hashed password. If you sign in with Google or GitHub, we receive your account identifier, email address, name and whether the provider has verified the email. We do not receive your Google or GitHub password.
- Workspace data: workspaces, members and invitations, projects, services, servers, domains, settings and the activity log of changes made in them.
- Source code access: when you connect GitHub, the repositories you grant our GitHub App access to, which we read to build and deploy your applications.
- Data your applications produce: build and runtime logs, metrics and request statistics for the services you run on Beep. Environment variables and secrets you store are encrypted.
- Billing details: your plan, invoices and billing address. Card details are collected and held by Stripe; we never see full card numbers.
- Technical data: IP addresses, browser and device information and request logs, kept for security, abuse prevention and troubleshooting.
- Messages: what you send us by email or through our contact and early-access forms.
Why we use it
- To provide the service you signed up for: authenticate you, run your workloads and show you their state.
- To keep accounts and the platform secure, including sign-in protection, rate limits and fraud prevention.
- To bill you and meet our tax and accounting obligations.
- To send service emails such as sign-in codes, password resets, invitations, alerts and billing notices.
- To answer your questions and improve the product.
We do not sell personal data and we do not use it for advertising.
Who processes data for us
We share data only with providers that help us run Beep, and only what each needs:
- Hetzner, Scaleway and Amazon Web Services: servers, storage and key management.
- Cloudflare: DNS, content delivery, object storage, bot protection and email delivery.
- PlanetScale: our primary database.
- Stripe: payments and invoicing.
- GitHub and Google: sign-in, and repository access you grant through GitHub.
When you run workloads on servers or cloud accounts you connect yourself, that provider processes your application data under your own agreement with them.
We may also disclose data when the law requires it, or to protect the rights and safety of our users and of Beep.
Where data is stored
Our platform runs primarily in the European Union. Some providers above may process data in other countries; where they do, they rely on recognised safeguards such as the European Commission’s standard contractual clauses.
How long we keep it
We keep account and workspace data while your account is active. Logs and metrics expire on a rolling basis. When you delete a workspace or ask us to delete your account, we remove the data within 30 days, except what we must keep for legal, tax or security reasons, and backups, which expire on their normal schedule.
Cookies
The dashboard uses cookies that are strictly necessary to keep you signed in and to protect your session. Our website uses Cloudflare Turnstile on its forms to block automated abuse. We do not use advertising or cross-site tracking cookies.
Your rights
Depending on where you live, you may have the right to access, correct, export or delete your personal data, to object to or restrict how we use it, and to complain to your local data protection authority. You can change most account details in the dashboard. For anything else, email hello@usebeep.dev and we will reply within 30 days.
Security
We encrypt data in transit. Our primary database and object storage are encrypted at rest, and we encrypt stored secrets such as environment variables with our own keys. We hash passwords, support multi-factor authentication and limit staff access to what their work requires. No system is perfectly secure; if a breach affects your data, we will tell you as the law requires.
Children
Beep is not meant for anyone under 16, and we do not knowingly collect their data.
Changes
We will update this page when our practices change and change the date at the top. For significant changes we will also email account owners.
Contact
Questions about this policy or your data: hello@usebeep.dev.