your data, explained
This Policy explains how Numsy handles information when you use the Numsy Discord bot, public website, leaderboard API and Numsy Party Discord Activity.
Controller / service operator: Štěpán Stanislav
Contact email: spravce@eetn.cz
Country of operation: Czech Republic
This operator is responsible for the Numsy website, Numsy HQ dashboard, bot services, public leaderboard API, seasons, cosmetics and Numsy Party, except for processing carried out independently by Discord or other third-party services.
| Area | Information | Why it is used |
|---|---|---|
| Counting bot | Discord server and channel identifiers; channel configuration; current count; previous counter’s Discord user ID; streak length; local highscore; rankability status. | To run counting, prevent back-to-back counting, save streak state and apply channel settings. |
| Global leaderboard | Channel ID, server name, channel name and score for ranked entries. | To show and maintain the top leaderboard. Ranked server and channel names with scores may be publicly displayed on the Numsy website. |
| Website and API | Technical request data that your web host, reverse proxy or API server may log, such as IP address, time, requested URL, browser/user-agent and error information. | To deliver the site, prevent abuse, diagnose failures and maintain security. |
| Numsy Party Activity | Discord-provided participant/session information needed to run the Activity, such as Discord user ID, display name, avatar, Activity or room context, selected mode, score and temporary game state. | To identify players in a round, synchronise multiplayer gameplay, show scores and keep a room state working. |
| Numsy HQ profiles and Discord login | Discord user ID, username, global/display name, avatar URL, profile level, XP, Aura balance, achievements, equipped cosmetics, inventory and profile settings. Where you sign into Numsy HQ through Discord, the service processes the Discord OAuth session information needed to identify your account. | To create and show your Numsy profile, provide dashboard access and connect your Discord identity to profile features. |
| Seasons, Clubs and weekly events | Server ID, server name, icon URL, channel/role configuration synced for dashboard controls, season points, count and Party statistics, league status, event participation and related history. | To run optional server Clubs, seasonal rankings, weekly events, server dashboards and integrity checks. |
| Cosmetics and seasonal shop | Cosmetic inventory, equipped items, purchase history needed to prevent duplicate purchases, Aura balance and the current/previous season linked to an item. Owner-created cosmetics may include uploaded or externally hosted artwork, title, icon, colours, description and price. | To operate seasonal cosmetic drops, preserve permanently owned items and render profile customisation in Numsy HQ and Discord profile embeds. |
| Owner dashboard and audit data | Authenticated owner identity, changes to future season names/themes, weekly events, cosmetics and one-time operational actions, together with timestamps and relevant configuration values. | To secure owner-only controls, operate upcoming content and investigate configuration changes. |
| Optional Wolfram|Alpha queries | The query text sent after a message starting with |, but only where a server has enabled this feature. |
To obtain a math answer from Wolfram|Alpha. Do not use this feature for sensitive information. |
Numsy is not designed to collect payment-card data, government IDs, precise location data, private voice recordings or the full content of ordinary Discord messages outside the configured features needed to operate the service.
Numsy HQ can use Discord login to identify a user and provide profile/dashboard features. Numsy does not currently offer paid purchases, payment-card storage or advertising. If you add analytics, payments, a public support form or other tracking, update this Policy before enabling them.
We use the information above to:
Where data-protection law requires a legal basis, Numsy generally relies on:
Service operation / performance for data necessary to run counting, scores and multiplayer rounds.
Legitimate interests for security, fraud prevention, diagnostics and maintaining fair leaderboards.
Consent where required by law for any optional feature that relies on consent. If you add cookies or analytics, disclose them here and obtain consent where required.
Numsy may share or make information available to the following recipients, only as needed for the service:
| query is used. The query text is sent to that service to obtain a result.We do not sell personal data.
Numsy keeps data only for as long as reasonably necessary to run the relevant feature, protect the service, resolve disputes or comply with legal requirements. The current code stores counting and leaderboard state locally, so the following is a practical summary:
We use reasonable technical and organisational measures for a small online service, such as access controls, secret-based API authentication and server security practices. No online system can be guaranteed completely secure, so please do not send sensitive data to Numsy.
Depending on where you live, you may have rights to request access to, correction of, deletion of, restriction of or objection to processing of your personal data, as well as data portability where applicable.
To make a request, email spravce@eetn.cz and include your Discord user ID, relevant server/channel details and what you want us to do. We may need to verify that the request relates to you or that you are authorised to act for a server.
Where GDPR applies, you may also complain to your local data-protection authority. In Czechia, this is the Office for Personal Data Protection (ÚOOÚ).
Discord and infrastructure providers may process information in countries outside your own. Where required, those providers are responsible for applying an appropriate lawful transfer mechanism under their own terms and data-processing arrangements.
Numsy is intended for people who meet Discord’s applicable minimum age requirements. We do not knowingly design Numsy to collect sensitive information from children. If you believe a child has provided personal information in a way that should not happen, contact us using the details above.
We may update this Policy when Numsy changes, when a provider changes, or when required by law. The current version will be published here with an updated date. Material changes may also be announced through the Numsy website, Discord app or support server where appropriate.
Privacy questions, deletion requests and data-rights requests:
Service operator: Štěpán Stanislav
Privacy contact: spravce@eetn.cz
Support contact: Contact us by DMing the Numsy bot