Terms of Service

These terms are between you and Teamable ("we", "us") and cover teamable.dev, api.teamable.dev and everything served from them (the "Service"). By creating an account you agree to them. They are written to be read; if a court finds a part unenforceable, the rest stands.

1. What the Service is

Teamable lets groups of people ("crews") work on a software build together, pool their own AI provider API keys, and route requests to AI providers through our gateway. We are not an AI provider. Every model reply comes from a third party — Anthropic, OpenAI, Google and others — under that provider's own terms, which you also agree to when you use a key for it.

2. Your account

• You must be at least 16, and old enough to form a binding contract where you live.
• Keep your password and session to yourself. Everything done with your account is on you until you tell us it was compromised.
• One person, one account. Crews are groups of accounts, not shared logins.
• You can delete your account at any time from Settings. Builds you own that still have other people in them must be transferred or deleted first, so nobody else's work disappears with you.

3. Your API keys

This is the part that matters most, so it is spelled out.

• Vault mode. You give us a copy of a provider key. We encrypt it (AES-GCM) with a key that lives only in our runtime's secret store and never in the database. The decrypted key exists in memory only for the duration of a request you or your crew made, and is never written to logs, returned by any endpoint, or shown to anyone — including our staff.
• On-device mode. The key stays in your browser. We never receive it. Your browser calls the provider directly and reports the call to us afterwards for your own records.
• Pooling. A vault key is only used on a build after you grant it there, only for work in that build, never more than the daily cap you set, and fair-shared with the crew's other keys. We email you the first time each crew uses it. You can see every request made with it and revoke it in one click; revoking wipes our encrypted copy.
• Your money. Calls made on your key are billed to you by the provider. We meter and show you an estimate, but the provider's invoice is the truth. Set caps you can live with.
• You are responsible for having the right to use any key you add. Do not add keys that belong to your employer, a client, or anyone else without their permission.

4. Credits, plans and payment

• Public, invite-only and application builds are free. Paid plans buy private builds, larger crews and platform compute credits. Prices are on the pricing page and may change with 30 days' notice for existing subscribers.
• A credit buys one AI turn on our provider keys. Work on a key you or your crew pooled costs zero credits. Credits expire as described on the pricing page; top-up packs do not expire.
• Payments are processed by Stripe. We never see your card number.
• Refunds. Ask within 14 days of a first subscription payment and we refund it, no questions. Renewals and top-ups are refundable at our discretion where nothing was consumed. Email support@teamable.dev.
• If a payment fails your plan keeps working while Stripe retries. If it cannot be collected, the plan lapses to free; your builds are not deleted, but private builds beyond the free limit become read-only until you upgrade again or make them public.

5. Sparks

Sparks are reputation inside a crew: attribution, vote weight, priority on the pooled-key queue. They have no cash value, are not redeemable, transferable, or purchasable, and we may recalculate or reset them to correct abuse. Nothing on Teamable pays users; if a crew ever monetises a build, that is negotiated by humans, off-platform.

6. Content and code

• What you and your crew create is yours. You give us only the licence needed to store it, show it to the people your build's access mode allows, and send it to the AI providers you route to.
• Model outputs are provided as-is. Check them. We make no promise that generated code is correct, secure, or free of third-party rights.
• Public and application builds are visible to anyone. A private build is visible only to its crew; our staff can see that it exists, its title and its audit log — enough to act on an abuse report — and nothing inside it.

7. Acceptable use

Don't use the Service to break the law, to violate a provider's usage policy, to attack or scrape other people's builds, to spam applications or invites, or to harm other users. Don't pool a key you don't own. Don't try to extract another member's key or credits. We may remove content, suspend accounts, or take down builds that do, and we log every such action.

8. Availability and changes

The Service is provided as-is. We aim for it to be up and will tell you about planned downtime, but we do not guarantee uptime, and provider outages are outside our control. We may change or end features with reasonable notice; if we end a paid feature, we refund the unused part of your period.

9. Liability

To the extent the law allows, we are not liable for indirect or consequential loss, and our total liability to you in any twelve months is the amount you paid us in that period, or $50, whichever is greater. Nothing here limits liability that cannot be limited by law.

10. Ending these terms

You can leave whenever you like. We can suspend or end your account for breaking these terms, with an explanation, and we will let you export your data first unless doing so would be unlawful.

11. Contact

support@teamable.dev. Questions about these terms get a human reply.