Legal

Terms of Service

The agreement between you and Jiayang Cloud for using the platform. Written to be read; if a section is unclear, ask us and we will fix the wording.

Last updated 1 November 2026

These terms take effect on 1 November 2026. Until then, the terms dated 24 September 2026 apply.

1. Who we are, and what these terms cover

Jia Yang Inc., trading as Jiayang Cloud (we, us), runs the platform at jiayang.cloud: the dashboard at app.jiayang.cloud, the API, the command-line tool, the SDKs, and the apps our customers deploy, which are served under jiayang-apps.cloud (together, the Service).

These terms apply to everyone who creates an account, owns or belongs to a workspace, deploys an app, or uses a bearer token issued by the Service (you). If you use the Service for a company or another organisation, you confirm you can bind it to these terms, and you means that organisation.

People who only visit an app someone deployed on the Service are governed by that app owner's own terms. Our Privacy Policy explains what we process about them at the door.

The Privacy Policy, the Data Processing Addendum, the Refund Policy and the plan table are part of these terms. Where they conflict, the DPA wins for personal data and these terms win for everything else.

2. Your account

You sign in with a code we email you. There is no password. That means:

• Whoever controls your mailbox controls your account. Keep it protected, and tell us at once if you lose control of it.
• You are responsible for what is done through your account and through any bearer token you create, until you revoke it. Treat tokens as secrets; never put one in code or a shared document.
• You must give a working email address that you are entitled to use, and keep it current.

You must be at least 18 and able to enter a contract. The Service is built for businesses and professional use; it is not for children.

One person may have one account. You may not sign up on behalf of someone who is not allowed to use the Service, or use the Service after we have closed your account.

3. Workspaces, members and sharing

Everything on the Service lives in a workspace. A workspace has an owner, may have other members, and is the unit a plan applies to.

• The owner is responsible for the workspace: its plan and payment, its members, its apps and what they do, and for accepting these terms on behalf of the organisation the workspace belongs to.
• Members act under the workspace's plan and these terms. The owner can add and remove them at any time; removal takes effect within a minute, including for open sessions.
• Sharing an app with someone by email gives that person access to that app, not to the workspace. Every request they make is logged with their identity. You decide who gets access, so you are responsible for that decision and for telling them what the app does with their data.
• Public paths open part of an app to anyone. The app is responsible for whatever arrives there. On a path with a webhook verifier, the platform checks the provider's signature before the app sees a delivery, with the signing secret you set on that path; on any other public path, checking a sender's signature is the app's job.

4. Acceptable use

You may use the Service to build, deploy and share software that is yours to run. You may not use it, or let anyone use it through you, to:

• break the law, or help anyone break it, including hosting or distributing content that is illegal where you are, where we are, or where the person you share it with is;
• infringe anyone's copyright, trademark, privacy or other rights;
• host or distribute malware, phishing pages, credential harvesters, or anything designed to deceive people about who runs it;
• mine cryptocurrency, run proof-of-work, or otherwise use the Service mainly as compute for its own sake;
• run an open proxy, VPN endpoint, Tor relay, scraper farm, or anything whose purpose is to relay other people's traffic, hide its origin, or route around another service's limits;
• send unsolicited bulk email or messages, or host the infrastructure for it;
• attack, probe, overload or interfere with the Service, another customer's workspace, or any third party, including trying to reach an app other than through its address and the door we put in front of it;
• get around a plan limit, a suspension, or a security control, or share an account to do so;
• harass, threaten or abuse anyone, including our staff;
• resell the Service as a hosting product without a written agreement with us.

Security research on the Service itself is welcome within the rules on the Security page.

If we believe an app or a workspace breaks this section we may take it offline first and tell you afterwards, because some of these cause harm by the minute. See section 9.

5. Your apps and your content

Everything you deploy, store or send through the Service (code, files, databases, environment values, the data your apps hold) is yours (your content). We claim no rights in it.

You give us permission to host, copy, run, transmit and back up your content, and to show it to the people you have shared it with, to the extent needed to provide the Service. That permission ends when the content is deleted, subject to the backup periods in the Privacy Policy.

You are responsible for your content: that you have the right to use it, that it complies with section 4, and that your apps do what you tell their users they do. We don't review apps before they go live and we don't read what they store; what the platform records about each request is the audit log described in the Privacy Policy, and, where a webhook provider signs the time it sent a delivery to a verified public path, a hash of that delivery's signature, kept so that a replayed copy can be refused and deleted within an hour.

Your apps must verify the signed identity the edge passes them if they rely on knowing who is calling. Trusting an unsigned header is a defect in the app, not in the Service.

6. Plans, payment and billing

The plans, their prices and their limits are on the pricing page, which is part of these terms. In short: Free costs nothing, Team is US$49 per workspace per month and Business is US$199 per workspace per month.

• Billing is monthly, in US dollars, per workspace, through Stripe. By starting a paid plan you authorise Stripe to charge your payment method each month until you cancel. We never see or store your card number, and we store no invoice amounts: your invoices and receipts are in Stripe's customer portal, which the workspace's Billing tab opens.
• Tax. Prices exclude tax. VAT, GST or sales tax is added at checkout where it applies, based on the billing details you give Stripe; keep them accurate. Enter your VAT, GST or tax ID at checkout for reverse charge.
• Included requests and overage. Each plan includes a number of requests. On Team and Business these are the requests the edge admits to your apps for a signed-in person or a bypass token; public-path traffic is not counted toward them, and anonymous requests to a public path are rate-limited per client instead. On Team and Business the allowance is per billing period, the month each invoice covers, and the count starts again with each period; on Free it is per calendar month, in UTC.
• Free. Free is never charged. A Free workspace that reaches twice its request allowance, or its limit on database rows read or its limit on database rows written, stops serving requests for the rest of the month (the edge answers 402). Every request the edge passes to its apps counts toward the request limit, including anonymous requests to a public path and webhook deliveries. The count is of usage while the workspace was on Free, so for a workspace that has just come onto Free the count starts from the hour the change takes effect: the end of the paid period after a cancellation or a downgrade, or the end of the two weeks of retries after a failed payment. We measure database rows from Cloudflare's analytics; if we can't measure a Free workspace's database rows for two hours, its apps that have a database answer 402 until we can.
• Team and Business workspaces don't stop serving because they use more requests than their allowance: requests past it are metered at US$3.50 per million and charged on the invoice for that period. They can stop serving for the database limit below.
• Limits on each request. Every request can use at most the CPU time its plan allows (50, 100 or 150 milliseconds) and make at most 50 subrequests (fetches and other calls, as Cloudflare counts them), and is stopped past either.
• Database storage. Your apps' databases count toward the plan's storage, and each plan also limits their total: 1 GB on Free, 2 GB on Team and 10 GB on Business. We measure databases every few minutes rather than stopping each write, so a database can go past the limit before its apps are paused: usually by what it writes in about ten minutes, and for longer when Cloudflare's analytics are unavailable. Once a workspace's databases are over its limit, its apps that have a database answer only the workspace's owners and admins (everyone else gets 507), and nothing new can be deployed. That access for owners and admins ends, and those apps answer no one, if the databases grow further or reach 10% over the limit. To get back under, delete rows through the app or with jiayang db exec, export data and remove it, or upgrade. On Free, or while a workspace's payments have lapsed, a workspace still over its limit after 7 days is suspended under section 9; if it is still over 30 days after that, we delete its largest databases until it is under, after emailing its owners 7 days and 1 day before. Export first.
• Other limits (apps, members, tokens, storage and the rest) are enforced when you create something, except database storage and the limits on each request, described above. You will be told which limit you hit and which plan lifts it. Container apps run on Team and Business only; a container app in a workspace on Free does not answer requests, and a container app cannot be deployed to a Free workspace.
• Plan changes are made on the workspace's Billing tab. Upgrades take effect once they are paid for: the difference for the rest of the current period is charged immediately, pro rata, and if that payment fails or needs your confirmation the upgrade waits on it for up to 23 hours and then lapses, leaving the plan as it was. The new plan's request allowance starts from the moment the upgrade takes effect; the requests served before it count against the old plan's allowance and are billed at the old plan's price. Downgrades take effect at the end of the paid period, at your renewal; until then the workspace keeps the higher plan, and you can undo the pending downgrade. A downgrade isn't made while the workspace's databases are over the lower plan's database limit. The renewal invoice is at the new price. Audit events older than the new plan's retention are deleted 30 days after the change; export first.
• Failed payments. If a payment fails we retry for up to two weeks and Stripe emails you each time; then the workspace moves to Free, container apps stop, and everything else keeps running within Free's limits: nothing already deployed is removed, but nothing that would exceed a Free limit can be created until you are paying again. The platform emails the workspace's owners three days before the move, and again when it happens.
• Disputes. If you dispute a correct charge with your card issuer, the workspace is suspended under section 9 while the dispute is open. The suspension is lifted if the dispute is decided in our favour; if it is decided in yours, it stays until you write to us and the charge is settled. Write to us first; a mistake on our side is refunded without argument.
• Price changes. We may change prices with at least 30 days' notice by email to the workspace owner. The new price applies from the first renewal after the notice period. If you don't want to pay it, cancel before then.

You are responsible for the fees of every workspace you own, whether or not you used it that month.

7. Cancellation and refunds

You can cancel a paid plan at any time from Stripe's customer portal, which the workspace's Billing tab opens. Cancellation takes effect at the end of the current paid period; until then the plan stays as it is. The workspace then goes back to Free: container apps stop, everything else keeps running within Free's limits, and nothing is deleted except audit events older than Free's retention, which are deleted 30 days after the change; export first. There is no further monthly charge; requests past the allowance in the final period are billed on that period's invoice, up to the last hour we were able to report.

Deleting a workspace on a paid plan cancels its subscription at once; the rest of the period is not refunded (section 10). There is no further monthly charge; requests past the allowance in the final period are billed on that period's invoice, up to the last hour we were able to report.

Fees are not refunded for a partial period, an unused period, or a workspace you forgot about, except where the law where you live gives you a right to a refund that cannot be excluded, and except for our own billing mistakes, which we always correct. The Refund Policy has the detail.

8. Availability and support

We aim to keep the Service running continuously and we publish incidents at jiayang.cloud/status. But:

• Free and Team come with no availability commitment. We do our best; we don't promise a percentage, and downtime doesn't entitle you to a credit.
• Business gets priority support. An availability commitment with service credits is available for Business workspaces by separate written agreement; ask support@jiayang.cloud.
• We may take the Service down for maintenance. Where we can plan it, we announce it in advance on the status page.
• The Service runs on Cloudflare and other providers listed on the Subprocessors page. When one of them has an outage, so do we.

Support is by email; what each plan gets is on the Support page.

9. Suspension and termination

By you. You can delete an app, a workspace or your account at any time from the dashboard. Deleting a workspace on a paid plan cancels its subscription at once, with no refund for the rest of the period, and then proceeds; the confirmation dialog says so. Deletion is immediate and permanent (section 10).

By us. We may suspend a workspace, an app or an account, or end this agreement, if:

• you break section 4, or we reasonably believe you have;
• a charge is disputed with your card issuer (a chargeback): the workspace is suspended when the dispute is opened, and the suspension is lifted if the dispute is decided in our favour;
• a court, regulator or law requires it, or continuing would expose us to legal risk;
• an app is being used to attack us or someone else, or is compromised;
• a workspace's databases stay over its plan's database limit (section 6) for 7 days, on Free or while its payments have lapsed;
• we stop offering the Service, with at least 90 days' notice.

Where it is safe to, we contact you first and give you a chance to fix the problem. Where it isn't (an active attack, illegal content, a compromised token), we act first and tell you as soon as we can. Whatever the reason, the platform emails the workspace's owners when it is suspended. A suspended workspace's apps answer 403, the third-party credentials it holds are not attached to any request, and nothing can be deployed or changed in it (new apps, deploys, rollbacks, tokens, environment variables, secrets, public paths, uploads) while it is suspended. The dashboard, billing and the workspace export stay available, and the workspace can still be deleted, so that the matter can be resolved; the data stays where it is until the matter is resolved or the workspace is deleted under section 10.

10. Your data when it ends

Before deleting anything, export it. On every plan, the workspace export is one JSON document: the workspace's configuration, its members, its sharing grants, the names of its tokens, secrets and environment variables (never a value), and the audit log the plan retains. Each app's database can be exported on its own, as SQL, from the dashboard or with the CLI (jiayang db export). A static site is the files you uploaded. Databases over a Free workspace's limit may be deleted as section 6 describes.

Deleting an app or a workspace is immediate and permanent. Its scripts, databases, containers and files are removed from Cloudflare right away, its tokens are revoked, and it disappears from the dashboard, the API and the CLI. A deleted app's configuration, versions, sharing grants, tokens, secrets and environment variables go at once. Its entries in the workspace's audit log, the one recording the deletion among them, stay for the plan's audit retention like any other entry, and go with the workspace. Only the control plane's own records of a deleted workspace linger, for 30 days, for accounting, and they are never restorable: we cannot undo a deletion, whether or not it was a mistake. Backups of the control-plane database age out on the schedule in the Privacy Policy and are not used to restore deleted workspaces.

Deleting your account removes your memberships and sessions and the account itself. It is refused only while you are the only owner of a workspace or of an app: delete it, or make someone else an owner, first.

Sections 5 (your content, for the licence to keep backups), 13, 15, 16, 17, 19 and 20 survive the end of this agreement.

11. Privacy and data protection

How we handle personal data is in the Privacy Policy. Where you use the Service to process personal data about other people (which you do the moment you share an app with someone, and whenever an app stores data about its users), you are the controller and we are your processor, on the terms of the Data Processing Addendum, which applies automatically to every workspace.

The providers we rely on, and where they run, are on the Subprocessors page. We tell workspace owners 30 days before we add one.

12. Third-party services

Your apps may call other services, and the Service can hold those services' credentials for you and add them to your app's outgoing requests. Those services have their own terms; we are not a party to them, and we are not responsible for what they do with your requests. Keep the credentials you give us within what those services allow.

The open-source SDKs under sdks/ are licensed under the Apache License 2.0, and that licence, not these terms, governs your use of them.

13. Intellectual property

The Service (its software, design, documentation and name) belongs to us and our licensors. These terms give you the right to use it while the agreement lasts, and nothing more. You may not copy it, reverse engineer it except where the law allows, or use our name or logo to suggest we endorse your apps.

If you send us ideas or feedback, we may use them without owing you anything. We won't say they came from you unless you ask.

14. Early and experimental features

A feature we label as early, beta, preview or experimental may change or disappear without notice, may have bugs, and comes with none of the commitments in section 8. Use it on that understanding.

15. Warranties and disclaimers

We warrant that we will provide the Service with reasonable skill and care. Beyond that, and as far as the law allows, the Service is provided as is. We don't promise it will be uninterrupted, error-free, or suitable for a particular purpose, or that it will keep your content safe from every possible loss. Keep your own copies of anything you can't afford to lose.

Nothing in these terms limits a right you have as a consumer that cannot be limited by contract.

16. Limitation of liability

Neither of us excludes liability for death or personal injury caused by negligence, for fraud, or for anything else the law says can't be excluded.

Otherwise, and as far as the law allows:

• Neither of us is liable to the other for indirect or consequential loss, lost profits, lost revenue, lost data (except as set out in the DPA), or loss of business, however it arises.
• Our total liability to you under or in connection with this agreement, in any 12-month period, is capped at the fees you paid us for the affected workspace in that period, or US$100 if you paid nothing.

These limits reflect the price of the Service; they are the reason we can offer a Free plan at all.

17. Indemnity

You will cover us against claims, damages and reasonable costs that arise from your content, your apps, the people you shared them with, or your breach of section 4, for example a copyright claim over something an app of yours served, or a complaint from someone whose data an app of yours mishandled. We will tell you about any such claim promptly, let you run the defence if you want to, and not settle it without your agreement unless you stop responding.

18. Changes

To the Service. We change the Service continuously. We won't remove a capability your paid plan depends on without at least 30 days' notice, except where we have to for security or legal reasons.

To these terms. When we change these terms in a way that matters, we email workspace owners at least 30 days before the change takes effect, and the dashboard asks you to accept the new version the next time you sign in. You can accept a new version as soon as it is published, before it takes effect, and then you won't be asked again on the day. Corrections and clarifications that don't change your rights take effect when published. The date at the top is the version; the current version is always at jiayang.cloud/terms. If you don't accept a change, stop using the Service before it takes effect and cancel any paid plan; we will refund any month you paid for and can no longer use.

19. Governing law and disputes

These terms are governed by the laws of Delaware, with the courts of Delaware having exclusive jurisdiction over any dispute, without regard to conflict-of-law rules, except that either of us may seek an injunction anywhere to protect intellectual property or confidential information, and except that a consumer keeps the protection of the mandatory law where they live.

Before either of us starts proceedings, we agree to try to resolve the dispute by writing to the other and talking it through for at least 30 days.

20. General

• Entire agreement. These terms and the documents they include are the whole agreement between us about the Service, and replace anything said earlier.
• Assignment. You may not transfer this agreement without our written consent. We may transfer it to a successor of our business, and will tell you if we do.
• Severability. If a part of these terms is unenforceable, the rest still applies, and the part is replaced with the closest enforceable version.
• Waiver. Not enforcing a term once doesn't mean we won't later.
• Force majeure. Neither of us is liable for a failure caused by something outside our reasonable control, such as a provider outage, a network attack we could not reasonably have prevented, or a natural disaster. Paying is not excused by this.
• Notices. We send notices by email to every owner of the workspace. The platform sends some by itself, when they are due: a payment still failing three days before the workspace would move to Free, and the move itself; a Free workspace passing its request allowance, and its apps stopping at twice the allowance; a suspension; and a plan change that means older audit-log entries will be deleted, with the date they go; a Free workspace passing its database rows allowances, and its apps stopping at its limits; a Free workspace's database rows that can't be measured; a workspace's databases nearing, reaching and going back under its database limit, and the end of owners' and admins' access to its apps when they grow further; a suspension or deletion scheduled for being over the database limit, 7 days and 1 day before; and a downgrade or cancellation that will put the workspace's databases over the new plan's limit, 7 days and 1 day before the renewal; and new limits, with the workspace's own figures, before they take effect. The rest we write and send ourselves, including notice of a change to the prices, these terms, the Privacy Policy or the subprocessors, and of a personal data breach. Send yours to the address below. A notice by email counts as delivered when it is sent, unless it bounces.
• No partnership. Nothing here makes us partners, employer and employee, or agents of each other.
• Language. These terms are written in English. A translation is for convenience only.

21. Contact

Questions about these terms: support@jiayang.cloud. Data protection: privacy@jiayang.cloud. Security reports: security@jiayang.cloud.