Privacy policy
The Ranpick website ranpick.com (the "site") and the Ranpick iOS and Android apps (the "apps") explain here, under Article 30 of the Personal Information Protection Act, how they handle your personal information. In short: no personal information is collected other than what you write in a bug report; the site keeps access logs briefly, uses Google Analytics for visit statistics and Google AdSense ads to stay free; the apps use Google Firebase for usage statistics, crash reports and win alerts, and Google AdMob ads to stay free. My Numbers, QR scanning and the apps' nearby-store calculation are processed only on your device.
1. Information collected and purposes
The site has no sign-up, login or comments. The only information you submit yourself is the ‘bug report’ below; no other personal information such as name, email or phone number is collected.
However, for operation and security the following may be recorded automatically in server logs when you connect.
| Item | IP address, time of access, requested page URL, browser and device type |
|---|---|
| Purpose | Diagnosing failures, blocking abnormal access and excessive requests, improving the service |
| Retention | Up to 3 months from the date logged, then deleted automatically |
The site's Bug reports & feedback and the Ranpick iOS and Android apps is handled as follows.
| Item | Report type and message, contact details (only if given), site/app version, OS and device (browser) type, the screen reported, and an irreversible hash of the IP address mixed with a server secret. The IP address itself is not stored. |
|---|---|
| Purpose | Checking and fixing errors, replying when contact details are given, preventing floods from one source |
| Retention | 1 year from receipt, then deleted automatically |
2. Visitor analytics (Google Analytics), ads (Google AdSense) and cookies
The site uses Google Analytics to learn which pages are viewed and how often. It stores cookies in your browser and sends the following to Google. Nothing that directly identifies you, such as a name or email, is included.
| Item | a random browser identifier (cookie _ga), pages viewed, time of visit, browser, device and screen size, approximate country/city, referrer |
|---|---|
| Purpose | Counting visitors and popular pages; improving the service |
| Recipient | Google LLC (USA). Data is transferred to and processed on Google servers. |
| Retention | Up to 14 months per Google Analytics settings; cookies up to 2 years |
If you don't want this, block cookies in your browser settings or install the Analytics opt-out add-on. The site works the same either way.
The site shows Google AdSense ads to stay free. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this site and other sites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the Internet.
| Item | Advertising cookies and the random identifiers in them, page address, browser and device type, approximate location inferred from IP address, and ad views and clicks |
|---|---|
| Purpose | Showing ads and measuring their performance, personalized ads, preventing invalid clicks |
| Recipient | Google LLC (USA). Data is transferred to and processed on Google servers. |
| Retention | As set by Google's policies |
To opt out of personalized advertising, use Google Ads Settings; for other third-party vendors' cookies, visit aboutads.info. See how Google uses information for ads in How Google uses information from sites that use its services.
3. Information used only on your device (My Numbers, QR scan, nearby stores)
- My Numbers: saved Lotto numbers stay only in your browser's storage (localStorage) and are never sent to the server. Clearing browser data deletes them.
- Scan QR: the camera view and uploaded photos are used only to read QR codes inside the browser and are never stored or sent. The camera turns on only when you allow it.
- Stores near me: if you allow it, your location rounded to three decimals (about 100 m) is put in the page URL and sent to the server, which uses it only to sort nearby stores. That URL may remain in the access log described in section 1.
4. Ranpick apps (iOS and Android)
The apps also have no sign-up or login. They use the following Google services. No name, email or phone number that directly identifies you is sent.
| Usage statistics | Firebase Analytics: a random app-installation ID, screens viewed and features used, app version, device type and OS, language, approximate country/city. Used to learn which screens are used and improve the app. Kept up to 14 months. |
|---|---|
| Error reports | Firebase Crashlytics: error reports when the app freezes or crashes, device type and OS, app version, a random installation ID. Used only to fix errors. Kept 90 days. |
| Win alerts | Firebase Cloud Messaging: a device token for notifications. Used only to announce new winning numbers; no longer used once you turn notifications off or delete the app. |
| Ad | Google AdMob: advertising identifiers (Android advertising ID; on iOS the IDFA only if you allow tracking), device type and OS, app version, approximate location inferred from IP address, and ad views and taps. Used to show ads and measure them. Retention follows Google's policy. In regions that require consent, such as Europe, consent is requested first. |
| Recipient | Google LLC (USA). Data is transferred to and processed on Google servers. |
If you don't want personalized ads, delete or reset your advertising ID under Settings > Google > Ads on Android, or turn off tracking for Ranpick under Settings > Privacy & Security > Tracking on iOS. Ads still show but are not personalized.
- My Numbers: saved numbers and notes are stored only inside the app and never sent to the server. Deleting the app deletes them.
- Scan QR: the camera turns on only when you allow it, and the view is used only to read QR codes on the device.
- 1st-prize stores near me: if you allow it, nearby stores are computed on your device from your current location, which is never sent to Ranpick servers. The map is drawn by Naver Maps (NAVER Cloud), so map tile requests go to Naver while you view it.
- Requests the apps make to fetch winning numbers go to Dhlottery and Ranpick servers and may leave the access log described in section 1.
You can turn off location, camera and notification permissions in your device settings at any time; everything else keeps working.
5. Sharing with third parties
Apart from Google Analytics and AdSense (section 2), Google Firebase, AdMob and Naver Maps (section 4), Ranpick provides no information, including access logs, to any person or company and outsources no processing. Lawful requests from authorities under due process are the exception.
When you follow a link to another site such as Dhlottery or Naver Maps, that site's privacy policy applies from then on.
6. Your rights
The only personal information Ranpick keeps itself is access logs and bug reports. To review or delete your access records or reports, contact the address below. We will respond within 10 days.
7. How we keep it safe
- Server access is restricted to the operator.
- Traffic between the site and your browser is encrypted with HTTPS.
- Bug reports are viewed only on an admin screen accessible to the operator.
- Access logs and bug reports are deleted automatically after their retention period.
8. Privacy officer
| Officer | Ranpick operator |
|---|---|
| Contact | [email protected] |
For further help with a privacy complaint you can contact the Korea Personal Information Infringement Report Center (118, privacy.kisa.or.kr).
9. Disclaimer
- Ranpick is run free of charge by an individual and keeps no personal information that identifies you other than what you write in a bug report. Write only what is needed and never include sensitive data such as ID or bank account numbers.
- The operator is not liable for privacy issues on external sites you reach through links, security problems on your device or network, or unlawful acts by third parties beyond the operator's control.
10. Changes to this policy
Changes to this policy are announced on this page with the effective date.
This policy is effective from October 31, 2026.