Privacy Policy

TecnoCore ("we," "our," or "the service") provides a Discord bot and web dashboard that lets server administrators build and deploy surveys, quizzes, and giveaways to their Discord servers. This policy explains exactly what data we collect, why, and how it's handled.

1. What We Collect

When you log in with Discord, we receive and store:

• Your Discord user ID, username, and avatar
• A temporary OAuth access token, used only to fetch the list of servers you administer
• Your email address, if your Discord account has one on file and you've granted the "email" permission during login - currently used only to send you a receipt when you pay for a subscription. If Discord doesn't provide an email (for example, an unverified account, or a login from before we started requesting it), we simply don't have one on file for you and skip anything that would otherwise be emailed. If we start sending any other kind of email to this address (for example, product update announcements), we'll update this policy first and give you a clear way to opt out
• A record of each successful login: a timestamp, your IP address, and - only for your very first login in a browser session - which site referred you here (or which tagged link you clicked, if any), so we can tell which channels actually bring people to the service. We keep this as individual login history, not just a single "last seen" value

When anyone (including someone who never logs in) visits our public landing page, we log the page path, referrer, any campaign tag on the link (utm_source/utm_medium/ utm_campaign), and IP address of that visit. This is aggregate marketing-attribution data (which channels bring visitors, and how many of those visitors go on to log in) - it is not linked to a Discord account unless that visitor subsequently logs in, at which point their login event separately records the same attribution for that one login only.

When you configure a server through the dashboard, we store:

• The Discord server (guild) ID and your ownership link to it
• Your chosen survey/quiz/giveaway channel, reward role, embed title/description, and questions

When a member of your server completes (or starts and abandons) a survey or quiz, we store:

• Their Discord user ID
• Their raw text or multiple-choice answers to your questions
• How long it took them, and whether it was completed or timed out

When someone enters a giveaway, we store:

• Their Discord user ID, display name, and avatar - or, for entrants without a Discord account (for example someone entering from TikTok, or someone migrated in bulk from an older giveaway run before entries lived in this system), whatever name/details the server admin manually adds on their behalf
• Which bonus tasks they've completed, and their resulting entry weight
• If they're drawn as a winner: the draw record, including a snapshot of the full entry pool at the moment of the draw (kept so the result can be audited later), and, if the prize was drawn from the Game Keys Vault, which key(s) were assigned to them and their delivery status

Game Keys Vault. Any Discord user with dashboard access can maintain their own private vault of game keys/codes, used to fulfil giveaway prizes or hand out keys directly. Keys are encrypted before they're stored, and are only decrypted at the moment a key is auto-DMed to a recipient, or if the vault's owner (or someone they've granted access to) specifically chooses to reveal one manually. A vault is private to its owner by default; the owner can grant specific other Discord accounts access to view, add, and deliver keys within their vault, and can revoke that access at any time - one admin's vault is never visible to another admin unless explicitly granted. We keep a chronological activity log for each vault (which key was added, sent, revealed, reclaimed, or flagged for support because it didn't work, by whom, and when) so its owner can audit what happened to their own keys; this log is visible only to the vault's owner and anyone they've granted access to. If a recipient flags a key as not working, they're shown a message directing them to contact the bot owner or support staff directly, with evidence they attempted to redeem it - we only log that this happened, not the content of any follow-up conversation.

Keys delivered by DM use a "Reveal Code" button with a 3-day claim window - the code itself isn't shown until the recipient clicks it. If it isn't claimed within 3 days, the key automatically returns to the vault as available again and is no longer addressed to that recipient. After revealing a code, a recipient can optionally choose to enter an email address to receive a confirmation copy of it. This is entirely opt-in - we do not collect or store an email address unless the recipient submits one themselves at that moment - and it's used once, to send that single confirmation email via our support mailbox, with only the fact that a confirmation was sent (not the address itself) kept in the vault's activity log. This is separate from, and unrelated to, the account email described in Section 1 - even if we already have an email on file for your account from login, a key confirmation is only ever sent to whatever address you type in at that moment.

If your server subscribes to a paid plan, we store:

• Your subscription tier and its status (active, cancelled, etc.)
• Payment metadata from our payment processor (PayPal) - the transaction/order ID, amount, currency, and status of each payment
• We do not receive or store your full card or bank details - that's handled entirely by PayPal

When a payment completes, we email a receipt to the address on file for your Discord account (see Section 1) - the plan, amount, date, and payment reference, so you have a record independent of PayPal's own emails. If we don't have an email on file for you, this is simply skipped; it never blocks or delays the actual upgrade.

If you submit a support ticket, we store:

• Your Discord user ID and username
• The ticket subject, category, and description you provide
• Any replies exchanged between you and our support staff, and which staff member handled the ticket

If a server admin has linked TecnoCore to an external game/platform via a Meta (Facebook/Instagram) account, we store the connected Meta account ID and display name against the linking Discord user ID.

If a server has the leaderboard feature receiving live game events, we store, per event:

• The in-game player ID, event type, level/progress data, and timestamp submitted by that server's game integration

When a moderator uses one of TecnoCore's moderation commands (kick, ban, timeout, warning, etc.) in a server, we store:

• The action type, reason given, and timestamp
• The target member's Discord user ID and username, and the moderator's Discord user ID and username

If a server has the anti-raid honeypot trap enabled, we store a per-member strike count (Discord user ID and how many times they've triggered it) so repeated triggers can be told apart from a one-off false positive.

To keep the service secure and monitor usage, we automatically log certain events, such as page views, survey saves, deployments, failed logins, access attempts to a server you don't administer, or access by a suspended account. These logs include:

• The IP address the request came from
• Your Discord user ID (when the request is tied to a logged-in account)
• The type of action or event and a timestamp
• Your browser's user agent string

2. What We Don't Collect

• We do not receive or store your full card or bank details for paid plans - our payment processor (PayPal) handles those directly, and only sends us transaction status/metadata in return
• We do not read messages, DMs, or channel content, except: survey/quiz responses submitted through the bot, and - only in a channel where a server admin has specifically turned on the auto-translate feature - the text of messages posted there, which is sent to a third-party translation API (MyMemory) to produce the translated version posted back to the channel
• We do not sell, rent, or share your data with third-party advertisers

3. How Your Data Is Used

• To display your servers and their survey/quiz/giveaway configuration back to you on the dashboard
• To post surveys, quizzes, and giveaways to your chosen channel and collect responses/entries from your members
• To automatically assign a reward role to members who complete a survey or quiz, if you've configured one
• To run a giveaway's draw, and - if a prize is linked to your Game Keys Vault - to automatically DM a winner their prize key(s), including bundled giveaways that need one key per linked game
• To let you (or someone you've granted vault access to) add, deliver, and audit keys in your Game Keys Vault, and to automatically return an unclaimed auto-DMed key to the vault after its 3-day claim window passes
• To send a one-off confirmation email, only when a key recipient opts in and provides an address themselves after revealing their code
• To let members search the public leaderboard for their own stats or another member's, by Discord name or player ID
• To process and track payments for paid subscription plans via PayPal, and email you a receipt when a payment completes
• To maintain a login history and understand which channels bring visitors to the service, for our own product and marketing decisions
• To translate messages in a channel, only where an admin has explicitly enabled that feature
• To show you aggregate analytics (completion counts, drop-off rate, average time) for your own servers
• To respond to and resolve support tickets you submit
• To detect abuse, investigate suspicious activity, and enforce our terms of use (for example, by suspending or terminating an account)
• To link your Discord account to a connected Meta account, where a server admin has set that up
• To ingest and display live player progress on a server's public leaderboard, where that server has an active game integration
• To give server moderators an audit trail of moderation actions taken (kicks, bans, timeouts, warnings) on their own server
• To detect repeated anti-raid honeypot triggers from the same member, where a server has that feature enabled

4. Where Data Is Stored

All data is stored in a private database on our own server infrastructure - it is not stored with, or shared with, any third-party analytics or data-processing company. As of 7 August 2026, the entire database is encrypted at rest (using SQLCipher/AES-256), on top of the Game Keys Vault's existing key-level encryption described above, so the data is unreadable without our encryption key even if the underlying storage were somehow accessed directly. Your login session is kept in an encrypted, signed cookie in your browser and is never readable by anyone but our server.

5. Data Isolation Between Servers

Every server's survey questions, settings, and responses are strictly isolated from every other server - one server's data is never visible to another server's administrator, and only the Discord account recorded as a server's owner can view or manage that server's dashboard. This isolation applies to your survey configuration and response data specifically. Support tickets are handled by a central support team rather than being server-isolated, and templates you choose to publish are visible platform-wide - see the sections below for details on both.

A Game Keys Vault is isolated per Discord account, not per server - it belongs to whichever account created it, and stays private to that account until its owner explicitly grants another Discord account access to it. Granting access to your own vault never gives anyone visibility into anyone else's vault.

6. Public Templates & Community Features

The dashboard lets you save a survey as a reusable template and optionally publish it to a public gallery that other users can browse, use, and like. When you save a template, it defaults to publicly visible, though the "Make publicly visible" option is shown to you at save time and you can uncheck it to keep a template private. A published template's name, description, tags, and questions (but not your server's responses) are visible to other users, along with your username. The dashboard also supports following other users; if you follow someone, that connection is stored and used to show you their activity.

7. How Long We Keep Data

Survey/quiz/giveaway responses, entries, and configuration are kept for as long as you continue using the bot in your server. Giveaway winner draw records are kept as a permanent audit trail of who won and what was drawn from. Vault keys and their activity log entries are kept for as long as you keep your vault, so you retain a full history of what was added, sent, revealed, or reclaimed; deleting a game from your vault requires its keys to be handled first (delivered or removed), and deleting a key that hasn't been handed out removes it outright. Payment metadata is kept as required for our own accounting and to resolve any billing disputes. Support tickets and security logs are kept for as long as needed to resolve the ticket or investigate the relevant activity. Login history and landing page visit/attribution data are kept indefinitely in aggregate for product and marketing analysis, but individual login records tied to your account can be deleted on request per Section 8. Referral records, Meta account links, moderation action logs, and honeypot strike counts are kept for as long as the relevant server keeps that feature enabled, so its staff retain an accurate history and audit trail. If you'd like your data (questions, responses, entries, templates, vault keys, tickets, referral records, moderation records, or settings) permanently deleted, contact us using the details below and we'll remove it.

8. Your Rights

• You can request a copy of the data we hold about your Discord account or your server
• You can request deletion of your survey responses, templates, tickets, or your server's configuration at any time
• You can remove the bot from your server at any time, which stops any further data collection for that server
• You can unpublish a template at any time to remove it from the public gallery

9. Account Suspension & Termination

If we detect abuse of the service or a violation of our terms, we may temporarily suspend or permanently terminate an account's access to the dashboard. Suspension or termination affects dashboard access only - it does not itself delete your data. If you believe your account was suspended or terminated in error, you can reach out through the support contact below.

10. Children's Privacy

This service is provided through Discord, which requires users to be at least 13 years old (or the minimum age required in your country). We do not knowingly collect data from anyone below this age.

11. Changes to This Policy

If this policy changes in a way that affects how your data is handled, we'll update the date at the top of this page.

12. Contact

For any questions about this policy, or to request access to or deletion of your data, please reach out through the support contact listed in our Discord server or bot invite page.