Definitions

1. Acceptable Use Policy

The policy published at /acceptable-use, which sets out what you may not build, run, or publish with the Service. It forms part of the Agreement. Breaking it is a breach of the Terms of Service.

2. Account

The sign-in identity you use to reach the Service: your email address, your authentication method, and the profile attached to them. An Account belongs to one person. You are responsible for everything done through it. Under the Indian Contract Act, 1872, a contract with a person under 18 is void, so you must be 18 or older to hold one.

3. Affiliate

Any entity that controls a party, is controlled by it, or is under common control with it, for as long as that control lasts. Control means holding more than 50% of the voting interests, or the power to direct the management of the entity.

4. Agreement

The Terms of Service, together with every policy those Terms incorporate by reference — the Acceptable Use Policy, the Usage Policy, the Refund and Cancellation Policy, the Privacy Policy, the Cookie Policy, the Copyright Policy and this page — and any Order you place. Where a policy and the Terms disagree, the Terms govern unless the policy says otherwise.

5. Beta Feature

Any feature, model, connector or template we make available and label alpha, beta, preview, early access or experimental. A Beta Feature is provided as-is, can change or be withdrawn without notice, carries no service commitment, and consumes Credits like any other work.

6. Confidential Information

Information one party discloses to the other that is marked confidential or that a reasonable person would treat as confidential. It does not include information that is public through no fault of the recipient, that the recipient already had, that a third party supplied without restriction, or that the recipient developed independently. Each party protects the other’s Confidential Information with reasonable care, and gives prior notice before disclosing it under legal compulsion where the law allows that notice.

7. Connector

An integration that lets a Project reach a third-party service — a database, a payment provider, an email sender, a repository host — using credentials you authorise. Connectors run against your own accounts with those providers and are billed by them. Vibely does not proxy or aggregate connector calls.

8. Credits

The prepaid unit in which the Service meters and charges agent work. Credits are granted monthly with a plan and can also be bought as top-ups. They are non-refundable, are not redeemable for cash, and are not transferable between Workspaces. Credits granted with a plan expire with it; credits bought as a top-up do not expire on a clock and last until they are spent or the account ends.

A build turn is charged for the tokens it actually used, priced by the model selected, subject to a small per-turn minimum. There is no per-turn ceiling: a heavy turn is charged what it cost. Three kinds of turn are charged nothing: an auto-fix turn, a build turn that ran no tools, and a very small chat turn. The metering is set out in full at /product-terms.

On a paid plan, credits you have not spent when the cycle renews roll over once: they stay spendable through the following cycle and expire at the end of it. On the Free plan the monthly grant tops your balance up to the allowance rather than accumulating.

9. Customer

The person or entity that creates an Account and agrees to the Terms. If you are using Vibely on behalf of an organization, you confirm that you have authority to bind that organization to these Terms, and that organization is the Customer.

10. Customer Content

Everything you supply to or create in the Service: prompts and instructions, uploaded files, images and screenshots, the connector credentials you authorise, and the source code, designs, assets and configuration held in your Projects. Customer Content expressly includes Generated Output, for the purposes of both indemnities in the Terms.

11. Customer Personal Data

Personal Data contained in Customer Content that Vibely processes on your documented instructions while providing the Service — including Personal Data your own End Users submit to a Published App. You are the controller (or Data Fiduciary) of it and Vibely is the processor (or Data Processor).

12. Documentation

The published product and API documentation at docs.vibely.sh, together with the policy pages the Terms incorporate by reference.

13. End User

A person who uses a Published App you built, rather than Vibely itself. End Users are your users, not ours. What a form in your Published App collects does not reach us: we host the build, not a backend for it, so a submission goes to the service you connected and the retention for it is yours to set there. See /product-terms.

14. Generated Output

The code, designs, text, images and other material the Service produces in response to your prompts, using third-party AI models. As between you and us, Generated Output is Customer Content. It may contain inaccuracies and is not warranted to be fit for any particular purpose, and it is subject to any third-party rights in the underlying AI models.

15. Mobile App

A native iOS or Android application generated from a Project, built through the Expo and EAS pipeline, and distributed through the Apple App Store or Google Play under your own developer account. Mobile generation is not available on the Free plan.

16. Order

A purchase of a plan, seat count or credit volume completed through checkout, or a written order form we and you both sign. Every Order is billed in advance in US dollars and incorporates the Agreement. The terms that apply to an executed Order are at /enterprise-terms. We do not publish a standard enterprise order form: each Order is drafted for the engagement, and those conversations start at /contact-sales.

17. Personal Data

Any information relating to an identified or identifiable natural person. It includes personal data under the GDPR and the UK GDPR, and personal data of a Data Principal under India’s Digital Personal Data Protection Act, 2023.

18. Plan

The subscription tier a Workspace is on — Free, Pro or Business — which sets the monthly credit allowance, the top-up rate, and which capabilities are available. Mobile generation, custom domains and team roles are paid capabilities. Restricted publishing — workspace, group or private — is a Business capability; Free and Pro Workspaces publish publicly.

19. Preview

The running build of a Project served from its Sandbox so you can see your changes. Web previews are served on a subdomain of vibelyagent.com and are cookie-gated to signed-in users by default; turning on public remixing opens a preview to anyone with the link. Mobile previews opened through Expo are not cookie-gated — the preview host is the access control, so treat its URL as a secret.

20. Project

A single application you build inside a Workspace: its generated source tree, message and version history, snapshots, Sandbox, Preview host, and any deployment attached to it. A Project is either a web app (Vite and React) or a native mobile app (Expo and React Native).

21. Published App

A build of a Project you make available to others through the Service — on a Vibely-operated subdomain of vibelyagent.com, on a custom domain you connect, or as a native binary submitted to the Apple App Store or Google Play through the EAS build pipeline under your own developer account.

22. Sandbox

The isolated cloud environment a Project builds and runs in: its own filesystem, its own dev server, its own process space, separate from every other Project. Sandboxes run on third-party cloud infrastructure in the United States; we do not operate the machines a Sandbox runs on. The providers we use are named on our Subprocessors page. A Sandbox is paused after inactivity and discarded 72 hours later; the Project then resumes from a snapshot or from its stored files.

23. Service

Also "Vibely". The platform operated by Mana Intelligence Private Limited at vibely.sh and api.vibely.sh: the AI agent that generates and edits application source code, the cloud Sandboxes it runs that code in, the Preview and publishing hosts at *.vibelyagent.com and connected custom domains, the Connector integrations, and the native mobile build pipeline — together with the Documentation.

24. Service Data

Personal Data that Vibely processes as controller (Data Fiduciary) in its own right, to run and secure the Service: account and profile details, billing and payment records, the credit ledger and usage metering, technical and diagnostic logs, support correspondence, and consented product analytics.

25. Sub-processor

A third party we engage to process Customer Personal Data on our behalf in providing the Service. The list published at /subprocessors is the authoritative public list.

26. Subscription Term

The period an Order covers — one month or one year, starting on the day the Order is placed. Fees are billed in advance in US dollars. A yearly Subscription Term is priced at ten months of the monthly rate. A Subscription Term renews automatically for another term of the same length unless you cancel before it ends. We email you 7 days before a renewal, 3 days before a trial converts, and 30 days before a card on file expires.

27. Support

Help with the Service itself, as distinct from help with the app you are building. Free plan support is community support. Paid plans can also email [email protected] for billing questions and [email protected] for privacy and security questions. First-response targets by plan are published at /support-policy; they are targets and carry no service credit. Availability is committed separately in the Service Level Agreement at /sla, and nothing on this page creates a support commitment.

28. Vibely Platform

Our own software, website, APIs and interfaces. The Vibely Platform expressly excludes Generated Output, your prompts, Customer Content, and any third-party software, AI model, package, template or integration reached through the Service. The distinction matters because the indemnity we give you in the Terms covers the Vibely Platform and nothing else.

29. Workspace

The billing and membership boundary of the Service. A Workspace owns the credit wallet, the subscription, the member roles (Owner, Admin, Editor, Viewer), the groups used for publishing access, and every Project created inside it. Credits do not move between Workspaces.

30. How these definitions are used

A term defined here carries the same meaning everywhere it appears capitalised in a Vibely agreement or policy. If a page defines a term differently, tell us at [email protected] and we will fix the page rather than argue the point. Vibely is operated by Mana Intelligence Private Limited, incorporated in India.