Kipp Security Privacy Policy

Effective: October 3, 2026

This policy explains what data Kipp Security ("Kipp": the Discord bot, its website and dashboard) collects, why, how long it is kept, and how to have it deleted. The Cookie Policy covers cookies and the Data Policy covers how long everything is kept and how deletion works. "We" means the Kipp Security team, based in Louisiana, United States, which decides how this data is used. Every protection and moderation feature is free; the optional Kipp Plus adds extras and higher limits. We don't sell data. Some public pages can show ads (see Ads below); server dashboards never do, and people who run a Kipp Plus server see none.

If you have a question, or want to ask for data to be deleted, email [email protected] or ask in the Kipp support server: https://discord.gg/8VHNkm4yU6. You don't need a Discord account, or to be in the support server, to email us.

What Kipp collects

Kipp only receives what Discord sends to bots in servers it has been added to. It stores the following. Everything tied to a server is also deleted 30 days after Kipp leaves that server.

Message content

Kipp reads messages as they are sent so that it can run Auto Mod (spam, scams, malware and blacklisted words), prefix commands, staff-chat leak detection and message logs. It does not store message text in its database, except:

• Message logs: edited and deleted messages are posted to the server's own log channel, if the server turned that on. They are never taken from protected staff channels.
• Snipe: p!snipe keeps the last deleted message in each channel in memory only for one hour. It is never written to disk, and it is gone when Kipp restarts. Messages Kipp removed itself (scams, spam, leaks) and staff-channel messages are never kept.
• Staff-chat leak detection keeps short one-way fingerprints of protected staff messages, never the text itself.
• Member reports keep an encrypted copy of the reported message, so staff can see it even after it's deleted.
• The Discord audit log copy (off unless a server turns it on) posts what Discord's audit log shows to the server's own channel; Kipp doesn't store it.

The threat database

To protect every server, Kipp keeps one shared list of accounts it has banned for nuking, raiding, or posting scams or malware, plus reports from server owners. Each entry holds:

• the user's id, username, display name, avatar and account age;
• what kind of threat they are;
• how many servers banned or reported them;
• a short summary, with channel, role and user mentions and message links removed.

Nothing is added without a person checking it. Every ban Kipp makes for nuking, raiding or scams, and every report sent with /threat-db submit, first goes to the Kipp team's DB Team in the support server, together with the server's name (and, for reports, the reporter's id and any screenshot). Only entries they approve go into the database; rejected ones are never added. Server names are never shown in lookups.

• Kept: until it is cleared on appeal.
• Appeals: anyone can appeal by email ([email protected]) or in the support server. We review every appeal within 14 days and remove entries we can't back up with evidence.
• Server data deletion doesn't remove threat database entries, because they protect other servers.

Global totals

Kipp keeps running totals across all servers: raids, nukes and scams stopped, and how many servers it has joined. These are plain numbers with no user or server details.

The web check, in detail

Servers can choose the web check for verification. It only runs when you open the verify page, sign in and tick the box to agree.

• What happens: after you agree, Kipp reads the network address your browser connects from and sets (or reads) a random id in a cookie on that browser (see the Cookie Policy). Nothing is set or read before you agree.
• What's stored: it turns each into a fingerprint with a secret key, a one-way process that can't be reversed to get the address back. For IPv6 connections only the network part (the first half) is used. The fingerprints are different in every server, so they can't be used to follow you from one server to another.
• What it's compared with: the fingerprints of other accounts that verified in the same server, and that server's network bans.
• Who sees what: if there's a match, the server's staff are told which accounts matched, never your address. Staff can always let you in by hand.
• Extra checks a server may turn on: your browser's characteristics (graphics card, screen and similar) to spot virtual machines, automated or tampered browsers and private windows; your country (from Cloudflare, or from the IP service below); whether your connection is a VPN, proxy or mobile network; whether your Discord account has two-factor authentication; and, only if the server blocks throwaway emails, whether your Discord email is verified and from a disposable provider. Only the result (allowed, or the reason for refusal) is used; the details aren't stored.
• IP intelligence: if the operator set it up, your address is sent to proxycheck.io to learn whether it's a VPN, proxy or mobile network and which country it's in. The result is cached in memory for a day, keyed by a hash, not the address. proxycheck.io handles the request under its own privacy policy.
• If you don't agree, don't tick the box; ask the server's staff to let you in another way.

Messages to the Kipp team

The Kipp icon at the bottom right of the website has Email the Kipp team.

• What's stored: your Discord id and name, the topic, subject and message, the email address if you gave one, whether we may DM you, the server you picked (if you ticked that box), and a one-way fingerprint of your IP address used only to stop spam. Your IP address itself isn't stored. The message, your email and our private notes are encrypted.
• Who sees it: the Kipp team, on the admin panel and in a private channel in the support server. If the operator set up email, it's also forwarded to the support address so we can answer by email.
• How we answer: by Discord DM, by email if you gave one, or both. Every answer also shows under Your messages on the website.
• How long: until the conversation is closed, then 180 days. You can ask us to delete it sooner.

Encryption

Private text is encrypted in the database (AES-256-GCM): staff notes, case reasons, appeal answers and review notes, application answers, ticket topics and close notes, feedback, threat reports, network ban reasons, member reports, comment IP addresses, and messages to the Kipp team (with the email address and our notes). Someone who got a copy of the database without the key couldn't read them.

The website

• Status page: Kipp checks itself once a minute (connected to Discord, database answering). Only those results are kept, in memory, for 24 hours. No visitor data.
• Ads from Google: where an ad from Google could show (public pages only, never a server dashboard), nothing from Google loads until you press Show ads. It then loads in a sealed-off frame that can't see the rest of the site or your sign-in, and Google may use cookies under its own privacy policy. People who run a Kipp Plus server never see ads.
• Google Translate: nothing from Google loads unless you press Translate. If you do, the text of the page you're on is sent to Google to translate it, under Google's privacy policy. The admin panel and the verify page never load it.
• Public appeal pages (Kipp Plus servers): you sign in with Discord and your answers go to that server's staff, just like appeals from Discord.

Legal basis (for people in the EU, UK and similar places)

• Running Kipp for a server (settings, moderation, protection, logs, analytics, invite tracking): legitimate interests of the server and its members in keeping the community safe, and providing the service the server asked for.
• Kipp Plus, codes and receipt claims: performing the contract you asked for, and keeping records the law requires.
• Comments, reviews, feedback and the launch perk: our legitimate interest in running the website and improving Kipp, and in the case of reviews and comments, the fact that you chose to post them publicly.
• The web check: your consent, given on the verify page, and the server's legitimate interest in stopping ban evasion. You can withdraw consent at any time by asking for deletion (below); it doesn't affect checks already done.
• The threat database: legitimate interests of every protected server in keeping known attackers out.
• Website security (rate limits, session cookies): what's strictly necessary to run a secure website.
• Your light or dark choice on the website is saved only in your own browser (local storage), is never sent to Kipp, and you can clear it by clearing the site's data.

Your rights

Depending on where you live (for example the GDPR in the EU and UK, or the CCPA in California), you can ask to see, correct or delete your data, object to how it's used, or get a copy of it. Email [email protected] or ask in the support server; we reply within 30 days. You can also complain to your local data protection authority. We never sell personal data, and we don't "share" it for advertising.

How we use data

We use data only to run Kipp's features in the server it came from, and the threat database across servers as described above. We:

• don't sell data or share it with advertisers or data brokers;
• don't build profiles of people for marketing or any purpose other than security. The threat database and the web check compare accounts only to stop attacks and ban evasion, as described above;
• don't use it, or message content, to train AI models.

Who else handles data

Kipp uses a few services to run. Each only gets what it needs:

• Discord: everything Kipp does goes through Discord's API, under Discord's Privacy Policy.
• Amazon Web Services: hosts Kipp and its database in N. Virginia, United States (us-east-1). It stores and runs Kipp for us and can't use the data for anything else.
• Cloudflare (when the website is behind it): passes website traffic to Kipp and tells it the visitor's country.
• proxycheck.io (only if the operator turned it on): see the web check above.
• Payment sites (for example Patreon or Ko-fi): only if you buy Kipp Plus, under their own policies.
• Google: only if you press Translate, or Show ads, on the website.

We may also share data if the law requires it, or to protect people from serious harm.

Where it's stored

Kipp and its MongoDB database run on Amazon Web Services in N. Virginia, United States (us-east-1), and only the Kipp team can access them. Access to the bot's token and database is restricted to the Kipp team. The website only works over HTTPS when it's online. Sessions, sign-in and every change are protected against the common web attacks, and security issues can be reported privately in the support server.

If you're outside the United States, your data is processed in the United States. Where the law requires it, we protect it with the safeguards the law provides for.

Deleting data

• Everything for a server: the server owner can run /data reset scope:everything. It is deleted immediately, and this cannot be undone.
• Just the settings: /data reset scope:settings puts Kipp back to its defaults and keeps the history.
• When Kipp is removed from a server: everything for that server is deleted automatically 30 days later. The delay is in case Kipp was removed by mistake or by an attacker.
• Your own data: email [email protected] or ask in the support server. We'll delete your user record and anything not tied to a server's moderation history. Moderation records a server keeps about its own members belong to that server; ask its owner.
• Seeing what's stored: Kipp admins can see what is stored for their server with /data view, or on the dashboard under Your data.
• Web check fingerprints: deleted after 180 days on their own, when the server's data is deleted, or when you ask.
• Comments and reviews: delete them yourself on the website at any time. Comment IP addresses are removed after 30 days on their own.

Children

Discord requires users to be at least 13 (or older where local law says so). Kipp is not aimed at anyone younger and doesn't knowingly collect their data.

Changes

If this policy changes, the new version is published here with a new effective date. Big changes are announced in the support server.