Snapshot 243647

Document
Terms
URL
https://zuplo.com/legal/terms
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
63388 bytes
SHA-256 (raw)
9fd6fb3b1ef3b505086d6094214e3b711e2307a89aefe32980275f7450561172
SHA-256 (normalized text)
106480449a2d41b7ceb9d4a266e525dedbb8295d171bd0fce58fbc4ec6b951fd

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Legal
Terms of Service
Last updated: November 9, 2026
Legal Documents
Acceptable Use Policy Data Processing Agreement End User License Agreement Privacy Policy Terms of Service Vulnerability Disclosure Policy
These Terms of Service apply to everyone who uses the Zuplo Cloud Service on a self-serve plan, including the Free and Builder plans, and to everyone who installs or uses Zuplo’s command-line or local development tools. If Customer signed a separate Cover Page or Order Form with Zuplo, Inc. for the same account (for example, an Enterprise agreement), and that agreement has not ended, the terms below do not apply to that account. Instead, the signed agreement applies to Customer’s use of the Product. These terms cover Zuplo’s managed edge hosting only. Managed Dedicated and self-hosted deployments are available only under a separate signed agreement.
This Agreement is between Zuplo, Inc. and the company or person accessing or using the Product. This Agreement consists of: (1) this Cover Page, which includes the Order Form, the Key Terms, and the Changes to Standard Terms below; (2) the Acceptable Use Policy and the DPA, which are referenced in the Key Terms; and (3) the Common Paper Cloud Service Agreement Standard Terms Version 3.0 posted at commonpaper.com/standards/cloud-service-agreement/3.0 (“Standard Terms”), which are incorporated by reference. Any modifications to the Standard Terms made in this Cover Page will control over conflicts with the Standard Terms. Capitalized words have the meanings given in this Cover Page or the Standard Terms.
If you are accessing or using the Product on behalf of your company, you represent that you are authorized to accept this Agreement on behalf of your company. By clicking to accept this Agreement, signing up for an account, or accessing or using the Product, Customer indicates its acceptance of this Agreement and agrees to be bound by its terms. If you do not agree, do not use the Product.
Please read this Agreement carefully. It includes disclaimers of warranties (Section 7 of the Standard Terms and, for Free Plans, “Free Plans” below), limits on each party’s liability (Section 8 of the Standard Terms and the General Cap Amount below), the exclusive choice of Delaware law and courts (Section 12.3 of the Standard Terms), and Provider’s right to update this Agreement with notice (“Agreement Updates” below).
Order Form
Cloud Service: Provider’s gateway platform for APIs, AI models, and AI agents, consisting of the following runtime components (the “Runtime Components”):
(i) API Gateway, which processes incoming API requests and applies policies to enforce Customer’s authentication, authorization, and traffic management requirements;
(ii) AI Gateway, which routes and manages requests from Customer’s applications to third-party AI model providers, including applying policies for authentication, usage controls, and cost management;
(iii) MCP Gateway, which manages and secures connections between AI agents and Model Context Protocol (MCP) servers; and
(iv) Developer Portal, an interactive portal for Customer’s API consumers.
The Cloud Service also includes Provider’s hosted development-time services, consisting of a web-based management portal (portal.zuplo.com) and a build service. Provider’s command-line and local development tools are Software, as defined in the Standard Terms, and are part of the Product. The features and Runtime Components available to Customer depend on the Plan Customer selects. The Cloud Service is provided only as Provider’s managed edge hosting, in which Provider runs the Runtime Components on its shared global network. Managed Dedicated deployments, and running the Runtime Components in Customer’s own environment other than for local development and testing, are not part of this Agreement and require a separate signed agreement.
Plan: The self-serve plan Customer selects in the Product, as described on Provider’s pricing page (for example, the “Free Plan” or the “Builder Plan”). Any plan that does not require payment of Fees is a “Free Plan”. Any other self-serve plan is a “Paid Plan”.
Order Date: The Effective Date.
Subscription Period: One month. Each Subscription Period renews automatically for another one-month Subscription Period. Provider may align Subscription Periods with Customer’s billing cycle as shown in the Product.
Non-Renewal Notice Date: For Customer, the last day of the then-current Subscription Period. Customer gives notice of non-renewal by cancelling its Paid Plan or closing its account in the Product, and the cancellation takes effect at the end of the then-current Subscription Period. Customer may stop using a Free Plan and close its account at any time. For Provider, 30 days before the end of the then-current Subscription Period.
Fees: The Fees for Customer’s Plan as published on Provider’s pricing page, including any usage-based Fees for use above the amounts included in Customer’s Plan. There are no Fees for a Free Plan. Provider may change Fees by giving Customer at least 30 days notice (including by email or in the Product), and the change will apply starting with the first Subscription Period that begins after the notice period ends.
Invoicing & Payment: Automatic payment. Provider will automatically charge the credit card, debit card, or other payment method on file at the start of each Subscription Period for recurring Fees and at the end of each Subscription Period for usage-based Fees, and Customer authorizes all such charges. Invoices, receipts, and transaction history are available in the Product or on request.
Use Limitations: The limits for Customer’s Plan as described on Provider’s pricing page and in the Documentation, including limits on requests, egress, users, and custom domains. Provider may enforce Use Limitations by rate-limiting, blocking requests above the limit, or requiring Customer to move to a different Plan.
Technical Support: Support as described for Customer’s Plan at zuplo.com/docs/articles/support, which for self-serve Plans is community support. Provider does not commit to any response time under this Agreement. Email addresses listed in this Agreement are for notices and legal, privacy, and abuse matters, and are not a technical support channel.
SLA: None. Provider does not offer service level commitments or service credits under this Agreement. They are available only under a separate signed agreement.
Key Terms
Customer: The company or person who accesses or uses the Product. If the person accepting this Agreement is doing so on behalf of a company, all use of the word “Customer” in the Agreement will mean that company.
Provider: Zuplo, Inc.
Effective Date: The date Customer first accepts this Agreement.
Governing Law: The laws of the State of Delaware.
Chosen Courts: The state and federal courts located in Wilmington, Delaware.
General Cap Amount: The greater of (a) the Fees paid or payable by Customer to Provider in the 12-month period immediately before the event giving rise to the claim, or (b) US$100.
Supercap: None.
Uncapped Claims: None.
Provider Covered Claims: None.
Customer Covered Claims: Any action, proceeding, or claim that (1) the Customer Content, when used according to the terms of the Agreement, violates, misappropriates, or otherwise infringes upon anyone else’s intellectual property or other proprietary rights; or (2) results from Customer’s breach or alleged breach of Section 2.1 (Restrictions on Customer), including the Acceptable Use Policy.
Security Policy: Provider will use commercially reasonable efforts to maintain the security practices described at zuplo.com/docs/security and trust.zuplo.com. Provider will maintain annually updated reports or annual certifications of compliance with the following: SOC 2 Type II.
DPA: The Zuplo Data Processing Agreement, which applies to Customer automatically when Customer accepts this Agreement and forms part of this Agreement.
Acceptable Use Policy: The Zuplo Acceptable Use Policy.
Notice Address for Provider: legal@zuplo.com, or by mail to Zuplo, Inc., 600 1st Avenue Suite 330 PMB 29897, Seattle, Washington 98104-2246, USA.
Notice Address for Customer: The email address of the owner of Customer’s account, as shown in the Product.
Changes to Standard Terms
Order Form and Framework Terms. This Cover Page is both the Order Form and the Key Terms for Customer’s account. When Customer changes Plans in the Product, the Order Form is updated to reflect the new Plan, Fees, and Use Limitations; this does not create a new Order Form or change the Effective Date. Section 5.2 (Framework Terms) of the Standard Terms is replaced with the following: “The Framework Terms will start on the Effective Date and continue until the Order Form ends.” Termination or expiration of the Order Form also ends the Framework Terms, and Section 5.6 (Survival) of the Standard Terms applies.
End Users. Customer may use the Runtime Components to make Customer’s own APIs, AI applications, MCP servers, and Developer Portals available to Customer’s customers, partners, and other end users (“End Users”). Doing so does not breach Section 1.1 (Access and Use) or Section 2.1(a)(ii) of the Standard Terms. Customer is responsible for End Users’ access to and use of the Product in the same way it is responsible for Users under Section 1.3 (User Accounts), and for Customer’s own terms with End Users. Customer may not resell, sublicense, or provide the Product itself to others (for example, as a hosted API gateway or developer portal service that others configure), except as part of Customer’s own products and services.
Software. Under Section 1.1(b) (Access and Use) of the Standard Terms, Customer may install and run the Software, including to run Customer’s projects locally for development and testing, only in connection with Customer’s use of the Cloud Service. Customer may not use the Software to serve production traffic or as a substitute for the Cloud Service. If a component of the Software is provided under an open source license, that license governs that component to the extent it grants broader rights than, or conflicts with, this Agreement.
Usage Data. Section 1.4 (Feedback and Usage Data) of the Standard Terms does not prevent Provider from disclosing Usage Data to its service providers that process it on Provider’s behalf, as required by Applicable Laws, or to a successor in a transaction described in Section 12.6 (Assignment).
Artificial Intelligence. The Standard Terms are amended to add the following Section 1.6, and Section 1.6(a) survives expiration or termination of the Agreement:
1.6 Artificial Intelligence.
(a) No Training. Provider will not use Customer Content to develop, train, fine-tune, or otherwise improve any artificial intelligence or machine learning model, whether owned by Provider or a third party.
(b) AI Features. Certain features of the Product use large language models or other artificial intelligence models, which may be provided by Provider’s third-party service providers (“AI Features”). When Customer or Users use an AI Feature, Customer Content submitted to that feature may be processed by such models solely to provide the AI Feature to Customer. Provider will require each third-party model provider to process Customer Content only on Provider’s behalf and not to train its models.
(c) Disabling AI Features. Customer may disable AI Features at the account level at any time. While AI Features are disabled, Customer Content will not be sent to AI Features.
(d) Service and Support. Nothing in this Section 1.6 limits Provider’s use of Customer Content under Section 1.5 (Customer Content) to provide, maintain, secure, and support the Product.
(e) Accuracy. Due to the nature of artificial intelligence, output generated by AI Features may be incorrect or inaccurate. AI Features are not human and are not a substitute for human oversight. Customer is responsible for reviewing output before relying on it. If a User directs an AI Feature to take an action in the Product, such as changing project files, the action is taken on Customer’s behalf.
Customer-Configured Services. Customer may configure the Cloud Service to send data to, or receive data from, services that Provider does not provide, including Customer’s own backends, AI model providers that Customer selects for use with the AI Gateway, and MCP servers that Customer connects to the MCP Gateway (“Customer-Configured Services”). Customer-Configured Services are not part of the Product, are not AI Features, and are not Provider’s service providers. Provider transmits data to and from them at Customer’s instruction, and Customer is responsible for its agreements with, and its use of, Customer-Configured Services, including any fees they charge. Provider is not responsible for the availability, security, or output of Customer-Configured Services or for how they handle data.
Acceptable Use Policy. Section 2.1(a) (Restrictions on Customer) of the Standard Terms is amended to include the restrictions in the Acceptable Use Policy, so a violation of the Acceptable Use Policy is a breach of Section 2.1 (Restrictions on Customer).
Prohibited Data. Customer may submit Prohibited Data to the Product, except protected health information regulated by the Health Insurance Portability and Accountability Act (“HIPAA”), which Customer may submit only under a Business Associate Agreement signed with Provider. Provider does not offer a Business Associate Agreement under this Agreement. Provider does not provide HIPAA or PCI DSS compliance under this Agreement, and Customer is responsible for determining whether the Product meets the legal and regulatory requirements that apply to the data it submits. Customer will not include Prohibited Data in URLs, query strings, log messages, trace data, custom analytics properties, or other metadata that the Product records as Usage Data, and will use the data scrubbing feature described in the Documentation to remove Prohibited Data before it is recorded.
Free Plans. For a Free Plan: (a) Section 6.3 (Representations & Warranties from Provider) and Section 6.4 (Provider Warranty Remedy) of the Standard Terms do not apply, and the Product is provided “AS IS” and “AS AVAILABLE”, without warranty of any kind, to the maximum extent permitted by Applicable Laws; (b) Provider may change, limit, or discontinue the Free Plan or any of its features at any time; and (c) in addition to Provider’s rights under Section 5 (Term & Termination) of the Standard Terms, Provider may suspend or terminate Customer’s Free Plan at any time and for any reason, with or without notice.
Termination by Provider. In addition to Section 5.3 (Termination) of the Standard Terms, Provider may terminate this Agreement for any reason by giving Customer at least 30 days notice. If Provider does so for a Paid Plan for a reason other than Customer’s breach, Provider will pay Customer a prorated refund of any prepaid Fees for the remainder of the then-current Subscription Period.
Agreement Updates. Despite Section 12.2 (Modifications, Severability, and Waiver) of the Standard Terms, Provider may update this Cover Page, the Acceptable Use Policy, or the DPA by posting the updated version on Provider’s website and updating its “Last updated” date. If an update materially reduces Customer’s rights or materially increases Customer’s obligations, Provider will notify Customer at least 30 days before the update takes effect, by email to Customer’s Notice Address or in the Product, unless a shorter period is required by Applicable Laws or is reasonably necessary to address security risks, abuse, or legal requirements. Other updates take effect when posted. Updates apply only from the date they take effect and do not apply to any dispute or claim that arose before that date. If Customer does not agree to an update, Customer may cancel its Paid Plan or close its account before the update takes effect. Customer’s continued use of the Product after an update takes effect means Customer accepts the update. Changes to Fees are governed by the Fees section of the Order Form. Each version of the Standard Terms is posted at its own address and does not change; Provider will move this Agreement to a later version of the Standard Terms only by updating this Cover Page under this section.
Common Paper Cloud Service Agreement Standard Terms (Version 3.0) free to use under CC BY 4.0.