Separate sharing choice
This version defines the separate choice scope for the game integration. Reading this page, starting the game or accepting the privacy policy does not create consent. The choice must not be preselected or required to play.
Scope of an affirmative choice
“I choose to share checkpoint and attempt times, success/failure/incomplete observations, resets/retries, stone-break game coordinates and reasons, obstacle relationships and limited game conditions for analysis by Yusuf Samed AYDIN to improve balance and level difficulty.”
The permitted fields exclude SteamID, username, real name, email, account/profile links, persistent device/advertising identifiers, fingerprinting, chat, voice, images/video, unnecessary hardware information and file paths. Free-form text/logs and unlimited metadata are rejected, as are unexpected fields. Fixed technical identifiers must not encode player identity or text.
Duration and withdrawal
Raw analytics is limited to thirty days from session creation. The choice must be withdrawable through game preferences, stopping new sending and allowing deletion of the relevant session records. Refusal or withdrawal must not block play. Deleting a shared team session removes all team contributions within that session.
Random session identifiers group observations for a short period, deduplicate retries and support deletion. A verification digest is stored instead of the raw session credential; credentials must not enter URLs, logs or reports. Sessions are not linked through a persistent person/device identifier. Random identifiers and gameplay context alone do not guarantee anonymity and can constitute personal data together with connection information.
Information supplied together
This text is provided with the detailed game notice and general policy. Game-world coordinates are not real-world location. No new application backups are created. Connection IP and separate infrastructure records follow the general policy’s log explanation; this choice is not unlimited permission for all their processing/transfers.
Pyramidion is intended for ages sixteen and over. An age rating does not verify a player’s age. Applicable age/capacity requirements and any necessary parental conditions must be handled by the game integration; analytics must not be sent without an eligible valid choice. The API does not request age or birth date, and refusing analytics must not block play.
A server requirement for an affirmative client declaration does not by itself prove correct implementation of the actual game interface. The text versions shown must match the current API policy.
Optional checkpoint journey and departure observations
The 2026-10-16.2 scope adds observed starts, terminals, outcomes and active durations of checkpoint attempts and visits when a supporting client has this feature enabled. Observed attempt, failure and incomplete counts, failed active time and visit active time are cumulative counters. These count active gameplay independently of a rewound game timer; reset/loading waits, connection pauses and wall-clock time are excluded. Missing origins or traces are not treated as complete history.
A random run_id links API sessions only within one continuous game context, team and consent scope. A random checkpoint_visit_id links the effort to pass one checkpoint pair; sequence is shared across both new event types. These are not person/device identifiers and must not create a persistent player profile. Linking another transport session also requires a previously associated session's valid authority; run_id alone grants no access or deletion authority. An earlier sharing choice is not silently extended to this new scope.
An observed host main-menu or quit request may be reported as main_menu/quit_game. This does not prove that menu travel or operating-system exit completed. Roster changes, world closure, game completion and other technical boundaries have separate reasons. Silence is not confirmed departure or gameplay failure, and one member leaving does not prove the entire team abandoned the course.
Administrator reports derive attempt distributions, active durations and departure boundaries by checkpoint pair and game conditions. Rule-based indicators such as high observed failures/time followed by a host exit request, if shown, are labelled inferred candidates with thresholds and missing-observation limits. They are not psychological motives or verified rage quits. No player profiles or exit survey are added.
The linked run retention deadline is the original 30-day deadline of its first associated session; transport rotation cannot extend it. A valid, unexpired bearer of any associated session deletes raw events, links and report contributions across that run's associated sessions. Unrelated runs/sessions are unaffected. Limited run revocations prevent late revival until that same original deadline. Application backups remain disabled and recovery starts empty.