Janus Privacy Policy
Effective date: November 4, 2026
This policy explains what data Janus ("Janus", "we", "us") collects, why, how long we keep it, and how you can delete it. Janus is a Discord application that verifies members who join Discord servers and helps server staff block alternate ("alt") accounts, VPNs, raids and automated accounts. Janus is operated by Zytrix Studio. You can reach us at matiasko.ferdinand@gmail.com.
Janus is not made by, endorsed by or affiliated with Discord Inc.
1. The short version
- We collect only what we need to verify members and stop abuse.
- We never store your IP address in plain text. We turn it into a one-way, keyed hash that can be compared with other hashes but cannot be turned back into your IP.
- Verifying never asks for your email, your Discord password or any payment details. Email is only used if you choose to create a website account.
- We do not sell your data, and we do not show ads.
- Old data is deleted automatically, and you can delete your data at any time with the
/privacycommand.
2. What we collect
When you verify in a server that uses Janus
| Data | Where it comes from | How we store it |
|---|---|---|
| Discord user ID, username, display name, avatar, account creation date | Discord, when you log in with Discord ("identify" scope) or join a server | As is |
| IDs of the Janus servers you verify in, and the roles Janus gives you | Discord | As is |
| IP address | Your browser, when you open the verification page | Hashed only. The raw IP is held in memory long enough to check it for VPN/proxy use, then discarded |
| Network type: VPN, proxy, Tor, hosting provider | Janus's own IP lists, checked on our server | As is (no raw IP) |
| How you moved the Janus Gate slider (positions and timing), and a small browser calculation (proof of work) | Your browser, if you're shown the challenge | Checked once to tell humans from bots, then discarded |
| Device and browser signals: screen size, time zone, language, browser features | Your browser, on the verification page | Hashed only, as a device fingerprint |
| A random verification cookie | Set by the verification page | As a random ID |
| Verification result, risk score (0–100), the reasons for it, and timestamps | Janus | As is |
| Appeal messages, if you send one | You | As is |
When you create a website account (Janus dashboard and Specula)
- Email login: your email address and your password. The password is stored only as a salted scrypt hash, never in readable form. We email you one-time codes to confirm your address or reset your password.
- Discord login or link: your Discord user ID, username, avatar and the list of servers you're in ("identify" and "guilds" scopes). This is how we know which servers you're staff in.
- We also keep the server's Janus settings, an audit log of dashboard changes, and a log of your Specula searches (who you looked up and when).
What we do not collect
Payment details, your messages, your friends list, or anything from servers that don't use Janus. When you only verify, we never ask for your email or password.
3. Why we use it
- Verification: to decide whether to let you into a server and to give you the verified role.
- Alt account detection: to find out whether two accounts share a network, device or verification link.
- VPN, proxy and Tor detection: to block anonymizing connections when a server has turned this on.
- Raid protection: to spot many suspicious accounts joining at once.
- Server logs: to show server staff why a member was allowed, flagged or blocked.
- Appeals: to let staff review a decision you disagree with.
- Security: to keep Janus itself safe from abuse.
Our legal bases, where privacy laws such as the GDPR apply: our legitimate interest, and the server's, in keeping communities safe from abuse and ban evasion; and performance of the service you ask for when you start verification.
4. Who can see your data
Staff of the server you verify in can see your verification result, risk score, the reasons, and any account in their own server that you were linked to. They never see your IP address or your raw device data.
Janus Network (optional): when a server turns this on, hashed signals are compared across participating servers. Staff can then see that an account was "flagged elsewhere", but not which server flagged it.
Specula (lookup website): staff of servers that use Janus can look up a Discord user ID. They see a risk score, how many accounts are linked, and summary counts (checks, flags, VPN attempts, Janus bans). Linked accounts are named only if they're in one of that staff member's own servers. Other linked accounts are only counted, and other servers' names are never shown. Data only comes from the staff member's own servers and Janus Network servers. Searches are limited per day and logged. You can hide yourself from Specula at any time with
/privacyin Discord or on your account page.Service providers that help run Janus, and only for that purpose:
- Discord, for login, roles and messages.
- Our hosting provider, Self-hosted by Zytrix Studio, which runs the server Janus lives on.
Janus does not send your IP address to any VPN-detection or CAPTCHA company. The VPN check uses public IP lists (network ownership data from RouteViews and DB-IP, the Tor Project's exit list, and Apple's iCloud Private Relay ranges) that Janus downloads and checks on its own server. The Janus Gate challenge is Janus's own and runs on Janus's server.
Authorities, only when the law requires it.
We do not sell or rent personal data, and we do not share it for advertising.
5. How long we keep it
| Data | Kept for |
|---|---|
| Hashed IP and device fingerprint, verification cookie | 90 days after your last verification, then deleted |
| Verification results and reasons | 90 days, or 12 months if the account was flagged as an alt or for ban evasion |
| Appeals | 90 days after the appeal is resolved |
| Dashboard audit log, Specula search log | 12 months |
| Website account (email, password hash, Discord link) | Until you delete it on your account page |
| Data for a server that removes Janus | Deleted within 30 days |
| Backups | Overwritten within 30 days |
Messages Janus posts in a server's log channel belong to that server. Its staff control them, and we can't delete them for you.
6. Your choices and rights
- Delete your data: run
/privacyin any server that has Janus and choose Delete my data, or email matiasko.ferdinand@gmail.com. Deletion removes your hashes, verification history and appeals. A server may then ask you to verify again. - Access or correct your data: email matiasko.ferdinand@gmail.com from a way we can link to your Discord account, for example by sending us a code we DM you.
- Object or restrict: you can always choose not to verify. Without verification, a server using Janus may not let you in.
- Depending on where you live (for example the EU, UK or California), you may have additional rights, such as data portability or lodging a complaint with your local data protection authority. We answer requests within 30 days.
7. Security
- IPs and device signals are stored only as keyed one-way hashes. The key is kept separately from the database.
- All traffic uses HTTPS. Bot tokens and keys are kept out of the code.
- Admin tools and the database are not reachable from the public internet, and old servers are shut down completely.
- Access is limited to the people who run Janus and is protected by two-factor authentication.
If a breach affects your personal data, we will notify the affected users and servers, and any authority the law requires, without undue delay. Where the GDPR applies, we will notify the authority within 72 hours.
8. Children
Janus is for Discord users only, and Discord requires its users to be at least 13 years old, or older in some countries. We do not knowingly collect data from anyone below that age. If you think we have, email matiasko.ferdinand@gmail.com and we'll delete it.
9. International transfers
Janus runs on servers in Slovakia. If you use Janus from another country, your data is processed there. Where the law requires it, we rely on safeguards such as Standard Contractual Clauses.
10. Changes
If we change this policy, we'll update the effective date. For important changes, we'll also post a notice on our website and in our support server.
11. Contact
Zytrix Studio — matiasko.ferdinand@gmail.com — https://janus.tail4c2fc9.ts.net/privacy