1. How to request removal
Data removal requests must be submitted through a support ticket in the official GUY2 Discord server from the Discord account associated with the data.
GUY2 Macros · Privacy
Data Removal Policy
How to request deletion of applicable GUY2 account data, what is normally removed, and what may need to be retained.
2. What can normally be removed
Applicable server-side records may include verification state, launcher sessions, registered device records, device-limit records, unverify-event records, and associated verification/audit records. The exact records removed depend on what is stored for the account and what must lawfully or reasonably be retained.
Removing server-side data does not automatically delete files stored on your own computer. You are responsible for deleting local GUY2 launcher data, settings, caches, and other local files if you also want those removed.
3. Aggregate statistics
Aggregate macro-usage totals, launcher-count statistics, and other statistics that no longer identify an individual user may be retained. These files are designed to store totals such as total seconds of official macro usage or concurrent-user counts rather than a per-user public history.
Backend operational logs may contain completed macro-run entries with a Discord username/user ID, macro name, and duration. Requests concerning identifiable logs will be reviewed subject to security, provider retention, and applicable-law limitations.
4. Blacklisted users and security records
Data-removal requests are accepted only through a support ticket in the official GUY2 Discord server. A blacklist does not disappear because a deletion request is submitted. Data associated with a blacklisted account or device may be required to identify the restricted user, link related accounts or devices, enforce the blacklist, detect blacklist or ban evasion, investigate abuse, protect the service, handle disputes, or establish, exercise, or defend legal claims.
Where the personal data retained for a blacklisted user is necessary for those purposes, GUY2 may retain that data for as long as it remains reasonably necessary. If all personal data still held for the blacklisted user is necessary for blacklist enforcement or related security purposes, a deletion request may result in no personal data being erased. Data that is genuinely unrelated and no longer necessary may still be removed where applicable.
Data deletion is not a blacklist reset. A deletion request cannot be used to remove or weaken a blacklist. Creating or using a new device identity, Discord account, verification state, or other method to evade a restriction or Discord-server ban is prohibited and may itself result in further restrictions.
5. When a request may be limited
A request may be refused, delayed, or only partially fulfilled where continued processing or retention is permitted or required by applicable law, including legal obligations, protection of others, security and abuse prevention, dispute handling, or the establishment, exercise, or defence of legal claims.
6. What happens after removal
Removing server-side verification/device/session data can sign the launcher out, revoke active sessions, and require a fresh verification if you use GUY2 again. If an account remains blacklisted, a new verification attempt may still be denied.
Deletion cannot be guaranteed to remove information instantly from transient caches, provider backups, or hosting logs that are controlled by service providers, although those copies may expire under the provider's normal retention process.
7. Submit a request
Open a ticket in the official GUY2 Discord server and state that you want a privacy/data-removal request. Do not post sensitive account information publicly.