BingBong Airlines FLIGHT TFA · TRUE FINAL ASCENT
PEAK

True Final Ascent Mod

PrivacyTrue Final Ascent

The short version

This website does not follow you around: no ads, no analytics, no tracking cookies.

Everything you see here comes from the True Final Ascent mod - and only if you switched on its online features in the game. With them off, the mod does not send your data. You can flip them (and the leaderboard tick) any time in the pause menu.

What we collect, who sees it, how long it stays

WhatWho sees itHow long
Daily leaderboard - your Steam name, name colour, time, time per biome and more details from the PEAK runEveryone - but only scouts who ticked Take part in the leaderboards. Ghosts are greyed out. The best time of each scout counts for the all-time top 50; searching for a name shows a scout's all-time place.Permanently
Death points - where and how a scout died: position, height, biome, cause, weather, difficulty, run time, group sizeEveryone, as anonymous dots - no names1 year
Apocalypse chronicle - outcome, climb, weather report, the scouts with the leaderboard tick and their stats, climb graphEveryone30 days, then only anonymous numbers for the statistics (no names, no IDs)
Steam ID - travels with every report; from mod 2.6.5 confirmed by Steam (see Steam check)Only for moderation. Never shown publicly.Permanent
Steam check - from mod 2.6.5 your game asks Steam for a one-time ticket, and our server hands only that ticket to Valve (Steam), which confirms your Steam ID. No password, no other account data. If Steam reports that someone else owns your copy of the game (Family Sharing), we note that - the owner only as a salted one-way fingerprintModeration onlyThe ticket is not stored; the Family Sharing note goes with your session or the run
Session key - after the Steam check your game gets a random key for 24 hours, so it does not have to ask Steam for every report. We store only a one-way fingerprint of it, with your Steam ID, mod version and connection fingerprintNobody - it only recognises your game24 hours
Route and mods - during a ranked daily run: height and position over time (from mod 2.6.5 also stamina and speed modifiers), the mods you have loadedThe climb graph (height over time) is public; positions and mod lists only for moderation, for the anticheatRoutes as long as their time (thinned to 15-second averages after 3 days), without a ranked time 30 days; mod lists 7 days
Live route parts - during a daily run your route is also sent in pieces once a minute, even if the run is abandoned later. Same content as the routeModeration only, for the anticheat3 days at most, also with a submitted time
Taking part and stamps - in a daily run every scout's game confirms that it takes part (leaderboard tick on or off, when its own clock started) and reports reaching each campfire and the finish with its own run timeModeration only, to check the time of the run2 days; with a submitted time as long as that time
Map digest - counts of what the daily map built on your computer (props per section) and a checksum. The content says nothing about you, but it is stored with your Steam ID, the run ticket and your connection fingerprintModeration only, to spot changed maps2 days; with a submitted time as long as that time, deleted together with the run
Mod fingerprints - after a run your game sends the checksums of its mod files. Only for a file the server has no fingerprint of from you yet (and knows fewer than 3 versions of), the names of its methods with a checksum each go up - at most 3 files per run. No code, no file. Stored with the Steam IDs of up to 20 sendersModeration only, to see what was changed60 days after the last new sender
Your connection - we never store your IP address. Only a salted, one-way fingerprint of it, for quotas, spam protection and map votesModeration onlyAs long as the entry it belongs to
Run timeline - what the server saw and decided about a run, and when: ticket, joining, stamps, route parts, report, checks, decisions of the moderatorsModeration only2 days; with a submitted time as long as that time
Stage times - how long a stage took by the server's and the mod's clock, without names, IDs or connectionModeration and statistics, anonymous1 year
"Climbing right now" - the host's biome, number of players (from mod 2.7.0 also players with the online features off, only as a number), Apocalypse level and modesEveryone, as counts - no namesUntil the run ends, then only as a number in the history
Your browser - your language and the range of the history graphNobody - it stays in your browserUntil you clear it
Summit Fire - when the host lights it in the game: where the group is (biome, Apocalypse level, weather and modifier, vote options) and every player in the lobby with name, name colour, stamina, afflictions and climb height over time - also players who turned the online features off. Only names and game values, no Steam IDsEveryone who opens the fire's page: with its code, or anyone if the host lists the fire publiclyOnly in the server's memory while the fire burns. Stored are only the code, a one-way fingerprint of its key, the host's Steam ID, a connection fingerprint and times
At the fire (website) - the name you choose, your votes, a random visitor ID and a seat ticket. At most 5 seats per connection, counted with the connection fingerprintEveryone at the same fire sees your nameOnly in memory; your seat is freed when you close the page, or after 75 s without a sign of life
Summit Fire in your browser - your name at the fire and the visitor ID (two cookies), the seat ticket and the sound volumeNobody - it stays in your browserCookies 1 year, the rest until you clear it

Who else is involved

  • Cloudflare carries all traffic to this website (delivery and protection) and sees your IP address like any network provider.
  • Thunderstore: asked to verify mod checksums and to load the mod images.
  • Valve (Steam): from mod 2.6.5 our server asks Steam to confirm the one-time ticket your game created. We send only that ticket; Steam answers with your Steam ID. Valve is certified under the EU-US Data Privacy Framework.
  • Nobody else. We don't sell or share anything.

Don't want to take part?

No problem. You can turn the online features off any time in PEAK's pause menu, and your choice is saved. Want your name removed from past entries? Contact @CptPICHU on the PEAK Modding Discord.

Privacy notice

Purposes and legal bases

  • The mod's online features (leaderboards, death maps, Apocalypse chronicle, live counts): your consent, Art. 6(1)(a) GDPR. You give it in the game and can withdraw it there at any time with effect for the future. Showing your name on the leaderboards is a separate, equally voluntary consent.
  • Moderation and abuse protection (Steam ID, Steam check and session, connection fingerprint, quotas, bans, anticheat with participation, stamps, live route parts, map digests, mod fingerprints and timeline): legitimate interest in fair leaderboards and in protection against spam and manipulation, Art. 6(1)(f) GDPR.
  • Providing the website, including delivery through Cloudflare and technical logs: legitimate interest in secure, stable operation, Art. 6(1)(f) GDPR.
  • Summit Fire (live page of a lobby): for the host part of the online features and so their consent, Art. 6(1)(a) GDPR. For the other players in the lobby and the visitors at the fire, legitimate interest in a shared live view of the run, Art. 6(1)(f) GDPR - names and game values only while it runs, none of it is stored. Your name at the fire is your own, voluntary choice. Limiting seats per connection serves abuse protection (see above).
  • Storage in your browser (language, history range, at the Summit Fire your name, visitor ID, seat ticket and sound volume; a login cookie for admins): only what the function you use needs, § 25(2) no. 2 TDDDG.

Recipients and transfers outside the EU

The website runs on the controller's own server. All traffic passes through Cloudflare, Inc. (USA) as a provider for delivery and protection. Transfers to the USA rely on the adequacy decision for the EU-US Data Privacy Framework, under which Cloudflare is certified. From mod 2.6.5 the server checks your Steam identity through the Steam Web API of Valve Corporation (USA): we send only the one-time ticket your Steam client created for this and receive your Steam ID. Valve is also certified under the EU-US Data Privacy Framework; this transfer, too, relies on the adequacy decision for it. Valve processes the data of your Steam account as a controller in its own right under its privacy policy. Names on the leaderboards and in the chronicle are public. Beyond that, we share nothing.

Retention

Daily times permanently (all-time top 50), their routes just as long, thinned to 15-second averages after 3 days; Apocalypse runs and routes without a daily time 30 days, mod lists 7 days; death points and map data 1 year. Run tickets with participation, stamps, map digests and timeline 2 days, or as long as the submitted time that belongs to them; live route parts 3 days at most. Sessions 24 hours (only a one-way fingerprint of the key), mod fingerprints 60 days after the last new sender, anonymous stage times 1 year. Player entries (Steam ID, name history, ban), anticheat hits and anonymous statistics without names or IDs are kept permanently. Live data stays in memory only and expires after 16 minutes. Summit Fire: code, key fingerprint, the host's Steam ID, connection fingerprint and times 2 days; everything else only in memory, at most one hour after the last request.

Your rights

You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21 GDPR), and to withdraw your consent (Art. 7(3)). You can lodge a complaint with a data protection supervisory authority (Art. 77), for example the one where you live.

Obligation to provide data

None. The game and the mod work fully without the online features.

Automated decisions

The anticheat checks reported runs automatically and can keep a run off the leaderboard. From mod 2.6.5: if the timing or the Steam check does not add up, the server only holds the run for review; a person decides. Older mod versions are checked by the old rules: there, a clear timing mismatch is still refused automatically. This has no legal or similarly significant effect within the meaning of Art. 22 GDPR. Players can be banned from the online features for serious violations. This has no effect on the game PEAK itself or on the offline features of the True Final Ascent mod.

Last updated: October 2026

All time
129times submitted
8212deaths
1392Apocalypse runs