Kero Studio Policies

Passing By Privacy Policy

Kero Studio (“we”) operates the Android app Passing By (app ID com.kero.passingby, the “App”). This policy explains what personal information is processed when you use the App, why, and how you can control it.

This English version is a translation of the Korean policy with additional information for users in the European Economic Area (EEA) and the United Kingdom (section 12). If the two versions differ, the Korean version prevails unless the law of your country requires otherwise.

At a glance

Topic Summary
Account registration None
Personal information we receive directly Only your email address and message when you email us. We do not run our own servers.
Stored only on your device Travel journal, app settings, list of courses you unlocked
Sent to Google Payment information when you buy a course (Google Play billing); an app data backup if device backup is on; usage statistics and crash reports (Google Firebase)
Ads None (the advertising ID is not used either)
Analytics and crash reporting Google Firebase Analytics and Crashlytics. You can turn them off in the App’s Settings → Data sharing

1. Information we process and why

The App does not ask for or collect your name, phone number, location, contacts, or photos, and it does not use the advertising ID.

Purpose Information When Processed by
Saving your journal and settings Selected course, direction, and focus length; travel journal (arrivals, focus time, stations visited, completed courses); sound, weather, and display settings While you use the App Your device only (never sent out)
Resuming a trip in progress Trip state, and the device boot count used to check whether the device restarted During a trip Your device only (never sent out)
Buying and restoring paid courses Purchased product (course) ID, purchase state, purchase token When you buy a course or the App checks your purchases Google Play billing (see section 5). The App stores only the IDs of unlocked courses on your device.
Confirming purchases and handling refunds Order information provided by Google Play (order number, course purchased, price, purchase date, payment and refund status, etc.) After a purchase Google Play Console (accessible only to us)
Answering your questions Email address, message, any attachments you send When you email us Our email account (Gmail)
Improving the App and fixing bugs (analytics and crash reporting) App usage events (starting, pausing, ending, arriving, and resting on a trip; selected course and focus length; course selection; tapping buy and the billing result code; whether notifications were allowed; language, sound, and power-saving settings), error information (the error and app state when the App crashed or hit an error), device information (device model, OS version, app version, language, approximate country or region), and identifiers Firebase creates for each installation (app instance ID, Firebase installation ID) While you use the App, and when an error occurs Google Firebase (see section 5)

Device backup: if Google backup is turned on in your device settings, Android includes the on-device information above in your Google account backup and can restore it when you reinstall the App or move to a new device. Google keeps this backup in your account; we cannot access it.

2. App permissions

Permission Used for If you deny it
Notifications (optional) Showing time remaining during a trip; arrival and end-of-break alerts You can still use the App, but you will not be alerted on arrival while the screen is off or you are using another app
Vibration, foreground service Vibrating on arrival; keeping the timer running while the screen is off Granted without a prompt
Internet, billing Connecting to Google Play billing; sending analytics and crash reports Granted without a prompt

You can change the notification permission at any time in device Settings → Apps → Passing By → Notifications.

3. How long we keep it

Information Retention
Data on your device Until you uninstall the App or clear its app data
Device backup Kept in your Google account under Google’s backup policy. It may remain after you uninstall the App.
Purchase records Kept by Google Play; we make no separate copy. Where the law requires us to keep transaction records, we keep them for the required period (5 years for payment and supply records and 3 years for complaint and dispute records under Korean law).
Support emails Deleted without undue delay once your request is resolved. Emails about purchases or refunds are kept for 3 years to handle disputes.
Analytics User- and event-level records are deleted automatically after 2 months. Only aggregated statistics that cannot identify you remain.
Crash reports Deleted automatically after 90 days.

4. How information is deleted

5. Sharing and service providers

We do not sell or share your personal information with third parties.

Service providers

Provider Service
Google LLC Receiving and storing support emails (Gmail)
Google LLC Collecting and storing analytics and crash reports (Firebase Analytics, Firebase Crashlytics)

Information Google processes directly

6. International transfers

To provide the service in section 5, your information is transferred outside your country.

  Support emails Analytics and crash reports
Recipient Google LLC Google LLC (Firebase)
Contact Via Google’s Privacy Policy Via Firebase privacy and Google’s Privacy Policy
Countries The United States and other countries where Google operates data centers The United States and other countries where Google operates data centers
When and how Sent and stored by email when you email us Sent over an encrypted connection (HTTPS) while you use the App and when an error occurs
Information Email address, message, any attachments you send The analytics and crash reporting items in section 1
Purpose Answering your questions; purchase and refund support Improving the App and fixing bugs
Retention Same as section 3 Same as section 3
How to refuse Do not email us Turn off “Send usage stats and crash reports” in the App’s Settings → Data sharing
Effect of refusing You cannot contact us by email. This does not affect your use of the App, and you can also request refunds through Google Play. No effect on your use of the App

Google Play billing and device backup are services you use directly with Google and may be processed outside your country under Google’s policies. Google states that it protects international transfers with legally recognized safeguards such as the European Commission’s Standard Contractual Clauses.

7. Advertising and analytics

8. Security

9. Your rights

10. Children

The App does not verify your age and does not knowingly collect personal information from children under 14 (under 13 in the United States). If we learn that a child’s personal information has been processed, we will help delete it at the request of the parent or legal guardian.

11. Contact

For questions, complaints, or requests about your personal information:

   
Privacy officer Operator, Kero Studio
Email ywlee861009@gmail.com

Users in Korea can also contact the Personal Information Dispute Mediation Committee (1833-6972, www.kopico.go.kr) or the Personal Information Infringement Report Center (118, privacy.kisa.or.kr).

12. Additional information for users in the EEA and UK

Controller: Kero Studio, ywlee861009@gmail.com.

Legal bases

Processing Legal basis (GDPR / UK GDPR)
Saving your journal, settings, and trip on your device Performance of a contract: providing the App you chose to use (Art. 6(1)(b))
Buying and restoring paid courses Performance of a contract (Art. 6(1)(b))
Keeping transaction records Compliance with a legal obligation (Art. 6(1)(c))
Answering your questions Performance of a contract, or our legitimate interest in responding to you (Art. 6(1)(b), (f))
Analytics and crash reporting Our legitimate interest in keeping the App stable and fixing bugs (Art. 6(1)(f)). You can object at any time by turning it off in the App’s Settings.

Your additional rights

Other information

13. Changes to this policy

If this policy changes, we will announce it on this page before it takes effect and record it below.

Effective date Change
October 17, 2026 First policy, published in Korean and English.
October 18, 2026 Added analytics and crash reporting (Google Firebase): updated At a glance and sections 1–9 and 12.