Privacy Policy

The controller for the personal data described here is the operator of traceify.win (see the Legal notice). Contact for anything about your data: xynterical@pm.me. We have not appointed a data protection officer.

This policy covers people who verify on traceify.win to join a server that uses Traceify (members), people who sign in to the dashboard (server staff), and people who just visit the website.

When a member verifies on traceify.win we collect:

• Your Discord user ID.
• The email on your Discord account, only if Discord marks it as verified.
• Your IP address.
• The IDs of the Discord servers you are in (IDs only, no names, at most 200).
• A device fingerprint: a hash made in your browser from settings such as screen size and time zone. The raw settings are not sent.
• Four coarse categories worked out from the above: whether your IP address belongs to a VPN, hosting or Tor network (checked on our server against public lists), whether your device is a phone or a computer, whether your email domain is a free, custom or throwaway provider, and how many days old your Discord account is (capped at one year).
• The result of the check (verified, held or pending), for which server, and when.

We do not collect your messages, your password, or your files. Traceify drops its Discord access as soon as it has the details above.

When server staff sign in to the dashboard we receive your Discord user ID, username and the servers where you can manage Traceify. We also set a session cookie (see the Cookie notice).

When anyone visits the website, our web server logs the request (IP address, time, page, browser type). Those logs are kept for 14 days. We use no analytics and no advertising trackers.

We get this data from you, and from Discord when you sign in with it. The server you join tells us which server you are verifying for.

We weighed these interests against your rights. What keeps that balance fair: we collect only what matching needs, we encrypt it, we keep it for two years, we do not read messages, shared VPN and Tor networks are discounted so strangers are not linked by them, and a person at the server decides what happens next. You can object at any time (see your rights).

We do not use your data for advertising and we do not sell it.

When Traceify finds a likely match to a banned account, what happens depends on the server's settings. By default the member is held without the verified role until a moderator decides. A server can instead choose to kick or ban automatically when the match is to an account banned in that same server. A ban made in one server never affects another server. The only bans that apply across servers are global bans: cases a server sent to us with proof, which Traceify staff reviewed and approved, and which a server applies only if it turned that on. A server that did can hold or ban a member who matches an approved global ban. You get a message from the bot with the case number and a link to appeal. A case stops counting after 365 days. When a server kicks or bans you because of an alt match, Traceify keeps a case record for a year with a random case number, your one-way network token, what was done and a short reason. Appeals you send are stored with your Discord ID and your message. If you appeal, we store your Discord ID and the text you write until the appeal is decided and then for as long as the case record exists. Traceify publishes counts and a log of decisions at /transparency, with no names, servers or proof.

This is automated processing that can affect your access to a server. You can ask the server's staff to review it, and you can write to us and ask for a person to look at your record and explain the match.

The staff of the server you verified for see the result for you: whether you passed or were held, which other Discord accounts you were linked to, and on what (email, device or network). They are told whether a linked account was banned in their own server. A ban in another server is never shown to them. They do not see your IP address, email or fingerprint.

Traceify is one network. Your record can be matched when someone verifies in any other server that uses Traceify. If you are linked to them, that server's staff see your Discord account as a linked account, as described above.

A very small number of Traceify staff can look up one member by Discord user ID, with a written reason. Each lookup is limited in number and logged with who made it. The user ID itself is not stored by the lookup. The lookup shows that member's own record and how it links to other accounts, and keeps the other accounts anonymous.

We use these providers to run the service. They cannot read your stored identifiers, because those are encrypted before they are stored.

We disclose data to an authority only when the law requires it and after checking the request.

Verification records are stored only on servers in the EU. The providers outside the EU in the table above handle code, DNS and network coordination, not member records. Cloudflare and GitHub are certified under the EU-U.S. Data Privacy Framework. You send data to Discord when you sign in, under Discord's own policies.

Each identifier is encrypted on our web server before it is written, with a key that only the bot can use, so the website can store a record but not read it back. Matching uses keyed one-way hashes, so equal values can be compared without being read. The same hashes are used in every server, which is what lets the network link an account across servers. The database disk is encrypted (LUKS2), connections use TLS, the database and admin tools are not reachable from the public internet, and backups are encrypted again.

No system is perfectly safe. Someone with administrator access to a server can still reach the keys on that server. We say so because it is true.

Under the GDPR you can ask us for:

• Access (Article 15): a copy of your record and how it links to other accounts.
• Correction (Article 16) of data that is wrong.
• Erasure (Article 17): deletion of your records.
• Restriction (Article 18) of how we use your data while a question is settled.
• Portability (Article 20): your data in a common file format.
• Objection (Article 21): you can object to us using your data for alt detection. We will stop unless we can show a compelling reason that outweighs your interests.
• Human review (Article 22): you are not subject to a decision made only by automated means that significantly affects you, unless you have the chance to have a person review it. See Decisions about you.

Providing your data is not required by law or by a contract with us. It is what a server that uses Traceify asks of you before it lets you in. If you do not verify, the server will not give you access, and you can leave the server instead.

To use a right, email xynterical@pm.me with your Discord user ID and, if you know it, the server you verified for. Our records are encrypted and hashed, so without your Discord user ID we cannot find them. We may ask you to confirm you control the Discord account. We answer within one month. For an access request we can send you a report of your record.

You also have the right to complain to a data protection authority (Article 77), in the EU country where you live, where you work, or where you think your rights were infringed.

Discord requires users to be at least 13. We do not knowingly process data of anyone below that age. If you think we have, email us and we will delete it.

We use only the cookies needed to sign you in and complete verification. See the Cookie notice.

We update this policy when what we do changes. The date at the top shows the current version. If a change affects how your data is used, we will say so on the website before it applies.