Terms of service
Effective 29 July 2026 · mddb Orbit
These terms govern mddb Orbit, the hosted sync service at
app.mddb.cc and api.mddb.cc. Using the service means accepting them.
If you do not, the same product runs on your own hardware — see below.
1. The software and the service are separate things
The mddb source is open: the CLI, the sync engine, the harness adapters and the shared contracts under Apache 2.0, and the server and dashboard under AGPL 3.0. Those licences govern the software and are not narrowed by anything on this page. These terms govern only the hosted service we operate for you. Running your own server is a supported alternative, and nothing here restricts it.
2. Your account
- You need a working email address; that address is your identity, and you are responsible for keeping access to it.
- You must be at least 16 years old.
- Each machine you enrol receives its own device token stored in
~/.mddb/device.json. Treat it as a credential: anyone holding it can act as that machine. Revoke a machine you no longer control from the dashboard. - You are responsible for what happens under your account, including what your machines push.
3. Acceptable use
Do not use the service to:
- store or distribute anything illegal where you are, or content you have no right to;
- distribute malware — including config that is executable, such as an MCP server command or a vault command source, aimed at machines that are not yours;
- probe, overload or circumvent the service's limits, rate limits or authentication, or access a workspace that is not yours;
- resell the hosted service, or operate it as a backend for your own product, without a written arrangement — self-hosting under the AGPL is the path for that;
- deliberately push secret values. The product scans for them and refuses them on both sides, and working around that scan is a breach of these terms as well as a bad idea.
4. Your content stays yours
The instructions, skills, MCP definitions, subagents and vault references you sync remain yours. You grant us only what running the service requires: to store them, transmit them between your machines, keep the version history the product is built around, and display them back to you in the dashboard. That permission ends when you delete the content or the account.
We do not sell your content, do not share it beyond the processors listed in the privacy policy, and do not use it to train models.
5. Plans, limits and billing
- The free plan is free and stays free, within its device, profile and history limits. Plan limits are enforced by the service, not by trust.
- Paid plans are being rolled out. Before your account is ever charged you will be shown the price and the billing cycle and will have to confirm — no plan converts to paid on its own.
- Payments are processed by Dodo Payments as merchant of record. Their checkout and their terms apply to the payment itself; card details never reach us.
- Subscriptions renew for the period you chose until you cancel. Cancel any time; access continues to the end of the paid period and no fee is refunded pro-rata unless the law where you live says otherwise.
- If a payment fails, the plan enters a grace period and you are emailed before anything is restricted. Dropping to a smaller plan means its limits apply — for example, history shortens to that plan's window.
- Prices shown on the site are current-beta prices and can change. A change never applies to a period you have already paid for, and you get notice by email before it applies to the next one.
6. Availability, and what you should still keep
This is a beta service run by a small team. We aim to keep it up and to warn you about planned interruptions, but there is no uptime SLA on the free and standard plans; an SLA is part of a custom (Galaxy) arrangement.
mddb syncs your configs — it is not their only copy. Every managed file also lives on your
machines, and mddb export gives you a full dump on demand. Take one before anything
you consider irreversible. We keep backups of the service database, but the copy you control is
the one that owes you nothing.
Features can change during beta. Removing something you rely on is not done quietly: material removals are announced to account holders by email.
7. Suspension and termination
You can leave at any time by deleting the account from the dashboard — the deletion takes an emailed code, then removes the workspace after a 7-day grace window during which signing in cancels it.
We may suspend or terminate an account that breaches section 3, that puts the service or other users at risk, or that we are legally required to act on. Except where the breach makes it impossible, we tell you why and give you a chance to export first.
8. Disclaimer and liability
The service is provided as is, without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose and non-infringement. We do not warrant that it will be uninterrupted or error-free.
To the extent the law allows: we are not liable for indirect, incidental, special or consequential damages, nor for lost profits or lost data, and our total liability for any claim is capped at what you paid us in the 12 months before the claim arose. Nothing here limits liability that cannot lawfully be limited — including liability for fraud, or for death or personal injury caused by negligence — and if you are a consumer, your statutory rights are untouched.
9. Changes to these terms
The effective date at the top is the version in force. Material changes are emailed to account holders before they take effect; continuing to use the service afterwards means accepting them. If you would rather not, delete the account — the export is yours either way.
10. Contact and disputes
mddb is operated by the developer behind mddb.cc. Reach us at support@mddb.cc — including about anything on this page. If something goes wrong, write first: nearly everything is settled faster by email than by anyone's legal department, and we would rather fix it than argue about it.