Aeperion Aim

Privacy

Last updated: 26 August 2026

Aeperion Aim is a browser aim trainer run by Aeperion (aeperion.com). This page says exactly what the trainer stores, where it lives, and why. There is no advertising, no data sale, and no third-party analytics on this site.

The identity cookie

The trainer sets one essential cookie (aep_pid): a random, signed player id. It is what ties your scores, personal bests, profile and rank together, and it is the only thing that does — no account is required to play. Clearing it is effectively starting a new player. It identifies a browser, not a person; we do not know who you are from it. Signing in (Discord or X, where enabled) sets standard session cookies from our own domain so your identity can follow you across browsers; sign-in is optional and adds nothing but that.

Stored in your browser

• Settings — sensitivity, crosshair, colours, video options (localStorage).
• Round history and personal bests — the numbers your results screen charts (localStorage).
• Local replays — a copy of each finished run's input tape, so you can rewatch your own runs (IndexedDB, most recent runs only).

All of it stays on your device unless you submit a run.

Stored on our server

• Submitted runs — the input tape, score, and the settings the run was played with (sensitivity, DPI, field of view, average FPS, and cosmetic look for replay playback). Tapes for top-ranked runs are kept so other players can watch them.
• Profile — anything you choose to set: display name, country flag, featured run. All optional, all public.
• Progression — playtime and completed-run counters that drive your account level.
• Moderation records — automated integrity signals and staff decisions about runs, kept to protect the leaderboards.
• Browser and system: the browser family and operating system a run was played on (for example "Chrome 140", "Windows"), reduced from the User-Agent header your browser already sends. The full string is not kept.
• Presence: while the trainer is open it sends a heartbeat every twenty seconds saying whether you are in a round, with your browser's time zone name and the same browser bucket. The server keeps a count of players online, sampled once a minute; the per-player entry lives in memory and is gone about a minute after your last heartbeat.
• Feedback: what you write in the feedback box, the contact you choose to leave, and the browser bucket above, tied to your identity so staff can reply.
• Staff messages: replies and announcements sent to your in-game inbox, and when you read them.
• Score reports: when you report a run, the run, your reason and any note you add, tied to your identity. Staff see reports; other players do not.
• Replay views: one view per viewer per day on each shared replay. A viewer with no identity cookie is keyed by a hash of network address and browser that changes daily; the address itself is not stored.
• Outbound clicks: a count of clicks on the store and Discord links, tied to your identity, with whether you were signed in at the time.

Country detection

If you have not set a country flag, we may offer a suggestion — derived from your browser's own timezone setting (computed entirely on your device, nothing sent anywhere), or, where our hosting provides one, a single two-letter country code attached to your network request. It is only a suggestion — nothing is set unless you accept it — and no network address is stored with your profile.

Separately, each submitted run and each player carries an estimated country, used for the "where players are" statistics staff see. It comes from the country code our hosting attaches to the request when it does, otherwise from the time zone name your browser sends with the run (for example Europe/Berlin), otherwise from the region in your browser's language setting (for example en-GB). Only the two-letter result is stored, marked as an estimate and with which of those it came from; the time zone name itself is not kept. A flag you set yourself always overrides the estimate.

Technical logs

Like every web service, the server keeps short-lived operational logs (request paths, status codes, coarse rate-limiting counters keyed on hashed network addresses) to keep the service running and fair. These are not used to profile players.

Your choices

• Play without an account, forever — everything works as a guest.
• Clear your browser's site data to remove everything stored locally, including your guest identity.
• Leave the name and country blank — boards then show "Anonymous" and no flag.

Contact

Questions or removal requests: reach us through aeperion.com or the Aeperion Discord. If this policy changes materially, the date above changes with it.

← Back to the trainer