Terms and Conditions.

Draft status and scope

These are proposed terms for ambiton.io and the AMBITON product. They are not effective. Viewing a preview, creating a test account or reading this draft does not accept it or change an existing agreement. A reviewed version, an identified contracting party, a lawful acceptance process and an effective date are required before these terms can govern service use.

A separately executed proposal, statement of work, processing agreement or service agreement may set the terms for a particular engagement. Its stated order of precedence controls any conflict; public draft language does not override an executed agreement. Submitting an inquiry alone does not create a project engagement or a professional-advice relationship.

Review required. Before activation: confirm the full legal operator and address, eligible users and minimum age, countries served, and how a specific version is presented and accepted.

Accounts and business authority

Provide accurate account information and protect your sign-in credentials. Use only accounts, projects and data you are authorized to access. If acting for a business, you must have authority for the relevant request. Tell us if you believe an account is compromised.

Workspace ownership, project roles and action permissions are distinct. Signing in or connecting another account does not approve a blueprint, transfer business ownership, authorize customer outreach or allow unlimited spending. You remain responsible for the business decisions you approve and for the lawful use of customer data you supply.

What the service can provide

AMBITON can help describe a business, prepare requirements and designs, maintain revisions, and use supported build or operational workflows when their configuration and approval requirements are met. Availability depends on the specific capability and environment. An authored blueprint, synthetic demo, provider catalog, local test or prepared preview is not a deployed product or proof of a live connection.

Review the scope, assumptions, limits and acceptance criteria for a requested build. A feature is not complete merely because files were generated. Unavailable integrations, unknown outcomes and failed checks must remain visible. No universal business support, launch time, uninterrupted service, revenue result or automated legal compliance is promised by this draft.

AI output, research and your review

AI output and research summaries can be inaccurate, incomplete, non-unique or outdated. A source link, generated statement, screenshot interpretation or business scenario does not independently verify its claims. Review business rules, prices, financial assumptions, food and allergen information, security and third-party rights before use.

You are responsible for obtaining qualified legal, tax, financial, medical or other professional advice when needed. AMBITON's drafts and suggestions do not replace that advice. Proposed requirements, designs and automation plans stay proposals until the relevant review and authorization steps are completed.

Actions, connections and automation

Authorize only the particular action, project, destination and budget you intend. A conversation, transcript, uploaded file, saved preference or remembered instruction does not expand permissions. Publishing, destructive changes, purchases, payments, account changes and customer messages need the applicable product controls and deliberate authorization.

Connecting a third-party account is separate from selecting data or authorizing an operation. Providers have their own terms, access rules, charges and availability. You must be entitled to use the selected resources. Stop, pause, disconnect or revoke controls affect future access as described by that feature; they may not reverse completed actions or revoke copies and provider grants immediately.

Recurring automation must have an approved scope, supported capability and applicable budget. Local rehearsals and draft messages do not send communications or operate a business. Real outreach also requires appropriate recipient permissions and applicable platform rules.

Your content, generated work and third-party assets

You retain the rights you already hold in the material you provide. You must have the necessary rights and permissions to submit business data, source code, images, recordings, brand assets and other content. Do not upload credentials or unnecessary sensitive personal information.

The proposed service permission is limited to processing your submitted content to provide the requested service, using approved providers and permitted workspace access. This draft does not authorize unrelated resale, advertising use or public promotion of your private content. Any broader use requires separate review and an appropriate permission.

Rights in deliverables, generated output, underlying AMBITON software and confidential materials must be allocated in the reviewed service agreement. This draft does not transfer third-party rights or guarantee that AI output is exclusive, copyrightable or free of infringement. Open-source components, stock images, fonts, provider assets and customer-supplied materials remain subject to their applicable licenses. A reference screenshot does not give permission to copy someone else's logos or artwork.

Review required. Before activation: settle output ownership and licenses, the limited service-use license, confidentiality and support access, third-party license delivery, and any agreed export or source-code entitlement.

Acceptable use

Use the service lawfully and within your permissions. Do not attempt unauthorized access, evade project boundaries or spending limits, upload malicious software, interfere with verification or abuse the service. Do not use it for fraud, infringement, unlawful surveillance, deceptive impersonation or unsolicited unlawful communications.

Use synthetic records on private test and rehearsal surfaces. Do not treat simulated checkout, payment status, message delivery or fulfillment milestones as evidence of real commercial activity. Real customer use requires its own verified configuration, rights and notices.

Prices, usage and payments

Any fee, subscription, deposit, usage charge, renewal or third-party expense must be set out in a reviewed offer or executed agreement before it is charged. Usage and cost displays can be estimates or incomplete records; they are not an invoice or a new payment authorization. A budget reservation or technical spend limit does not itself authorize a charge to you.

The reviewed product includes separately gated Stripe test flows for a customer prototype. These do not establish live AMBITON billing, renewal or refund policies. No paid plan, recurring charge or live payment is activated by these drafts.

Review required. Before paid service: confirm currency, taxes, invoice and payment timing, provider-cost allocation, renewals, cancellation, refunds, credits and any mandatory consumer withdrawal rights. No blanket non-refundable policy is proposed.

Privacy, exports and ending use

The Privacy Policy draft describes the reviewed information flows and unresolved retention decisions. Do not treat it as a data-processing agreement or consent for every optional feature. A business using real customer information must determine its responsibilities, necessary notices, permissions and any processing agreement with AMBITON.

Available exports contain the scope described by that feature and may not be a complete account backup or directly restorable application. Review an export before sharing it and retain your own appropriate copies. Signing out or closing a preview does not remove saved data. Account closure, deletion, backup expiry, export timing and outstanding fees need a reviewed process.

The proposed approach to suspension or termination is proportionate action where necessary for unauthorized use, security risks, legal requirements or material breach, with notice and a reasonable opportunity to resolve the issue when appropriate. Immediate restrictions may be necessary for an urgent risk. The exact grounds, notice, appeal, export window and consequences must be approved before activation.

Service commitments and liability

Service levels, support, acceptance, warranties and remedies must be set out in the applicable reviewed agreement. AI output and previews require review; neither guarantees a business outcome. Security and availability depend on verified implementation and configuration.

Liability caps, excluded losses, indemnities and required exceptions are unresolved. This draft does not insert a zero-liability clause, waive statutory rights or shift every risk to the customer. Mandatory rights and liabilities that cannot lawfully be excluded must be preserved in the final agreement.

Review required. Before activation: counsel must review balanced liability, warranty and indemnity terms for the actual business model, customers and jurisdictions.

Law and resolving disputes

Contact contact@ambiton.io about a service concern so the issue can be assessed. This draft does not select governing law, a court, mandatory arbitration, a class-action waiver or a contractual deadline for bringing claims. Those decisions depend on the identified operator, audience and applicable mandatory protections.

Review required. Before activation: confirm governing law, venue, complaint handling and any dispute process; preserve applicable consumer and privacy rights.

Changes and contact

Changes to the product create proposed revisions for owner and counsel review. A new draft does not automatically become effective, alter an accepted version or prove that you consented. Material-change notice, timing and any renewed agreement or consent must be reviewed for the particular change. Preserve the applicable version and its activation history.

Questions about these drafts can be sent to contact@ambiton.io. This contact address is supplied for review; the legal operator's full identity and notice address must be completed before activation.