Privacy policy
For neo1668.de, neo1668.online and PS99 Clan Watch: the website clanwatch.neo1668.online, the Discord bot “PS99 Clan Watch” and the overlay app.
This is a translation for convenience. The German version is legally binding.
- Controller
- Hosting & security
- Sign-in & cookies
- Roblox link
- Game data
- Warning list & reports
- Discord bot
- Overlay app
- Advent calendar
- Admin area
- Retention
- Your rights
1. Controller
René Schween, Weiherstraße 4, 35753 Greifenstein-Arborn, Germany, email: neo1668@gmx.de
2. Hosting and security
All pages, the bot and the databases run on Cloudflare, Inc. (101 Townsend St., San Francisco, CA 94107, USA) as a processor. When you visit, Cloudflare processes technically necessary connection data (including IP address, time and requested address) to deliver and protect the service (Art. 6 (1) (f) GDPR). Cloudflare is certified under the EU-US Data Privacy Framework. I do not analyse access data myself and use no analytics or advertising tools.
All connections are encrypted via HTTPS (TLS); unencrypted requests are redirected to HTTPS and browsers are told to use HTTPS only (HSTS). Stored data lives in Cloudflare databases, which Cloudflare states are encrypted at rest. Sign-in codes, sign-in links and overlay device access keys are stored only as cryptographic hashes, never in plain text; session cookies are tamper-proof signed. A website session lasts at most 30 days from sign-in; signing out invalidates it on the server (for this we keep only a random session ID until it would have expired). When you sign in with a code, Discord shows you the browser and country (derived from the IP address, country code only) of the signing-in device, and afterwards the bot sends you a direct message so you spot foreign sign-ins. Data is only available to those entitled to it (see the individual sections).
3. neo1668.de
A plain information page without cookies, forms or embedded third-party content. Links to other platforms (Discord, YouTube etc.) are only loaded when you click them.
4. PS99 Clan Watch
PS99 Clan Watch is a private, free tool for an alliance of clans of the game Pet Simulator 99. Purpose: analyse clan battles live, protect clans from unreliable members (shared warning list) and manage clan roles in the alliance's Discord server. The legal basis is the legitimate interest of the participating clans and players (Art. 6 (1) (f) GDPR); where you sign in, link an account or connect the overlay app, providing the service you requested (Art. 6 (1) (b) GDPR).
a) Sign-in and cookies
Sign-in with a code or link (default): the website shows a random code that you enter and confirm in the Discord server
(channel #sign-in or command /login), or the bot sends you a one-time link only you can see. For this we store: the code or
link only as a hash, a rough browser label (e.g. “Chrome on Windows”) so you can see in Discord which browser you are signing in, times,
and after confirmation your Discord ID and Discord name. Codes and links are valid for 10 minutes and once only, and are deleted at the
latest one hour after they expire. To prevent guessing we count failed attempts per Discord account and new codes per IP address; the IP
address is stored only as a keyed hash (HMAC) and deleted after one hour.
Sign-in with Discord (older links): Discord gives us your Discord ID, display name, the list of your servers and your roles in alliance servers. No messages are read and nothing is posted on your behalf.
Cookies (all technically necessary, § 25 (2) no. 2 TDDDG; no tracking cookies):
pcw_sess– your session (Discord ID, name, officer clans), signed; valid for 30 days and extended on every use. Your rights are re-checked every hour; “Sign out everywhere” in your profile ends all sessions on all devices.pcw_lang– your language (English/German), 1 year.pcw_code– binds a sign-in code to your browser, 10 minutes.
When you sign in we create a user record (Discord ID, name, first and last sign-in, number of sign-ins) and store your language setting.
b) Roblox link and clan roles
You link your Roblox account to your Discord account once – with a code in your public Roblox profile description. There is no Roblox sign-in through us; we only read the public description. We store Discord ID, Discord name, Roblox ID, Roblox name, method and time of the link, plus your current PS99 clan and whether you are in the community server (updated with every role sync). Your public rank in your PS99 clan (leader, officer, member) automatically sets your clan role on the website and in the Discord server; if you are in a clan outside the alliance, you get a role named after your clan in the Discord server. Signed-in users see only numbers per clan under "Who's here?" (how many linked players, how many of them in the Discord server), no names; the same numbers also appear in #leaderboard. Leagues: whoever creates a league is stored as its creator with Discord ID and name, together with the league's name and clans. Players whose linked clan is in a league automatically get its role and see the private league channel; its live images only show public clan data (rank, points, pace). When the creator ends the league, channel and role are deleted. On the website every signed-in user sees all leagues with name, clans, live standings and the creator's display name; the creator can add clans, and a clan's leader or clan admin can add their own clan. After every battle we permanently store each clan league's final standings (name, creator, creation time, places and points of the clans) for the league history in the profile. For the official PS99 league we store, per season and with your Roblox ID, the league name, your points and – after the season – the league's place, points and reward, once you use the "PS99 Leagues" page or the ClanWatch app; your profile shows it. The app receives this information about your own league together with your points. Allied clans: when the PS99 leader of a clan proposes an alliance to another clan, we store both clan names, the status and the Roblox IDs of the leaders who proposed, accepted or ended it (with time). An alliance is only visible to members of the two clans; it grants no rights. The “Am I on the list?” button in #player-check and #warnings only looks up whether your own linked Roblox account is on the warning list; other players can't be looked up there, and nothing is stored. Automatically assigned roles only give insight into your own clan; access to the warning list and its evidence only has whoever a clan admin or the team explicitly grants it (exception: the PS99 leader of an approved alliance clan). Authorised officers can see in the player check which Discord account a Roblox account is linked to. You can remove the link in your profile at any time; it is then deleted and the automatic roles are removed.
c) Public game data and evaluations
Source of the data (Art. 14(2)(f) GDPR): The game data comes mainly from the public Pet Simulator 99 API by BIG Games
(ps99.biggamesapi.io), profile details from public interfaces of Roblox. BIG Games and Roblox are not processors of
PS99 Clan Watch: we only retrieve data they make publicly available and pass no data to them – with one exception: for the
“PS99 Leagues” page we ask BIG Games' API with your public Roblox ID which league you are in (only when you open the page; nothing is
stored). The league leaderboard itself (league names, points, members with Roblox names) is shown as BIG Games publishes it.
From public interfaces of BIG Games and Roblox we process: Roblox ID, user and display name, avatar, online status (as far as the player's privacy settings allow), clan membership and rank in the clan, and clan battle points. We cover the alliance clans (about every 2 minutes) and the top 500 clans of the running battle with their members (about every 5 minutes).
- Intermediate standings (points per player and clan) and the overtakes derived from them: for clans outside the alliance thinned to one reading per hour after 48 hours, and deleted 7 days after the battle ends.
- Playtime and battle results: activity (points per player and hour) and final standings per player (points, place in the clan): permanently, until you ask for deletion, so your battle history stays on your account (see below).
- Joins/leaves per clan (clan moves, with the points at leaving): 400 days.
- Final results of the alliance clans (place, points and rank per player): permanently, as clan statistics – your entries in them until you ask for deletion. Place, clan points and the top 10 (Roblox name and points) of every battle are also posted once in the
#<clan>-resultschannel of the community server.
Permanent battle history, deletion on request and objection: The legal basis for keeping playtime and battle results permanently is our legitimate interest (Art. 6(1)(f) GDPR) in showing players and clans a complete battle history; this is public game data. You can object at any time (Art. 21 GDPR) and ask for erasure (Art. 17 GDPR) by email to the address above or by message to the operator on Discord. Only the operator can delete it; the operator deletes it for your Roblox ID after checking that the account is yours. Your profile shows whether your history has been deleted. This deletes playtime, final standings and placements, clan moves and any remaining intermediate standings for your Roblox ID; after that we no longer track you. We only keep your Roblox ID and the time, so we can respect your request permanently, plus a log entry. Clan points (the clan's total) and the per-battle distribution without player IDs remain; the member management of your alliance clan (membership, rank, clan roles) continues. At your request the operator turns tracking back on; deleted data does not come back.
From this, Clan Watch automatically calculates leaderboards, forecasts of the final standings, activity overviews and, for officers, hints about unusual point patterns (“hack check”) and a pre-analysis for reports. These are hints for the officers; decisions (e.g. a warning-list entry) are always made by a person.
The public start page shows only clan names, clan points and overtakes between clans – no player data. For the chart images in the Discord clan tracker, clan names, points and the Roblox names of clan members are sent to the chart service QuickChart (quickchart.io, USA), which renders an image (Art. 6 (1) (f) GDPR); this is public game data anyway. The website draws its own charts.
d) Warning list and reports
Officers of the alliance clans can list players with category, reason and evidence (screenshot or link). We store Roblox ID and name and
the Discord ID of the listed person, reason, evidence, date, Discord name and ID of the reporting officer, and a player file at the time
of the report (account age, clans, battles, statistics, earlier reports) so it remains traceable what applied at the time. Each report is
also posted with the player file and evidence to the #reports channel of the alliance's main server, which only the team can see; the other
alliance clans only receive a short notice without evidence; these notices only go to channels for officers or the team. The warning list is
not public on Discord: the #warnings channel of the community server only shows how many players are listed in total – no names,
no IDs, no categories, no single entries. The number is updated at most once a day (in the morning), so a new entry can't be
matched to an event by its timing. Whether someone is listed is only shown to the person concerned, after they have linked
or confirmed their Roblox account with a code in their profile (“Am I on the list?” button, website or /statement), and to officers,
moderators and the team of the alliance clans, who see the list on the website and with /check. Reason, evidence and player
file are only visible to authorised officers of approved alliance clans and the team. Other bots run by the same operator (e.g. the AX0C bot) may query only a few details through an internal interface (listed yes/no, category, since when, reporting clan) and may show them only to their team or officers, plus public game data (clans, battle results, account age) – no reasons, evidence or links between Discord and Roblox accounts. Every time an evidence screenshot is opened, the person and time are logged. Entries expire after the chosen time (default
180 days); unlimited entries are flagged for review every 90 days. Expired or removed entries remain traceable for officers for one more
year (e.g. in case of repeated misconduct) and are then completely deleted together with all evidence, statements, tickets and the report
posts in Discord. Every change is logged with name, Discord ID and time; the log is deleted after one year.
Reports via Discord: Clan moderators and higher of an alliance clan and the team can report a player with
/report or the button in the #<clan>-reports channel (a member of their own clan or any Roblox player). We store the
Roblox ID and name of the reported player, category, the description, evidence (screenshots, links), the Discord ID and name of
the reporter with their clan and clan role, the time and the decision (who, when, reason). A report is not yet a warning-list entry.
It is posted with the player file as a card with a thread to the #<clan>-reports channel of the reporting clan, which only its
moderators, officers and admins and the team can see – there without earlier warning-list entries and without Discord accounts from the
player file –, and to the #reports channel of the main server, which only the team can see. Officers of the reporting clan or team admins
decide on the report; if it is accepted, a warning-list entry is created as described above. On the website, officers and moderators of the
clan and the team see a list of open reports without evidence. To prevent abuse, at most 10 reports per person and hour are possible; if the
same person reports the same player again within 24 hours, it is added to the existing report. Retention: reports without a decision
count as dismissed after 90 days; dismissed reports are deleted with their evidence and Discord posts 90 days after the decision; accepted
reports are deleted together with their warning-list entry (see above). The legal basis is our legitimate interest and that of the alliance
clans in protecting themselves against scams, scripting and rule breaking (Art. 6 (1) (f) GDPR); you can object (see Your rights).
e) Statements, tickets, applications, team
Listed players can object right away (button “Am I on the list?” in #warnings, website or Discord command /statement); after a
rejected statement only again after 14 days. The button only checks the Roblox account linked to the clicking person's Discord account; if it
is listed, the bot shows them – visible only to them – category, date, reason and how to respond. On the website the link or a code in the public Roblox profile
description confirms the account. Whether and why an account is listed is only shown after this confirmation, and lookups are
limited. We store the text and Discord ID and name; the statement is visible to the officers and is deleted or kept together with the entry.
For each statement the officers keep a ticket history (messages, internal notes, screenshots, each with name, Discord ID, role and time).
The player sees the non-internal messages and can reply.
Applications to an alliance clan (text, Discord and Roblox account, status) are visible to the officers of that clan and of the main server. New clans are registered by their PS99 leader; we store clan, leader account and time. For team roles (admin, moderator) we store Discord ID, name, role and who granted it. Clan members see the battle activity and game profiles of their own clan (public game data).
Activity card and clan moves: on player profiles, every signed-in member with a linked Roblox account sees a
player's battle activity (points, active hours, rank in the clan and among all tracked players) and their clan moves (joins, leaves
with the running battle's points at leaving, current clan with the time it was recorded) – across all tracked clans, i.e. the alliance
clans and the top-500 clans. This is public game data from the PS99 API; combined, it shows when a player was in which clan. For a
leave we show whether the player was kicked or left on their own – derived from the public time of the clan's last kick
(LastKickTimestamp); for this we store only that time per clan. After a leave we look up once (up to three times
on errors) in the public PS99 API which clan the player is in now, and store only that clan's name with the leave; players who
asked for deletion are never looked up. It is
kept as above (activity permanently until deletion on request, clan moves 400 days), and requests are limited per person. Only the owner decides whether a battle was an active or a passive
event; for this we store the battle, the type, the owner's Discord ID and the time, and the change is logged.
Activity score and member activity: from the same game data (points per player and hour, joins and leaves, final standings), Clan Watch calculates four values per player and battle: hours with points per battle day, share of battle days with points, points, and points per active hour. Each value is compared with all tracked players of all tracked clans who took part in the same battle (percentile: "better than X %", from a sample of about 1,000 participants per battle). For this, the central service only stores a summarised distribution per battle (101 steps per value) without player IDs. Added to that is reliability (battles with points while a member, and no leaving mid-battle). From this come an activity score from 0 to 100 (weighted separately for active and passive events), an activity level, a trend, a short reason, figures such as active days, sessions, longest break and main playtime, and a "permanent farming" hint (no deduction). Roblox online times are not used. Assessment on player profiles: every signed-in member with a linked Roblox account sees these values and the personal score list per battle on every player profile – across all tracked clans, like the activity card. There is no list of all players. Member list: only a clan's officers and admins and the owner see the list of all its members. Requests are limited per person. The purpose is an overview of how active players really are. The values are a hint, not an automated decision – Clan Watch does not remove anyone or change roles. For the member list, per alliance clan and battle we only store the Roblox ID with derived figures (points, hours, days, sessions, breaks, time-of-day blocks, join/leave in the battle; no names) while the battle is among the clan's last 20; the finished list (without names) is cached for at most 10 minutes. As with the other evaluations, the legal basis is our legitimate interest in organising the clan (Art. 6(1)(f) GDPR); you can object (see Your rights).
f) Discord bot and community server
The bot only processes commands and buttons addressed to it and posts messages in the channels set up for that. It reads no other messages. Replies containing personal data (e.g. sign-in links) are visible only to you. In the community server the bot creates channels and roles and assigns roles matching Clan Watch: “Verified” for linked accounts, the clan role by your PS99 rank, and team and clan roles. For assigned clan roles we store Discord ID, name, role, clan, who assigned it and when. Roles are removed as soon as they are revoked in Clan Watch or the link is removed. For the alliance overview the bot creates permanent invite links to the servers.
Joins and leaves: the #joins-and-leaves channel of the community server records who joined or left the server – with display name, username, profile picture (avatar), the age of the Discord account (from the public Discord ID) and the running member number, without any mention. If you linked your Roblox account with Clan Watch, your Roblox name and current PS99 clan are shown as well. For this the bot compares the member list about every 10 minutes and stores Discord ID, display name, the address of your public Discord avatar and join time per member, only while you are a member; the entry is deleted when you leave. All members of the server can see the posts in that channel. The purpose is overview and protecting the community (Art. 6(1)(f) GDPR).
Moderation by clan admins: with /clanmod clan admins can time out members of their own clan, delete their messages in the clan chat or remove them from the server. For this we log who did what to whom (Discord ID, name), with which reason and when; the same note appears without mentions in the team channel and the clan's team channel (Art. 6(1)(f) GDPR).
g) Overlay app (download, connection, updates)
The “ClanWatch” overlay app for Windows is optional and free. It shows your battle points and clan data on top of the game and only talks to clanwatch.neo1668.online (HTTPS). There is no telemetry, no analytics, no crash reporting and no third-party services.
Connecting: the app shows a code that you confirm at clanwatch.neo1668.online/verbinden after signing in. We then store a device access: the access key only as a hash, your Discord ID, the device name (“ClanWatch on <your PC's name>”), creation, last-use and expiry times (30 days, extended on use, at most 90 days). With it the app requests only your own data about once a minute (points, clan, rank, linked names) and checks for a new version at start and every few hours. At /verbinden you see all connected devices and can sign them out individually or all at once; if you remove your Roblox link, your device accesses are deleted. To prevent abuse we count connection attempts per IP address; the IP address is stored only as a salted hash and deleted after one day at the latest. On the confirmation page we show the country the request came from (derived from the IP address; only the country code is stored briefly) so you can spot foreign devices. To protect against codes sent to you by someone else, we also store a salted hash of the network range (not the IP address) at start and warn on the confirmation page if your browser comes from a different network; it is deleted with the code after one day at the latest. Newer app versions create their own key pair on your PC and sign every request; we store only the public key with the device access, so a copied access key does not work without your PC (signature checksums are kept for at most 10 minutes to prevent replays). After you confirm, the bot sends you a Discord direct message that a new device was connected.
On your PC the app stores in the folder %APPDATA%\ClanWatch its settings (display, keys, colours, language), the device
access encrypted with Windows (DPAPI, readable only by your user account) and a technical log (at most 1 MB, without access keys). It needs
no administrator rights. From the game it reads only the position and size of the Roblox window and whether it is in the foreground – no
reading of game memory, no inputs, no screenshots, no modification of the game. Uninstalling and deleting the folder removes everything
from your PC.
Download and updates: the app is only offered via clanwatch.neo1668.online. For downloads and update checks Cloudflare processes the usual connection data (section 2); there is no download tracking of our own. Every version comes with a SHA-256 checksum and file size. The app only installs automatic updates if the update's digital signature (ECDSA) is valid and checksum and size match; otherwise it keeps the old version. The program file itself is not signed with a Windows certificate (Authenticode), so Windows SmartScreen may warn on first start.
h) Advent calendar
From December 1 to 24, 2026, signed-in members with a linked Roblox account can reveal one card per day on clanwatch.neo1668.online. Only in-game Gems can be won; taking part is voluntary and free. The result is drawn only by our server.
Stored for each revealed card: your Discord ID, Roblox ID and Roblox name (from your link), the day, the prize and the time, plus the ID of the Discord post and whether and when the prize was marked as sent (with the name of the person who marked it). This makes sure each person and each Roblox account reveals at most one card per day, and lets us send the Gems to the right Roblox name. Prize and sent mark are also kept in the change log (Discord ID and name, Roblox ID, door, prize; 1 year like the rest of the log).
Publication: Every win is posted in the #advent-wins channel of our community server with a mention of your Discord account, your Roblox name, the prize, the door and the time. Only members with the "Verified" role and the team can see the channel; the mention only notifies you. The calendar points this out before you reveal a card.
Images: The card pictures come from the official Pet Simulator 99 API by BIG Games. Our server fetches them there and delivers them itself; your browser does not connect to BIG Games for this.
Legal basis is running the calendar under these rules (Art. 6(1)(b) GDPR). Deletion: From February 1, 2027, we automatically delete the calendar data and the posts in #advent-wins.
i) Admin area and BIG Games connection
admin.clanwatch.neo1668.online is an area for the operator only. Sign-in uses the official BIG Games player API (OAuth); only the operator's Roblox account is let in. Only two permissions are requested: the operator's own profile (to check the account) and the operator's own Pet Simulator 99 mail history. If any other account signs in, access is denied, its access key is discarded immediately, and only the attempt (Roblox ID, browser, country, time) is noted in the change log (1 year).
Purpose: Clan Watch detects whether the operator has sent the Gems of an advent calendar prize by in-game mail and then marks the prize as sent automatically. For this, recipient name, diamond amount and time of the operator's sent mails are only read for the comparison with the Roblox name, prize and time of open prizes. Mail contents are not stored; only a one-way identifier (hash) of each mail that ticked off a prize is kept so it cannot count twice. The prize is labelled "Automatisch (Mailbox)" (automatic).
Also stored: the BIG Games access key (encrypted), the operator's Roblox name and the time of the last check. Deletion: the access key immediately on sign-out, expiry or revocation, at the latest after 30 days; mail identifiers after 30 days. Legal basis is running the calendar (Art. 6(1)(b) GDPR) and our legitimate interest in reliable payouts (Art. 6(1)(f) GDPR).
j) Enchant calculator
clanwatch.neo1668.online/tools offers an enchant calculator, open to everyone, also without signing in. Our server fetches the game data (enchants with book pictures, ranks, mastery) from the official BIG Games API and passes it on; your browser does not connect to BIG Games. We set no cookies for this and store nothing about you. Your entries (rank, mastery, gamepasses, books) stay only in your browser (local storage); if you share a link, it contains these entries. To prevent abuse, Cloudflare counts requests per IP address (as a shortened hash) for 60 seconds in memory; the counter then expires. Legal basis is our legitimate interest in stable operation (Art. 6(1)(f) GDPR).
5. Retention at a glance
| Data | Kept until |
|---|---|
| Sign-in codes and links, failed-attempt counters | at most 1 hour after expiry (valid 5 or 10 minutes) |
| ID of signed-out website sessions | until the session would have expired (at most 31 days) |
| Session cookie | 30 days after last use |
| Overlay: device access | until signed out, or 30 days after last use, at most 90 days |
| Overlay: abuse counters (IP only as salted hash) | at most 1 day |
| Intermediate standings, overtakes, battle leaderboard | 7 days after the battle ends |
| Playtime (hourly activity per battle) and battle results per player | permanently, until you ask for deletion (profile or email) |
| Joins/leaves (clan moves) | 400 days |
| Final results of the alliance clans | permanently (clan statistics); your entries in them until you ask for deletion |
| Objection to tracking (Roblox ID and time only) | until you turn tracking back on |
| Member list: derived figures per alliance clan battle (Roblox ID, points, hours, days, sessions, breaks, join/leave) | while the battle is among the clan's last 20 battles; finished list without names at most 10 minutes |
| Distribution per battle for the comparison (no player IDs) | permanently |
| Discord ↔ Roblox link | until you remove it |
| Warning list, player files, evidence, statements, tickets, report posts | while the entry is active (default 180 days); after expiry or removal 1 more year (traceability in case of repetition), then complete deletion |
| Reports via Discord (/report): reporter, reported player, description, evidence, Discord posts | dismissed after 90 days without a decision; dismissed reports deleted 90 days after the decision; accepted ones together with their warning-list entry |
| Change log and evidence views | 1 year |
| Applications | 1 year after the decision |
| Advent calendar: revealed cards, prizes, sent status, posts in #advent-wins | until January 31, 2027, then automatic deletion |
| Admin area: the operator's BIG Games access key (encrypted) | until sign-out, expiry or revocation, at most 30 days |
| Admin area: identifiers (hash) of matched mails; mail contents are not stored | 30 days |
| User record without link, team or clan role | 1 year after the last sign-in |
6. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21), as well as the right to lodge a complaint with a data protection supervisory authority. Much of this you can do yourself: remove the link in your profile, sign out overlay devices at /verbinden, sign out. Please send all other requests to the email address above.
Last updated: November 20, 2026