1. Controller, purpose and method
The controller is Yusuf Samed AYDIN; contact techdevaydin@gmail.com. The purpose is to assess balance and level difficulty from normal play by people who choose sharing. The game client automatically transmits events over HTTPS; analytics is not required to play.
Optional balance and level-difficulty analytics relies on consent under KVKK Article 5(1) and, where applicable, GDPR Article 6(1)(a). Reading a notice or accepting a general privacy policy does not authorize analytics. Refusal or withdrawal must not prevent play. Short-lived application security and rate limiting are separate from analytics consent and rely on necessity and rights balancing under KVKK Article 5(2)(f) and, where applicable, GDPR Article 6(1)(f).
2. Permitted data
Events can include checkpoint arrival and game-clock time; attempt start/end/duration and success, failure or incomplete/invalid outcomes; retries and resets; and stone-break game-world coordinates, defined reason codes and obstacle relationships. Build, map, settings version, difficulty and party size accompany them. Defined active-pusher counts, strong-push or buff states may provide limited necessary context. Coordinates are game-world centimetres, not real-world location. Client game-clock times and durations use milliseconds and are separate from server receipt time.
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.
3. Accuracy of break attribution
Obstacle relationships distinguish a directly known cause, an inferred relationship and unknown. The last touched or nearest obstacle is not automatically a definite cause. Without a known or sufficiently inferred relationship the source is unknown and obstacle identifier/type are empty. Unmeasured values are not filled with zero; incomplete attempts do not enter the failure-rate denominator.
4. Separate choice and sessions
Sharing is off by default and optional; events are sent only after an affirmative choice for the current notice and separate scope text. This webpage does not create a consent record. Withdrawing through the game preference must stop further sending and allow deletion using the relevant session authority. A shared team session must respect everyone’s current choice; deleting it removes the entire team’s contribution within that session. A declaration received by the API alone does not prove a real informed choice; the game integration must implement that flow.
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.
A policy-version/availability request before a sharing choice also creates a technical connection. This is separate from gameplay analytics and subject to the connection-record limits below.
5. Retention, deletion and providers
Raw events and session context are retained for no more than thirty days from session creation, or deleted sooner on request. Upload authority lasts twenty-four hours; authority to delete that session lasts until its original thirty-day deadline. Expired records are excluded from reports and physically removed by cleanup scheduled at least hourly. Deletion removes events, attempt relationships and their report contribution. Minimal revocation entries and the local deletion journal may remain until new sessions’ original expiry to reject retries; they contain no raw token or gameplay event. Reports use retained raw records; there is no indefinite player profile or separate aggregate store.
No new application analytics backups have been created since 15 October 2026. Earlier encrypted copies contain synthetic data only; they expire within their original maximum seven-day limit and are not restored. Recovery initializes an empty analytics database and new journal while the service is in maintenance; old session credentials become invalid. This application policy does not eliminate possible provider infrastructure copies or statutory/security records.
The game API and MySQL/MariaDB database run on the TURKTICARET.NET Web Eko account. Its official hosting statement identifies Türkiye. Account support also stated that the offered JetBackup service is in Türkiye and that there is no overseas support team; that backup service is not active on this account. These are provider statements, not an independent country guarantee for every infrastructure copy or administrative access. Gameplay events are not automatically forwarded to Vercel or Gmail.
During a connection the server can see the IP address, requested address, time and technical headers. The application does not log raw IP addresses, tokens or request bodies. A seven-day retention setting is saved for account access-log archives in cPanel; the panel reports a 24-hour raw-log processing interval. This setting does not control the provider’s separate security, system or control-panel records. Their retention follows the provider’s published statutory and purpose-based criteria; an account-specific numerical maximum has not been confirmed for every category. We therefore do not promise deletion of all infrastructure records within seven or thirty days.
6. Rights and age scope
Contact techdevaydin@gmail.com to ask whether data is processed, request information/access, correction, erasure or recipient notification, and exercise applicable rights to object, restrict processing, portability or complain to a supervisory authority. KVKK requests are answered within thirty days; where GDPR applies, normally within one month, with any applicable extension explained. The appropriate submission method and proportionate verification depend on the request. Never email a raw session token or put it in a URL. Since we do not link sessions to accounts or names, we may be unable to locate a record by your identity if session authority is lost. We do not request unnecessary SteamIDs, birth dates or identity copies.
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.
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.