Legal / Privacy
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.
01
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
03
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.
04
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
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
Two kinds of outbound request exist when you load the site.
07
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
Where the GDPR or UK GDPR applies, the limited processing described here rests on the following bases.
09
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.
10
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
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
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
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
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
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.