Terms of Service

Version 3.10 — effective 31 August 2026

These Terms govern your use of owaua, a privately operated Discord bot. The public contact for this instance is ckazros@owaua.com. The full text lives at https://owaua.com/owaua/terms. The Privacy Notice is at https://owaua.com/owaua/privacy.

To agree to this exact version, use /tos or !tos, click the Discord button, read this page, tick the acceptance box, submit it, and return to Discord. A typed tos accept command no longer records acceptance. Until the website flow is complete, the bot will not chat or run ordinary commands. /privacy, /tos, /help, /about, and DM-block commands still work without acceptance so you can read this, export or delete data, and refuse the service.

Accepting these Terms is not consent to store raw message history. That is a separate opt-in described in the Privacy Notice.

Opening or submitting the acceptance page processes your client IP address with your Discord user id for abuse and block-evasion prevention. The raw address is not stored; a keyed network token is retained for at most 30 days. Cloudflare also supplies the network ASN and organization name. owaua uses those in memory to refuse VPN, proxy, Tor, and hosting/datacenter networks; it does not store the ASN or organization name. A match to a currently blocked account hard-blocks the visiting Discord account regardless of Discord account age. Shared, workplace, school, and mobile-carrier networks can be inaccurate, and VPN classification can be wrong. Contact the address above to appeal.

1. Who operates this

owaua is not a registered company in this codebase. This instance is run by a private operator. The bot process and its SQLite database run on Daki Hosting infrastructure in Germany. The public website and legal pages are reached through Cloudflare. Discord remains a separate service with its own terms.

The Discord user id configured as the bot operator (OWAUA_OWNER_ID) is exempt in code from the acceptance gate, the automatic ToS strike/block path, and some rate limits, and can use operator tools such as the DM-relay CLI. That exception is real. It does not place the operator above Discord's rules, Daki's rules, or the law.

2. Eligibility

You must be allowed to use Discord. Discord's current age minimum is 13 (or higher where Discord or local law requires it). owaua does not collect dates of birth and does not independently verify age. If you are not allowed to use Discord, you are not allowed to use owaua.

You may only use owaua in servers and channels where you are permitted to be, and only with a Discord account you are authorized to use.

3. The service, honestly

owaua is a Discord assistant. It can chat, remember facts you or moderators store, run optional moderation helpers, describe images, speak in voice channels, look up web results, and propose Discord administration actions. It is not a lawyer, doctor, journalist, or infallible database.

4. Acceptable use

You must follow Discord's Terms of Service, Discord's Developer Policy as it applies to bots you interact with, the rules of the server you are in, and applicable law.

Do not use owaua to:

Automated detectors look for those categories with regular expressions and with optional model flags. Detectors miss things and also false-positive. A miss is not permission. A false positive can still warn or block you until the operator reviews it.

5. Enforcement

Only clear, targeted detector hits on the categories above warn on the first two strikes and hard-block on the third (TOS_STRIKE_LIMIT = 3). A confirmed ClamAV malware signature on a non-media attachment is the exception: the bot deletes the message where Discord permits, sends an incident report to a private staff channel, and immediately hard-blocks the non-bot sender. Scanner outages, timeouts, and file-size limits can remove an unscanned attachment under the fail-closed setting but do not block its sender. Prompt-leak attempts have their own strike counter (block at 3). Repeated model-policy flags can also block. Rate-limit noise does not add ToS strikes.

A hard block stores your Discord user id, a reason, a category, guild and channel ids if known, a display tag, and a SHA-256 prefix plus length of the offending text — not the raw message. The operator can unblock ToS blocks through an owner CLI. Manual operator bans are separate and are not cleared by the ToS-review CLI.

The operator may also add ids to a static block list. Blocked users can still use privacy/ToS/help commands so they can export or delete data. Privacy deletion removes the identifying incident details from a confirmed-malware block but retains the user id, minimal malware category/evidence hash, and block state until the operator explicitly unblocks it.

Web acceptance uses a random, single-use capability linked to the Discord account that requested it. It expires after 15 minutes. Recent keyed network tokens are compared against accounts that are currently blocked. Visiting or submitting the acceptance page from a matching network hard-blocks that Discord account regardless of Discord account age. When a block is created, the blocked account's network token is retained so the website can refuse later visits from the same network. Accounts that already accepted from that network before the block are moved into owner review rather than auto-blocked; they stay locked until the operator allows them. Unblocking the source account forgets that network token.

Acceptance from a VPN, proxy, Tor exit, or hosting/datacenter network is refused. That decision uses Cloudflare's ASN and organization name for the client IP. It does not hard-block the Discord account; turn the network off and open a fresh acceptance link. Classification misses some VPNs and can flag shared or unusual networks by mistake.

6. Owner access discretion

The bot owner/operator may refuse, restrict, suspend, or permanently end any person's access to owaua at any time, for any reason or no stated reason, including where that person has not violated these Terms. The owner may apply that decision globally or only to a server, channel, command, feature, or other part of the service, and may do so with or without prior notice. No user has a right to continued access or to receive a reason for an access decision. Attempts to evade an access restriction are prohibited. This discretion is subject to applicable law, Discord and Daki rules, and rights that cannot legally be waived; blocking access does not remove any applicable privacy or data-rights process described in the Privacy Notice.

7. Servers and administrators

Adding owaua to a server is an administrator decision. Administrators can enable or leave disabled raw history, passive moderation, server-rules review, voice transcription, and the dashboard community/automation modules. New high-impact dashboard modules are off by default; existing safe features remain enabled for compatibility. Configuration changes are attributed to the dashboard session and retained in an audit trail.

Administrators remain responsible for the actions they approve through /act and for staff review of moderation or rules findings. owaua does not ban, kick, timeout, or delete messages merely because a model said so. Staff buttons and confirmation previews control model-proposed actions. Deterministic rules explicitly configured by administrators (for example an account-age autoban or banned-phrase automod rule) are a separate automation path.

8. Third-party services

Using owaua means Discord delivers your content to the bot, and the bot may send the minimum needed prompt, image, or audio to whatever AI, search, speech, or chart providers this instance has configured. Those providers have their own terms. The Privacy Notice lists the classes of provider the code can call.

Music commands only return a YouTube search URL. The bot does not download or rehost audio. Charts are rendered by constructing a QuickChart URL. Web search may call Tavily and/or DuckDuckGo.

9. Changes

If this document's version string changes, previous acceptances stop working. You will have to read the new version and accept again before ordinary use. That is how the code works; it is not a courtesy email.

10. Termination

You can stop using the bot, reject the Terms, or run /privacy delete. The operator can remove the bot, block you, or shut the instance down. Discord can remove the application. Data handling after that is described in the Privacy Notice, including what deletion does not erase.

11. No warranty

The service is provided as-is. The operator does not promise fitness for a particular purpose, uninterrupted availability, or that outputs are accurate or safe to follow. To the extent the law allows, the operator is not liable for indirect or consequential loss arising from use of the bot. This does not exclude liability that cannot legally be excluded, including for death or personal injury caused by negligence where that rule applies.

12. Contact

Questions, privacy requests, and reports: ckazros@owaua.com.

These Terms are meant to describe the running software. If a sentence here and the code disagree, the code is what the bot will do, and that is a bug in this page which you should report.