Terms

Last updated 2026-10-11

These Terms are an agreement between you and the Rindo team (“Rindo”, “we”), which builds and operates the Rindo cloud service at app.rindo.io (the “Service”) and the website at rindo.io. The team is not yet incorporated; the company that takes over these Terms and the Service will be named here when it exists, and account holders will be told.

If you accept these Terms for an organisation, you confirm that you may bind it, and “you” means that organisation. Otherwise “you” means you personally. Being the Owner of a project is a product role; it does not by itself mean you are contracting for an organisation.

The self-hosted edition of Rindo is licensed under a separate Subscription Agreement, and the open-source clients (rindo-runner, rindo-convert, rindo-provisioner) under the Apache License 2.0. Those agreements govern those products. A cloud agreement we sign with you separately prevails over these Terms only where it says so.

Paid plans are bought through our reseller, Paddle (section 9). Paddle’s Buyer Terms govern the purchase; these Terms govern the Service. Nothing in these documents reduces rights the law gives you that cannot be reduced.

The English text of these Terms controls over any translation, to the extent the law allows.

1. Words we use

Project — a workspace inside the Service with its own members and roles (Owner, Admin, Member, Viewer).
Owner — the person whose account a Project belongs to; the Owner’s account pays for the Project.
Content — everything you or your agents put into the Service: projects, tasks, documents, comments, files, test cases, chat, skills, and their history.
Agent — software that acts in the Service through an account or token you created: an AI assistant connected over MCP, a runner, or any other automated client.
Runner — the program that runs an Agent’s jobs: on your own machine with your own model provider (“your runner”), or, by separate arrangement, on a sandbox Rindo provisions (“a managed runner”).
Person — for the Team plan, a human account holding Member or above on at least one Project you own that is not archived or deleted, counted once however many of your Projects they are on. Viewers and Agents are never counted.

2. Eligibility and accounts

You must be at least 16 and able to enter a binding agreement under the law that applies to you.
You create an account by signing up, from an invitation, or through a sign-in provider. An account is for one person and may not be shared. Keep your credentials private and take reasonable care of the tokens and Agents you create; you are responsible for what is done with them. If you suspect your account has been compromised, revoke what you can under Account and tell us at security@rindo.io. You are not responsible for unauthorised use that results from our own breach of these Terms.
Keep a working email address on your account: it is how we reach you about security and these Terms, and how Paddle reaches you about billing. We send no marketing mail.
We may ask you to verify your email address before you buy a plan or take over a Project.

3. Agents and automation

Rindo is built for people and Agents to work side by side, so these rules matter:

Your permissions, your responsibility. An Agent acts under the account or token that connected it. A runner or a project agent is capped at Member and never approves, deletes or configures; an MCP client or a script using your own token acts with your roles, except that deletion and ownership actions are available only in the web app. You authorise what it does within the access you gave it, you configure and monitor that access, and its edits and comments are your Content. Review what it produces, including any human review the law or your organisation requires. This does not excuse us from enforcing the Service’s permissions.
Your runner. When a Runner on your own machine executes a job, the job’s contents (the triggering comment, the entities it references and what the Agent reads over MCP) go to your machine, and the Agent may send them to the model provider you configured there under your agreement with that provider. That traffic does not pass through Rindo; the Service receives only the job log and the changes the Runner sends back.
Managed runners. Where we provision a sandbox for your Agent by separate arrangement, the sandbox receives the job, a one-job credential and the environment you supplied (for example your model API key), and its log is kept for 30 days. The sandbox provider is listed in our Privacy Policy.
Clients you connect. When you connect an MCP client (for example Claude or ChatGPT), you authorise us to send that client exactly what the token you granted allows, and that client’s operator handles the data under the terms that apply to your connection. You can revoke any connection under Account → MCP access → Connected apps.
No generation by us. The Rindo server does not call a generative model to write text or make decisions for you. Its only call to an external model is embedding generation for search (section 7). Agents you connect, including Agents on managed runners, may call generative models and write their results into the Service under the configuration you supply.

4. Your Content

You own it. As between you and Rindo, you keep every right you hold in your Content. These Terms transfer no ownership of it to us.
Our licence. You give us the non-exclusive, worldwide licence we need to run the Service for you and the members of your Projects: to host, store, back up, index and search your Content (including sending titles and text to our embedding provider for search), to display it to the people your roles allow, to transmit it to services you connect (a git provider, an MCP client, a Runner), to build the exports you ask for, and to keep the shared history the product keeps. Our suppliers may do these things on our behalf, for these purposes only. The licence lasts as long as these purposes need it, including the retention described in the Privacy Policy. Closing your account does not delete Content you contributed to shared Projects (section 14). This licence does not replace any notice, consent or other safeguard the law requires for personal data.
No training. We do not use your Content, your prompts or your Agents’ outputs to train, fine-tune or improve any machine-learning model, ours or a third party’s, and we use an embedding provider whose terms do not allow it to train on what we send.
Who sees it. Your Content is visible to the members of the Project it belongs to, according to their roles. The operator role in the product has no “support read” of your Content and no feature to sign in as you. Authorised personnel may access infrastructure only as needed to operate, secure and support the Service, investigate abuse or comply with law, under confidentiality and access controls.
Your responsibility. Upload only what you have the right to share. For personal data of other people, give the notices and obtain the consents or other lawful authority the law that applies to you requires. Do not upload material that is unlawful where the law prohibits it. Keep production credentials out of ordinary Content; use only the settings designed for a connection or a managed runner. Our data-protection roles are explained in section 17 and in the Privacy Policy.

5. Acceptable use

Do not: attack, probe or overload the Service or other people’s accounts; scrape or bulk-export Content you do not have access to; share accounts or otherwise avoid the way People are counted; resell the Service or run it for a third party as your own product; use it to break the law, to infringe others’ rights, or to send spam; reverse-engineer it beyond what the law allows; or copy protected elements of the Service in breach of intellectual-property rights. Security research is welcome on your own Projects with ordinary care; report vulnerabilities to security@rindo.io.

6. Third-party services

Services you choose to connect — a git provider, an identity provider, an MCP client, your own model provider — have their own terms and data practices. You decide whether and what to connect; we do not control them, but we remain responsible for our own integration and our own obligations. Providers we engage to deliver the Service (hosting, mail, embeddings, managed-runner sandboxes) are our suppliers, and their involvement does not remove our responsibility for the work we entrust to them. The Privacy Policy names them.

7. Search and embeddings

To make your Content searchable, the Service sends the titles and text of tasks, documents (including files you turn into pages and skills you promote), test cases and their translations, and your search queries, to our embedding provider, which returns vectors we store beside the Content. The embedding pipeline does not send comments, chat threads or raw attachments; text extracted from a file and saved as a page is page text and may be sent. The vectors are deleted with the Content. The provider is named in the Privacy Policy.

8. Plans and People

Free. One active Project and the quotas shown in the product. Free may change or be limited for new accounts, and we may end it with 30 days’ notice.
Team. Billed monthly: a base price that includes five People, plus a price per additional Person, as shown at rindo.io/pricing and at checkout. People are counted across all the Projects you own, each human once; Viewers and Agents are free.
How People are counted. We count People regularly, normally every hour, from your Projects’ membership and reflect changes in your next charge, prorated. While a cancellation is scheduled, an increase is charged at once for the rest of the period and a decrease is not credited. A deferred adjustment is not collected or credited if the cancellation ends the subscription before the next bill. A Person leaving does not by itself entitle you to a refund (section 10).
Prices. Our published prices are introductory and may change for new customers at any time. For an existing subscription we give at least 30 days’ notice by email before a new price applies to a renewal; you may cancel before it applies.
Taxes. Before you pay, the checkout shows the total price and any tax that applies. Paddle calculates, collects and remits sales taxes and VAT/GST as merchant of record.

9. Purchases through Paddle

Our order process is conducted by our online reseller Paddle.com. Paddle.com is the Merchant of Record for all our orders. Paddle provides all customer service inquiries and handles returns. Product support stays with us at support@rindo.io. Until self-serve checkout is available, Team is arranged with us by agreement.

When you buy Team you contract with Paddle under its Buyer Terms for the purchase, and with us under these Terms for the Service. The Paddle company that sells to you is named at checkout and on your receipts; it varies by where you are. Paddle collects your payment details and billing address; we never receive your card number. Your receipts and tax invoices come from Paddle, and Account → Billing → Manage billing opens Paddle’s customer portal for your payment method, invoices and cancellation.

10. Renewal, cancellation and refunds

Team renews monthly until cancelled. You cancel in Paddle’s customer portal (Account → Billing → Manage billing); the cancellation takes effect at the end of the paid period, and you can undo it there before then. When it takes effect, your account returns to Free with its quotas; nothing is archived or deleted.
Refunds follow our Refund Policy and Paddle’s Buyer Terms. The refunds we offer voluntarily do not limit any right the law gives you or any refund commitment Paddle makes. If you are a consumer in the EEA or the UK, the withdrawal rules that apply, and any request to start the Service at once, are disclosed at checkout; accepting these Terms alone does not waive them.

11. If a payment fails

If a renewal payment fails, Paddle retries it and sends payment-recovery notices under the settings that apply to the subscription. During that time the Projects you own are limited: no new members can be added and no new Agent jobs can be queued, while everything else works. If the payment is still not made, the subscription is paused and your Projects become read-only until you fix the payment method in Manage billing and press Resume in Account → Billing; resuming charges a new period at once. If you cancel with nothing owed, your account returns to Free. If the subscription is cancelled or ends while a payment is still owed, your Projects stay read-only until you buy Team again; nothing is deleted.

12. Availability, support and changes to the Service

We work to keep the Service available and announce planned maintenance where we can, but we offer no uptime guarantee on Free or Team.
Support is by email at support@rindo.io; security reports go to security@rindo.io; sales to hello@rindo.io.
We may change, add or remove features to maintain, improve or secure the Service or to meet legal requirements. For a material reduction in paid functionality, or a change that requires you to migrate data, we give at least 30 days’ notice by email unless urgent security or legal action requires less, and we keep your export available. If a material reduction takes effect during a paid period, you may cancel and ask for a proportionate refund of the affected unused period.
Features marked beta or preview may change or be withdrawn. Their stated limitations do not exclude our confidentiality, data-protection or other non-excludable duties.

13. Suspension and termination

By you. Close your account at any time under Account → Close account (section 14).
By us, for cause. We may suspend your account or restrict a Project where reasonably necessary to address a material breach, comply with law or protect the Service or other people, in proportion to the reason. We tell you the reason by email unless the law or an active security investigation prevents it, and normally give you 14 days to cure a breach that can be cured before we terminate. We may act at once where serious harm, unlawful activity or an urgent legal duty requires it. You may ask support@rindo.io to review the action. A Project taken down by the operator can be restored for 7 days, so contact us promptly.
By us, for convenience. We may end the Service for everyone with at least 90 days’ notice, during which exports stay available, and we arrange through Paddle a proportionate refund of prepaid fees for any period after we stop providing the paid Service.
Effect. When your account or subscription ends, accrued payment and refund rights, section 4 (your ownership and the licence for retained Content), sections 14 to 20 where relevant, and sections 23 to 25 survive for as long as their subject matter requires. Retention of data follows the Privacy Policy.

14. Closing your account

Closing is yours to do, confirmed with your password or an emailed code. It is refused while you own a Project that is neither archived nor deleted; hand it over, archive it or delete it first (the product offers it to a member for you).
At once: every session, access token, connected app, runner and pool token you created ends and jobs queued on your pools are cancelled; invitations and ownership offers you sent are withdrawn; an export still building is cancelled. Download your export first.
For 14 days you can cancel the closure by signing in with your password or an emailed code (single sign-on never cancels it). After that, the closure process removes your email address and display name, replaces your password with one nobody can use, removes your sign-in links, and replaces your username with a placeholder; a protected record of your former username stays so nobody can take it. Your teammates see “Deleted user” where your name was from the moment you ask to close. Your contributions to shared Projects stay, attributed to that placeholder, so your teammates’ history stays intact; the account record, your memberships, the record of which Terms you accepted and your preferences also stay. The Privacy Policy explains why, for how long, and how to ask for more. An account lock or a legal hold can delay the process.
Closing also cancels your Team subscription — at the end of the paid period while it is active (or when the closure process runs, if that comes first), at once while it is past due or paused — and cancelling the closure does not restore it.

15. Open-source components, intellectual property and feedback

The Service, its design and its marks belong to Rindo and its licensors. Nothing in these Terms transfers them. The Rindo name and the layered-plans mark may not be used to suggest endorsement. Quoting this site with attribution is fine.
The Service includes open-source components under their own licences. The clients you install are Apache-2.0 and are not part of the Service.
If you send us product feedback, you permit us to use it to improve and operate the Service without payment. This does not let us publish your confidential information or change who owns your Content.

16. Confidentiality

Each of us protects the other’s non-public information with reasonable care, uses it only to perform this agreement, and discloses it only to people, advisers or suppliers who need it for that purpose and are bound to protect it. Your non-public Content is your confidential information; our unpublished roadmap and non-public pricing are ours. This does not cover information that is independently developed, already lawfully known, lawfully received without restriction, or made public without a breach. If the law requires a disclosure, the receiving party gives prompt notice where lawful and discloses only what is required. Personal data stays protected by the law that applies to it even where a confidentiality exception applies.

17. Privacy and data protection

Our Privacy Policy explains how we handle personal data; accepting these Terms acknowledges that notice. Where we process Content only on behalf of, and for the purposes of, a customer that is an organisation (which can be an individual acting in a business capacity) under this written agreement, we act as that customer’s data intermediary under Singapore’s Personal Data Protection Act and as its processor where the GDPR or UK GDPR applies: we process the Content only to provide the Service, carry out its authorised settings and requests, and comply with law; we protect its confidentiality, apply appropriate safeguards, engage suppliers under suitable data-protection terms, and help with rights requests, deletion and breach response. For processing we decide ourselves — account administration, billing records, security, legal compliance — and where those conditions are not met, we carry the obligations of an organisation or controller ourselves. If the law that applies to you requires a separate data processing agreement, write to privacy@rindo.io and we will put one in place; it is not limited to paid plans.

Where we act as a data intermediary and have credible grounds to believe a personal-data breach has occurred in Content processed on your behalf, we notify you without undue delay, with the information we have, without waiting for the investigation to finish. We also meet our own notification duties under the law.

18. Warranties and disclaimers

We warrant that we provide the Service with reasonable skill and care. For business customers, and only where lawful, the Service is otherwise provided “as is” and “as available”, without implied warranties of merchantability, fitness for a particular purpose or non-infringement, and we do not promise uninterrupted or error-free operation or the accuracy of Agent output. This does not remove the express commitments in these Terms. Consumers keep every mandatory standard, guarantee and remedy the law gives them.

19. Limitation of liability

For business customers, subject to the exceptions below: neither of us is liable to the other for indirect or consequential loss, and our total liability for claims arising from one event or a connected series of events is limited to the greater of the Service fees you paid through Paddle in the 12 months before the first such event and US$100.

For consumers, we are responsible for reasonably foreseeable loss caused by our breach of these Terms or our failure to exercise reasonable skill and care, subject to the law that applies; the business exclusions and cap above do not apply to you.

Nothing in these Terms excludes or limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, for wilful misconduct, or for anything that cannot lawfully be excluded or limited; nor does it reduce an amount we or Paddle must refund, or restrict your non-excludable data-protection rights or your recourse to a regulator.

20. Indemnity

For business customers: you will defend and indemnify us against third-party claims to the extent they are caused by your unlawful Content or your material breach of sections 4 or 5, including authorised Agent actions that amount to such a breach, but not to the extent a claim is caused by our own breach, negligence or misconduct. We will notify you promptly, cooperate reasonably at your expense, and let you control the defence with competent counsel; no settlement may admit fault on our behalf or impose a non-monetary obligation on us without our consent, not to be unreasonably withheld. This indemnity does not apply to consumers.

21. Export control and sanctions

You must not use the Service in breach of export-control or sanctions laws that apply to you, to Rindo or to the transaction, or where those laws prohibit us from providing it to you.

22. Changes to these Terms

We may change these Terms to reflect changes in the Service, the law, security or our business. For a material change we give at least 30 days’ notice by email and in the product, explaining the change and when it takes effect, and the app asks you to accept the new version before you continue. If you do not agree, cancel any renewal, export your data and close your account; the previous version governs you until then. A price change follows section 8. Where a legal requirement takes effect sooner, we give as much notice as we can. Each published version stays available from this page.

23. Governing law and disputes

These Terms are governed by the laws of Singapore, without depriving a consumer of the mandatory protections of the law that applies to them.

For business customers, any dispute arising out of or in connection with these Terms, including any question regarding their existence, validity or termination, shall be referred to and finally resolved by arbitration administered by the Singapore International Arbitration Centre in accordance with the Arbitration Rules of the SIAC for the time being in force, which rules are deemed incorporated by reference in this clause. The seat of the arbitration shall be Singapore. The Tribunal shall consist of one arbitrator. The language of the arbitration shall be English. The arbitration agreement is governed by Singapore law.

If you are a consumer, this arbitration agreement does not apply to you. You may bring a claim in a court or tribunal that has jurisdiction under the law that applies to you, including where you live, and we bring claims against you only in a forum that law permits.

Either party may bring an eligible claim before a small-claims court or tribunal with jurisdiction, and either party may seek urgent interim relief from a competent court. Nothing prevents a complaint to a regulator.

24. General

Notices to you go to your account’s email. Notices to us go to support@rindo.io. These Terms and the Refund Policy, together with any cloud agreement, order form or data processing agreement we sign with you, form the whole agreement about the Service; the Privacy Policy is our notice of data practices and does not by itself amend this contract. If a provision is unenforceable, the rest stands. You may not assign these Terms without our consent, not to be unreasonably withheld; we may assign them to a successor of the business, including the company that incorporates it, with notice, if the successor takes on our obligations. No waiver is implied. These Terms are offered and accepted electronically under Singapore’s Electronic Transactions Act.

25. Contact

support@rindo.io (support and notices) · security@rindo.io (vulnerabilities) · privacy@rindo.io (your data) · hello@rindo.io (sales)