FlaptownAdvancementsYour account

Flaptown / Privacy

Privacy at Flaptown

Effective October 16, 2026; updated November 10, 2026 to add Flapcoin, True Flaptime and the Flaptown Relic. This explains how Flaptown Advancements handles information on flaptown.com, shared Flaptown accounts and connected projects. Features are being introduced in stages; an account does not imply that every service is available.

Account information

We use an opaque account ID, your chosen profile name, sign-in methods, project memberships and service eligibility to operate your account. Passwords and recovery codes are stored as protected hashes, not readable passwords. Sessions and authorization records keep sign-in working and help prevent misuse.

Google sign-in

If you choose Google, we request your Google account identifier and verified email address for sign-in and explicit account linking. We do not request access to Gmail messages, Drive files, contacts or calendars. We do not retain Google access, refresh or ID tokens after completing sign-in. Google data is used for account authentication and owner review of requested service access; it is not sold or used for advertising. Linking is an explicit action, not an automatic merge based on matching email.

Profiles and activity

Your shared profile starts private. You can choose to make it public and select which authorized projects' activity is shared. Connected projects may submit achievements and session summaries associated with your account; private security records are not published on your profile. Shared activity is limited to the latest 1,000 events per account and a 180-day display window. Account maintenance removes older stored activity. Individual games can retain their own progress and multiplayer records separately.

Computology experiments

Computology runs its simulations and training in your browser. When you save to your account, we store the setup title, notes, parameters and experiment state needed to restore it, including any edited data, learned weights and training state. Saves are private by default and are included in account export and deletion. Publishing a saved revision makes its complete reproducible setup available to visitors only while your profile is public and Computology sharing is enabled. Visitors can download or fork published setups. Unpublishing or hiding your profile prevents new public reads from Flaptown, but cannot remove copies someone has already downloaded or forked. Whole-workbench JSON exports are files you control; exporting a file does not publish it or save it to your account.

Flapart artwork

You can draw and export without an account. Browser recovery stays in this browser. Account saves store your editable artwork privately. Sharing publishes a separate PNG snapshot; later edits do not change that snapshot until you share again. You can make a shared snapshot available in your profile image library or attach it to a Town Square post. Withdrawing it prevents new reads of that image and removes its forum attachment. Deleting the project or account removes its saved artwork and shared snapshots. Downloads and copies made by others cannot be recalled.

Reepo source projects

New projects and personal editions start private. Publishing makes their source files and version history downloadable under the license you choose. Ideas and replies follow the project visibility. When you suggest changes, a frozen source snapshot and your explanation are shared privately with the original project owner. You can withdraw an unaccepted suggestion. Accepted source becomes a separate version in the receiving project under its license; it and a minimal project/version ancestry record remain if you later delete your edition or account. We store source versions, discussions, reports and moderation restrictions to operate the workshop; reports are not public. Account export includes your projects and contributions. Deleting a project removes its versions and discussions; deleting your account also removes your projects and your discussion text. Copies downloaded or made into someone else’s edition remain with their recipients. Uploaded source is stored as text and is not run on our servers.

Town Square

Forum posts and replies are public, including the forum name you choose and a short public badge that distinguishes namesakes. Your forum name is separate from your private account profile. We store your contributions, likes, reports and participation restrictions to operate and moderate the community. Like counts are public; voter identities and reports are not. You can edit or remove your own text. Account export includes your forum data. Account deletion removes your text and public name from live contributions and removes your likes, reports and forum preferences; empty thread structure remains so other people’s replies still make sense. Copies made by readers cannot be recalled. Database backups follow the retention period below.

Music releases

You can stream public releases and download free albums without creating an account or providing an email address. Download requests use necessary security cookies and short-lived signed links. Album pages show aggregate download starts, not unique listeners or confirmed completed transfers. To avoid counting retries, artist-release downloads use a random, signed cookie lasting 24 hours. The counter stores no IP address or account identity; temporary download-receipt hashes expire after 48 hours and are removed on the next download, while aggregate totals remain until the release is deleted. Requests pass through our hosting infrastructure. Paid checkout is not connected yet; when enabled, card details will be handled on Stripe’s hosted checkout, and payment status will be checked with Stripe before a paid receipt download is offered. Public music releases and their artwork are separate from account-profile sharing.

Your music workspace

Music drafts, uploaded files, preparation notes and approval history are private to your signed-in account. Approval records retain the reviewed version, selected destinations/services/territory, file fingerprints, confirmation time and any revocation reason. They are included in your exports and deleted with the release or account. Publishing is a separate choice: only the selected recordings, cover, public description, credits and platform links become public. Your account email, private profile and preparation notes are not included. Public music can be accessed without an account. Files may contain metadata added by your recording or artwork tools; review it before publishing. You can export your saved release and original uploads, withdraw publication, or delete a release. Account deletion withdraws its public music and removes its workspace records; unreferenced uploaded files are removed by daily cleanup after a 24-hour grace period. Database backups follow the retention period below. Files already downloaded by others cannot be recalled.

Service access and notifications

Minecraft eligibility and proof of Minecraft account ownership are separate from downloading a modpack. Private service access is enabled separately by the owner. The owner receives account-creation and access-request notices and can review your account ID, display name and verified Google contact when available. Approval does not mean remote setup has finished. Decisions and pending service updates are recorded to support reliable access changes.

Benchlight

Benchlight keeps your progress on your own device, in the browser or the app. The only thing it sends anywhere is for its public leaderboard. The first time the game starts with a connection, the leaderboard gives it an anonymous player number and a random key that stays on your device; we store a fingerprint of that key, the time you joined and your leaderboard count. When a leaderboard round is completed, the game sends that round's moves so the server can check them, then keeps only the updated count. The leaderboard shows player numbers and counts and nothing else. If you play on flaptown.com while signed in to Flaptown, your player is linked to your account and the leaderboard shows your account's display name instead of the number; "Hide my name" in the game switches that back. Without signing in, nothing is linked to an account and the game uses no cookies. Clearing the game's site data or uninstalling the app forgets your key. To have your row removed, contact us with your player number.

Flapcoin

Flapcoin (FLAP) is earned by using Flaptown while signed in; it can't be bought. While you are signed in, the account service records each earn: what it was for (a short code such as visit, section:music, forum:post or music:download), the amount and the time. For visits that means the first visit to each part of Flaptown (Music, Town Square, Tools and so on) each day, never which pages within it. For music it means a keyed digest that tells one release from another, never which release. Signed out, nothing is recorded.

Your wallet is opened when you choose a public handle. From then on, your earns and transfers are written to Flapchain, a public ledger anyone can read and copy: each line shows the handle, the amount, the short earn code or the note you added, and the time. Flapchain is permanent by design. Deleting your account removes the records kept by the account service and unlinks the handle from your account, but lines already on Flapchain stay, and the handle stays reserved so no one else can take it. Your wallet's key is kept in Flaptown's key vault and never leaves it. Flapcoin moves only between Flaptown wallets and has no cash value.

True Flaptime and the Flaptown Relic

The True Flaptime page at flaptown.com/flaptime asks for your location only when you choose "Use my location". It uses it in your browser to find sunrise and sunset, remembers it in that browser only, and never sends it to Flaptown or anyone else.

The Flaptown Relic app for Android requests approximate location only when you tap My sky. It uses it on your phone to find sunrise and sunset, stores it on your phone, and never sends it anywhere. The app has no internet access, no ads and no accounts.

Infrastructure and cookies

We use necessary account and security cookies. Cloudflare routes and protects the website and account connection; Google handles Google sign-in when selected. These providers receive connection information needed to deliver their services. The account service uses a hashed client IP for short-lived rate limiting. Infrastructure and game services may retain operational logs for troubleshooting and security. We do not add advertising trackers to the account interface.

Your controls and deletion

Account settings provide profile sharing controls, sign-out, Google linking controls, recovery codes, data export and deletion as those shared-account features become available. Deletion removes the live account data and queues withdrawal of managed access; remote services may take time to apply removal. Minimal provider-identifier reservations and service-deletion records are retained to prevent accidental account reassignment or restoration of revoked access. Consistent account database backups are retained for up to 30 days after routine rotation. A restored backup must have subsequent access removals reapplied before service resumes.

Contact and changes

For privacy questions, corrections or deletion assistance, contact skinflap@flaptown.com. We will update this page when our practices change. Your applicable privacy rights are not reduced by this notice.