Terms of service

1.1Re0 provides retrieval and citation over knowledge libraries. We return context passages carrying their source, version and citation. We do not make judgements for you, and we are not responsible for decisions taken on the basis of those passages.

1.2Using the service requires an account. You may link several sign-in methods, but you are responsible for everything that happens under the account, including calls made with an API key. Revoke a leaked key in the console immediately.

1.3We grant you a non-exclusive, non-transferable right to access public libraries and your own private libraries within your quota. That licence does not cover reselling retrieval results in bulk, replicating the platform index, or using retrieval output to rebuild a dataset that substitutes for this service.

1.4You may stop using the service and close your account at any time. If you seriously breach these terms, the acceptable use policy or applicable law, we may suspend or terminate the account; unless the law requires otherwise, we give notice and a period to put things right first.

1.5After an account is closed, private libraries and their indexes are deleted. Where a published public library has already been cited by others, its version history remains.

2.1Do not submit content you have no lawful right to use, and do not upload sensitive personal information, credentials, keys or export-controlled material.

2.2Do not work around quota and billing: no sharing accounts to exceed plan limits, no automated bulk registration, and no load testing well beyond normal use. Contact us in advance for capacity planning.

2.3Do not use the service to produce or distribute unlawful content, malware or phishing material, or to gain unauthorised access to anyone else’s systems.

2.4Security research is welcome, but keep it within your own account and data, do not affect other users’ data, availability or quota, and report findings through the security disclosure channel.

3.1Content you submit belongs to you or to the original rights holder. To provide the service you allow us to fetch, parse, chunk, index and cache that content, and to return passages to callers according to the visibility you set.

3.2Public libraries are published after review and keep their source attribution and licence information in retrieval results. The original source’s licence takes precedence over the rules on this page; being indexed never widens the licence a source grants.

3.3Ownership of a library is established solely by a DNS TXT record or a well-known file. Writing a public key, token or any declaration into a config file (such as re0.json) grants no ownership — being able to write that file is not the same as controlling the source.

3.4If you believe indexed content infringes your rights, submit an appeal through the content channel, stating the basis of the right, the Library ID involved and the specific passages. Once confirmed we will remove, correct or restrict the affected version, and keep a record of the action.

3.5Repeated and evident infringing submissions will suspend the libraries concerned, and serious cases will terminate the account.

4.1The billing unit is the API call: one accepted API or MCP query is 1 call, regardless of chunk count, token count or cache state. Client errors and refusals after a quota is exhausted are not billed.

4.2Quota is settled per monthly period. Deduction order is fixed: plan allowance first, then call pack balance. Packs do not auto-renew and their balance does not expire.

4.3When quota is exhausted, new billable calls pause. Published content and account data are unaffected.

4.4Claimed public libraries take part in revenue share, allocated linearly from platform revenue by successful retrievals rather than weighted by Trust Score. Platform-owned, private and unclaimed public libraries do not take part. Payout thresholds and holding periods follow the rules published on the pricing and settlement pages, and payouts run through an external payment provider.

4.5Price changes are announced in advance and take effect from the next billing period. Call packs already purchased are unaffected.

5.1This refund policy forms part of these terms and covers Pro subscriptions and call packs paid directly to Re0. Purchases made through an app store, cloud marketplace or reseller follow that channel’s published refund rules. Payments, invoices and refunds are executed by an external payment provider; we hold no user funds.

5.2Within 7 calendar days of your first Pro subscription charge, you may claim a full refund provided the period has consumed no more than 10% of the plan allowance. On refund the plan drops to Free immediately, and libraries beyond the Free limits become read-only.

5.3Within 7 calendar days of a renewal charge, the same consumption condition applies for a full refund. You can also turn renewal off in the console at any time: it takes effect at the end of the current period, and a period already begun is not refunded pro rata.

5.4Call packs are one-off purchases. Within 30 calendar days of purchase you may claim a refund for the calls still unused, in proportion; calls already consumed are not refunded. After 30 days packs are no longer refundable, but the balance does not expire and stays usable.

5.5If the service is continuously unavailable for more than 24 hours in a billing period through our fault, you may claim compensation: call quota equivalent to the downtime, issued as credit rather than cash. The status page record determines the incident.

5.6No refund is given for: accounts suspended or terminated for breaching these terms or the acceptable use policy; calls consumed by builds that completed successfully; amounts already settled to publishers as revenue share; and repeated refund claims from the same party that amount to abuse.

5.7To claim, write to support@re0.com with your account email, the transaction reference and the reason. We reply within 5 business days; approved refunds are returned by the external payment provider to the original payment method, and arrival depends on your bank, typically 5 to 10 business days.

5.8Nothing in this policy limits mandatory refund or withdrawal rights that consumer law gives you; where the two conflict, the law prevails.

6.1The service is provided "as is". We work to keep it available and publish incidents on the status page, but we do not promise uninterrupted or error-free operation.

6.2We are not responsible for the accuracy of third-party source content, nor for decisions you make on the basis of retrieval results, nor for indirect loss, lost profit or lost data arising from them.

6.3To the extent the law allows, our aggregate liability in any circumstance is capped at the total fees you actually paid Re0 in the 12 months before the event giving rise to the claim.

6.4Non-performance caused by force majeure, upstream network failure or third-party service outage is not a breach.

7.1When the terms change we update the effective date on this page; material changes to rights or obligations are announced in the product or by email in advance. Continuing to use the service after a change takes effect means you accept it.

7.2For questions about these terms or content appeals, write to legal@re0.com; for refunds, write to support@re0.com; for security issues, write to security@re0.com.