Privacy policy
Last updated
This policy explains what personal data we handle when you use Stagd, why we handle it, and the rights you have. Stagd covers stagd.dev, the dashboard at app.stagd.dev, preview URLs, the Stagd CLI and API, and the Stagd GitHub App.
1. Who we are
Stagd is in early access and is run by its founder as a private individual in Norway. No company has been set up yet. In this policy, "we" and "us" mean the people who run Stagd.
When a company takes over Stagd, it will take over the responsibilities in this policy. We will update this page and email account owners before that happens.
Questions about privacy go to hello@stagd.dev.
2. Our two roles
Controller. We decide how account, website, waitlist, usage and support data is used, and we are responsible for it under the GDPR.
Processor. Your previews contain your code, your database seeds, the mail and text messages your app sends, and the logs it writes. We handle that data only to run previews for you, on your instructions. Your workspace's organisation is the controller of it. We sign a data processing agreement with any customer who asks.
3. What we collect
| Data | Where it comes from | What we use it for |
|---|---|---|
| Account data: name, email address, avatar, GitHub username, workspace memberships and roles | GitHub when you sign in with it, or you when you sign in with a code by email | Signing you in, showing who did what, deciding what you may see |
| Repository data: repository and branch names, commits, pull request details, and the files needed to build a preview | The GitHub App, only for repositories your organisation picks | Building and deploying previews, and commenting on pull requests |
| Preview records: each preview's repository, branch, commit, status and activity, why a deploy failed (with a few masked log lines), and a screenshot of the preview | Your previews | Showing your team its previews and their history |
| Secrets and credentials you store in Stagd | You | Starting previews, pulling private images, reaching your compute and storage |
| Sessions and security data: IP address, browser, request times, CLI and API calls | Your browser and tools | Keeping you signed in, showing your sessions, security, preventing abuse |
| Usage events and error reports: what was used and what went wrong, with your user and workspace ids, the page's route and your country. No code, names, emails, logs or URLs with ids in them. | The dashboard, the CLI and our servers | Finding and fixing bugs, and learning which parts of Stagd are used |
| Feedback: what you write, your email address, your workspace and the page you were on | You, with Send feedback in the dashboard | Answering you and improving Stagd |
| Waitlist and support: email address, the page you signed up from, your country, and what you write to us | You | Letting you in, answering you |
We don't sell personal data, and we don't use advertising or cross-site tracking. Your IP address is used to look up your country for usage events, then dropped; it isn't stored with them.
Cookies. We only set cookies Stagd needs to work, so we don't ask for consent:
- a session cookie that keeps you signed in to the dashboard;
- a short-lived cookie (15 minutes) that carries an invite through sign-in;
- a cookie on stagd.dev that only says you're signed in, so the website can show the way to the dashboard;
- a pass (12 hours) that lets you open a preview only your workspace's members may see.
Usage events and error reports keep nothing in your browser. The dashboard remembers your display preferences, such as the theme, in your browser's local storage.
The status badge in stagd.dev's footer is loaded from Better Stack, our status page, which sees your IP address and browser as any site you open does. It sets no cookies.
4. Legal basis
- Contract: to provide Stagd to you and your organisation.
- Legitimate interests: to keep Stagd secure, prevent abuse, find and fix bugs, and learn how Stagd is used so we can improve it.
- Consent: for waitlist and product emails. You can withdraw it at any time.
- Legal obligation: when the law requires us to keep or hand over data.
5. Where previews run
Previews run on compute your organisation connects: a Namespace workspace, a Kubernetes cluster or a Docker host. Database seeds come from storage it connects, such as S3, Azure Blob Storage or a URL. These are your organisation's own services, under its own agreements with their providers, and not our sub-processors. We send them data only because your organisation set them up.
Stagd sends your compute instructions and reads status back. A preview's logs, captured mail and text messages stay on that compute: we read them when someone on your team looks, and we don't keep copies.
Database seeds are streamed from your storage through Stagd to the preview. Your storage credentials never reach the preview, and we don't keep copies of seeds. When a preview goes to sleep on compute that can't pause it, its data is saved with us until it wakes, and deleted then.
6. Sub-processors
We use these companies to run Stagd. Each is bound by a data processing agreement.
| Company | Purpose | Location |
|---|---|---|
| Cloudflare, Inc. | Hosting the website, dashboard, API, database, backups and preview URLs; DNS and edge network; sending Stagd's email | Global |
| GitHub, Inc. | Sign-in and repository access | United States |
| PostHog, Inc. | Usage events, error reports and feedback | European Union |
| Better Stack, Inc. | Uptime checks, alerts, and the status page and badge at status.stagd.dev | European Union and United States |
| Google Ireland Limited | The hello@stagd.dev mailbox, where replies to Stagd's email and support mail arrive | Global |
When data leaves the EEA, we rely on the EU Commission's standard contractual clauses or the EU-US Data Privacy Framework. We announce new sub-processors on this page at least 30 days before they start.
7. How long we keep data
- A preview's running data (its services, database, logs, captured mail and messages, screenshot and saved data) is deleted when the preview is destroyed: when the pull request is merged or closed, when the preview expires, or when someone destroys it.
- Preview records are kept while your workspace exists, so your team can see its previews' history.
- Sessions end 30 days after you last used the dashboard, or 90 days after you last used the CLI.
- Usage events and error reports are kept for 1 year.
- Our servers' request logs are kept by Cloudflare for 7 days.
- Account and workspace data is kept while your account or workspace exists. Email us to delete either, and we delete it within 30 days.
- Backups are taken nightly and kept for 90 days, then deleted.
- Waitlist entries are kept until you join or ask us to remove you.
- Support mail and feedback are kept while we need them to help you.
8. Security
All traffic is encrypted in transit. Secrets and credentials are encrypted at rest (AES-256-GCM), each with its own key, and decrypted only to start a preview. The GitHub App asks only for the permissions it needs, and only the people who run Stagd can reach your data, when they need to.
9. Your rights
You can ask us for a copy of your personal data, to correct it, to delete it, to limit how we use it, to receive it in a portable format, or to stop using it based on our legitimate interests. Email hello@stagd.dev and we will answer within one month.
For data inside your organisation's previews, contact your organisation first, since it is the controller.
You can also complain to the Norwegian Data Protection Authority, Datatilsynet.
10. Changes
We update this page when our practices change and change the date at the top. If a change is material, we email account owners before it takes effect.