Legal / Privacy

Privacy Policy

LuckyFinder was built so that a giveaway list never has to leave the organiser’s computer. This page explains exactly what is stored, where it lives, and what leaves your browser.

Last updated — Applies to the hosted LuckyFinder web app

ကိုယ်ရေးအချက်အလက် ကာကွယ်ရေး မူဝါဒ

  • သင့် CSV၊ ပါဝင်သူအမည်နှင့် winner စာရင်းများကို server သို့ လုံးဝ မပို့ပါ။
  • အချက်အလက်များကို သင့် browser ၏ localStorage ထဲတွင်သာ သိမ်းဆည်းပြီး winner စာရင်းကို AES-GCM ဖြင့် encrypt လုပ်ထားပါသည်။
  • Cookie၊ analytics နှင့် ကြော်ငြာ မပါဝင်ပါ။ Google Fonts နှင့် hosting ဝန်ဆောင်မှုသာ အပြင်ဘက် request ရှိပါသည်။
  • Browser data ရှင်းလင်းခြင်းဖြင့် သင့်အချက်အလက်များကို အပြီးအပိုင် ဖျက်နိုင်ပါသည်။

01

Summary

There is no LuckyFinder account, no analytics script, no advertising network, and no server that receives your participant list. The application runs in your browser and keeps its state there.

The only routine outbound requests are the page, its static assets, and the web fonts it loads from Google Fonts. Everything else — parsing, shuffling, drawing, encrypting, and recording — happens on your device.

02

Data we do not collect

  • No CSV files, participant names, email addresses, phone numbers, or account identifiers are transmitted to us.
  • No winner records are transmitted to us.
  • No accounts, passwords, or sign-in credentials are created or stored on a server.
  • No cookies are set by LuckyFinder.
  • No analytics, session recording, heat maps, A/B testing, or advertising pixels are loaded.
  • No participant data is sent to an AI or machine-learning service in this build.

03

What is stored on your device

LuckyFinder uses your browser’s local storage for five things. All of them stay on the device you are using, and all of them are removed when you clear site data for the site.

  • `luckyfinder_settings_v1` — campaign name, prize label, spin duration, sound preference, palette, and, if you enable it, your uploaded logo as a data URL.
  • `luckyfinder_winners_vault_v1` — the encrypted winner history. Only ciphertext, an IV, and (for passphrase-protected vaults) a PBKDF2 salt are written.
  • `luckyfinder_device_key_v1` — the random 256-bit AES key used when no passphrase is set. It is stored in the same browser and never transmitted.
  • `luckyfinder_theme_v1` — whether you chose the light or dark interface.
  • `luckyfinder_vault_width_v1` — the width you dragged the winner sidebar to.

04

Encryption and passphrases

Winner history is encrypted with AES-GCM using a 256-bit key and a fresh 12-byte random IV for every save. Only ciphertext is written to local storage; the readable data exists in memory while the studio is open, and in any CSV export you choose to download.

If you set a passphrase, the key is derived with PBKDF2-HMAC-SHA-256 at 100,000 iterations using a random 16-byte salt. The passphrase itself is not stored; it exists only in memory while you are unlocked. A lost passphrase cannot be recovered, and the encrypted vault cannot be decrypted without it.

If you do not set a passphrase, the vault is encrypted with a device key kept in local storage. That protects the winners from casual inspection of local storage, but anyone with access to your unlocked browser profile can open the vault. Use a passphrase if the device is shared.

05

Recordings and downloads

The “Record Wheel” feature captures the draw canvas with the browser’s MediaRecorder API and offers the result as a video download through a temporary blob URL. The file is named .webm; the actual container depends on which formats your browser supports.

Recordings, exported winner CSVs, and any loaded logo never leave your device through LuckyFinder. Where you upload or share them afterwards is your decision and is governed by the service you choose.

06

Third-party requests

Two kinds of outbound request exist when you load the site.

  • Google Fonts — the page loads Bricolage Grotesque, Plus Jakarta Sans, JetBrains Mono, and Noto Sans Myanmar from fonts.googleapis.com and fonts.gstatic.com. Google receives your IP address, user agent, and the requested stylesheet, and may set its own cookies on those domains. See Google’s privacy policy for details. You can block or self-host these fonts without breaking the application; it falls back to system fonts.
  • Hosting and delivery — our hosting provider processes the request for the page and its static assets and may keep standard server logs containing your IP address, user agent, requested URL, and timestamp for security and reliability purposes.

07

Cookies, local storage, and tracking signals

LuckyFinder sets no cookies. It uses local storage strictly to remember your own settings and to keep your encrypted winner vault available on your next visit. Local storage is not shared between sites and is not readable by us.

Because there is no analytics or advertising code, there is nothing to opt out of and no cross-site profile to build. Browser “do not track” signals are therefore honoured by default: there is no tracking to disable.

08

Legal bases for visitors in the EEA and UK

Where the GDPR or UK GDPR applies, the limited processing described here rests on the following bases.

  • Legitimate interests — serving a static page and its assets, and keeping the service secure and available.
  • Consent — if you choose to load a logo or set a passphrase, that data is processed locally on your instruction. You can withdraw by clearing the relevant field or your site data.
  • Legal obligation — where we must retain or disclose information to comply with the law.

09

Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or port personal data, and to object to processing. Because LuckyFinder holds no participant data on a server, most requests are best addressed by the organiser who ran the draw, or by clearing your own browser storage.

You can exercise the deletion right yourself at any time: clear site data for the LuckyFinder origin in your browser settings. This removes the settings, the device key, and the encrypted winner vault immediately and irreversibly.

For anything else, open an issue on the project tracker. We will respond within the period required by applicable law.

Open an issue on GitHub

10

Retention and deletion

Data stored in your browser remains until you delete it, clear site data, or uninstall the browser. We do not keep a copy and cannot restore it.

Server logs held by our hosting provider are retained for the short period set by that provider’s standard policy, typically days to a few weeks, and are used only for security and operational purposes.

11

Children

LuckyFinder is a tool for organisers and is not directed to children. We do not knowingly collect personal data from children. If a promotion is open to minors, the organiser is responsible for obtaining any parental consent the law requires.

12

International transfers

Your participant data does not travel anywhere, so there is no transfer of it to another country. The font requests described above are handled by Google and may be served from infrastructure outside your country.

13

Security

Participant files are parsed in memory. Winner records are encrypted with the Web Crypto API before they are written to local storage. The hosted application is served over HTTPS.

No system is perfectly secure. The weakest link in a browser-only tool is usually the device itself: malware, a shared profile, or a browser extension with broad permissions can read local storage while the vault is unlocked. Use a passphrase, lock your device, and export results you need to keep.

14

Changes to this policy

If the product starts to do something new with data — for example adding optional cloud sync or analytics — this page will be updated before that feature ships, and the revision date at the top will change.

15

Contact

Privacy questions and data-protection requests can be raised through the project issue tracker. Please do not include participant data in a public issue; describe the problem instead.

Open an issue on GitHub

LuckyFinderTerms of ServicePrivacy PolicyUser guide