The rules of the road.

Last updated: 26 September 2026

These Terms of Service ("Terms") govern your access to and use of the Zora Discord bot and its associated website and dashboard (together, the "Service"), operated by the Zora Team. By adding Zora to a Discord server, using any of its commands, or signing in to the dashboard, you agree to be bound by these Terms.

1. Discord's Terms come first

Zora runs on Discord and is subject to Discord's rules. As a condition of using the Service you agree that you will:

• comply with the Discord Terms of Service and the Discord Community Guidelines at all times;
• meet Discord's minimum age requirement in your country (13, or older where local law requires it) and have the legal capacity to accept these Terms;
• not use the Service in any way that is prohibited by Discord's Developer Terms of Service and Developer Policy.

If your use of Discord is suspended or terminated, your right to use the Service ends with it.

2. What the Service is

Zora is a multipurpose Discord bot. Depending on what is enabled, it provides AI chat, moderation and auto-moderation, anti-nuke protection, logging, welcome and farewell messages, leveling, music, tickets, giveaways, reaction roles and related tools, and a web dashboard for configuring them. Features may be added, changed, limited or removed at any time, and some features depend on third-party services that may be unavailable from time to time.

3. Acceptable use

You agree not to use the Service for any purpose that is illegal or prohibited by these Terms, by Discord's rules, or by applicable law. In particular, you agree not to:

• spam, flood, or otherwise abuse commands, the dashboard, or the bot's APIs, or attempt to evade rate limits;
• exploit, probe, or attempt to discover bugs or vulnerabilities in the Service, or interfere with its operation or that of other users;
• use the Service to harass, defame, threaten, dox, or harm others, or to distribute malware, scams, or unlawful content;
• use the Service to post or generate content that is illegal, sexually explicit where not permitted by Discord, hateful, or that infringes anyone's rights;
• use the Service to automate a user account (self-bots), to farm artificial activity, or to misrepresent the Service as your own product;
• resell, sublicense, or claim ownership of the Service, or access it by any means other than the interfaces we provide.

You are responsible for your own conduct, for the content you or your server generate, and for every configuration you enable on a server you manage.

4. Data we do not store

We designed Zora to keep as little as possible, and none of it personal. Specifically, the Service does not store:

• Message content. Command text, chat, attachments and embeds are not written to any database. A message is held in memory only long enough to respond to a command, evaluate auto-moderation, or fire a trigger, and is then discarded.
• Personal information. No names, usernames beyond the Discord ID, email addresses, phone numbers, postal addresses, dates of birth, or payment or billing information.
• Credentials. We never see or store your Discord password, email, or token. The dashboard signs you in through Discord's own OAuth flow; we receive only the basic profile Discord returns (your ID, username, avatar and the list of servers you can manage).
• Your server's contents. No message history, no full member lists, no uploaded files, no voice or audio recordings.
• Your raw IP address. See section 7 — visitor counting keeps only an irreversible hash.
• Any location, device fingerprint, advertising identifier, or behavioural profile.

5. Data we do store

The Service must keep a small amount of configuration to work. Everything below is scoped to a Discord ID and exists to make a feature you turned on behave as you set it:

• Server settings. Your prefix, the channels and roles chosen for welcome, farewell, logging, auto-moderation, anti-nuke, join-to-create, reaction roles and similar features, feature on/off switches, thresholds and durations, custom message templates you write, auto-react triggers and emojis, and auto-moderation word lists.
• Moderation records. Case entries such as warnings, mutes, kicks, bans and temporary roles, including the affected user ID, the moderator's ID, the reason, and the time — kept so your staff can review what happened and appeal fairly.
• Member-scoped feature data. Things a member created and would expect to persist: AFK status and reason, to-do lists, music favourites and playlists, a profile description and background, no-prefix grants, and temporary voice-channel state.
• Giveaway data. Entries and winners, by user and message ID, for as long as the giveaway exists.
• Abuse-prevention records. A blacklist of user or server IDs, with a reason, used only to keep the Service and its users safe.
• Dashboard session. While you are signed in, your session is held so the dashboard knows who you are; it ends when you sign out or it expires.

None of this is sold, rented, shared, or used for advertising. It is used solely to run the features you configured.

6. How your messages are handled

Zora necessarily receives the messages in servers where it can read them, but it treats them as transient:

• a message is read only to decide whether it is a command, whether it trips auto-moderation, or whether it matches a trigger you configured;
• if a reply is needed, the relevant text is used to produce that reply and is not retained afterwards;
• nothing is added to a database, and message history is not reconstructable from anything we keep.

If you enable a feature that sends text to a third-party service — for example an AI prompt, a lyric lookup, or a web search — only the text needed for that one request is sent, under section 8.

7. Cookies, sessions and visitor counts

The public site sets no advertising or tracking cookies. It uses:

• A session cookie when you sign in to the dashboard, so you stay signed in while you use it. It is essential to the login and is removed when it expires or you sign out.
• A visitor count. To know how many people visit, the site stores a salted SHA-256 hash of the incoming IP address together with the date. The raw IP is never stored, and the hash cannot be reversed to recover it. It is used only to count unique daily visits.

8. Third-party services

Some features rely on services outside Zora. When you use those features, the minimum information needed is sent to the relevant provider under their own terms:

• Discord — all bot and login functionality, under Discord's Terms and Developer Policy;
• Music infrastructure (Lavalink nodes) — the track query or URL you ask for, so audio can be streamed;
• AI providers — the prompt you send to an AI command, used to generate that reply;
• Lyrics and search providers — the song title or search term you supply for a lyrics or web-search command;
• Image-generation providers — the prompt you supply to an image command.

We do not control these providers and are not responsible for their practices; please review their terms before using the corresponding feature. These integrations can be turned off on your server at any time.

9. Retention and deletion

We keep data only while it is useful for the feature it belongs to, and we delete it when that purpose ends:

• clearing a setting in the dashboard, or turning its feature off, removes or empties the stored configuration;
• ending a giveaway, or removing its entry, removes the associated entries;
• removing Zora from a server stops all processing for that server immediately.

You may ask us to delete the data associated with your server or your user ID at any time by contacting us in the support server. We will action reasonable requests within a reasonable period, except where we must keep a minimum record to prevent abuse or to comply with the law.

10. Security

We take reasonable technical measures to protect what we hold, including hashing visitor addresses and limiting what is stored in the first place. No service can promise perfect security, so please do not send the Service anything you would not want stored, and never share your Discord password or token with anyone, including us — we will never ask for them.

11. Intellectual property

The Service, its name, logo, and its original content, features and functionality are and remain the exclusive property of the Zora Team, and are protected by copyright and other laws. You may not use our name or logo in connection with any product or service without our prior written consent. You retain whatever rights you hold in the content you provide; you grant us only the limited permission needed to operate the features you use.

12. Availability and changes to the Service

The Service is offered on an "as is" and "as available" basis. Features may be added, changed, limited, put behind limits, or removed, and the Service may be interrupted for maintenance or because a third-party dependency is down. We do not guarantee any particular uptime, and we are not liable for interruptions.

13. Termination

You may stop using the Service at any time by removing Zora from your server and signing out of the dashboard. We may suspend or terminate your access, or block a server or user, immediately and without prior notice if you breach these Terms, if we are required to by law or by Discord, or to protect the Service or other users. Repeated or serious abuse may result in a permanent block.

14. Disclaimers and limitation of liability

The Service is provided without warranties of any kind, whether express or implied, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the Service will be uninterrupted, secure, timely, or error-free, or that any content obtained through it is accurate.

To the maximum extent permitted by law, the Zora Team shall not be liable for any indirect, incidental, special, consequential or punitive damages, or for any loss of data, goodwill, profits, or other intangible losses, resulting from your access to or use of, or inability to access or use, the Service. Where liability cannot be excluded, it is limited to the amount you paid us, which for the free Service is zero.

15. Changes to these Terms

We may modify or replace these Terms at any time. When we do, we will update the "Last updated" date above and, for material changes, give notice on this page or in the support server. By continuing to access or use the Service after a revision takes effect, you agree to be bound by the revised Terms. If you do not agree, stop using the Service.

16. Governing law

These Terms are governed by the laws applicable at the operator's place of establishment, without regard to conflict-of-law rules. Nothing in these Terms limits any right you have under the mandatory law of your own country of residence.

17. Contact

Questions about these Terms or about the data described above are welcome. Reach us in the support server, or read how we handle data in more detail in the Privacy Policy.