ZURRO.AI STUDIO

Terms and Conditions

Effective 8 September 2026 · Version 2026-09-08.1

Back to sign in
Please read these Terms and Conditions before using Zurro.ai Studio.

These Terms and Conditions govern access to and use of Zurro.ai Studio ("Zurro", "Studio", "we", "us"), including Built-in AI and OneClick. By creating an account and accepting these Terms and Conditions, you agree to the whole document. If you use Studio for a company or other organisation, you confirm that you are authorised to do so.

1. Your account

You are responsible for keeping your account credentials secure and for activity carried out through your account. Information supplied during registration must be accurate and you must keep it reasonably up to date. Company Account Owners and Admins are responsible for the users and access they manage within their account.

2. What Studio provides

Studio helps users create, edit, version, manage, publish and export digital work, including Sites, Applications, Slides, Documents and Help/Walkthrough projects. Features may depend on your subscription, Built-in AI allowance, optional infrastructure and third-party services used by Studio. Beta and pre-release functionality may change, be interrupted or be withdrawn as the product develops.

3. Your content, projects and responsibility

You keep responsibility for the materials you upload, the instructions you provide and the work you create, publish, host, export or deploy using Studio. You must have the rights and permissions needed to use those materials and must ensure that your output and use of Studio comply with applicable law, contracts, intellectual-property rights, privacy obligations and any rules that apply to your organisation or industry.

Studio is a creation and management tool. We do not approve, certify or accept responsibility for the legality, accuracy, safety, suitability or regulatory compliance of something merely because it was created, edited, published, hosted or deployed through Studio. You must review and test your work before relying on it or making it available to others.

4. Built-in AI, OneClick and AI data

Zurro.ai Studio includes Built-in AI where enabled by your Studio subscription or Evaluation access. Built-in AI uses AI services managed by Zurro; no customer API key or separate external AI account connection is required.

OneClick is the Studio action used to hand queued AI changes or other supported project work to Built-in AI when you are ready for Studio to process them. You can prepare and queue changes in Studio before choosing OneClick. OneClick is a Zurro Studio workflow and uses the same Built-in AI access and allowance described in these Terms.

Built-in AI, including work started through OneClick, is subject to the monthly AI allowance and any purchased extra AI capacity shown in Studio. Monthly allowance is used before purchased extra capacity.

To perform an AI task, Studio may send the selected project instructions, relevant project content, uploaded or extracted material, and the minimum operational context needed to Zurro-managed AI service providers. Provider processing is governed by Zurro's provider arrangements and these Terms. Do not submit content you are not authorised to process.

5. Publishing, hosting and applications

If Studio lets you publish, preview, host or run content, you remain responsible for that content and for any data, integrations, users or third-party services used by it. You must not use Studio to publish or operate unlawful, infringing, malicious or abusive content or services. We may restrict, suspend or remove access to content or functionality where reasonably necessary for security, legal compliance, platform integrity or enforcement of these Terms.

Zurro may collect basic service analytics for published or hosted output, such as requested page or route, coarse device type, country or region, and referrer domain, to operate, measure and improve the service. Zurro's built-in analytics are designed not to rely on advertising or analytics cookies or persistent visitor identifiers. If you add or configure cookies, tracking pixels, third-party analytics, advertising, embeds or similar technologies in your project, you are responsible for providing any legally required notices, consent or choice controls, and for complying with applicable privacy and electronic-communications laws for your end users.

Optional managed runtime or hosting services do not remove your responsibility for application security, business logic, data handling, legal compliance, backups you are required to keep, or the consequences of deploying or operating your work.

Purchase, activation or use of a Production Environment is also subject to the Production Hosting Terms, which supplement these Terms for managed Production hosting.

6. Trials, subscriptions, Grace and payments

The current Zurro Studio Trial lasts 3 days. During Trial you can author supported project types, publish with the Trial banner and use the normal export routes available for the relevant project type, including Project/Version exports. Trial includes a configurable starter percentage of the standard monthly Built-in AI allowance. Trial does not include a Development Environment or Production Environment, and Application project creation requires an active Development Environment assigned to the user. A Trial does not become a paid subscription unless you actively purchase or otherwise agree to a paid plan, and Trial expiry does not receive the paid Grace period.

Paid Zurro Studio access includes the monthly Built-in AI allowance shown in Studio. The same allowance is used for Zurro-managed AI operations, including project creation and changes, Roadmap work, research and generated images. Purchased extra AI capacity carries forward until consumed and is used only after the monthly allowance. Each licensed Builder currently includes 3 active custom hostnames. One Builder cannot consume another Builder’s included custom-hostname allowance. Optional products such as Development Environment, Production Environment, additional AI capacity and additional Custom URL units are separate where offered. Additional Custom URL units are recurring monthly account capacity and are used only after the Builder’s own included allowance is consumed. Application project creation and managed Application preview/runtime require an active Development Environment assigned to the user; Development is not included automatically merely because Studio authoring access is active.

Zurro may grant temporary Evaluation Access for a stated period. Evaluation Access is promotional access rather than a paid subscription and may include a temporary Developer Standard Environment where expressly granted. Evaluation Access does not prevent you from purchasing a normal subscription. Unless paid access has taken over, Evaluation Access ends automatically on its stated expiry date and the account returns to the Expired state.

Paid subscriptions may renew automatically for the billing period shown when you subscribe, until cancelled. Unless different terms are shown at checkout, cancellation stops future renewal and access continues until the end of the already-paid period. Fees are exclusive of applicable taxes unless stated otherwise. Refunds are provided where required by law or where the checkout/order terms expressly provide for one.

When paid Studio access ends, the current paid Grace period is 3 days. During Grace, authoring, publishing and normal exports remain available according to the configured lifecycle policy, while new Development Environment, Production Environment, AI-capacity or Custom URL add-on purchases may be unavailable. Published output may display an inactive-subscription banner during Grace. When Trial or Grace expires, Studio becomes read-only: AI runs, editing, publishing and export are unavailable until Studio access is reactivated.

Built-in AI usage is included only within the shared Built-in AI allowance or extra AI capacity you purchase from Zurro.

7. Third-party services

Studio relies on third-party services such as AI service providers, payment processors, hosting/runtime providers and external websites. Their availability, technical behaviour and service changes can affect Studio. Where Zurro selects and manages a provider as part of Studio, including for Built-in AI, your access to that capability is through Studio. If you separately choose to connect Studio, your project or your published output to an external third-party service, your use of that external service may also be subject to its own terms and privacy practices.

8. Acceptable use

You must not misuse Studio, interfere with its security or operation, attempt unauthorised access, use it to distribute malware or harmful code, infringe the rights of others, or use it for unlawful purposes. You must not attempt to circumvent account, subscription, usage, security or access controls.

9. Availability, changes and data retention

We aim to operate Studio reliably, but we do not promise uninterrupted or error-free availability. Maintenance, provider outages, beta changes, security incidents or other events can affect functionality. You should keep independent copies or exports of information that you are required to retain where Studio provides an appropriate export route.

After Studio access reaches Expired status, account and project data is retained for 90 days. Export is available during Trial, active paid Studio access and the paid Grace period, but not while the account is Expired/read-only. A current Studio subscription or applicable Grace access is therefore required to export after a paid subscription ends. Reactivating Studio during the retention period can restore normal access to retained data.

We may update Studio and these Terms as the service develops. Where a material Terms update requires renewed acceptance, Studio may ask you to accept the new version before continuing to use affected services.

10. Suspension and termination

You may stop using Studio at any time and may cancel paid subscriptions through the available account/billing controls once those controls are offered. We may suspend or terminate access for material breach of these Terms, non-payment, fraud, security risk, unlawful use or where necessary to protect Studio, other users or third parties. Following normal subscription expiry, the 90-day retention period in section 9 applies. Separate suspension or termination for breach, fraud, security or unlawful use may require different handling where necessary for legal, security or platform-integrity reasons.

11. Disclaimers and limitation of liability

To the maximum extent permitted by applicable law, Studio is provided on an "as available" basis and we do not guarantee that generated output, recommendations, code, documents, published content or third-party integrations will be accurate, complete, secure, fit for a particular purpose or free from defects.

To the maximum extent permitted by applicable law, Zurro is not responsible for indirect or consequential losses arising from use of Studio, third-party provider behaviour, user-created content, or decisions made in reliance on generated output. Nothing in these Terms excludes or limits liability that cannot lawfully be excluded or limited, or affects mandatory consumer or statutory rights that apply to you.

12. Contact and legal review

Questions about these Terms can be raised through the Zurro support/contact route made available with the service. These Terms are intended to provide the operating terms for the current beta and production-readiness phase and should be reviewed alongside the final contracting-entity, privacy and payment disclosures before broad public launch.

PRODUCTION

Production Hosting Terms

Effective 25 August 2026 · Version 2026-08-25

These Production Hosting Terms apply when you purchase, activate or use a Zurro Production Environment.

They supplement the Zurro.ai Studio Terms and Conditions. If an order form or separately signed agreement expressly replaces a provision here, that agreed term applies for that customer. Otherwise these Production Hosting Terms form part of your agreement with Zurro for Production hosting.

1. Production Environment

A Production Environment is Zurro's managed runtime for a live Application. The purchased tier provides the resource envelope and included capabilities shown in Studio or at checkout, which may include managed compute, persistent application data, managed PostgreSQL where required, internal or internet-facing access, inbound and outbound networking controls, recovery features, deployment operations and monitoring.

Production is separate from the Studio authoring service and from a Development Environment. Restarting or updating Studio does not intentionally start, stop or replace a Production Application. Production changes occur through explicit Production operations such as deploy, start, stop, apply configuration, upgrade, rollback, restore or delete.

2. Resource tiers and fair use

Each Production tier has defined CPU, memory, persistent-storage and traffic allowances or limits shown in the current catalogue. Zurro may enforce those limits to protect service stability. If an Application materially exceeds its purchased tier, it may perform poorly, fail readiness, be restricted, or require an upgrade.

Included traffic is intended for normal Application use, not bulk media distribution, abusive automated traffic, cryptocurrency mining, denial-of-service activity or workloads designed primarily to consume infrastructure. Additional usage charges or higher-capacity arrangements may apply where shown before purchase or agreed with you.

3. Application versions, testing and deployment

Zurro may require the exact Application version to have completed a successful Development run before it can be deployed or upgraded in Production. This is a deployment safeguard, not certification that the Application is free of defects.

You remain responsible for reviewing and testing Application behaviour, business logic, data migrations, integrations, access controls and compliance before and after a Production change. Zurro can provide deployment, readiness, rollback and recovery mechanisms, but does not approve the business correctness of user-created Applications.

4. Production access and networking

Production Applications may support Internal, Internet-facing or Mixed access where available. Internal access can be limited to authorised Zurro users or Viewers. Internet-facing access makes the configured Application surface reachable from the public internet; any authentication implemented by the Application remains the customer's responsibility.

Inbound and outbound networking rules can be declared by the Application and, where supported, added by authorised users. You are responsible for the endpoints, credentials, domains, IP addresses and third-party systems you configure. Zurro may block undeclared or unsafe traffic, rate-limit abusive traffic, or change underlying routing for security or operational reasons while preserving the intended Application access where reasonably possible.

5. Recovery points, backups and data recovery

Standard Production currently includes one automatic Zurro recovery point approximately every 24 hours with automatic recovery points retained for the previous 7 days, plus manual recovery points and optional pre-upgrade recovery points where offered. A recovery point is scoped to the relevant Production Application and can include managed PostgreSQL data, persistent filesystem state, Production configuration metadata and the reference to the deployed Studio version.

The Application source itself is normally restored by rebuilding or redeploying its Studio version rather than by storing another full copy inside each recovery point. Secrets remain in Zurro's managed secret system and are not exposed as readable values inside recovery artifacts.

Recovery is a safety feature, not a guarantee of zero data loss or an uninterrupted restore. An automatic point can fail, become unavailable because of an infrastructure/provider failure, or be unusable if the underlying Application/data is itself corrupt. Unless a separate plan or written agreement states otherwise, Zurro does not promise a contractual recovery-point objective (RPO) or recovery-time objective (RTO). You should maintain any independent records or exports required by law, contract or your own business-continuity policy.

Underlying cloud/database backup or point-in-time recovery facilities may also be used operationally by Zurro, but the Studio Recovery screen is the customer-facing recovery mechanism unless Support instructs otherwise.

6. Upgrade, rollback and restore

Code rollback and data restore are separate operations. Rolling Production code back to an earlier Studio version does not automatically overwrite newer Production data. Restoring a recovery point can replace current mutable Production data with older retained state and may therefore remove changes made after that recovery point.

Where supported, Zurro attempts to preserve or return to the previous working Production version when a new deployment or upgrade fails. This reduces deployment risk but is not a guarantee that every failed change can be automatically recovered, particularly where an Application itself performs irreversible changes to external systems or data.

7. Data isolation and shared infrastructure

Zurro may operate shared cloud infrastructure across multiple customers for efficiency. Customer Production Applications and managed databases are logically isolated using platform controls and Application-scoped credentials/resources. A standard Production purchase does not imply dedicated physical servers, dedicated clusters, a dedicated database instance or a dedicated public IP unless the order or plan expressly says so.

8. Security and customer responsibilities

Zurro manages the security of the hosting platform within the scope of the service. You remain responsible for the security and lawful use of your Application, including business permissions, Application authentication, user roles, secrets you provide, third-party credentials, data classification, consent and regulatory obligations.

You must not deploy malware, attempt unauthorised access, attack other systems, evade platform controls, process unlawful content or data, or use Production in a manner that creates material security or availability risk. Zurro may suspend or isolate a Production Environment where reasonably necessary to protect customers, the platform or third parties.

9. Availability, maintenance and support

Production is designed as a continuously available managed runtime, but unless your order or a separate written agreement includes an SLA, no specific uptime percentage is guaranteed. Maintenance, cloud-provider failures, internet routing, third-party dependencies, Application defects, capacity limits, security incidents and force-majeure events can affect availability.

Zurro may perform maintenance, security updates and infrastructure changes. Where practical, we aim to minimise disruption. Support routes and any plan-specific response commitments are those shown in Studio, on the website or in the applicable order.

10. Pricing, renewal and changes

Production Environment charges are separate from the Zurro Studio licence and Development Environment unless expressly bundled. The billing period, tier, quantity, price, taxes and renewal terms are shown at checkout, in Studio, or in an applicable company order.

Stripe or another payment provider may be used for online billing. Existing negotiated/manual contracts can have pricing different from the public catalogue. We may change catalogue pricing for future purchases or renewals as permitted by the main Terms and applicable law; a change does not silently rewrite an already agreed manual contract price.

11. Cancellation, deletion and retained data

Stopping Production pauses Application compute where supported but is not the same as deleting Production. Deleting Production can permanently remove runtime data and retained Production resources after the confirmation shown in Studio. Unassigning a Production Environment can release that entitlement for another Application when the product permits it.

Subscription cancellation, expiry, account closure or enforcement action can affect Production availability and retention. Any specific retention period shown in Studio, the main Terms, checkout or an applicable order controls. Do not rely on a cancelled or deleted Production Environment as long-term archival storage.

12. Third-party services

Zurro Production relies on third-party cloud, networking, payment and other infrastructure providers, and your Application may rely on services you choose. Their availability and behaviour are outside Zurro's complete control. Third-party terms may also apply directly to you.

13. Relationship with the Terms and Conditions

The Zurro.ai Studio Terms and Conditions continue to apply, including provisions concerning acceptable use, intellectual property, third-party services, suspension, disclaimers and limitation of liability. These Production Hosting Terms add the terms specific to managed Production hosting. If there is an inconsistency, a separately signed agreement or order form takes priority to the extent it expressly says so; otherwise these Production Hosting Terms control for the Production-specific subject matter.

14. Contact and legal review

Questions about Production hosting or these terms can be raised through the Zurro support/contact route made available with the service. These terms are intended for the current Production service and should be reviewed with the final contracting-entity, privacy, data-processing, tax and payment disclosures before broad commercial launch.

Production Hosting TermsSign inCreate an account