Cookie and Storage Policy
Last updated: 5 October 2026
Lumy stores a small number of items in your browser so you stay signed in, your projects stay yours and your choices are remembered. This policy lists every one of them. It forms part of our Privacy Policy, which explains how we handle the personal data involved.
We do not use advertising cookies, and we do not let other companies track you on Lumy for advertising.
1. Cookies and browser storage
Most of what Lumy keeps on your device lives in your browser's local storage (kept until you or we clear it) or session storage (cleared when you close the tab), rather than in classic cookies. The law treats them in the same way, so we list them all here and use the word "storage" for all of them.
We group storage into three types:
- Necessary: needed for Lumy to work, such as keeping you signed in, securing sign-in and remembering your consent choice. These cannot be switched off in our settings, because the service does not work without them.
- Preference: remembers choices you make so you do not have to repeat them. These do not track you.
- Analytics: helps us understand, in aggregate, how people use our pages. These are used only if you allow them.
2. Local storage
| Name | What it does | Type | How long |
|---|---|---|---|
pf_uid |
Your Lumy identity (guest or signed in). It points to your account record, which is kept on our servers. | Necessary | Until you sign out or clear it |
pf_key |
The secret that proves this browser is signed in as you. Signing out ends it on our servers too. | Necessary | Until you sign out, sign out everywhere, or clear it |
pf_code |
Remembers your early-access code. | Necessary | Until you clear it |
pf_consent |
Remembers your cookie and storage choice, so we do not ask again. | Necessary | Until you clear it |
pf_tstate |
A one-time security value that protects sign-in with a provider against forged requests. | Necessary | Replaced at your next sign-in; until you clear it |
pf_return |
Remembers the page to bring you back to after sign-in. | Necessary | Replaced at your next sign-in; until you clear it |
pf_ref |
Remembers the referral code from a friend's link, so the reward can be credited when you sign up. | Necessary | Until it is used at sign-up, or you clear it |
pf_tickets |
Remembers the reference numbers and private links of up to 30 support requests you sent from this browser, so you can follow them on My requests. | Necessary | Until you clear it |
pf_dev |
Remembers which phone you chose for the phone preview in the studio. | Preference | Until you clear it |
pf_engine |
Remembers which model you chose for building. | Preference | Until you clear it |
pf_last_provider |
Shows "Last used" next to the way you signed in last time. | Preference | Until you clear it |
3. Session storage
| Name | What it does | Type | How long |
|---|---|---|---|
pf_wall |
When you run out of tokens, carries the name of the project you were building to the Pricing page, so your request is kept. | Necessary | Read once, then removed; cleared when the tab closes |
pf_referred |
Remembers that you arrived through a friend's link, so we can tell you when your referral tokens land. | Necessary | Removed after the message shows; cleared when the tab closes |
pfh |
Keeps your current conversation with the "Ask Lumy" help agent (the last 30 messages) while you move between pages. | Necessary | Cleared when the tab closes |
pf_desk |
Used only by Lumy staff on the internal support desk. It is never set for users. | Necessary | Cleared when the tab closes |
Help agent conversations are also sent to our servers to produce answers and are kept as described in our Privacy Policy.
4. Analytics
The cookie banner shows Reject and Accept side by side. Analytics events are sent only after you press Accept. If you press Reject, no analytics events are sent and no analytics storage is set. You can change your choice later in "Cookie preferences".
When you accept, we collect information about visits, such as pages viewed, the referring site and device type. We do not use it for advertising.
The same choice applies to published projects. Makers see analytics for their own projects on their Data page, and it only counts visitors who pressed Accept. For those visitors, it records a private ID per person (or the account, for signed-in people), sign-ins, coming back the next day, time per visit, the screens visited, device, the referring site, visits per day, the actions the app reports, errors, and wins and losses for games. Visitors who press Reject are not counted. See our Privacy Policy.
A maker can also add their own Google Analytics or Plausible to a published project. Those load only after you press Accept for analytics, never when your browser sends Global Privacy Control, and are run by Google or Plausible under their own policies, for the maker.
5. Sign-in providers
If you choose to sign in with a third-party provider, that provider may set its own cookies while you are on its sign-in page. Those are governed by the provider's own policies, not this one.
6. Inside games and apps
- Played on Lumy. When you play a game on Lumy, its saves and leaderboard entries are stored on our servers against your identity, not as cookies on your device.
- Downloaded projects. A project downloaded as a single HTML file runs with an offline stand-in for the backend. When you open it, it may keep scores and saves in that browser's local storage under names beginning with
pf_(for examplepf_best). That data stays on the device where the file is opened and is not sent to us. - Apps built with Lumy may use their own storage. Their makers are responsible for telling their users about it and asking for consent where the law requires.
7. Your choices
- Change your choice at any time with Cookie preferences in every page footer.
- You can also clear or block storage in your browser settings. If you clear the necessary items, you will be signed out on this browser and your list of support requests on this browser will be forgotten. Your account and projects stay safe on our servers.
- Where the law requires, we honour browser privacy signals such as Global Privacy Control as a refusal of analytics.
8. Changes
We update this policy when we add, change or remove any item. The date at the top shows the latest version.
9. Contact
Questions: open a ticket at /support, or write to our notices address, hello@luminary.gg. See also our Privacy Policy.
