Privacy
Bay is built by Supersonic Software, Inc. This page says what we hold and why, in the same words we would use to describe it to each other.
What an account is
Signing in with Google or GitHub gives us your email address, your display name and your avatar URL, and nothing else from that account: the profile and the email address, no repositories and no contacts. Google also tells us whether it considers that address verified, which is what an “anyone at acme.com” rule needs in order to mean anything. If you connect GitHub so that a push can deploy, we also hold an installation token for the repositories you chose, and we can read those repositories and nothing outside them. Signing in with an email and a password instead stores a bcrypt hash; the password itself never reaches our database.
The session is one httpOnly cookie on thebay.cloud. It is not shared with anyone, it carries no profile data, and there is no advertising or cross-site tracking cookie on this site or in the dashboard.
What we hold about your apps
The code you ship, the build output, the environment variables you set, and the logs the running app writes. Secrets go into Google Secret Manager rather than into the container's configuration, and are mounted into the build and the running app from there; they are never printed in a log or shown to anyone who cannot already open the app's settings. Databases we provision for you are yours: we take backups so that we can restore them, and nothing else on our side reads what is in them.
When a deploy fails, the repair agent reads the failing build log and the parts of the repository the failure points at, in order to propose a fix. That is a model call with your code in it: Gemini, through Vertex AI, on the same Google Cloud account that runs everything else here — so the code does not leave that account. It happens only on a failure, and only for your own app.
Visitors to the apps you publish
Every app gets an audience view: page views, referrers, countries, browsers. It runs on an instance of umami that we host ourselves, and the tag it uses is served from your app's own domain rather than from somebody else's CDN — so no request about your visitors goes anywhere but to us. There is no advertising identifier and no third-party cookie. On a paid plan the tag can be turned off entirely.
Who else sees any of it
Two companies, each for one job. Google Cloud runs the machines, the database, the storage and the model the repair agent calls. Stripe takes payments — we hold a customer id and the plan you are on, and never see a card number. That is the whole list; we do not sell data, and there is nobody on it whose job is marketing.
How long, and how to end it
Deleting an app deletes its containers, its images, its secrets and its database. Deleting your account does that for every app you own, cancels the subscription, and removes the account — immediately, from the dashboard, guarded by retyping your own email address. There is no waiting period and no soft delete to change your mind during. You can also ask for a copy of what we hold, or for it to be removed, by writing to founders@thebay.cloud; a person reads it.
Changes
If what we hold changes, this page changes on the same day, and the change is listed in the changelog like any other. It is versioned in the same repository as the product, so what it said on any given date is a matter of record.