Terms of Service

Last updated: October 25, 2026

These Terms of Service (“Terms”) govern your use of Podclave, the service operated by Podclave LLC, a Florida limited liability company (“Podclave,” “we,” “us”), at podclave.com. By creating an account or using the service, you agree to these Terms. The service and these Terms can change as the product changes.

If you have questions, email us at hello@podclave.com.

1. What Podclave is

Podclave gives your team Worlds: prepared environments with your projects, tools, and shared context. Each member works in a personal Workspace, with agent chats, a terminal, and files available from a browser. Podclave supplies the compute through Vercel and keeps saved work when that compute parks or is replaced. Running services pause while compute is parked.

A Lab is your team and billing account. It can contain Worlds with different members and configuration. Section 7 describes plan and credit billing.

Podclave LLC is an independent company. We are not affiliated with, endorsed by, or sponsored by Anthropic, OpenAI, SpaceXAI, Google, GitHub, Atlassian, or Slack. We integrate with their platforms so their tools work in Podclave.

2. Worlds and Workspaces

A World Admin prepares the World and chooses who can enter. Members start personal Workspaces from its prepared environment. You do not need a separate compute-provider account.

  • Your Workspace and its chats are private to you. Other World members and World Admins cannot inspect them through Podclave.
  • Shared files are available to the World’s members. My files are private to you within that World. Putting content in Shared files or sending it to a connected service makes it available under that feature’s access rules.
  • A World connection can give members access to external content even if they do not have a personal account with that service. Admins must have authority to share that access and must choose members and permissions with care. Section 4 describes the supported connections.
  • Public URLs can expose an app to anyone with its link or limit access to permitted members, depending on the setting you choose. You are responsible for the app’s content, access controls, and handling of visitor data.
  • You are responsible for the programs you run and actions you ask agents to take. Agent settings and available credentials affect what an agent can do.
  • Removing a Workspace permanently removes its saved work. A Lab Admin can remove a World after its Workspaces are removed and its Drive connections are disconnected; removing it also removes its Shared files and members’ My files. Export anything you need before removal.

3. Accounts and membership

You sign in with an email address and a one-time code, optionally with a passkey. You are responsible for keeping access to your email account secure. Anyone who controls your email can sign in as you.

Lab Admins manage the team and billing. World Admins manage World access and configuration. Admins are responsible for whom they invite and the access they grant. Members can connect their own agent credentials or choose Lab-funded access where a World Admin permits it (see Section 4).

You must be at least 13 years old to use Podclave, or older where your country’s law sets a higher minimum age for online services (for example, 16 in some EEA countries). If you are under 18, you may use Podclave only as an invited member of a Lab whose admin is an adult — a parent, guardian, or teacher — who accepts these Terms on your behalf; minors cannot be the paying admin.

4. Connected providers

Personal credentials. Podclave can use credentials you connect — an Anthropic (Claude) sign-in, an OpenAI (Codex) sign-in or API key, a SpaceXAI (Grok) sign-in, and a GitHub authorization — so those tools arrive ready. This is optional and always your action: you complete the provider’s own sign-in or consent flow or enter your own key, and each teammate connects their own.

  • We store these credentials encrypted and use them only to make them available to your sessions, to keep them fresh where the provider supports refresh, to show your provider usage, and to give World members the read-only repository access you choose to share. See the Privacy Policy.
  • Your use of Claude, Codex, Grok, and GitHub through those credentials is governed by the respective provider’s terms, including any usage policies attached to your accounts there. We and our hosting providers process the credentials and service traffic needed to connect your sessions. Prompts, responses, and content you supply are processed by the agent provider you select.
  • You can disconnect at any time in Podclave, and/or revoke the grant at the provider (Claude settings, OpenAI settings, SpaceXAI account settings, or GitHub authorized applications).

Repositories. A World Admin can connect GitHub through a GitHub App installation or Bitbucket through repository access tokens, or share read-only access to selected repositories from their own GitHub or Bitbucket account. Every World member can then use those repositories within that access.

Lab-funded agents. Where a World Admin enables this option, a member can choose Lab funding instead of a personal agent subscription for a new Session. That choice remains fixed for the Session. We do not automatically switch a subscription Session to paid access. Lab-funded requests pass through Vercel AI Gateway and the model providers used to serve them. Turning off the World option blocks new paid requests; requests already in progress and provider access changes can take time to finish. Section 7 describes AI charges.

Google Drive. A World Admin can connect Google Shared Drives. For each one, Podclave creates a dedicated Google service account, and the Admin chooses its authority by adding it to the Shared Drive with a Google role. By connecting a Drive, the Admin confirms that they have authority to make that Drive available to the World and directs Podclave to process its data as described in the Privacy Policy.

Every World member can ask an agent to use the tools enabled by that Google role. Those tools can search names, metadata, and indexed content; read supported Google Docs; and, for a write-capable role, create files and edit Docs. Requested Drive content can be supplied to the member’s selected agent provider and can remain in the agent session’s runtime transcript. The Admin is responsible for choosing the correct members and Google role. Google remains the source of truth, and use of Google Drive is also governed by the customer’s agreement with Google.

Each member must use Drive tools only with an agent-provider plan that excludes general model training or after the member turns training off for that provider. A member must not submit a conversation that contains Drive data as provider feedback if the provider can use that feedback for model training.

A World Admin can disconnect a Drive in Podclave. This blocks new tool calls and deletes the dedicated Google service account and its credential. The Admin must then remove the deleted account from the Shared Drive member list. Disconnecting does not delete the customer’s Google Drive files.

Slack. A World Admin can connect a Slack app and bot to public channels intended for that World. The Admin must have authority to share those channels with the World’s members. Members can ask agents to read messages and threads, including members who do not have a personal Slack account. If the Admin enables posting, members can ask agents to send messages and replies as the bot. Requested content can reach the selected agent provider and remain in Session history or saved work. Slack’s terms and the workspace’s settings apply to content there. Disconnecting stops new reads and posts; it does not erase messages already posted or copies already returned to members.

5. Your content

Your code, files, repositories, and other content remain yours. These Terms do not transfer ownership to us or change any third party’s rights in content you use or in results your tools produce. Configuration you store in Podclave (settings and selected repositories) is also yours. We claim no ownership of any of it.

You grant us the limited rights needed to operate the service: to transmit, store, and display your content when you use a feature that requires it — for example streaming a file you upload or download, showing a directory listing, relaying your terminal or chat session, or writing the configuration you asked us to apply to a World or Workspace. We can also access it to secure the service, investigate abuse, enforce these Terms, comply with law, or provide support you request, as the Privacy Policy describes. We do not use your content to train machine-learning models.

You are responsible for your content: that you have the rights to it, and that it doesn’t break the law or these Terms.

6. Acceptable use

Don’t use Podclave to:

  • break the law, or store or distribute content you have no right to;
  • attack, probe, or disrupt the service, other users, or anyone else’s systems;
  • attempt to access another user’s account or Workspace;
  • circumvent our metering or billing;
  • resell or white-label the service without our written agreement.

Because Podclave hosts your compute, the programs you run are also subject to this section: use that harms the service, other users, or third parties — or that generates abuse complaints to us or our infrastructure providers — violates these Terms.

We may suspend or terminate accounts that violate this section. When practical, we will warn you first.

7. Fees and billing

Plans and credits. Light and Pro plans provide a prepaid credit allowance for your Lab’s Workspace compute. Each paid cycle includes an allowance valid for up to one calendar month. Usage varies with the compute your Workspaces use. Credits are not a fixed number of messages or hours. Unused credits expire at the end of the cycle and do not roll over. They belong to the Lab, are not transferable to another Lab, and cannot be redeemed for cash.

Prices, allowances, usage, and renewal dates are shown in billing and at checkout. Personal agent subscriptions and requests under your own API key remain separate and subject to your agreement with the agent provider. Existing agreed billing rates continue unless changed with the notice required by these Terms.

AI funds. A Lab Admin can buy AI funds, a prepaid US dollar balance that is separate from compute credits. AI funds pay the actual cost reported by our AI Gateway provider, with no Podclave AI markup. They do not expire at compute renewal. They belong to the Lab and cannot be transferred to another Lab or redeemed for cash. Compute does not use them. Stripe shows sales tax before payment; the purchase adds its stated AI funds amount after payment is confirmed. Empty AI funds pause new Lab-funded AI requests. Funded compute, terminal, files, and chats under your own agent subscription remain available.

New Lab-funded AI requests need AI funds. After a Lab starts its first AI funds purchase, Lab-funded AI uses only AI funds, even if that payment is not completed. Compute renewal permission does not authorize AI purchases.

Automatic AI purchases. These are optional and off by default. A Lab Admin selects a threshold, a target balance, and a monthly limit, and accepts the charge terms. The Admin saves a card on Stripe through a $0 monthly subscription; that subscription adds no funds. When available AI funds are below the threshold, you authorize a charge that restores the target balance, plus applicable tax. A purchase can occur as soon as the setting is saved. Automatic charges in one calendar month (UTC), including tax, stay within the limit. If the next charge does not fit, a smaller purchase of at least $10 can occur; otherwise automatic purchases pause until the next month. A failed payment pauses automatic purchases until the Admin pays or cancels it and saves the settings again. Manual purchases do not count toward the limit. An Admin can turn automatic purchases off at any time; a payment already sent can still complete. A Lab Admin changes the card on Stripe’s hosted page, where Link’s terms apply; after a failed payment, Stripe can retry it on the new card. Canceling the card agreement on Stripe or Link, including at the end of a billing period, stops new automatic purchases at once.

If a Lab without AI funds has earlier Lab-funded Sessions, their AI use is paid from compute credits at their recorded purchase value. Reports show AI charges in dollars, earlier charges in credits, and provider cost. Reports can be delayed, so recent AI use can reduce the balance later. Personal subscription use does not reduce the Lab’s AI balance.

Renewal and plan changes. Your subscription renews at its scheduled date unless canceled. An upgrade can take effect immediately, with a prorated charge and corresponding additional allowance for the time left. A downgrade applies to the next paid cycle. Cancellation takes effect at the current paid period’s end and prevents early renewal.

If credits run out before the scheduled renewal, a Lab Admin can renew early and pay for a new cycle. Automatic early renewal is optional and off by default. If an Admin enables it, you authorize a new cycle charge each time compute credits reach zero. You can change or disable it in billing. A new paid cycle starts only after payment is confirmed. An early renewal starts a new one-month cycle, and the next renewal date becomes one calendar month after that payment.

Compute and stored work. When credits run out, compute pauses and new compute cannot start. An in-progress renewal payment can briefly keep already running compute available. Running out early does not end the paid storage period: saved Workspace work remains through the scheduled period end. You can renew early or wait for the scheduled renewal, then resume with available credits.

If the paid period ends without a completed renewal, compute stays paused and stored Workspace work enters a seven-day grace period. This grace does not start merely because credits ran out early. Payment during grace restores eligibility to resume. After grace, we may delete the stored Workspace work; continued retention is not guaranteed. Keep independent copies of important work. The Privacy Policy describes other retention and deletion rules.

Stripe handles payment and acts as merchant of record for Worlds plans and AI funds bought in Podclave. The Refund & Cancellation Policy is part of these Terms. We will give at least 30 days’ notice by email or in the product before a price increase takes effect for you. Charges already incurred are not repriced.

8. Termination

You can stop using Podclave at any time. Cancel your subscription to stop future renewals; removing a Workspace alone does not cancel the subscription. To request account and data deletion, email hello@podclave.com. We will delete the service data described in the Privacy Policy, including your private Workspace work. Retrieve anything you want to keep before requesting deletion. Content you shared with others may remain under the receiving service’s rules.

We may suspend or terminate your access if you materially violate these Terms, if we are required to by law, or if we discontinue the service. If we discontinue the service or terminate without cause, we will give you reasonable advance notice and a chance to retrieve your data before deletion, and refund any prepaid fees covering the period after termination.

9. Service changes and availability

Features may change, improve, or be removed; we will not remove a capability you pay for without notice. The service depends on platforms we do not control — our infrastructure and hosting providers, Anthropic, OpenAI, SpaceXAI, Google, GitHub, Atlassian, and Slack — and an outage or change on their side can degrade or break features on ours. We do not promise any particular uptime, and we do not offer an SLA.

10. Disclaimers

The service is provided “as is” and “as available”, without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. The Privacy Policy describes our security measures, but no system is perfectly secure. We do not warrant that the service will be uninterrupted, error-free, or free of vulnerabilities, or that it will preserve any particular content.

Saved Workspace state supports return between Sessions. It is not a separate backup service or file-version history. Keep code in version control and independent copies of important files. Review agent results and actions before you rely on them.

11. Limitation of liability

To the maximum extent permitted by law, Podclave LLC will not be liable for any indirect, incidental, special, consequential, or punitive damages, or any loss of profits, revenue, data, or goodwill, arising out of or related to the service — even if we have been advised of the possibility.

To the same extent, our total liability for all claims arising out of or related to the service is capped at the greater of (a) the amounts you paid us in the 12 months before the claim arose, or (b) $100.

Some jurisdictions do not allow certain limitations, so parts of this section may not apply to you.

12. Indemnification

If your content or your use of the service in violation of these Terms causes a third-party claim against us, you agree to defend and indemnify Podclave LLC against the resulting damages, liabilities, and reasonable legal costs.

13. Governing law and disputes

These Terms are governed by the laws of the State of Florida, without regard to conflict-of-laws rules. Courts located in Florida have exclusive jurisdiction over disputes arising from these Terms or the service, and both sides consent to venue there. Before filing a claim, email us so we can try to resolve it.

14. Changes to these Terms

We may update these Terms as the product and the law evolve. The “Last updated” date above always reflects the current version, and prior versions are available on request. For material changes we will notify you — by email or prominently in the product — before they take effect. Continuing to use the service after a change takes effect means you accept the updated Terms.

15. Miscellany

These Terms, the Privacy Policy, the Refund & Cancellation Policy, and the Cookie Policy are the entire agreement between you and Podclave LLC about the service. If a provision is found unenforceable, the rest remain in effect. We may assign this agreement in connection with a merger, acquisition, or sale of assets; you may not assign it without our consent. Our failure to enforce a provision is not a waiver. Claude, Anthropic, Codex, OpenAI, Grok, SpaceXAI, Google Drive, Google, GitHub, Bitbucket, Atlassian, and Slack are trademarks of their respective owners; their mention here describes interoperability, not endorsement.

Podclave LLC · Florida, USA · hello@podclave.com

© 2026 Podclave LLC · Operated by Podclave LLC, a Florida limited liability company · hello@podclave.com