AACGUARD Privacy Notice

1. Who is responsible for your data?

AACGUARD is developed and operated by Pelea Raul-Daniel, Cluj-Napoca, Romania (“we”, “us”, “our”), who is the data controller under EU data protection law (including the GDPR) for the personal data processed through the AACGUARD client, the website and the API. More detail on your rights is on our GDPR page.

You can reach us primarily via our community Discord:

• Discord: https://discord.gg/gsyVyc4xUp
• Steam profile (owner): https://steamcommunity.com/id/DefinitelyNotAppo/
• Support Email [email protected]

2. What the AACGUARD client reads on your PC

The client runs as administrator, because most of the records below can only be read with administrator rights, and it runs in user mode (it does not install a kernel driver). It reads your PC in four situations:

• Full scan: only when you press Start or Restart (or Full scan in the tray menu). Everything in 2.1–2.7.
• Quick check: only when you choose it in the tray menu. What is running right now (2.1 and the proxy DLL check in 2.2). It stays on your PC.
• AACGuard Live: automatically, all the time AACGuard is running: what is running now every minute, and while CS2, CS:GO, CS 1.6 or another Valve game (such as Team Fortress 2, Dota 2, Deadlock or Left 4 Dead) is open, the game every 30 seconds (see 2.8).
• Fresh Start (PRO): only when you start it (see 2.9).

Since v0.0.12 AACGuard keeps running in the system tray when you close its window, and starts with Windows by default (a Task Scheduler task named “AACGuard”; you can turn this off in the tray menu and it stays off). While it runs in the tray it runs AACGuard Live (2.8), which only looks at what is running right now and never reads history; full scans only run when you start them. Everything listed here is analysed on your PC; Section 3 explains what is sent.

2.1 Running software and the game

• Running processes and their start times, and which supported game is running (CS 1.6, CS:GO, CS2, FiveM, Minecraft, Roblox).
• Modules (DLLs) loaded into the game, and code placed in the game's memory without a file on disk.
• Other programs that have the game's memory open for reading or writing (program name and path only; memory contents are not read).
• The memory of the running CS or other Valve game itself is searched for byte patterns and text of known cheats (signatures downloaded with the scan rules); cheat names are only searched in game code that has no file on disk. AACGuard Live does this at most every 5 minutes. The memory contents are not saved or sent: a match reports only the signature name, the memory address and the kind of memory.
• In CS 1.6 and other OpenGL Valve games, the first bytes of the game's OpenGL drawing functions and the game's OpenGL import table are read to see whether they were redirected (hooked). Graphics drivers, Windows and known overlays and recorders (Steam, Discord, OBS, RivaTuner, NVIDIA, AMD, Fraps, Bandicam and similar) are ignored. Only the name and path of the module a hook leads to are reported; no memory is saved or sent.
• Visible windows that are transparent, always on top and click-through and cover most of the screen, the way ESP overlays work (owning program, window title and size; window contents are not captured).
• Loaded kernel drivers, and registered services, drivers and scheduled tasks (their names and the programs they start).
• The Counter-Strike server you are connected to, or the last one from Steam's server history. The client may query that server's public information and look up its domain name.
• Network connections (since v0.0.15): the list of open internet connections with the program that owns each one, matched to host names using the addresses your PC already looked up (Windows' DNS cache) and the cheat-site list. Only connections to cheat servers are reported (program, server name and address). No network traffic is read.
• Windows memory since start-up (since v0.0.15): the memory of Explorer and of the Windows services PcaSvc, DPS, DiagTrack and SysMain is searched for the paths of programs that were run or opened since the PC was last started. Only paths that match cheat names are reported; nothing else from that memory is kept or sent. Paths of programs that still exist are passed to the program-content check in 2.2.
• Devices (since v0.0.15): the USB, HID and PCI devices Windows has registered (device name, ID and last connect / removal time) are checked for hardware cheats: Arduino / Teensy boards set up as a mouse or keyboard, KMBox, Cronus, Titan Two and XIM input adapters, and DMA cards (Xilinx FPGA boards, FTDI FT601 bridges). They only count when connected now or today.

2.2 Files and folders

• File and folder names in AppData, Downloads, Desktop, the Recycle Bin, the CS game folders, RAM disks and currently connected removable drives, compared with cheat-name lists. Some files are hashed (SHA-256) to compare with known cheats.
• Game folders (Half-Life / CS 1.6, CS:GO, CS2) are checked for DLLs named like Windows graphics, input, sound or network DLLs and for .asi plugins; their signature, version information and hash are compared with the genuine files.
• CS 1.6, CS:GO and CS2 cfg files are read and analysed for cheat / HvH settings.
• Program contents (since v0.0.15): unsigned .exe, .dll, .sys and .asi files (8 KB - 32 MB) in Downloads, Desktop, Documents, Temp and AppData, programs that are running, and programs Windows recorded as run are read for the names a CS cheat needs (CS2 / CS:GO memory offsets and player fields, CS 1.6 client functions). Only the names found and the file path are reported, never the file.
• CS 1.6 game files (since v0.0.15): wall textures (.wad), player models, sprites, textures, maps and game DLLs of Steam and non-Steam CS 1.6 installs are compared with fingerprints of Valve's original files. Only the names of changed files and how they differ are reported.
• Macro scripts (since v0.0.15): AutoHotkey scripts (.ahk, .ah2, including the ones AutoHotkey is running), Logitech G Hub / Logitech Gaming Software Lua scripts and Bloody macros (.amc) in your folders are read to see whether they control recoil, repeat jumps or aim by screen colours. Having macro software installed does not count.
• Discord cache (since v0.0.15): the cache of the Discord app (stable, PTB, Canary) is searched for links to attachments; only the file names of programs, archives, scripts and configs are compared with the cheat-name lists. Messages and images are not read.
• File fingerprints (since v0.0.15): for a finding whose file is still on the PC (a program, game plugin or archive up to 64 MB), its SHA-256 and SHA-1 hash and size are added to the scan log.
• Other file contents are not read: apart from the items above, only cfg files and the version / signature information of program files are read.

2.3 Windows activity records

• Program execution records: Prefetch (program path, drive, last run times and run count), BAM / DAM, ShimCache, AmCache (path, SHA-1 hash, publisher, compile date; read through a temporary Windows shadow copy when the file is locked), MUICache, UserAssist (programs started from the desktop, Start menu or taskbar, with run count and last start; since v0.0.15, for every user profile), Run keys, shortcuts and the Windows 11 program launch log.
• Recently used items: Recent files, Office recent files and Jump Lists, and Explorer folder history (ShellBags). These are read for every Windows user profile on the PC, including accounts that are not signed in.
• Recently deleted or renamed file names from the NTFS change journal.
• Windows Defender detection history (threat name, file path and time).
• Virtual-machine software and installer events, RAM-disk software, and cleaner / anti-forensics tools.

2.4 USB devices

• The USB storage devices this PC has recorded: device name, serial number, drive letters, volume labels and serials, and first-installed / connected / removed times.
• Programs, files and folders that were used from USB drives or other drives that are no longer present, linked to the device they came from. The contents of drives that are not connected are not available to the client.

2.5 Browsers, network and Steam

• Browser history of Chrome, Edge, Brave, Opera, Opera GX, Vivaldi, Yandex, Firefox and similar browsers: page addresses and titles are compared with cheat-site and cheat-search lists. Only matches are kept (with visit count and first / last visit time); the rest of your history is not stored or sent.
• Domain names in Windows' DNS cache (recently looked-up sites), compared with the cheat-site list. Only matches are kept.
• The Steam account last signed in on the PC (SteamID64 and display name) and Steam's server history.
• All Steam accounts used on the PC (since v0.0.15): the SteamID64, profile name and last sign-in of every account in Steam's sign-in list and every account folder in Steam's userdata folder. Login names are never put in the report. Section 3.5 explains the ban check the website does with them.

2.6 Tampering checks

• Whether Windows event logs were cleared, Prefetch was switched off or the clock was changed by a program (last 30 days, from the System log and, since v0.0.15, the Security log; when the clock was moved back, older traces are no longer given a lower weight in the verdict); whether aacguard.com is blocked by the hosts file, DNS or Windows Firewall rules; and whether Windows started with test-signing, kernel debugging or integrity checks disabled.

2.7 Hardware fingerprint and spoofers

• Serial numbers of the motherboard, BIOS and system disk, the SMBIOS UUID, the Windows machine ID (MachineGuid) and the factory address of the network adapter are read and turned into one-way salted hashes on your PC. The raw serial numbers are not stored or sent; generic placeholder serials are skipped.
• Traces of hardware-ID spoofer tools, and wired network adapters that use a changed MAC address.

2.8 AACGuard Live (automatic, while AACGuard runs)

• From the moment AACGuard starts (including at Windows start), every minute: running programs, overlay windows and loaded drivers.
• While CS2, CS:GO, CS 1.6 or another Valve game is open (Team Fortress 2, Dota 2, Deadlock, Left 4 Dead 1 and 2, Half-Life, Half-Life 2, Portal 1 and 2, CS: Source, Day of Defeat, Half-Life: Alyx and other games on Valve’s engines), every 30 seconds: modules and code loaded into the game, programs that have the game's memory open, overlay windows over the game, proxy DLLs in the game folder, running programs and loaded drivers, and the server you are connected to.
• Since v0.0.15 Live checks also look at which programs are connected to a cheat server (Section 2.1, Network connections).
• No history is read during Live checks (no program history, browsers, USB devices or deleted files).
• You can turn AACGuard Live off in the tray menu (“AACGuard Live: ON / OFF”) until AACGuard restarts; it starts on again with AACGuard. To stop it completely, exit AACGuard and turn off Start with Windows. If a supported game opens while it is off, the app tells you once.

2.9 Fresh Start (PRO, only when you start it)

• Runs the full scan locally (nothing is uploaded) and lists the cheat files still on the PC. Only the files you tick are deleted, permanently; a cheat still running from one of them is closed first.
• It never deletes Windows' activity records (Prefetch, recent files, logs, registry, browser history), anything in the Windows folder, or installed programs other than files inside game folders, and it cannot run while a supported game is open.
• Each Fresh Start is recorded on the PC (date and paths of deleted files) and, for 30 days, included in your scan reports as an informational finding (Section 3.1).

The client does not upload executable files, documents, browser databases, registry files, screenshots or memory contents.

3. What the client sends to our servers

3.1 Scan report (sent after every completed scan)

The report is sent over HTTPS to api.aacguard.com and contains:

• Identity: your SteamID64 and current Steam display name.
• Result: client version, verdict (CLEAN, SUSPICIOUS or CHEAT DETECTED), score, number of checks and detections, and the status of each check.
• Context: the game / process that was running and whether it was closed during the scan, which browsers were found, and the current or last Counter-Strike server address.
• IP address (masked): your public IPv4 address in a masked form (for example 2*.42*.**.2*). Our server also sees the network address of the HTTPS connection itself, as every website does.
• Hardware fingerprint: one overall hash plus one hash per hardware component (Section 2.7), used to recognise a PC that returns on a different Steam account after a ban. Raw serial numbers are never sent.
• Scan log: the full log of the scan. It contains the details of every finding and of the records checked, and can include file and folder paths, Windows user account names, cheat-site addresses with visit times, USB device names and serial numbers with connect times, programs run from USB drives, Defender detections, deleted-file names, and service and task names. If you used Fresh Start in the last 30 days, the report also lists when and which files it removed. Since v0.0.15 the log also contains, for each finding, the dates Windows recorded for it, how many points it counted and why, the fingerprint (hash) of cheat files still on the PC, how long each check took, and the list of Steam accounts used on the PC (Section 2.5). On the scan pages, Windows user account names are hidden wherever they appear: in file paths (for example C:\Users\***\Downloads), in account names such as DESKTOP-1\***, and elsewhere in the log, people's names found in folder and file names (and the real name on your Steam profile, if it is public) are hidden too, e-mail addresses are masked, and USB serial numbers, volume serials and network (MAC) addresses are partly masked (for example 0302***540).

3.2 Optional detailed diagnostics

Only if you tick the option in the client's Data use & consent window, the report also includes detailed messages for each check and the full content of cfg files identified as cheat / HvH configurations (path, name and content).

3.3 Other requests the client makes

• aacguard.com: downloads the scan rules (cheat lists, whitelist, hash lists), the required client version, and the list of today's scans shown in the Detected Players window.
• api.ipify.org: a public service used to learn your public IP address, which is then masked before it is sent to us.
• The game server you are connected to, and DNS, to show the server's name.
• api.aacguard.com, only when you are signed in with Steam in the app: your profile (plan, scan totals, public Steam, FACEIT and Leetify statistics) and AACGuard Live heartbeats (Section 3.6).
• Microsoft Edge (installed with Windows), on your PC only: used to turn an exported report into a PDF. Nothing is sent anywhere.
• aacguard.com/sponsorship/, while the app runs: the sponsor banners shown at the bottom of the window (checked about every 15 minutes; videos are cached in your Temp folder). Only normal connection data such as your IP address reaches our server; nothing about you or your PC is sent. Clicking a banner opens the sponsor's website (or our Discord) in your browser, where their own privacy policy applies. The same banners appear in a small “Sponsored” area on some pages of this website; they are served from aacguard.com itself, with no third-party ad network, cookies or tracking.

3.4 Declining the upload

In the client's Data use & consent window you can turn report uploads off for the current session. The scan then still runs and shows its local report, but nothing (including the hardware fingerprint and the log) is sent. A scan that is not uploaded does not appear on the website and cannot be used as proof on a server.

3.5 Data collected on the website and panel

• Standard server logs (e.g., IP address, user-agent, request URLs, timestamps).
• Aggregated visit and usage statistics via analytics tools (see Section 7).
• Our own page-view counter (no cookies, no third party): for each page view we store the page, the time, your country as reported by our CDN (Cloudflare), the site that linked you, whether you use a phone or a computer and whether you are signed in. To count unique visitors we store a one-way hash of your IP address and browser that changes every day; it cannot be turned back into your IP address or used to follow you across days. Search-engine bots are not counted. These records are only shown to the site owner as totals and are deleted after about 13 months.
• Cheat file fingerprints (since v0.0.15): the hashes, size, name and path (with the Windows account name hidden) of cheat files found by scans are stored in a list of known cheat files, linked to the scans and players they were found for. Only the site owner sees this list; confirmed cheat files are added to the scan rules so the same file is recognised on other PCs, and files reviewed as legitimate are added to a list the client ignores.
• Linked Steam accounts (since v0.0.15): for the Steam accounts used on a scanned PC (Section 2.5), the website asks Steam's public Web API for their VAC, game, community and trade bans (cached up to 6 hours) and checks them against AACGUARD's own bans. The full list is shown only to the site owner; other visitors and server owners with a PIN only see how many of the other accounts are banned, never which ones.
• Appeals: if you appeal a verdict or ban (signed in with Steam), we store your SteamID, the scan you appeal, your message, the optional Discord name and the screenshots you upload, plus the owner's answers. Screenshots are re-encoded and stored privately; only you and the site owner can open them. Appeals are kept while the related scan or ban exists, and you can ask for them to be deleted at [email protected].

3.6 AACGuard Live status (everyone running AACGuard)

Every minute and whenever the status changes, the app sends api.aacguard.com: a random session id, the game (or none), the detected server address, the status (CLEAN, SUSPICIOUS or CHEAT DETECTED), the descriptions of up to 10 findings and the client version.

• Signed in with Steam in the app: your SteamID64 comes from your sign-in and your status is marked verified.
• Not signed in: the app also sends the SteamID64 and Steam name of the account logged in to Steam on your PC, and your status is marked not verified. For these, the server stores a one-way hash of your IP address, used only to limit how many players one connection can report. If no Steam account is found on the PC, nothing is sent.

3.7 Signing in in the app, and AACGUARD PRO

• Desktop sign-in: the app opens aacguard.com in your browser and Steam confirms your SteamID64; we never see your Steam password. We store a hash of the app's session token (never the token itself) with its expiry, last use, the app version and the IP address it signed in from. On your PC the token is kept encrypted for your Windows account.
• PRO purchases: payment is handled by PayPal on PayPal's pages; we never receive card or bank details. We store the plan, amount, currency, the PayPal order and capture references, the payer e-mail address PayPal returns, and the dates, plus your PRO status and end date.
• PRO profile customisation: if you have PRO and choose to, we store the avatar and banner images you upload (re-encoded to remove hidden metadata where possible, kept outside the public web folder under random names), your bio, the Discord, YouTube and Twitch names or links you enter, and your chosen name animation, colours and profile theme. You can change or remove them at any time in Settings. They are shown only while your PRO is active, are kept (hidden) if PRO ends so they come back when you renew, and are deleted if you ask us to delete your account. We may remove content that breaks the Terms.
• PRO revocations: if staff revoke your PRO for breaking the rules, we store the reason, the message shown to you, an internal staff note, up to 5 evidence screenshots made by staff (kept outside the public web folder; only you and staff can open them), who revoked it and when, the PRO time you had left, the end of the 5-month purchase block and how many times the notice was shown to you. The records are kept while the block lasts and afterwards as a record of the decision, for as long as needed to handle disputes and repeated abuse.
• Discord link (optional, in Settings): when you link Discord, Discord tells us your Discord user ID and name; we store only those, never your Discord password or login tokens. We use them to add you to the AACGUARD Discord server and to give or remove the PRO role there automatically while your PRO is active. Your public profile shows a “Discord Verified” badge while the link exists (your Discord name and ID are not shown). You can unlink at any time in Settings, which removes the role, the badge and the link.
• Country and custom profile link (optional, in Settings): the country you pick (suggested from your Steam profile until you save) is shown as a flag on your profile and next to your name on Detected players; a custom link you claim (aacguard.com/yourname) opens your profile while profile sharing is on. Flag images are loaded from flagcdn.com, which receives the visitor's IP address like any image host. You can change or remove both at any time.

3.8 Things that are only sent when you press a button

• Report false positive (scan report window): one finding - its description, file path or address, source, strength, points, game, why it was flagged - plus your optional note, your SteamID64 and Steam name, the app version and a keyed hash of your IP address (used only to limit reports to 20 a day). Your Windows account name is removed from paths before sending. Reports are reviewed by us to fix false detections and are deleted after at most 12 months.
• Pre-match check share link: the result of the check (CLEAN / SUSPICIOUS / CHEAT DETECTED), the number of counted findings and, if it was not clean, up to five finding names without paths, the game, the app version, your SteamID64 and Steam name, and a keyed hash of your IP address (limit: 6 links per 10 minutes). Anyone with the link can see it on aacguard.com/check.php for 3 hours; the record is deleted 7 days after the link expires. The pre-match check itself stays on your PC unless you create a link.
• Without Steam sign-in in the app, both use the Steam account logged in on your PC and are marked “not verified”.

The app also keeps your last 10 scans in %LOCALAPPDATA%\AACGuard\scan_history.json on your PC (never uploaded; “Clear history” deletes it), and checks aacguard.com/downloads/min_version.txt at start and every 6 hours to show when a new version is available.

4. How and why we use your data

• Cheat detection and integrity: to detect cheat programs, loaders, injected code, external cheats, cheat configurations and traces, and to compute a score and verdict.
• Admin review and moderation: to show scan results, the scan log and the masked IP to server administrators so they can make their own moderation decisions.
• Ban-evasion checks: to compare hardware fingerprints between scans and recognise a PC that returns on another Steam account.
• History and evidence: to keep a long-term history of scans so communities can see patterns over time and reference past results.
• Improving AACGUARD: to refine detection logic, add new cheat names, hashes and heuristics, and reduce false positives.
• Website and service operation: to keep the site secure, monitor traffic, and understand how many users visit and download the client.

Under EU law, our legal bases are your consent (Section 5) and our legitimate interest in protecting game servers from cheating and abuse.

5. Your consent, public visibility and GDPR

By downloading AACGUARD, installing the client and running scans with uploads enabled, you consent to:

• The scan report described in Section 3.1 (including the scan log and hardware fingerprint) being sent to and stored on our servers.
• Your SteamID64, Steam name, verdict, score, game, server and scan date being shown publicly on the AACGUARD detected-players pages.
• Each scan having its own page (scan_view.php) that shows the scan details including the scan log (with Windows user names hidden and device serial numbers partly masked), which can be opened by anyone who has or finds the link.
• Each uploaded scan getting a random 6-digit server owner PIN, shown to you at the end of the scan and valid for 7 days. Anyone you give it to can open the same scan details in the AACGuard app (Server owner), with the same masking as on the scan page. Only the PIN is sent when someone looks a scan up; nothing about their PC.
• Long-term storage of your scan history for anti-cheat and moderation purposes.
• Your AACGuard Live sessions (Steam name, SteamID64, avatar, whether it is verified, game or “no game open”, server, status and how long the session ran) being shown publicly on the Live page and your profile while AACGuard runs and for two hours after. This applies whether or not you are signed in. Finding descriptions sent with Live heartbeats are not shown publicly.
• Your plan (FREE or PRO) being shown next to your name on public pages.
• Your PRO profile customisation (custom avatar, banner, bio, Discord / YouTube / Twitch links, name animation and colours, profile theme) being shown on your profile, through your share link, and (avatar and name style) on the public Detected players list, while your PRO is active.
• If your PRO was revoked for breaking the rules: a community guidelines notice with a short reason (not the evidence) being shown on your public profile until the 5-month purchase block ends.

You can review exactly what a scan contains in the client's local report before closing it, and you can decline the upload as described in Section 3.4. If you do not agree with this notice, do not download, install, or use AACGUARD.

We are based in the EU and aim to comply with GDPR principles, but AACGUARD is designed for anti-cheat and moderation use. By using it, you acknowledge that your scan data may be publicly visible to help protect servers from cheating.

6. Where we store data and for how long

• Location: scan data is stored in a MariaDB database on our VPS in Germany, behind our web backend and API.
• Retention: we do not automatically delete scan records. Clean, SUSPICIOUS and CHEAT DETECTED scans, including their logs and hardware fingerprints, may be kept indefinitely to maintain a complete history.
• Accounts, Live and PRO: app sign-in sessions expire after 90 days and are deleted when you sign out; AACGuard Live sessions are kept like scan history (they are not automatically deleted today); PRO payment records are kept for as long as accounting and tax law requires.
• On your PC: temporary copies of Windows records (for example AmCache and user registry files) are made in your Temp folder during a scan and deleted when it finishes. The client does not keep scan history on your PC. It keeps a few small settings files in %LOCALAPPDATA%\AACGuard (the encrypted sign-in token and your choices for themes, AACGuard Live and Start with Windows), the Fresh Start record in %ProgramData%\AACGuard\fresh_start.json, and the “AACGuard” Task Scheduler task while Start with Windows is on. Reports you export are saved only where you choose.

If we introduce automated deletion or archiving rules in the future, we will update this page.

7. Analytics, DDoS protection, and third-party services

• Analytics: we use tools such as Google Analytics, Matomo, and similar analytics platforms to measure visits, page views, and general traffic. These services may set cookies and process your IP address, user-agent, and basic usage information according to their own privacy policies.
• DDoS protection and CDN: we use Cloudflare (and may add other anti-DDoS and security providers in the future) to protect the AACGUARD site, panel and API. This may involve routing your traffic, including scan uploads, through their infrastructure, where additional logs and security checks are performed.
• ipify: the client asks api.ipify.org for your public IP address (Section 3.3).
• Steam, FACEIT and Leetify: to sign you in and build your profile we use Steam's OpenID sign-in and request public data for your SteamID64 from the Steam Web API, the FACEIT Data API and Leetify's public API. They receive your SteamID64 in those requests.
• PayPal: processes PRO payments as an independent controller under its own privacy statement.
• Google AdSense (ads on the server list): the server list on this website shows one ad from Google AdSense, only if you accept “marketing” cookies in the cookie banner; otherwise no ad network is loaded. Google and its partners (third-party vendors) use cookies to serve ads based on your prior visits to this and other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the Internet. You can opt out of personalised advertising in Google Ads Settings or at aboutads.info, and change your cookie choice here at any time. See also how Google uses information from sites that use its services. Ads are never shown in the desktop app, on scan results, the Trust Center, legal pages or checkout, and PRO members do not see them.

We currently use only our own anti-cheat code for scanning. If we ever incorporate code or modules from other anti-cheat projects, we will mention this in our changelog and respect any applicable licenses.

8. Your rights and access to your data

Each scan page shows the data we store for that scan: Steam ID, Steam name, verdict, score, game, server, the status of each check and the scan log. The hardware fingerprint is stored as hashes and is not shown publicly. We do not maintain a separate hidden profile with additional personal details.

You have the rights listed on our GDPR page: access, correction, deletion, restriction, objection, portability and complaint to a supervisory authority. Send requests to [email protected]; we answer within one month.

Account data (desktop sign-in sessions, website profile, AACGuard Live sessions) is deleted on request, except payment records we must keep by law. Requests to delete scan records are assessed one by one: we may keep a scan where we have overriding legitimate grounds, in particular protecting game communities from cheating and ban evasion, or where it is needed for a dispute, and we will tell you why. Scans that were wrong (for example a confirmed false positive) are corrected or removed.

9. Future deeper scanning

The current client runs in user mode and does not install a kernel driver. In the future we may introduce deeper or kernel-assisted checks, or process certain signals on our servers to remain compatible with official anti-cheat systems.

Our intent is to process only the information necessary for cheat detection. We do not plan to store raw memory dumps or unrelated system content.

Every client release that changes what is read or sent updates this notice and the client's in-app Data use & consent window, and is listed in the changelog.

10. Changes to this Privacy Notice

We may update this Privacy Notice to reflect changes in AACGUARD, our data practices, or applicable laws. When we do, we update the “last updated” date at the top of this page.

Your continued use of AACGUARD after an update becomes effective means you accept the revised Privacy Notice. If you do not agree with the changes, stop using AACGUARD and uninstall the client.