Patchy Cloud Beta Terms
Last updated: November 10, 2026
These terms cover Patchy Cloud, the hosted service at cloud.patchyhq.com, together with the patchy command line tool and SDK, while it is in private beta. The patchyhq.com website and PatchPage have their own terms.
The short version: Patchy Cloud is a free beta, provided as it is, with no uptime promise. Your company keeps its rights in what it puts in. Our databases and file storage are in the United States. We do not sell your content and we do not train models on it. Your company is responsible for what its people, guests, agents and patches do, and defends us against the claims Liability lists. Either of us can end this at any time. Our liability is limited as described below, subject to applicable law.
How this agreement is put together
This page is the Cover Page, both Order Form and Key Terms, of an agreement between your company and Patchy. It incorporates the Common Paper Cloud Service Agreement Standard Terms, Version 2.1, which are part of this agreement as if they were written out here. Where this page and the Standard Terms disagree, this page wins. Capitalised words such as Customer Content and Prohibited Data mean what the Standard Terms say they mean.
Who agrees, and how
- Customer, or “you”, is the business or other legal person that a company on Patchy Cloud is created for. Provider, or “Patchy” and “we”, is Patchy, the team that operates Patchy Cloud from the United States.
- You accept these terms by ticking the box when you create your account. If we create an account for you, you accept them when you first use it. If you create a company on Patchy Cloud, that acceptance is for Customer, and you confirm that you have the authority to bind it. The day you create the company is the Effective Date, the Order Date and the Subscription Start Date.
- If you join a company someone else created, you agree to follow these terms as one of its Users.
- The beta is for companies based in the United States. By accepting, you confirm that yours is, and that you use Patchy Cloud for business and not for personal or household purposes.
What you get
- Cloud Service: Patchy Cloud. Your company publishes and runs patches, from a static page to a hosted tool, with their tables, files and connections. Software: the
patchycommand line tool and SDK. All of it is a Beta Product under Section 12.7 (Beta Products). - Fees: none during the beta. See Money below.
- Subscription Period: from the Subscription Start Date until you or we end it. It does not renew and it does not lock you in, so the automatic renewal in Section 5.1 does not apply.
- Technical Support: by email, as well as we can manage. We are a small team and promise no response time.
- Use Limitations: the limits the service enforces on sizes, rates and capacity, which we may change, and the rules under What you may not do.
It is a beta
Patchy Cloud is provided as it is. Features will change and some will go away. It may be slow or unavailable, and it may lose data. We make no promise about uptime or recovery.
Keep your own copy of anything you cannot afford to lose. Patchy Cloud should not be the only place an important record lives. Any database history we keep is for our own recovery. It does not cover stored files, and it is not a backup service for you.
Your content
- As between your company and Patchy, your company keeps its rights in its Customer Content, such as its patches, tables, files, descriptions, connection settings and company look. Section 1.5 (Customer Content) lets us use it to provide and maintain Patchy Cloud. We may also use it to secure and support Patchy Cloud, to comply with the law and to enforce this agreement.
- We may use patch names and descriptions, alongside the usage records the privacy notice describes, to understand what people build with Patchy Cloud and to improve it.
- Section 1.6 (Machine Learning) does not apply. We do not use Customer Content to train models, and we do not sell it.
- Sharing is your instruction to us. A patch shared with your company is open to every member of it. A patch shared with a guest is open to them, as themselves. A patch you make public is open to anyone with the link, at our address. Public is not confidential, and a copy someone has taken cannot be recalled.
- A guest is someone at another company with their own Patchy Cloud account. Everyone outside Patchy who creates one, or uses one we created for them, agrees to Patchy Cloud’s terms, so a guest has agreed to them too. Whom your company shares its patches with is its choice and its responsibility. A guest uses what is shared with them as one of your company’s Users, so your company is responsible for their use of it, as it is for its members’. We are not responsible for what a guest does with what they are shown, and ending a share cannot take back what they have already seen.
- Everyone in your company can build and publish, and your company’s admins can manage every patch. Patchy Cloud is built to keep each company’s content apart from every other company’s, except what a company shares. Inside your company, what a patch shows to whom, and what people’s AI agents can do in it, is decided by whoever built it. An agent reaches only the agent tools a patch’s builder added. Treat any source files your company publishes as visible to every member who can open the patch, whatever the patch itself shows them, and keep secrets out of those files.
- A patch may show your company’s member directory, meaning names and email addresses, to signed-in members of your company and to the guests it is shared with. A patch’s guests appear in its directory while it is shared with them.
Services you connect
An admin can connect services your company uses: Postgres databases, PostHog projects, Attio workspaces, email addresses on Pidgeon and mailboxes at your company’s email provider. Your company authorises us to reach each one with the credentials the admin gives us, and to carry out the requests its patches, members, their AI agents and its guests make, including the reads a builder’s agent makes while building a patch. Your company is responsible for having the rights and permissions this needs, for the access each credential grants and for what its patches ask for. Patches can use a connection for their guests too, unless an admin blocks guests from it. That setting is your company’s to manage, not a safeguard we promise.
They are your services. Each runs under your company’s own account and agreement with its provider, who may change, limit or end it. We do not guarantee that a connected service works, what it returns or that mail sent through it arrives, and we are not responsible for what its provider does with your company’s data. Your company pays any charges it agrees with those providers. Section 6.2 (From Customer) applies to the data in them as it does to Customer Content.
Email sent from your address. An admin chooses whether patches may only read a connected email address, or also send from it. If sending is allowed, any patch that uses the address can send and reply from it, and change the status and labels of its mail. Your company is responsible for every message its patches send from a connected address, including one that a member’s AI agent, a guest or a fault in a patch caused: what it says, who it goes to, the permissions it needs, and following Pidgeon’s rules and the laws on email that apply to it, such as CAN-SPAM. Sections 1.3 (User Accounts) and 1.5 (Customer Content) apply to it. We do not review mail before it goes out, and we may block mail or turn off sending to prevent abuse. Any limit or check on sending, such as a daily cap or mail held for approval, is part of how Patchy Cloud or Pidgeon works, may change, and is not a safeguard we promise.
We keep a log of the calls patches and builders’ agents make to these services, so that your company and we can see what ran. It can include query text, and the subject and recipients of email a patch sends.
People, machines and agents
- Your company is responsible for everything done through its Users’ accounts, its patches and the machine logins and agent connections its people make, including messages sent, changes made and what guests do in its patches. Section 1.3 (User Accounts) applies to all of it. Once a person logs a machine in, any agent on that machine can act as them. Once a person connects an AI agent, it can use your company’s patches as them, through the agent tools each patch’s builder added, but cannot publish.
- Your company is responsible for reviewing the code and output that AI produces for it, and for the actions it lets AI agents take.
- A person can revoke a machine or disconnect an agent at any time from Your agents. Deactivating a person ends all of theirs.
- Agent access is off until one of your admins turns it on, and an admin can turn it off at any time, which refuses every agent until it is back on. Turning it on is your company’s instruction to us to let each member connect AI agents that read and change what that member can, through the agent tools in your patches. Whether an agent asks before making a change is set in the agent, not by Patchy Cloud.
- The AI agents your people use may run on their computers or on their makers’ servers, and may send what they read or send through Patchy Cloud to their makers. If they do, the makers’ terms and the settings on your company’s or your people’s accounts with them, not these terms, govern how they keep and use it, including whether they train models on it.
What you may not do
On top of Section 2.1 (Restrictions on Customer), do not publish, run or send:
- illegal content, or content that helps someone break the law;
- phishing or impersonation, including pages that imitate a sign-in screen, a brand or a person, ours included;
- malware, or anything that tries to escape the sandbox, attack a viewer’s browser or get around a limit;
- spam, deceptive messages, or mail your company is not allowed to send;
- link farms or pages published mainly to move search ranking or traffic;
- harassment or hate aimed at a person or a group;
- other people’s private information that you have no right to publish;
- pages built to track their readers, for example by embedding remote images in order to profile whoever opens them;
- content that infringes someone else’s copyright, trademark or other rights;
- sexual content involving minors, in any form. We report it.
In addition to Section 2.2 (Suspension), we may take a patch down, turn off a connection or its sending, or suspend an account or your company, at any time, with or without notice. To report a patch, email us its address.
Data you must not put in
These rules cover data a patch reads from a connected service, such as your database, your CRM or an inbox, as well as anything you upload to Patchy Cloud. An inbox holds whatever people send it, so connect only an address that is not meant to receive such data.
- No Prohibited Data, as Section 3.2 says: health information covered by HIPAA, card or bank account numbers, social security, driver’s licence or other government ID numbers, and similar sensitive categories.
- No personal information about children.
- No personal data governed by the GDPR or UK GDPR. The beta is for the United States and we do not offer a data processing agreement during it. Patchy Cloud can connect services hosted outside the United States, such as a PostHog project in PostHog’s EU region, but making sure a connected service holds no such data is your company’s responsibility.
- No data that a law or contract requires to be kept on certified or audited systems. Patchy Cloud holds no security or compliance certifications, such as SOC 2, HIPAA or PCI DSS.
Ordinary business information about people, such as a customer contact list, is fine. Your company is responsible for having the right to store it and for telling those people what the law requires.
For that information we are your service provider. Where the California Consumer Privacy Act or a similar state law applies to your company, these are our commitments under it:
- Your company discloses it to us, and we process it, only to provide Patchy Cloud to you: hosting, serving, securing and supporting what your company builds.
- We do not sell or share it.
- We do not keep, use or disclose it for any other purpose or outside our relationship with you, and we do not combine it with personal information from elsewhere, except where that law lets a service provider do so.
- We follow that law and its regulations, give the information the same level of privacy protection they require of your company, and tell you promptly if we decide we no longer can.
- We help you comply with requests from the people the information describes, when you tell us about one.
- You may take reasonable steps to check that we handle it in a way consistent with your obligations under that law, and to stop and put right any use that is not.
- We may use service providers to help us process it, under the written contracts that law requires, and the privacy notice describes them. It also goes where your company directs, such as to the AI agents its members connect, to the guests it shares patches with or in the email its patches send, and where the law requires.
Where your data lives and who can reach it
Patchy Cloud keeps Customer Content in databases and file storage in the United States. The privacy notice lists the vendors we rely on, what each one handles and where. A few of them may process or store what reaches them in other countries. Some of them receive usage records that carry account ids, so that they can work for us. That is part of running the service, not a disclosure to others under Section 1.4 (Feedback and Usage Data). What your people’s AI agents read through Patchy Cloud goes wherever those agents, and any makers they send it to, process it.
The Patchy team can reach production in order to run it, and uses your company’s content as Your content says.
Money
Patchy Cloud is free during the beta, and we may end free access. Paid service needs your company’s agreement to separate paid terms.
Ending
- You can stop at any time. Email us to close your company.
- We may suspend or end the beta, your company’s access to it, or any patch or connection, at any time, with or without notice, subject to applicable law.
- Keep your own copies before your access ends. We may help with an export, but we do not promise one.
- After this agreement ends, if an admin asks, we delete your company’s Customer Content within 60 days, as Section 5.5 (Effect of Termination) says, subject to the retention Section 5.6(b) (Survival) and the law allow. What we keep under Section 5.6(b) stays protected as that section requires. Account and usage records are kept as the privacy notice describes.
These rights to end the agreement apply despite the fixed periods in Section 5 (Term & Termination).
Naming you
Section 12.8 (Logo Rights) applies: we may name your company and use its logo to say that it uses Patchy Cloud, including to investors and in fundraising materials. Apart from your company’s name and logo, we never share your content when we do, and any usage figures we give others follow Section 1.4, which means they are aggregated and identify nobody.
Liability
- General Cap Amount: US$100.
- Increased Claims: none.
- Unlimited Claims: claims against your company under Section 9.2 (Protection by Customer), or for intentional misuse of Patchy Cloud by your company or its Users. Claims against Patchy are not Unlimited Claims.
- Provider Covered Claims: none. We do not indemnify you.
- Customer Covered Claims: claims by others arising from your company’s Customer Content, the data in the services it connects, the messages its patches send, or unlawful use of Patchy Cloud by your company or its Users, except to the extent that our breach of this agreement or our own unlawful conduct caused them. Section 9.5(b) does not exclude a claim arising from your company’s or its Users’ unauthorised or unlawful use.
- Additional Warranties: none.
Despite Section 8.4 (Exceptions), Section 8.2 (Damages Waiver) applies to our breaches of Section 10 (Confidentiality). It does not limit Unlimited Claims.
Sections 7 (Disclaimer of Warranties), 8 (Limitation of Liability) and 9 (Indemnification) say the rest: no warranties beyond the ones written there; apart from Unlimited Claims, neither of us owes the other more than the General Cap Amount in total; and apart from Unlimited Claims and your company’s breaches of Section 10, neither of us owes the other for lost profits or indirect losses. None of this limits liability where the law does not allow it to be limited.
Changes to these terms
We may change these terms. We post each revision at its own address, under the date it prints. A revision applies to you, and to any company you create, when you accept it in Patchy Cloud. That is electronic acceptance under Section 12.2. We may require you to accept a revision to keep using Patchy Cloud.
This version applies at once to anyone who accepts it when they create their account, and to any company they create. If you accepted an earlier version, that version applies to you, and to any company you create, until you accept this one in Patchy Cloud.
Law, notices and who Patchy is
- Governing Law: the laws of the United States and of the state in which Patchy is established. Chosen Courts: the state and federal courts located in that state.
- Notice Address: for Patchy, allison@patchyhq.com. For you, the email addresses of your company’s admins on Patchy Cloud.
- Patchy may assign this agreement, by giving notice, to the company formed to operate Patchy Cloud. Section 6.1(b) applies to Patchy from the day that company exists.
Contact us
Questions, support, abuse reports and security reports all go to one place: email us.
The Standard Terms are the Common Paper Cloud Service Agreement, Version 2.1, by Common Paper, used under CC BY 4.0.