Who is responsible
AOE2TEAM is operated by a non-professional publisher. Privacy requests can be sent to privacy@aoe2team.uk. General or legal correspondence can be sent to contact@aoe2team.uk.
Only the data needed to run AOE2TEAM.
Match analysis remains available without an account. Google or Steam sign-in is optional.
Data used
For public match analysis, AOE2TEAM uses public Age of Empires II player and match data, including profile identifiers, player names, ratings, match information and replay data when available. If you choose to sign in, AOE2TEAM stores the identifier supplied by Google or Steam, your account display name, your optional linked AoE profile and any favorites you save. Google may also provide your email address. Steam sign-in provides your Steam identifier; AOE2TEAM does not receive your Steam password.
Personal chronicle
If you use the chronicle, AOE2TEAM also stores your saved match IDs and analysis snapshots, folders and labels, Elo goal, selected teammates and dated Style Radar measurements (scores and sample sizes). These records are deleted with your account and included in your account export. Public match data used for calculations are retrieved from the game service.
Why it is used
Public game and account data are used to provide the analysis and account features you request. This processing is necessary to provide those services. Limited technical and security processing is based on AOE2TEAM's legitimate interest in operating and protecting the service. A strictly necessary session cookie keeps you signed in; it is not used for advertising.
Providers and retention
AOE2TEAM uses Cloudflare Workers for application hosting and Cloudflare D1 for account data where applicable. Cloudflare also provides domain and DNS infrastructure. Google processes authentication data when Google sign-in is chosen, and Steam processes authentication data when Steam sign-in is chosen. These providers may process data outside the EEA under their applicable safeguards. Account data are kept while the account is used and are automatically deleted after 24 months of inactivity. You can export your account data or immediately delete the account and its sessions at any time. AOE2TEAM does not sell account data and does not use advertising tracking in this release.
Audience measurement
AOE2TEAM uses limited first-party audience measurement to count aggregate page views, player searches and replay reliability. The same first-party measurement stores only the normalized page path and, for the first page of a visit, the landing path, a normalized traffic-source label and Cloudflare’s two-letter country code. Visit boundaries are determined server-side from the same pseudonymous daily hash with a short inactivity window; the analytics beacon does not create a browser identifier or use browser storage for this purpose. External referrers are reduced to a search-engine, AI/social-source label or hostname; full referrer URLs, search terms and query strings are not stored in the acquisition table. For daily unique-visitor counting, a pseudonymous hash is derived from the request IP address and user-agent with a secret salt; the raw IP address and user-agent are not stored in the analytics tables. Global Privacy Control and Do Not Track are respected. Daily visitor hashes are deleted after 31 days and daily aggregate counters after 400 days. Cloudflare Web Analytics integration is prepared but is not currently enabled in production. If enabled later, Cloudflare states that Web Analytics uses no cookies or localStorage, does not fingerprint visitors and does not collect visitors’ personal data for Web Analytics.
Your rights
Where the GDPR applies, you may request access, correction or deletion of your personal data and exercise other applicable rights. Signed-in users can export or delete their account directly. Requests can be sent to privacy@aoe2team.uk. You may also lodge a complaint with the CNIL.