Plumki saves some settings on your device to remember configuration and resume the game. This page describes local entries identified in the release code. A key name may contain a technical version when we change the data format.
1. Categories of entries
| Example keys | What they store | Why |
|---|---|---|
plumki.graphics.quality.v1, plumki.graphics.frameLimit.v1, plumki.audio.*, plumki.throwPreview*, plumki.swingSensitivity, plumki-arena-map | Graphics, audio, throw-preview, sensitivity and map settings. | Remembering choices in the game. |
plumki:menu-section:v1, plumki:menu-online-used:v1, plumki:tutorial-offer:v1, plumki:tutorial-completed:v1, plumki.socialEntry.v1 | The last menu tab chosen, whether online play was opened from this browser, the choice in the tutorial offer and its completion, and when choices were made in the prompt to open the game in a real browser (from TikTok, Instagram and similar apps). No identifiers. | Opening the menu where you left it and not repeating the same prompts; the browser prompt returns after 30 days at the earliest. |
plumki.courtOcclusion.v1:* | A technical cache of court visibility calculations for maps, with no player data. | Faster repeat map loading. |
plumki-skin-v1, plumki-*-skin-v1, plumki-*-appearance-v1:*, plumki-*-inventory-v1* | Selected appearance and local unlocks for skins, bottles, sticks and pets. | Showing the selected appearance and preserving guest or account progress. |
plumki-run-v1, plumki-online-session-v1, plumki-intro-v1, plumki-victory-dance-v1 | Solo progress, online session resume, selected greeting and victory animation. | Resuming the game and preserving selected animations. |
plumki-guest-invite-v1 in session storage, plumki-guest-name-v1 | Signed guest ID with its expiry time (12 hours) and the last guest nickname you entered. | Joining a match from an invitation link without an account and returning to the room after a tab reload; the nickname is suggested for the next invitation. |
plumki-guest-return-v1 in session storage | Room code and save time, created when you click “Create account” at the end of a guest match. | Offering a return to the same room after registering or signing in. Valid for 30 minutes; removed after returning to the room or closing the tab. |
plumki-shadow-deck-v1 | Position in the recorded throw deck of “Ghost training” for up to 24 recently chosen ghosts: the ranked player's identifier, deck seed, throw number and time of last use. | Later matches against the same ghost continue the deck, so its accuracy matches the recorded one. |
plumki-next-arena-map | The map rolled in advance for the start of your next visit and the list of maps it was drawn from. No player data. | Downloading that map in the background during the current visit, so the next start is faster. |
plumki-throw-archives in IndexedDB | Copies of throw-map data from finished matches in the profiles you open: match and profile-owner identifiers, the owner's throw origins, the match's flight-path archive and the time saved. Up to 1000 matches (usually a few MB); the oldest are removed. | Opening the throw map in a profile faster, without downloading the same matches again. The copy is removed when you sign out or switch accounts. |
plumki-engagement-v1:* in local/session storage | Random browser pseudonym and engagement-session context when optional analytics is enabled. | Distinguishing returns and sessions in analytics; without a player name or account UUID in the analytics layer. |
plumki.privacy-consent.v1 | Analytics choice, consent version and time of choice. | Remembering consent for up to 180 days. After that, the choice must be made again. |
sb-*-auth-token | Supabase sign-in session token. | Keeping you signed in and making account-function calls securely. This is authentication data — do not share it. |
plumki.language | Your language preference. | Remembering the selected language for future visits. |
Local settings and progress remain until changed or site data is cleared. Session storage is tied to the browser tab; the browser may restore it with the tab. The account session remains until sign-out or expiry and may renew automatically. The analytics choice must be made again after 180 days.
2. Consent and device storage
Settings needed to operate the game may be stored when necessary for the requested feature. Optional analytics requires prior, voluntary consent. Refusing analytics does not block the game. We provide information about the purpose and the ability to change settings before storing consent, in accordance with Article 399 of the Polish Electronic Communications Law.
Clearing browser storage removes local entries on this device, but does not remove the account, results, match history or archives stored in online services. To request online data, write to contact@plumki.games and say what the request concerns.
3. How to clear local data
- Open the site settings for plumki.games in your browser.
- Choose to clear site data, local storage and session storage.
- If you only want to withdraw analytics, open “Privacy” in the game, turn analytics off and save your choice. If you instead delete
plumki.privacy-consent.v1in browser tools, reload the page.
Note: Removing sb-*-auth-token signs you out of the browser. It does not delete account data from Supabase. Signing out and clearing storage are not the same as closing the account.
4. Related documents
Information about online data, rights, providers and retention is in the Privacy policy. Account, user-content and online-feature rules are in the Terms.