Privacy Policy
Exactly what we store, field by field, why we store it, who else sees it, and how to make us delete it.
Who we are and what this covers
This Privacy Policy explains what personal data the operator of Zenith ("we", "us", "our") collects when you use zenithmenu.com (the "Site") and the Zenith software (the "Software"), why we collect it, who else sees it, how long we keep it, and what you can require of us.
For the purposes of the General Data Protection Regulation (EU) 2016/679 ("GDPR") and equivalent legislation, we are the data controller in respect of the data described in Section 3.
The Operator is established in a member state of the European Economic Area and is subject to its law, including the General Data Protection Regulation. The Operator does not publish its country of establishment on this page, and will disclose it on request through a support ticket, to any supervisory authority, and to any court or tribunal before which a claim is properly brought.
All privacy requests are handled through the Zenith community server on Discord, which is our sole published contact channel. If you wish to complain to a supervisory authority and need to know which one supervises us, ask in a ticket and we will tell you.
We do not run advertising, we do not use analytics or tracking pixels, we do not build behavioural profiles, we do not sell or rent personal data to anyone, and we never see your card number.
This policy forms part of the Terms of Service and uses the definitions set out in Section 2 of those Terms.
How your data reaches us
There are only four ways personal data about you enters our systems:
- 01You sign in with Discord, and Discord passes us a defined set of fields described in Section 3.1.
- 02You use the dashboard, and your actions are written to an activity log described in Section 3.3.
- 03You buy a Licence, and our payment provider tells us that an order settled.
- 04You open a ticket on our Discord server, and you tell us whatever you choose to put in it.
We do not operate a registration form, a newsletter, a contact form, or a comment system. There is no other collection point.
What we actually store
This is the complete contents of our database as it concerns you, field by field. Nothing about you is stored by us outside of what is listed here.
3.1 Your account record
| Field | What it is and why we hold it |
|---|---|
| Discord user ID | The permanent numeric identifier for your Discord account. It is the primary key of your record and the only reliable way to recognise you across sessions, since usernames change. |
| Discord username | Your handle, shown in the dashboard so you can confirm you are signed in as yourself. Refreshed on each sign-in. |
| Discord display name | Your global display name, if you have set one. Shown in preference to the handle. |
| Discord avatar hash | A reference used to build the image URL shown in the dashboard sidebar. We do not store the image itself. |
| Email address | Supplied by Discord under the email scope. Held so that we can identify you if account access is disputed. We do not send marketing and there is no mailing list. |
| Software username | The username issued to you for the Software. You may change it, and the current value is the one we hold. |
| Software password | Stored encrypted with AES-256-GCM under a key held only in our server environment. It is never stored in readable form and is decrypted only at the moment your dashboard asks to display it. |
| Machine change counters | The number of times your machine binding has been released and when it last happened, used to enforce the limits in Section 11 of the Terms. |
| Restriction flags | Whether your account is restricted and the reason, where one applies. |
| Timestamps | When your account was created and when it was last seen, used to run the scheduled role reconciliation. |
3.2 What Discord gives us, and what it does not
We request four OAuth scopes and no others: identify, email, guilds and guilds.join. In plain terms this lets us see who you are, your email, which servers you are in so we can confirm you are in ours, and add you to our server if you are not.
We do not receive and cannot see your Discord password, your direct messages, your message history, your friends list, your payment details, or any content of any server. The list of servers you are in is checked at sign-in and is not stored.
3.3 Activity log
Actions taken on your account are written to an append-only log, visible to you in full under Dashboard, Activity. Each entry holds:
- what happened, such as a key redemption, a credential change, a role grant or a failed attempt;
- a short detail, such as a masked key fragment or the reason a request was rejected;
- the IP address the request came from;
- the browser user agent string;
- whether the action succeeded; and
- the time it happened.
The IP address and user agent are held for security and dispute resolution: to investigate account compromise, to detect licence sharing, and to answer a chargeback with evidence. They are not used to profile you, to target anything at you, or for any commercial purpose.
3.4 Rate limiting counters
We keep short-lived counters keyed to your Discord user ID recording how many times you have attempted a rate limited action, such as redeeming a key or changing a credential. These hold no content, only a count and a window start time, and they are overwritten as each window rolls.
3.5 Cookies
We set one cookie: an encrypted session cookie that keeps you signed in for up to seven days. It is strictly necessary for the Site to function and no consent banner is required for it under Article 5(3) of Directive 2002/58/EC.
We set no analytics, advertising, or tracking cookies of any kind. Clearing the cookie signs you out and has no other effect.
Why we process it, and on what legal basis
| Purpose | Legal basis under GDPR Article 6 |
|---|---|
| Creating your account, validating your licence, and giving you access to the Software | Performance of a contract, Article 6(1)(b). Without this data we cannot supply what you bought. |
| Applying and removing your Discord tier role | Performance of a contract, Article 6(1)(b). |
| Handling support tickets, refunds and machine binding requests | Performance of a contract, Article 6(1)(b). |
| Keeping the activity log, and logging IP and user agent | Legitimate interests, Article 6(1)(f), namely preventing fraud and licence sharing, investigating account compromise, and defending chargebacks. Balanced against your interests by keeping the log visible to you and by not using it for anything else. |
| Rate limiting and abuse prevention | Legitimate interests, Article 6(1)(f), namely keeping the service available and resisting automated abuse. |
| Retaining transaction records | Legal obligation, Article 6(1)(c), where tax or accounting law requires it. |
| Enforcing the Terms, including restrictions and terminations | Legitimate interests, Article 6(1)(f), namely protecting the service and other users. |
We do not rely on consent for any of the above, so there is no consent for you to withdraw. Where you object to processing carried out under legitimate interests, Section 8 explains how to do that.
We carry out no automated decision making that produces legal or similarly significant effects for you within the meaning of Article 22. Rate limits and fraud screening are mechanical thresholds, and every restriction or termination decision is reviewed by a person.
Who else receives it
We share the minimum necessary with the following processors and independent controllers. We do not sell, rent, trade or otherwise disclose personal data to anyone for their own marketing.
| Recipient | What they receive and why |
|---|---|
| Discord | Independent controller. Handles your sign-in, your membership of our server, your tier role and your support tickets. Everything you post in a ticket is held by Discord under their own privacy policy. |
| Licensing provider | Processor. Receives your Software username, your encrypted password and your licence state in order to validate the Software. It independently records the IP address and hardware identifier of the machine the Software runs on. |
| Payment provider | Independent controller. Receives your payment details and the email address you give at checkout. We receive only confirmation that an order settled and its reference. We never receive your card number, security code or bank credentials. |
| Hosting provider | Processor. Serves the Site and runs the server-side code. Sees request metadata including IP addresses in the ordinary course of serving traffic. |
| Database provider | Processor. Stores the records described in Section 3 at rest, in the European Union. |
We may also disclose data where we are legally required to, where it is necessary to establish, exercise or defend a legal claim, or where it is necessary to protect the rights or safety of a person. We will not volunteer your data to anyone who simply asks for it.
We do not proactively report our users to Rockstar Games, Take-Two, Cfx.re or any server operator, and we hold no data about what you do inside a game session. We would respond to a validly issued legal order, as any operator must, and would tell you unless prohibited from doing so.
Where your data is held
Our database is hosted in the European Union. Our hosting provider serves the Site from a global content delivery network, which means static assets may be served from a location near you.
Some of the providers listed in Section 5 are established outside the European Economic Area, principally in the United States. Where personal data is transferred to them, that transfer relies on the European Commission’s Standard Contractual Clauses, on an adequacy decision where one applies to that provider, or on the derogation in Article 49(1)(b) for transfers necessary to perform a contract with you.
You may ask us through a ticket which providers we currently use and on what transfer basis, and we will tell you.
How long we keep it
| Data | Retention |
|---|---|
| Account record | For as long as your account exists, and for twelve (12) months after your last licence expires, after which it is deleted unless you have asked for deletion sooner. |
| Activity log | Twenty four (24) months from the date of each entry, then deleted. Kept this long so that a chargeback, which can be raised many months after a purchase, can still be answered. |
| Rate limit counters | Until the relevant window elapses. Not retained beyond it. |
| Session cookie | Up to seven (7) days, or until you sign out or clear it. |
| Transaction records | For the period required by applicable tax and accounting law, which is typically between five and ten years. Held by our payment provider. |
| Restriction records | Where an account was terminated for cause, we retain the Discord user ID and the reason indefinitely, so that a terminated user cannot simply return. This is the narrowest record we can keep and serves only that purpose. |
Your rights
Where the GDPR or comparable law applies to you, you have the following rights. Exercising any of them is free, and we will not treat you differently for doing so.
| Right | What it means here |
|---|---|
| Access | You can ask for a copy of everything we hold about you. Much of it is already visible to you live under Dashboard, Activity and Dashboard, License. |
| Rectification | You can ask us to correct inaccurate data. Your name and avatar come from Discord and refresh on each sign-in, so correcting them there corrects them here. |
| Erasure | You can ask us to delete your account and its data, subject to Section 9. |
| Restriction | You can ask us to stop processing your data while a dispute about its accuracy or our legal basis is resolved. |
| Portability | You can ask for the data you provided to us in a structured, machine readable format. |
| Objection | You can object to processing we carry out under legitimate interests, including the activity log. We will stop unless we can demonstrate compelling legitimate grounds that override your interests. |
| Complaint | You can complain to the supervisory authority in your country of residence, place of work, or where you believe an infringement occurred. You do not have to contact us first, though we would prefer the chance to fix it. |
To exercise any right, open a ticket on the Discord server from the Discord account the request concerns. That account is itself the proof of identity, so we will not ask you for documents. We respond within one (1) month, extendable by two (2) further months for complex requests, in which case we will tell you within the first month and explain why.
Deleting your account
You can ask us to delete your account at any time. On deletion:
- your account record and its encrypted credentials are removed from our database;
- your account with the licensing provider is removed, together with any remaining licence time on it;
- your activity log entries are deleted; and
- your tier role is removed in Discord.
If you delete your account while a licence is still running, that time is gone and is not refundable. If you want your money back instead, read the Refund Policy first and ask for a refund rather than a deletion.
Two narrow exceptions survive deletion. We retain transaction records where tax or accounting law requires it, and where an account was terminated for cause under Section 19.1 of the Terms we retain the Discord user ID and reason so that the termination cannot be trivially undone by re-registering. Both are the minimum the purpose requires.
Deleting your account does not delete anything you posted on our Discord server, which is held by Discord. Ask in your ticket if you want your messages removed as well.
Security
We take the following measures. None of them make a system perfectly secure, and we do not claim otherwise.
- All traffic to the Site is served over TLS.
- Your Software password is encrypted at rest with AES-256-GCM under a key that exists only in the server environment and is never written to the database or to source control.
- Credentials that reach third parties are held server-side only and are never exposed to your browser or included in any page sent to it.
- Sensitive actions are rate limited per account and every attempt, successful or not, is written to the activity log where you can see it.
- Dashboard access requires a valid session and current membership of our Discord server, checked on every request.
- Administrative access to the database is restricted to the operator.
If a breach occurs that is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority within seventy two (72) hours where required by Article 33, and will notify you directly where Article 34 requires it.
You are responsible for the security of your own Discord account. It is the key to everything described in this policy, and we cannot recover it for you.
Children
The Site and the Software are not intended for anyone under eighteen (18) years of age, and Section 3 of the Terms makes that an eligibility condition. We do not knowingly collect personal data from children.
If you believe a child has provided us with personal data, tell us through a ticket and we will delete the account and its data promptly.
Changes to this policy
We may revise this policy at any time. The version in force is the one published at this address, identified by the effective date at the top of the page.
Where a revision materially changes what we collect, why we collect it, or who receives it, we will use reasonable efforts to give notice through the Site, the dashboard, or the Discord server at least seven (7) days before it takes effect.
Contact
Privacy questions, access requests, deletion requests, objections and complaints are handled through the Zenith community server on Discord, linked in the footer of the Site. Open a ticket from the Discord account your request concerns.
We do not publish a postal address or an email address. Correspondence sent to any address purporting to be ours other than through the Discord server is not validly served on us.