Jikju Privacy Policy

Version 1.0 · Effective 2026-10-03 · 한국어 (the Korean version prevails if the two differ)

Yoonseong Dan (TrendX) ("we") provides the mobile app "Jikju" (직주 — 직장 기준 집 찾기, "the app"). This policy explains what the app processes.

1. Summary

• The app has no sign-up or login. It does not ask for or collect your name, contact details, email, account identifiers, advertising identifiers or precise location, and it does not request location permission.
• The commuting statistics, transaction prices and workplace data shown in the app are bundled inside the app. Browsing screens or changing your budget sends nothing to us; we do not run a server for the app.
• To improve the app we analyse anonymous usage statistics (which screens and features are used) with Google Analytics for Firebase. The budget amount you enter and the age band / sex you select are not sent.
• The app is not an official app of any government or public institution and is not affiliated with the National Pension Service or the Ministry of Land, Infrastructure and Transport.

2. What is processed

Usage statistics (automatic). Tool: Google Analytics for Firebase by Google LLC, configured without advertising identifiers and with ad personalisation signals off (no AD_ID permission on Android; the iOS app uses FirebaseAnalyticsCore, which has no IDFA support).

• Items: fixed code values such as screen names, feature codes and "empty result" reason codes; the district (si/gun/gu) codes you looked at (workplace or home candidates you selected — not where you are); a random app-instance ID created at install (removed when you delete the app); device model, OS version, app version, app language and country; session start/end times and time spent on a screen. Google estimates a country/city-level approximate location from the IP address and does not log the IP address itself (Google's documentation).
• Not sent: budget amounts, selected age band or sex, complex names, precise location, advertising identifiers.
• The app sends these directly to Google over HTTPS (not through any server of ours).

Stored only on your device: whether you have confirmed the first-launch notice, and whether the "first budget result" event has already been sent. Deleted when you delete the app.

Links in the in-app "직주 안내" screen (e.g. the Public Data Portal) open in your browser and are governed by those sites' policies.

3. Purpose

Usage statistics are used only to improve the app (which screens and features are used, where results come back empty or people stop). They are not used for advertising, marketing, identifying individuals or combining with other services.

4. Retention

• Google Analytics event and user-level data: 14 months, then deleted automatically.
• Raw analysis copy (Google BigQuery export): expires automatically after 60 days.
• On-device values: until you delete the app.

5. Sharing, processors and international transfer

We do not provide personal information to third parties. Collection, storage and analysis of usage statistics are entrusted to Google LLC (Google Privacy Policy, Firebase privacy); the data is transferred over HTTPS while you use the app to Google data centres, including in the United States, and kept for the periods in section 4. There is no in-app switch to turn collection off; to stop it, stop using or delete the app.

6. Your rights

You may request access, correction, deletion or suspension of processing by emailing us. Because we hold no information that identifies you (such as a name or contact details), we may be unable to locate a specific person's usage statistics; deleting the app removes the app-instance ID so later data is no longer linked to you.

7. Children

The app is not directed to children under 14 and we do not knowingly collect their personal information.

8. Security

All transmission is encrypted with HTTPS. Only the developer account can access the analytics console. The app does not use web cookies.

9. Contact

Privacy officer: Yoonseong Dan (developer, TrendX) · dys0707y@gmail.com

10. Changes

We announce changes on this page and in app update notes at least 7 days before they take effect (30 days for material changes such as new data items). 1.0 (effective 2026-10-03): first version, with app 1.0.0.