Privacy policy.

pyrovue stores what it needs to run your account, your boxes and your billing, and nothing more. There are no analytics, no advertising and no selling or sharing of personal information.

The controller is Yusuf Badar, in the United States. Questions go to hello@pyrovue.com.

Everything below lives in one database on our server.

Accountemail · name · password hash

Your email address and name; a scrypt hash of your password, never the password; your GitHub or Google account id and picture if you sign in with them; when your email address was verified; when you accepted the terms; and where the sign-up came from (a run link's ref and repository), if it came from one.

Sign-in and securitysessions 30 days · activity log 1 year

For each signed-in device: a hash of the session token, its IP address, browser and last use, kept for 30 days or until you sign out. An activity log of sign-ins, failed attempts, sign-outs, password changes, revoked sessions, boxes created and deleted, visibility and plan changes and abuse stops, each with the time, IP address and device, kept for one year and at most 1,000 events. Two-factor seeds, where that feature is turned on for you, encrypted with AES-256-GCM. Sign-in codes sent by email are kept only as a hash for ten minutes.

Boxesrepository · setup log · tour · Code Map

The repository's owner and name, branch, commit and pull request number; the setup steps and their log, capped at 4 MB; the start command and its environment; notes, errors, visibility and times; the guided tour and the Code Map; and when the box ran, for metering.

BillingStripe ids · plan · status

Your Stripe customer and subscription ids, your plan, its status and renewal date. Card details go to Stripe's checkout and never reach pyrovue.

Usagebox-hours · Claude setups · boxes running

How many box-hours and Claude setups your account used this month and how many boxes are running, to enforce your plan's limits.

Email linkshashed tokens

Verification and password-reset links are stored as hashes and deleted when they expire.

Support mailwhat you send us

Emails to hello@pyrovue.com and our replies stay in our mailbox.

Some things stay in your browser only and never reach us: your theme, the banners you dismissed and the plan you picked before signing up.

Cookies: the session cookie that keeps you signed in, and short-lived cookies that hold a sign-in step, such as a GitHub or Google sign-in in progress. Nothing else. No third-party scripts run on pyrovue.com; the page's Content Security Policy allows only our own code.

• To run the service you asked for: your account, your boxes and the emails the account needs (performance of a contract).
• To keep pyrovue safe and stop abuse: the sign-in records, the activity log and the watchdog (legitimate interest).
• To bill you and keep the records the law requires (contract and legal duty).
• To answer legal requests we have to answer.

We send no marketing email. If that ever changes, it will be opt-in.

These companies process data for us, each for one job:

Amazon Web Serviceshosting · United States

The server pyrovue runs on and its disk, including the database and backups.

Stripepayments

Your email address and account id, and the card details you type into Stripe's own checkout.

Anthropiconly when Claude sets a repository up

The repository's file list, key files and command output, never your account data. Under Anthropic's commercial API terms, which do not use API data for training.

Resendtransactional email

Your email address and the email's content: verification links, password resets and sign-in codes.

GitHub and Googlesign-in

If you sign in with one of them, we receive your name, email address and picture. If you connect GitHub for My Repos, we keep an access token for your repositories, encrypted, until you turn it off or disconnect GitHub, and use it only to list your repositories, clone the private ones you open, and let git in a box push where you turn that on. Other repository lookups on GitHub carry no user data.

GitLabpublic project lookups

Looking up a public gitlab.com project carries no user data.

CloudflareDNS · www redirect · mail routing

DNS for pyrovue.com and pyrovue.app, the redirect from www, and routing of mail sent to hello@pyrovue.com to our mailbox at Google.

Two things to know plainly. Code running inside a box has internet access and sends whatever it sends; that is the repository's behaviour, not pyrovue's. And anyone with a public box's link can watch it, with anything that looks like a credential masked in the log.

Sessions30 days

Or until you sign out of that device.

Activity log1 year

Older events are deleted, and the log keeps at most 1,000 events per account.

Email linksuntil they expire

Then the hashed token is deleted.

A box's containerthe plan's retention after it sleeps

24 hours on Hobby, 7 days on Pro and Team. Waking the box sets it up again.

A box's record, log, tour and mapuntil you delete the box

Deleting a box removes all of them at once.

Your accountuntil you delete it

Deleting it removes your boxes and your record at once.

Backupsdaily · the last 14 kept

A copy of the database is made every day and the last 14 are kept, so a deleted record ages out of the backups within 14 days.

Server logsa short time

Rotated by size and kept only for troubleshooting.

Recipes and setup statisticskept

A working setup's commands are saved for the repository, not for you, and which kinds of setup work is counted in aggregate. Neither is personal data.

Passwords are hashed with scrypt, session tokens are stored only as hashes, two-factor seeds are encrypted at rest, and every box is a fenced-off container. The security page says what pyrovue does, in detail, and what is not done yet.

• See and correct your details in Settings.
• Export: email hello@pyrovue.com and we send you a copy of your data within 30 days.
• Delete: Settings, Delete account, removes your boxes and your record at once; backups age out within 14 days.
• Object to or restrict a use: email hello@pyrovue.com.
• Visitors in the EU and the UK can also complain to their supervisory authority.
• California: we do not sell or share personal information, and the rights above apply to you.

On servers in the United States. If you use pyrovue from elsewhere, your data is transferred there.

pyrovue is not for anyone under 13. If you learn that someone under 13 has an account, tell us at hello@pyrovue.com and we delete it.

Changes are posted here with a new effective date, and emailed to account holders when they are material. Questions and requests go to hello@pyrovue.com; the terms of service are next door.