Legal

Terms of Service

Last updated 5 November 2026 · Extended enterprise edition · Operated by AuR AI (“AunuCore”, “we”, “us”). Contact: dwia20353@gmail.com · Telegram @AunuHostv.

In short: you get a personal key tied to a paid plan, you must not abuse or resell it, model output comes from third-party providers and may be wrong, and we may suspend keys that break these rules. This summary does not replace the full terms below.

1. Agreement

These Terms of Service govern your access to the AunuCore website, dashboards and API (the “Service”), operated by AuR AI. By redeeming an access key or calling any endpoint, you accept these terms. If you do not agree, do not use the Service.

2. Accounts, keys and webhooks

  • Keys are issued by an AunuCore administrator once a plan is selected and paid for.
  • A key identifies one account. You are responsible for all activity under your key, including usage by your own end users.
  • Keep keys server-side. Do not embed them in mobile apps, browser bundles, public repositories or screenshots.
  • You may rotate your key at any time from your dashboard. Rotation invalidates the previous key immediately.
  • You may issue up to five named secondary keys for separate projects. Secondary keys authenticate as your account, share its plan limits, and may be revoked independently; you remain responsible for their use.
  • You may register up to three webhook URLs. We deliver event notices (usage summaries, quota warnings, key rotations) to the endpoints you register; you must keep them under your control and protect any data received there.
  • We may revoke any key without notice if we detect compromise, fraud, non-payment or abuse.

3. Plans, priority and payment

  • Plans are Free, Personal (Rp50,000 / month) and Business (Rp150,000 / month).
  • Higher plans receive greater throughput, larger context ceilings and a higher dispatch weight. Priority is relative and is not a guaranteed latency figure.
  • Plans are prepaid. Fees are non-refundable once a key has been issued and used, except where required by law.
  • Daily request budgets reset at 00:00 UTC and do not roll over.
  • Upgrades take effect immediately. Downgrades apply at the next renewal unless agreed otherwise.
  • We may change prices or limits with at least 14 days notice. Prepaid periods already purchased are unaffected.

4. Acceptable use

You must not use the Service to:

  • generate or distribute content that is unlawful, defamatory, sexually exploitative of minors, or that incites violence or self-harm;
  • create malware, phishing material or spam;
  • infringe intellectual property, privacy or publicity rights;
  • attempt to extract model weights, reverse-engineer routing internals, or bypass authentication, quota or safety controls;
  • resell raw API access, share your key with third parties, or operate a competing reselling service without a written agreement;
  • run load or penetration tests without prior written permission;
  • submit personal data of others without a lawful basis, or regulated data (payment card, health records) without a separate agreement.

You must also comply with the acceptable-use policies of the model providers your requests reach.

5. Model routing

  • Requests are routed across our inference layer automatically. Model availability may change as we add or retire models.
  • We select providers to keep responses fast and reliable; individual model IDs are stable aliases that may be served by more than one upstream.
  • If every inference route for your request is unavailable, the request fails with an explicit error rather than degrading silently.

6. Third-party model output

Requests are fulfilled by third-party model providers. Their availability, output quality and content policies are outside our control. Output may be inaccurate, biased or offensive. You must review output before relying on it, and must not present it as professional legal, medical or financial advice.

7. Your content

You retain all rights in the prompts you send and, as between you and us, in the output you receive. You grant us a limited right to process your content to operate the Service, enforce these terms and produce aggregate statistics. We do not use your prompts to train models.

8. Availability, support and consent

The Service is provided on a best-effort basis. Published availability figures are historical and are not a contractual SLA unless your plan states otherwise. Support targets are: Basic — community; Personal — 24 hours by email; Business — 4 hours priority. Planned maintenance and material platform events are announced on the status page and through in-product announcements where practical.

When you submit a support request you must explicitly accept these Terms and our Privacy Policy via the consent checkbox on the support form. Submitting the form with the box ticked constitutes your signed consent for us to process the request and the contact details in it, solely to respond to you. Requests submitted without consent are rejected by the platform.

9. Suspension and termination

We may suspend or terminate access immediately for breach of these terms, non-payment, legal obligation, or risk to platform integrity. You may stop using the Service at any time. On request we delete your key and profile within 30 days, subject to legal retention duties.

10. Disclaimers and liability

The Service is provided “as is” and “as available”, without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose and non-infringement. To the maximum extent permitted by law, our aggregate liability arising out of or relating to the Service is limited to the fees you paid in the three months preceding the event giving rise to the claim. We are not liable for indirect, incidental, special, consequential or punitive damages, nor for lost profits, data or goodwill.

11. Indemnity

You will indemnify and hold harmless AuR AI and its personnel against claims, damages and reasonable costs arising from your use of the Service in breach of these terms or applicable law.

12. Changes

We may update these terms. Material changes are announced on this page and, where we hold your email address, by email at least 14 days before they take effect. Continued use after the effective date constitutes acceptance.

13. Governing law

These terms are governed by the laws of the Republic of Indonesia. Disputes will be resolved in the competent courts of Indonesia, without prejudice to mandatory consumer protections in your jurisdiction.

14. Enterprise terms

  • Order of precedence. A signed enterprise agreement or order form with AuR AI prevails over these terms for that customer to the extent of any conflict.
  • Support. Enterprise support targets follow Section 8 (Business — 4 hours priority). Support is provided in English and Indonesian via the support page, email and Telegram.
  • Availability reporting. Live component status is published on the status page. Published figures are informational and are not a contractual SLA unless an enterprise agreement states otherwise (Section 8).
  • Invoicing. Enterprise plans may be invoiced monthly in IDR; keys are provisioned once payment is confirmed, as in Section 3.
  • Security documentation. Our security practices are summarised on the security overview; enterprise customers may direct security questionnaires to dwia20353@gmail.com.

15. Platform intellectual property

The Service, including the gateway software, routing logic, website, documentation and the AunuCore and AuR AI names and marks, is owned by AuR AI or its licensors. These terms grant you no rights in that property except the limited right to use the Service as described. You must not copy, frame or mirror any part of the Service, or use our marks, except as permitted in writing. Feedback you send us may be used without restriction or payment.

16. Confidentiality

Each party must protect the other’s non-public information — including your API keys, account data and any enterprise pricing — and use it only to perform under these terms. This duty does not apply to information that is public without fault, already known, or required to be disclosed by law (with notice to the other party where lawful).

17. Compliance

You must comply with applicable laws in your use of the Service, including export-control and sanctions laws that apply to you, data-protection law for any personal data you submit (Section 4), and the acceptable-use policies of upstream model providers. You must not use the Service from, or for the benefit of, any jurisdiction or party where that use would be unlawful.

18. Notices and contact

Notices under these terms are given by email or through the Service. You can reach us at dwia20353@gmail.com, via Telegram @AunuHostv, or through the support page. Keep your account email current — notices to your registered address are effective when sent.

19. General

  • Entire agreement. These terms, the Privacy Policy and any enterprise agreement or order form between us are the entire agreement about the Service and replace earlier understandings.
  • Severability. If a provision is unenforceable, the rest remains in effect and the provision is read down to the minimum extent necessary.
  • No waiver. Not enforcing a provision once is not a waiver of it.
  • Assignment. You may not assign these terms without our written consent. We may assign them in connection with a reorganisation or transfer of the Service, with notice on this page.
  • Headings. Headings and the “In short” summary are for convenience only and do not affect interpretation.

20. Automated agents, bots and third-party platform integrations

This section applies whenever you connect the Service to an automated agent or bot that interacts with people on a third-party messaging or community platform — for example Telegram, Discord or WhatsApp — or on any similar platform. It supplements the rest of these terms; Section 4 (acceptable use), Section 9 (suspension and termination), Section 10 (disclaimers and liability) and Section 11 (indemnity) apply to agent use in full.

Definitions.

  • “Operator” — the AunuCore account holder who configures, deploys or controls an Agent, whether an individual, a team or a company.
  • “Agent” — any bot, automated client, script, workflow or integration that calls the Service’s endpoints using an Operator’s key, including agents built on messaging-platform libraries, bot frameworks and no-code automation tools.
  • “End User” — a person who interacts with an Agent on a third-party platform. End Users are not AunuCore account holders and have no direct relationship with us.
  • “Platform” — the third-party service on which an Agent operates, such as Telegram, Discord or WhatsApp.

Operator responsibility.

  • The Operator is fully responsible for its Agents: their configuration, system prompts, connected tools and data sources, the content they send, and every action they take or omit.
  • Every call made with an Operator’s key is treated as the Operator’s own act, whether it was triggered by the Operator, by the Agent’s automation, or by an End User’s message.
  • The Operator is responsible for anyone it gives key access to — including employees, contractors and collaborators — and for Agents it operates on behalf of its own clients.
  • An Agent is not a separate legal person and cannot hold rights or duties under these terms; all rights and duties remain with the Operator.

Platform rules and unofficial clients.

  • The Operator must comply with the terms and policies of each Platform its Agents run on, including the Telegram Bot API terms, Discord’s API Terms of Service, Developer Terms and Developer Policy, and the WhatsApp Business Platform / WhatsApp Business API terms and policies, as applicable.
  • Where a Platform’s rules are stricter than these terms, the Platform’s rules govern the Agent’s conduct on that Platform.
  • AunuCore is not affiliated with, endorsed by or acting on behalf of Telegram, Discord, Meta or WhatsApp. We provide the AI gateway only; we do not provide, operate or control your messaging client, bot account, community server or phone number.
  • Unofficial clients. Connecting to a Platform through an unofficial client — including linked-device or WhatsApp Web protocol libraries — may breach that Platform’s terms. The Operator bears that risk in full, including detection, feature restrictions, and temporary or permanent bans of the bot account or number by the Platform. Platform enforcement is outside our control and does not entitle the Operator to a refund (Section 3) or to compensation of any kind.
  • The Operator must not use the Service to evade a Platform’s enforcement, anti-spam or anti-abuse systems, or to continue operating an Agent that a Platform has banned.

Prohibited agent conduct. In addition to Section 4, an Operator must not use an Agent to:

  • send spam or unsolicited bulk messages, or message people who have not initiated contact or given the consent the Platform requires;
  • harass, threaten, stalk or intimidate any person, or coordinate others to do so;
  • commit or facilitate fraud, phishing, scams, social engineering, or deceptive impersonation of any person, brand, institution or official;
  • collect, harvest or infer personal data about End Users or third parties without a lawful basis, or build profiles of people who have not interacted with the Agent;
  • bypass rate limits, request budgets or token quotas — including by rotating keys, splitting traffic across multiple accounts, or re-registering after a suspension;
  • redistribute, resell or share API access with parties not authorised under Section 2, or allow unidentified third parties to drive an Agent with the Operator’s key;
  • present the Agent as a human being, or conceal its automated nature where a Platform or applicable law requires disclosure.

Duties toward End Users.

  • Disclosure. The Agent must clearly identify itself as an automated AI system — in its profile description, greeting or first reply — to the extent the Platform allows.
  • Opt-out. The Agent must offer a working way to stop, such as a stop command, keyword or block, and must honour opt-outs promptly and permanently.
  • Sensitive data. The Operator must obtain any consent required before the Agent requests or processes sensitive personal data from End Users, and must not solicit data the Agent does not need.
  • Data-subject requests. The Operator is the party who answers End Users’ access, correction and deletion requests about their data. Where a request concerns data we process for the Operator, the Operator must forward it to us as described in Section 18 of the Privacy Policy.
  • Human contact. End Users must have a way to reach the Operator — a named contact, channel or support route — for matters the Agent cannot resolve.

Limits, fair use and enforcement.

  • Agent traffic uses the same rate limits, daily request budgets and token quotas as any other traffic on the Operator’s plan (Free, Personal or Business — Section 3). Running an Agent does not create a separate allowance.
  • Operators should implement their own per-End-User limits, queues and backoff, so that one busy chat or one abusive End User cannot exhaust the plan or degrade the Agent for everyone else.
  • We may throttle, queue or suspend a key without prior notice where agent traffic endangers platform stability, shows abuse patterns, or breaches this section and delay would increase harm. Other suspensions follow Section 9.
  • We may require an Operator to pause an Agent while an abuse report or Platform complaint is investigated.

Credentials.

  • Keys used by Agents must be stored server-side as described in Section 2. A key must never be embedded in a public client, a public repository, a shared configuration file or a screenshot.
  • A leaked or suspected-leaked key is the Operator’s responsibility. The Operator must rotate it immediately from the dashboard; we may revoke a compromised key without notice (Section 2).
  • Credentials held by the Platform client itself — a bot token, or the session credentials of a linked device — are the Operator’s assets, not ours. We never receive them, cannot recover them, and are not responsible for their loss or compromise.

Agent output. Output generated for an Agent is third-party model output (Section 6) and may be inaccurate. The Operator who configures an Agent to publish or relay output to End Users is responsible for that publication, including reviewing output where the context requires it, and must not present output as professional legal, medical or financial advice. Output carries no warranty from us (Section 10).

Indemnity for agent use. In addition to Section 11, the Operator will indemnify and hold harmless AuR AI and its personnel against claims, damages, fines and reasonable costs brought by End Users, Platforms or regulators arising from the Operator’s Agents, their conduct, or the Operator’s breach of a Platform’s terms.


Questions? Reach us on the support page. See also our Privacy Policy and security overview.