← Back to YASA

Privacy & analytics

YASA uses account and game records to provide sign-in, saved armies, online battles and battle history. Firebase manages authentication. Passwords are not sent to our analytics.

Records that keep the game running

Online matches create server records including the leaders selected, start and finish times, and a pseudonymous identifier for each seat. These allow us to count matches once and understand online activity, including guest matches. Service monitoring counts requests, errors and response times. These operational records do not require optional analytics cookies.

Your player profile and competition records

Your display name, permanent player tag and selected avatar identify you to other players. Level, leader mastery and preseason rank may appear on your profile; you can make progress details private and appear offline in Play online → My profile. Qualified ranked standings show your display name, tag, rating and match count. Your email and internal sign-in identifier are not included in public player profiles.

We store friend requests, accepted friendships, invitation preferences and blocks to provide social features. Reports and staff review notes are private operational records available to the authorised YASA owner. Blocking prevents social contact; it does not prevent ranked matchmaking against that player.

Battle records and shared replays

The server records match outcomes, rating changes and earned XP. Replays contain public board positions and public card information, never hidden hands, future draws or face-down Stratagems. Participants can view their completed replays. A replay becomes accessible through its link only after both participants allow sharing. Either participant can withdraw access for future requests; this cannot retract copies someone has already saved.

These player and competition records are retained to support account progress, replay access, moderation and result auditing. They are separate from the optional analytics retention periods below. The account export includes your tag, preferences, progression, saved armies and battle history.

Your optional analytics choice

If you allow analytics, we measure visits, game and tutorial starts/completions, download clicks and visible game activity. A random browser identifier helps estimate returning visitors. We collect broad device type, approximate country, referring service and a campaign label. Guest and shared-device counts are estimates.

Google Analytics also receives these selected events after you allow analytics. Advertising storage, advertising personalisation and Google signals are disabled. We do not send names, email addresses, passwords, room codes, hidden hands or verification/reset links to analytics. Account-action and owner pages do not load analytics.

Choose Analytics preferences in the game footer to change your choice. Declining does not stop you playing. Withdrawal stops future optional collection and removes this browser’s YASA analytics identifier and accessible Google Analytics cookies; it does not delete records already collected.

Retention and access

Detailed first-party optional analytics events and sessions are removed after 30 days through regular bounded cleanup. Hourly service counts are kept for 90 days. Pseudonymous play-day and match summaries are retained for longer-term game statistics. Only the YASA owner can open the aggregate monitoring dashboard. Google Analytics retains data according to the project’s configured settings.

Guest usage cannot be measured perfectly. Entirely offline downloaded play does not report analytics. Your signed-in account can export its profile, armies and battle history from the account.

Updated 30 October 2026.

Competitive standings and seasons

Your display name, public tag, rank and rating appear in public standings only when you opt in. A private progress profile always stays out of the standings. Turning visibility off removes you from subsequent responses; previously copied material cannot be recalled. Match records and rating history remain stored for competitive integrity. Matchmaking uses the region you select, not your precise location.