Terms

what you are using

Cubby is in early access. Access is by sign-in. During early access we admit a limited number of new accounts each day, and we can remove access under §04. The platform is built and run by one person, Matt Heiting: these terms are an agreement between you and him, and “we” on this page means him. Support is that person reading email. Things will occasionally move under you; when they do, tell us, and a human answers.

• It is early-access software, and it is provided as it is. No warranty of any kind: not that it will be available, not that it will be correct, not that it will keep working the way it does today. During early access you may lose access, and you may lose data. The privacy page says exactly what we hold and for how long; the security page says exactly how it is built. Neither promises more than the code does, and neither does this one.
• Keep your own copy. Every Cubby app is an ordinary React/Vite TypeScript project, and every app database is a real Postgres database you can export any time. If something we do costs you data, that export is the safety net, and it is yours to run.
• Liability. To the fullest extent the law allows, we are not liable to you for lost data, lost access, lost business, or any indirect or consequential loss that comes from using early-access software. Paid plans exist (the pricing page lists them).

your apps and your users

• You own what you build. The code your chat deploys, the app it becomes, and the database behind it are yours. We hold them because serving your app requires it, under everything the privacy page promises, and we claim nothing in them.
• The provenance rule, same as everywhere: anything on cubbyapps.com is us; anything on cubby.pro is user-built. An app at a cubby.pro address is yours, in your name, and it speaks for you, not for Cubby.
• You are responsible for what your app does. What it collects, what it shows, who it emails, what it calls through a connection: that is your app's behaviour and your responsibility, including the law that applies to you and to the people whose data it holds.
• And for the people you share it with. The people you share an app with sign in with their own Cubby identity, and your app checks access itself. What they type into your app lands in your app's database, which belongs to your workspace. You are the one they are trusting; we are the infrastructure underneath.

what you may not do

The short list. Each of these is a reason for us to act under the next section.

• Anything unlawful. No content or use that breaks the law that applies to you, to the people using your app, or to us.
• Other people's data without a basis. Do not collect, store, or process personal data you have no right to hold, and do not put regulated data here: no PHI, no PCI-scope cardholder data, nothing that needs an attestation we do not have. The privacy page says the same thing, and means it.
• Abuse of other tenants or of the platform. No mining, no scanning or probing of other apps or of Cubby itself, no spam or bulk unsolicited mail, and no working around the quotas, the rate limits, or the egress allowlist. Your app can call what you granted it and nothing else; that rule is enforced at runtime, and trying to route around it is a violation on its own.
• Anything that puts the shared ground at risk. Every app on Cubby shares one cubby.pro zone, one Cloudflare account, and one Neon organization with every other app. Phishing from a cubby.pro address, malware, impersonating Cubby, or anything else that gets those shared accounts flagged, throttled, or shut off endangers every other person on the platform, and we treat it that way.

what we may do, and how

Three instruments exist today. This section describes them as they are, not as a bigger company would write them.

• Pause deploys for everyone while we look. There is one switch that stops every new deploy on the platform at once. Apps that are already running stay up; a deploy attempted while it is on is refused with the reason, and nothing is built or uploaded. It exists for incidents and abuse, and it comes off as soon as we have looked.
• Delete a workspace and its apps, on request or for cause. On request is the account deletion the privacy page describes: a human does it, promptly, and confirms when it is done. For cause is the same action, taken by us, when a workspace is the source of one of the violations above.
• Take one app's address down, by hand. Today this uses the same hold your own delete uses: the address stops answering, nothing is destroyed for 14 days, and you can restore the app from the dashboard's Deleted apps inside that hold. It is a removal, not a pause, because a per-app switch does not exist yet; if that changes, this page changes with it.
• Tell you why, by email, when we can. We cannot promise notice before acting, because the cases that need these instruments are usually the ones where waiting harms somebody else. We can promise a reason afterwards, at the address on your account, and a real reply when you answer it.
• What we do not do. We do not go through your app's database looking for violations. We act on what is reachable at a public address, on reports sent to us, and on what the platform itself records, which the privacy page lists in full.

data

Everything about your data lives on the privacy page, and that page is part of these terms: what we hold and why, the complete list of subprocessors, how long we keep it (including the hold after you delete an app), and your controls: export any time, delete an app yourself, delete your account by email. It is written to the same standard as this page. No sentence on it survives a release it is not true of.

changes and contact

Questions about these terms, reports of abuse on a cubby.pro address, and appeals of anything we did under the section above: security@cubbyapps.com. One mailbox, one person reading it, for security, privacy, and terms alike.

This page ships with the build and changes when the system changes. Each substantive revision is dated at the bottom; no silent edits. If you keep using Cubby after a change, you are agreeing to the page as changed. If you do not agree, stop using it and ask us to delete your account; the privacy page says how, and what happens next. These terms are governed by the laws of the State of California, and any dispute about them goes to the state or federal courts located in California.