EasyTicket Privacy Policy
Effective: July 6, 2026 · Last updated: October 9, 2026
EasyTicket (the “Operator”) complies with the Personal Information Protection Act of Korea and other applicable laws. This policy applies to the EasyTicket blog (easyticket.co.kr) and to the mobile apps published by the Operator. Neither the blog nor the apps have sign-up or log-in, and there is no step where you enter your name or contact details.
This is a translation of the Korean policy. If the two differ, the Korean version prevails.
1. Controller and scope
- Controller: EasyTicket (an individual, not a business). Responsible person: Kwangjo Kim
- Website: easyticket.co.kr and all of its pages (including the web apps at easyticket.co.kr/play/ — see 2-1 below)
- Mobile apps: Travel for P Types (P들의 여행), NCS Vitamin, Planet Pop: Merge Pinball, NCS Modular, STASH
2. Information processed and purposes
The Operator does not itself collect or keep personal information (web app records keep only values that cannot identify a person, as described in 2-1). The information below may be generated or collected automatically through analytics and advertising tools.
| Category | Information | Purpose |
|---|---|---|
| Access logs | IP address, date and time of visit, browser, device and operating system information | Visit statistics, preventing abuse |
| Usage | Pages visited, navigation path, time spent | Improving content |
| Cookies | Cookie identifiers for analytics and advertising | Telling repeat visits apart, measuring ad performance |
| Advertising identifiers (some apps) | Android advertising ID, iOS IDFA | Personalised ads and ad measurement |
2-1. Web app records (Random Dart)
The web app "Random Dart" (easyticket.co.kr/play/dart/) shows "Everyone's darts" statistics about where people's darts landed. Each time a dart is thrown, it records the items below in the Operator's server (a database on the dothome web hosting). There is no sign-up or login.
- What is recorded: the destination drawn, the chosen distance setting (domestic radius or overseas flight time), the time of the throw, and a 16-character value made by mixing the IP address with a secret that changes every day, so the original address cannot be recovered.
- Purposes: showing counts and rankings per destination and how many people threw today, and keeping one person from skewing the statistics by throwing excessively in a short time (throws beyond 120 in 10 minutes are left out of the statistics).
- Not recorded: name, account, contact details, location or device identifiers. If you choose "from my location", your location is used only on your device to calculate distances and is never sent to the server.
- Retention: throw records (including the masked value) are deleted after 30 days. Cumulative counts per destination are totals that cannot identify anyone and are kept.
- Stored only on your device: "My darts" and your chosen settings are kept only in your browser and can be removed with the on-screen "Clear" button or by clearing your browser data.
3. Retention
The Operator does not store personal information itself. Web app records are kept as described in 2-1, and information collected by analytics and advertising tools is kept according to each provider's policy.
4. Provision to third parties and processors
The Operator does not provide your personal information to third parties. However, the services below may collect and process information under their own policies.
| Company | Service |
|---|---|
| Google LLC | Google Analytics (visit analytics), AdSense (web ads), AdMob (app ads), Firebase (app analytics, remote configuration) |
| NAVER | Naver Analytics (visit analytics) |
| Coupang Partners · MyRealTrip | Their own policies apply when you follow an affiliate link |
| dothome | Web hosting (server access logs, storage of web app records — 2-1) |
5. Cookies
- This site uses cookies for visit analytics and advertising.
- Third-party advertisers such as Google may use cookies to show ads based on your interests.
- You can refuse or delete cookies in your browser settings, and turn off personalised ads in Google Ad Settings. Some features may then not work fully.
6. Your rights
You can ask to access, correct or delete your information, and you can refuse collection by blocking cookies and turning off ad personalisation. Please send requests to the contact below.
7. Advertising and affiliates
This site takes part in advertising such as Google AdSense and in affiliate marketing such as Coupang Partners and MyRealTrip. We may earn a commission on purchases made through affiliate links at no extra cost to you, and posts that contain affiliate links say so in the text.
8. Mobile apps
The apps published by the Operator have no sign-up or log-in and do not directly collect your name, email or phone number. What each app processes differs. 'Travel for P Types' and 'STASH' send or store some information on servers for certain features; see 8-1 and 8-2 below. 'NCS Modular' keeps study records on your device but sends some information for usage analytics, remote configuration and update checks; see 8-3. The game and study records of the other apps are stored only on your device and are not sent to the Operator's servers.
| App | Ads | Collected automatically · stored on servers |
|---|---|---|
| Travel for P Types | Google AdMob (rewarded) | Anonymous identifier, advertising ID, device and usage information, the itinerary, member list and expenses of trips shared with companions, published itineraries, Travel Talk posts and comments, notification token, AI itinerary requests (see 8-1) |
| NCS Vitamin | Google AdMob | Advertising ID, device and usage information |
| Planet Pop: Merge Pinball | Google AdMob | Advertising ID, device and usage information |
| NCS Modular | Google AdMob (banner, interstitial, rewarded) | Advertising ID, device and usage information, app usage statistics (Firebase Analytics), installation ID for remote configuration (see 8-3) |
| STASH | Google AdMob (native, interstitial), Meta app events (ad measurement) | Advertising ID, device and usage information, crash reports, address and title of links the app could not read (can be turned off), temporary data and notification token for sending collections and sending from a computer, bug reports and suggestions you send, app events sent to Meta (see 8-2) |
- Publisher: '이지티켓' (EasyTicket) on Google Play and 'KWANGJO KIM' on the Apple App Store (the same operator).
- Opting out of personalised ads: You can reset or delete the advertising identifier or turn off personalised ads in your device settings. (Android: Settings › Google › Ads / iOS: Settings › Privacy & Security › Tracking)
- Third parties: App ads are handled by Google LLC (AdMob) under the Google Privacy Policy.
- Children: The apps are for general users and are not directed at children under 14. We do not knowingly collect children's information.
For the exact information each app collects, see the Data safety section (Google Play) and the App Privacy section (App Store) of its store listing.
8-1. Additional notes for 'Travel for P Types'
'Travel for P Types' has no sign-up or log-in and never asks for your name, email or phone number. Some information is generated automatically or stored on servers for the features below.
A. Anonymous account
When you first open the app, Firebase Authentication creates a random anonymous identifier (UID). It is used only to tell users apart for companion invitations, published itineraries and notifications, and is not linked to your real name or contact details. It is removed from the device when you delete the app, and you can ask for the data left on servers to be deleted as described in E below.
B. Information stored on servers (Firebase, Google LLC)
- Trips planned with companions: trip name, dates and destination; itinerary, places saved on the map, checklist and document links; the member list (nickname, avatar, role); expense entries and settlement; game results. Only companions who know the invitation code can see them, and access ends when the trip is deleted or you leave it.
- Files in the document box: only files you turn on with "Show to companions too" (동행에게도 보이기), such as e-tickets, are uploaded. Other files stay on your device.
- Published itineraries: the destination, dates, route, one-line introduction and nickname of itineraries you choose to publish (공개). Notes are included only if you turn on "Publish notes too" (메모도 함께 공개). You can make them private again at any time.
- Travel Talk posts and comments: titles, bodies and comments you post to Travel Talk are stored with your anonymous identifier, nickname, avatar, travel type and time of writing. If the body contains a web address, the first one is also stored for a preview, and the numbers of likes, views, comments and reports are counted. If today falls within one of your trips when you post, a "traveling" (여행중) mark is stored too; this is decided only from the trip list on your device, without location data. Photos cannot be posted.
- Likes and reports in Travel Talk: who liked which post or comment, and who reported which post or comment for what reason, are stored with the anonymous identifier, to stop the same person reporting the same post again and again.
- Anti-spam record: to stop posts and comments being repeated within a short time, only the time of the last post and the recent number of posts are stored for each anonymous identifier. It has nothing to do with what you write, and you cannot delete it yourself so that it cannot be bypassed.
- Nickname, avatar and travel type: the profile shown in member lists and published itineraries. Nicknames are reserved on the server to avoid duplicates.
- Notification token (FCM): stored to send companion invitations, game invitations and deal alerts, and deleted when you leave the trip.
- AI itinerary requests: when you tap "Fill with AI" (AI 일정 채우기), the destination, dates, flights, accommodation, travel type and saved places are sent to the Google Gemini API to create the itinerary. These requests are counted per device identifier to manage the daily limit. Your name and contact details are not sent.
- Bug reports and suggestions: what you write, with the app version and device type.
C. Ads and advertising identifiers (Google AdMob)
After the first use, "Fill with AI" is available after watching a rewarded ad. Google AdMob may collect advertising identifiers (Android advertising ID, iOS IDFA) and device and usage information to show and measure ads. On iOS the App Tracking Transparency prompt is shown before personalised ads; everything works if you decline, and ads are then not personalised.
D. Processed only on your device
- Photos: to mark the places you have been on the globe timeline, only the location and date of the photos you choose are read on the device. The photos and their location data are not sent to servers.
- Google Timeline file: the file you choose is read on the device to extract only the cities you visited. The file is not sent to servers.
- Location: used only to pick nearby places in "Destinations near me" (내 주변 여행지) on the Explore tab and in the destination picker. The coordinates are used on the device only to measure distance and are neither sent to servers nor stored. Everything else works if you decline location access.
- Records, expenses and checklists of trips you plan alone: stored only on your device.
E. Your rights and deletion
If you ask for server data to be deleted, in the app under My › Bug report & suggestion (마이 › 버그 제보·건의) or by email to the address in section 9, we delete the anonymous account and the server data linked to it (member lists, published itineraries, Travel Talk posts and comments, anti-spam records, notification tokens and profile). The shared data of a trip planned with companions is deleted when the trip owner deletes the trip.
F. Processors and third-party services
| Company | Service | Information |
|---|---|---|
| Google LLC | Firebase (Authentication · Firestore · Cloud Messaging · Analytics · App Check), Gemini API, AdMob, Google Maps Platform (Places) | Anonymous identifiers, companion trip data, notification tokens, usage statistics, AI request content, advertising identifiers, place search terms |
| Kakao | KakaoTalk sharing (invitation cards and travel type result cards) | The card content at the time of sharing (destination, dates, invitation code) |
| Affiliate partners (MyRealTrip and others) | Booking links | Their own policies apply when you follow a link |
G. Retention
Server data is kept until you delete it or ask for it to be deleted; there is no fixed retention period or automatic deletion. When you delete a Travel Talk post, the post is deleted from the server at once, but the comments, likes and report records attached to it remain on the server (they are not shown in the app). To delete those too, please ask as described in E above. Companion invitation codes expire 30 days after they are issued. Ad and analytics information is kept according to each provider's policy.
8-2. Additional notes for 'STASH'
'STASH' has no sign-up or log-in and never asks for your name, email or phone number. The links, screenshots and their copies, places, notes and collections you save are stored only on your device. Some information is sent to or briefly stored on servers for the features below.
A. Processed only on your device
- Screenshots, photos and videos: New screenshots and screen recordings are imported from your photo library, and the photos and videos you choose are kept as copies on the device. The pictures and videos are not sent to servers. When you attach a file in another app and pick STASH, only the file you pick goes to that app.
- Text in screenshots: Text is recognised on the device for search and is not sent to servers, except that sending a collection sends the text of the screenshots in it.
- Clipboard: Checked when you open the app, only to see whether a link was copied. The link is saved only when you tap the add button or turn on Save copied links automatically. Clipboard contents are not sent to servers.
- Location: The app does not ask for access to your current location. On Android, when it keeps an original, it may ask for access to photo locations so that the place a photo was taken is not stripped from it; this stays in the copy on your device.
B. Sent to or briefly stored on servers (Firebase, Google LLC)
- Usage statistics: App instance ID, device and OS information, app version, country and language, how often features are used, the domains of links you save or open, and in-app purchase events, collected with Firebase Analytics to improve the service.
- Crash reports: When the app crashes, the error and the device state are sent to Firebase Crashlytics.
- Link reading reports: When the app cannot read a link's title or picture, it sends the link's address (with tracking parameters removed), domain, page title, the result, app version, OS and language. They are used only to fix the reading rules, carry no device identifier, and can be turned off under Settings, Send data to improve the app.
- Bug reports and suggestions: What you write under Settings, Bug reports and suggestions, with its kind (bug report or suggestion), the app version, OS and language. It is used only to improve the app; we ask for no name or contact details and do not reply. So that one device can send up to five a day, the number sent that day is kept with an anonymous identifier.
- Place look-up: When you save a place shared from a map app, its name and approximate coordinates are sent to the Google Places API to find the same place on Google Maps.
- Sending a collection (STASH Pro): The name of the collection you choose to send, and the links, titles, notes, photos, text recognised in screenshots and places in it, are stored briefly with a random identifier. Only people with the code can receive them. To count receipts accurately and let only those recipients download the files, the anonymous identifiers of the people who received it are recorded with the share and deleted together with it.
- Sending from a computer (STASH Pro): Links, photos and addresses sent from a computer browser are stored until your phone receives them. So that you can pick a collection for them on the computer, the names of your collections and how many items each holds are also stored while sending is open, with a notification token (FCM) to tell you they arrived. The computer page uses Google reCAPTCHA to prevent automated abuse; device and browser information is sent to Google for this, and the Google Privacy Policy applies.
- App integrity: Firebase App Check and an installation ID are used to confirm that requests come from the genuine app.
C. Ads and ad measurement (Google AdMob, Meta)
Google AdMob may collect advertising identifiers (Android advertising ID, iOS IDFA) and device and usage information to show and measure ads. Where the law requires it, such as the European Economic Area, the app asks for consent before showing ads, and you can change it in the app's settings. On iOS the App Tracking Transparency prompt is shown; everything works if you decline, and ads are then not personalised. With STASH Pro no ads are shown.
To measure how STASH's own ads perform, the app uses Meta Platforms' app events (Facebook SDK). It sends the app's install and launches, finishing the first-run guide, the first time something is put into a collection, and STASH Pro purchases (amount, currency, product) to Meta, with the advertising identifier and device information (model, OS and app version, language, time zone, IP address). The links, photos, notes and collections you save are not sent. Where consent is required before ads (the European Economic Area, the UK, Switzerland and similar), nothing is sent to Meta. On iOS the advertising identifier is sent only if you allow App Tracking Transparency; on Android you can delete or reset the advertising ID in the device settings.
D. Permissions
| Permission | Used for | If you decline |
|---|---|---|
| Photos and videos | Importing screenshots and screen recordings, choosing photos to import, albums to add automatically (STASH Pro), and deleting originals from or saving to the photo library when you choose to | Screenshots and screen recordings are not imported; saving links and places still works |
| Photo locations (Android) | Keeping the place a photo was taken when an original is kept | The kept copy may lack the place it was taken |
| Notifications | Reminders when items pile up, and when something arrives from a computer | The app works without notifications |
| Tracking (iOS) | Personalised ads and ad measurement | Ads are not personalised, and measurement goes without the advertising identifier |
E. Payments
STASH Pro payments are processed by the App Store and Google Play. We receive only whether a purchase was made and for which product, never card numbers or other payment details.
F. Processors and third-party services
| Company | Services | Information |
|---|---|---|
| Google LLC | Firebase (Analytics, Crashlytics, Firestore, Storage, Cloud Messaging, App Check, Authentication), AdMob, Google Maps Platform (Places), reCAPTCHA | Usage statistics, crash reports, link reading reports, bug reports and suggestions, temporary data for sharing features, notification tokens, anonymous identifiers, advertising identifiers, place names and approximate coordinates, device and browser information on the page for sending from a computer |
| Meta Platforms, Inc. | App events (Facebook SDK) | Advertising identifier, device information, install and launches, first-run guide finished, first item put into a collection, STASH Pro purchase amount and currency |
G. Retention
- Sent collections: Kept while the code is open (50 minutes) or until everyone allowed has received them, then deleted automatically. Files are removed from storage within a day at the latest.
- Sending from a computer: Each item is deleted as soon as your phone receives it; the rest, collection names and counts included, and the notification token are deleted within an hour after the session ends.
- Link reading reports: Deleted automatically 50 days after they are received.
- Bug reports and suggestions: Deleted automatically one year after they are received; the count for a day is deleted once that day is over.
- Crash reports: Deleted after the Firebase Crashlytics retention period (90 days).
- Usage statistics and ad data: Under each company's policy.
H. Your rights and deletion
Data stored on your device disappears when you delete it for good in the app or remove the app. What you move to the Trash is deleted when the period you set (30 days by default) ends or when you empty the Trash, and the Trash also stays on your device. Link reading reports can be turned off in Settings. Because there are no accounts, server records are hard to match to a person; if you write to the email in section 9 below, we may ask for details from the app to find them.
8-3. Additional notes for 'NCS Modular'
'NCS Modular' has no sign-up or log-in and never asks for your name, email or phone number. Your answer history, statistics and wrong-answer notes are stored only on your device. Some information is collected automatically or sent for the features below.
A. Processed only on your device
Your study records, statistics and wrong-answer notes, the information used to space out ads (first launch time, time of the last ad and how many have been shown), whether the update notice has been shown, and whether you bought ad removal are stored only on your device and are not sent to servers. Study records can also be erased with the reset option in the app's settings, and everything is removed when you delete the app.
B. Usage analytics (Google Analytics for Firebase)
To improve the app, anonymous usage information is collected. It does not include your name or contact details and is used only for statistics.
- App launches, sessions, time spent and screens viewed
- Subjects studied, time spent on summary screens and playing text-to-speech (TTS) audio
- Number of questions, correct answers and time taken
- Screens where an ad was or was not shown and why, and what you chose on the ad removal offer
- Whether the update notice was shown
- Device and app information (model, OS version, app version) and approximate region
The study records themselves (questions answered, wrong-answer notes, statistics) are not sent.
C. Remote configuration (Firebase Remote Config)
Used to adjust some settings, such as how often ads appear, without an app update. When the app fetches settings, the country and language code, time zone, OS version, app identification details and an identifier assigned to each installation (Firebase installation ID) are sent to Google. The installation ID is a random value created when the app is installed; it is not linked to your name or contact details and is used to provide Firebase services (remote configuration and usage analytics).
D. Update check
To tell you once when a new version is out, the app checks for updates. On Android it sends device information and the app version to Google Play to see whether an update is available; on iOS it looks up the latest version on the Apple App Store using the app's identifier. No personal information such as your name or contact details is sent.
E. Ads and consent (Google AdMob)
Banner, interstitial and rewarded ads are provided by Google AdMob, which may collect the advertising identifier (Android advertising ID, iOS IDFA) and device and usage information to show ads and measure their performance. In regions where consent is required, such as Europe, a consent form for using data for ads and analytics appears on first launch, and on iOS an App Tracking Transparency (ATT) prompt appears separately. You can use every feature without consenting; ads are then shown in a non-personalised form.
F. Payments
The in-app product that removes ads permanently is paid for through the Apple App Store or Google Play, and the app never collects card numbers or other payment details. Only whether you bought it (the ad removal entitlement) is stored on your device, and it is restored from your store purchase history.
9. Privacy officer
| Operator | EasyTicket (an individual, not a business) |
|---|---|
| Responsible person | Kwangjo Kim |
| kj920503@gmail.com |
10. Changes to this policy
If anything in this policy is added, removed or changed, the change is posted on this page together with the effective date and the date of the last update.