Privacy Policy

1. Who we are

This policy covers Iris ("the Bot") and its website, dashboard, documentation, verification pages and vote page ("the Website"). The operator of Iris ("we", "us") is the data controller for the data described here. You can contact us about any privacy matter, including your rights, by email or through the support server on Discord (see Contact).

Server administrators choose which features run in their server. When they turn on a feature that records information about members (for example message logging, ticket transcripts, levels or verification), they decide that it is collected in their community, and we store the results for them. This policy explains what we hold either way.

2. What we collect

We collect what Discord makes available to bots through its API, what you type into the Bot or the dashboard, and the limited technical data described in sections 4 to 6. The Bot does not request or receive your email address, and it does not receive presence data (your online status or what you are playing).

From Discord, automatically

• User, server, channel, role and message IDs - Discord's numeric identifiers, used to attach records to the right person, server and place.
• Names and avatars - processed as Discord provides them so the Bot and the dashboard can show who did what. Names are stored where a record has to stay readable after someone leaves, such as ticket transcripts, moderation cases, applications and some logs.
• Account creation date - read from your user ID, which encodes it, so verification and anti-raid can treat very new accounts with more caution.
• Member events - joins, leaves, role and nickname changes and voice channel activity, which the Bot sees in real time and records only where a feature that uses them is on.

Server configuration

Module settings, assigned channels and roles, custom messages, embed and panel designs, welcome cards, thresholds and similar settings made through the dashboard or commands, together with the user ID of whoever last changed them. When settings are reset or imported, a restore point of the previous settings is kept for up to 90 days so the change can be undone.

Records created by features

Each of these exists only in servers where the feature is used:

• Moderation - warnings, mutes, timeouts, kicks, bans and automatic actions, with the target and moderator IDs, time and reason; ban appeals and their outcome; temporary punishments waiting to expire.
• Protection - short-lived counters used to spot spam and raids; raid incidents, including a hashed list of the accounts that joined during them; accounts caught by a honeypot channel; removed-message records (see section 3).
• Verification - see section 4.
• Logs - if a server turns on logging, records of message edits and deletions, member events and server changes.
• Tickets and forms - who opened a ticket, its status and history, its transcript and copies of images posted in it; application form answers, with your user ID and the outcome.
• Levels and activity - your XP, level, message count and voice minutes in a server, and per-day message and voice counts per member and per channel that power the dashboard's activity charts. These are counts, not a copy of what you said.
• Economy - your balance, bank, cooldowns and streaks, and a ledger of every balance change (who, how much, why and when), including payments between members and admin adjustments.
• Community features - giveaway entries and winners; poll votes; suggestions and bug reports you submit and their status; starboard entries; quote cards; counting game progress; event sign-ups; reminders you set; your AFK message; server boost records; self-role and reaction-role panels.
• Invites - which invite a member joined through, who created it, and each member's invite totals, plus a log of manual adjustments.
• Temporary voice channels - the owner, settings and allowed-member list of a VoiceMaster channel while it exists.
• Custom content - custom commands, autoresponders, auto reactions, embed messages and notification subscriptions configured for a server, and the personal command shortcuts you create.
• Preferences - the language you choose for the Bot, and which dashboard guides you have finished or skipped.
• Enforcement records - if we ban a user or server from Iris, the identifier, time and reason, so the ban can be applied and its evasion detected.

What we do not collect

• Your email address, unless you give it to us (for example when you email us).
• Voice or video. The Bot never records, listens to or transcribes voice channels; it only sees who is connected to which channel.
• Card or bank details. Payment details go directly to Stripe and never reach us (section 9).
• Your IP address in the Bot's own records. Voting keeps only a one-way hash (section 5). Web verification (section 4) and the Website's request log (section 6) are the exceptions.
• Anything from third-party trackers, data brokers or advertising networks. We use none.

3. Message content

The Bot reads messages in real time to run commands, auto-moderation, anti-link, autoresponders, auto reactions, levels, the counting game and similar features. Reading a message for those purposes does not store it. Message content is stored only in these cases:

• Message logs - if a server turns on logging, the content of edited and deleted messages (up to 4,000 characters) with the author, channel and time. Kept for 30 days.
• Ticket transcripts - when a ticket closes, a transcript of the channel (message text, author names and IDs, embeds, attachment links and copies of posted images) is kept for the server's ticket history, can be read on the Website by the person who opened the ticket and by the server's staff, and is sent by direct message to the ticket's opener and the staff member who closed it.
• Removed-message records - if a server turns on anti-link or auto-moderation, the content of a message the Bot removed, with the reason, so staff can see why.
• Text you submit on purpose - the text of a form answer, suggestion, bug report, poll, reminder, AFK message or appeal is part of that record.
• Quote cards - when someone uses the quote command on a message, the Bot draws that message into an image and posts it. The image lives in Discord; we keep only the card's style and message references.

4. Verification and alt detection

If a server turns on web verification, you are sent to a page on our Website to complete it. That page exists to tell a real new member apart from a second account of someone already known. When you complete it, we store against your user ID and the server's ID:

• Your IP address - stored as a hash (an HMAC computed with a secret key) for alt matching, and also in readable form against your user ID in the Website's account records, so Iris's operators can find accounts that share an address and block an address from the Website and from verification. It is kept for the same period as the request log addresses (section 6).
• A browser fingerprint hash - a hash of characteristics your browser reports, such as its user agent, platform, language, timezone, screen size, pixel ratio, processor count and how it draws a test image. Only the hash is stored.
• A cookie identifier - a random value stored in a cookie so a later verification from the same browser can be recognised (section 10).
• The outcome and time - whether verification passed or failed, and when.

When any of these match an earlier record, a detection is stored listing the matched user IDs and which signals matched, and the server's staff are alerted. A fingerprint match on its own is ignored because it is too common. By default only records from the same server are compared; a server can choose to compare against verification records from every server that uses Iris verification, so an account already verified somewhere else can be recognised.

VPN check. If a server turns on VPN blocking, your IP address is sent to proxycheck.io at the moment you verify, to ask whether it belongs to a VPN, proxy or hosting provider. The answer is kept in memory for up to six hours and is never written to disk.

A match is a signal, not proof: shared homes, shared networks, universities, mobile carriers and common devices all produce matches between unrelated people. What happens next is decided by that server's staff, not by us. We use this data for alt detection, abuse prevention and enforcing our Terms of Service, and for nothing else.

5. Voting

If you vote for Iris on a bot list or on our vote page, we record your user ID, where the vote came from and when, so we can apply cooldowns, keep your streak and totals, give any reward a server's economy offers for voting, send the reminder you asked for, and detect vote farming. Votes on our own page also store a one-way HMAC of your IP address and a cookie identifier; the address itself is never stored. Bot lists are separate services with their own privacy policies.

6. Website and dashboard

You sign in to the dashboard with Discord, which shares with us only what the "identify" and "guilds" permissions allow:

• Your Discord account - user ID, username and avatar.
• Your server list - the servers you are in and your permissions there, used only to work out which dashboards you can open.
• An access token - held on our server for as long as your sign-in lasts, so Discord does not have to be asked again on every page.

Your sign-in lasts up to 30 days, or until you log out. When you change a server's settings, your user ID is recorded with the change so administrators and we can see who made it. Actions taken by our own staff through internal tools are recorded in an audit log.

Request log

We keep our own log of requests to the Website for security, abuse prevention, capacity planning and debugging. Each entry records the time, the page or endpoint, the response status and how long it took, your IP address, the approximate country your connection comes from (supplied by our network provider), your browser's user agent and the referring site. While a page is open, it also tells us once a minute that someone is viewing it, so we can count live visitors. This is first-party only: no third-party analytics service, tracking pixel or advertising network is involved.

While you are signed in, these entries are linked to your Discord account. That means we can see the addresses and devices an account has signed in from, when, and which pages it requested. We do this to investigate abuse, account sharing and fraud on our own service. It is not used for advertising or profiling, it is not sold or shared, and it is never combined with data from any other site.

Individual entries are deleted after 30 days. An account's sign-in history and its lists of addresses and devices are kept for 180 days after that address or device was last used. Daily totals (visits, popular pages, referring sites), which contain no address and are not linked to anyone, are kept for about 13 months. Only the operator can view these records, behind a separate login with a second factor, and every look at an individual account's record is written to the audit log.

The Website serves its own fonts, scripts and styles, and loads no third-party scripts. Server icons and avatars load straight from Discord's image servers (cdn.discordapp.com), so your browser talks to Discord while you use the dashboard. If you search for a GIF in the dashboard, the search goes from our server to Tenor (Google), and the GIF previews then load from Tenor's image servers.

7. Early access and waitlist

While Iris is in early access, we keep a record of who joined the waitlist (user ID, username, the server you want Iris in and its name, where you signed up from, and your place in line), which invite and referral codes were issued, who redeemed them and for which server, and any founder perks granted. These records are kept for as long as the perks they describe are honoured.

Joining the waitlist asks Discord for one extra permission, "join servers for you", used once to add you to our support server so the Bot can message you when your access is ready. We do not use it for anything else.

8. Sponsored content

The verification page may show sponsored boxes, labelled "Sponsored". We sell and serve them ourselves: the images are hosted on our own server and no advertising network, exchange or third-party tracking script is involved. Nothing about you is shared with an advertiser.

We count how often each sponsored box is shown and clicked, as daily totals per advertisement, so advertisers can be billed for what was delivered. These counts are not linked to your account, your IP address or any identifier, and cannot show that a particular person saw a particular advertisement. Clicking one takes you to the advertiser's site, where their privacy policy applies. Servers on a paid plan do not show sponsored content at all.

If you buy a placement, we store what the booking needs: your Discord ID and username, the advertiser name and any contact email you give us, the artwork you upload, the destination link, any note you send with the request, and a reference to the Stripe payment. We use it to review the request, contact you, run the placement and show you its delivery figures, and keep it for about 13 months for accounting and disputes. See the Advertising Terms.

9. Payments and billing

Iris is free to use; paid plans are optional. Checkout and card processing happen entirely on the systems of our payment provider, Stripe. We never see, receive or store your card number, bank details or billing address. Stripe processes your payment data as its own controller under its own privacy policy.

What we store is only what is needed to apply and support a plan:

• The server ID the plan applies to, and the user ID of the person who bought it.
• Stripe's subscription and customer IDs. These are references, not payment details.
• The plan, its status, the current period end, and whether it is set to cancel.
• Which discount code or complimentary grant applied, if any, and who issued it.
• The IDs of billing events Stripe has sent us, for 7 days, so the same event can never be applied twice.

We do not receive your name or email address from Stripe, and we do not use billing data for marketing. Our legal bases are performance of a contract (Art. 6(1)(b)) for running the plan, legal obligation (Art. 6(1)(c)) for the records tax and accounting rules require, and legitimate interests (Art. 6(1)(f)) for preventing payment fraud and abuse of trials, discounts and refunds. Cancellation and refunds are covered by the Refund and Cancellation Policy.

10. Cookies

The Website sets at most three cookies, all first-party and none readable by scripts:

Each is strictly necessary for something you asked for (signing in, the anti-alt check a server requires, or a fair vote), so they do not need consent under the UK and EU ePrivacy rules. We use no analytics, advertising or third-party cookies, and sponsored content sets no cookie.

11. How we use data and legal bases

We use the data described here only to:

• Run the Bot's features and the dashboard, and apply each server's configuration.
• Keep the moderation, ticket, form and other records a server's staff create.
• Detect and prevent abuse, alt-account exploitation, vote farming, payment fraud and other breaches of our Terms of Service, and apply bans and restrictions.
• Keep the Service secure, find and fix faults, and recover from failures using backups.
• Reply to you when you contact us, report a bug or appeal a decision.

Where the UK or EU GDPR applies, our legal bases are:

• Performance of a contract (Art. 6(1)(b)) - providing the features and dashboard you or your server asked for, including sign-in and any paid plan.
• Legitimate interests (Art. 6(1)(f)) - keeping the Service secure and working, preventing and investigating abuse and fraud, alt detection where a server has turned it on, enforcing our Terms, and keeping the records server administrators create.
• Legal obligation (Art. 6(1)(c)) - where we must keep or disclose data by law.

We do not sell, rent or trade your data, and we do not use it for advertising or profiling. We may disclose data where the law requires it, or where it is needed to protect the rights, safety or property of our users, Discord or ourselves.

12. Third parties

Iris talks to the services below. Most receive nothing about you; where one does, it is listed.

No other third party receives your data.

13. Storage, security and backups

All data is stored in databases on the server that hosts the Bot, split by feature. Access is limited to the operator and the bot administrators, and protected by authentication, a second factor for internal tools, rate limiting and a strict content security policy. IP addresses in the Bot's records are one-way hashed, and dashboard sessions are held on our server rather than in your browser. No system is perfectly secure; if a breach affects your data and the law requires it, we will tell you and the relevant authority.

The databases are backed up every hour to the same server, and once a day an off-site copy is uploaded to a private Discord channel that only the operator can access, so the Service can be restored if the server fails. Backups are checked for integrity and rotated out automatically: every backup from the last 48 hours, one a day for 30 days and one a week for 180 days. A backup holds the data as it was when it was taken, so deleted data can remain in backups until they rotate out.

14. How long we keep data

Most records are deleted automatically by a nightly clean-up. The main windows are below; anything not listed is kept while the Bot remains in the server, or until it is deleted by a server's staff or on request.

Enforcement records (bans, ban evasion, exploitation, fraud and abuse) are kept under our legitimate interest in Art. 6(1)(f), and are the one category we will refuse to erase on request.

15. Who can see a server's data

• The server's administrators - anyone with the Administrator permission in the server can open its dashboard and see and change its configuration and records.
• Transcript readers - a ticket's transcript can also be read by the member who opened it and by roles the server allows to read transcripts.
• Us - the operator and the bot administrators, for maintenance, support, security and abuse investigation. Our staff actions are recorded in an audit log.

Much of what the Bot records is also posted in Discord (log channels, mod actions, announcements) where anyone who can see that channel can read it. That is controlled by the server's own channel permissions.

16. Deleting your data

Server data. Removing the Bot from a server stops all further collection for it straight away, and the server's stored data is deleted automatically 30 days later. If you want it gone sooner, email us or ask in the support server. Administrators can also reset or export each module from the dashboard's Danger Zone, and clear moderation records with the Bot's commands.

Your personal data. Anyone can ask us to delete the data tied to their user ID across every server, such as levels and economy records, giveaway entries, verification records, votes, reminders, preferences and website sign-in history. We confirm the request comes from the account owner before acting.

Deletion applies to the live databases straight away and works through existing backups as they rotate out. Two categories are excluded: the enforcement records described in section 14, and the billing records we must keep for tax purposes.

17. Your rights

Depending on where you live (for example under the UK GDPR, the EU GDPR or the California Consumer Privacy Act), you have the right to:

• Access - get a copy of the personal data we hold about you.
• Rectification - have inaccurate data corrected.
• Erasure - have your data deleted.
• Restriction - ask us to limit how we use your data.
• Portability - receive your data in a structured, machine-readable format.
• Objection - object to processing based on legitimate interests.

To use any of these, contact us. We will reply within one month and may ask you to confirm your Discord account first, so a request cannot be used to reach someone else's data. We never sell or share personal information for advertising, so there is nothing to opt out of under the CCPA. If you are in the UK or EU you can also complain to your data protection authority (in the UK, the Information Commissioner's Office).

These rights are not absolute. We may decline a request that is manifestly unfounded or excessive, that would reveal someone else's data, or that would undermine the enforcement records in section 14.

18. International transfers

The Bot's databases are kept on a server in one country. Discord, Cloudflare, Stripe and some of the services in section 12 process data in other countries, including the United States. Where the law requires it, those transfers rely on appropriate safeguards such as adequacy decisions or standard contractual clauses offered by those providers.

19. Automated decisions

Some features act automatically: auto-moderation can delete messages and apply timeouts, anti-raid and honeypots can kick or ban accounts, and verification can flag or block a possible alt or VPN. They follow rules a server's administrators set, affect your standing in that server only, and a member of that server's staff can review and reverse them. Bans we issue from Iris itself are decided by a person, not by an automated system.

20. Children

The Bot and Website are not intended for anyone below the minimum age to use Discord in their country (13, or higher where local law requires it). We do not knowingly collect data from children below that age; if you believe we have, contact us and we will delete it.

21. Changes to this policy

We may update this policy at any time. The "Last updated" date at the top shows when it last changed, and material changes will be announced in the support server where reasonably possible. Continuing to use Iris after a change means you accept the updated policy.

22. Contact

For privacy questions, deletion requests or any of the rights above, email yourbotdev.daniel@gmail.com or contact us through the support server on Discord. Requests are handled by the operator of Iris, who is the data controller.