Namhae: Spacetime Diary Privacy Policy
Romantic Rider (the "Operator") values the privacy of everyone who uses the Namhae: Spacetime Diary app (the "Service") and complies with applicable laws, including the Personal Information Protection Act and the Act on the Protection and Use of Location Information of the Republic of Korea. This policy explains what data the Service handles and how.
At a glance
- Namhae: Spacetime Diary has no sign-up or login, and no Operator server that stores your personal data.
- Photos, location, notes, and commemorative stamps you create are stored only on your device.
- Coordinates are sent transiently to external APIs for address display and Namhae tourism information; the Operator does not store them.
- If the app crashes, a crash log with device and app information is sent to Google (Firebase Crashlytics). It contains no photos, location data, or notes.
- This app shows no ads and collects no advertising identifier (ad ID).
- To deliver news about new features by push notification, a per-device notification token is sent to Google (Firebase). Notifications appear only if you allow them and can be turned off in device settings at any time.
- No analytics or tracking tool that profiles your usage is used.
Scope — This policy covers Namhae: Spacetime Diary (the Namhae edition) published by the Operator. The nationwide edition, Spacetime Diary, is governed by a separate privacy policy.
1. Data handled and purposes
The Service processes the data below only on your device; the Operator does not collect it. The one exception is the crash log used for error diagnosis, which is sent to Google as described in the table and in section 3.
| Data | Purpose | Storage / retention |
|---|---|---|
| Camera feed (captured images) | Taking photos and compositing the timestamp / location overlay | On device · until you delete it |
| Location (GPS coordinates) | Recording the coordinates at capture, showing photos on the map, address conversion, nearby tourism information, confirming visits to Namhae landmarks (commemorative stamps) | On device · until you delete it |
| Photo library (gallery) access | Importing existing geotagged photos into the map diary (only when you run it) | On device · until you delete it |
| Crash log and device / app information (when the app crashes) |
Diagnosing app errors (crashes) and improving stability | Google (Firebase Crashlytics) servers · 90 days |
| Notification token (Firebase registration token) | Delivering push notifications about new features and service news | Google (Firebase Cloud Messaging) servers · until the app is uninstalled |
Each permission (camera, location, photos) is activated with your consent the first time you use the corresponding feature and can be withdrawn in device settings at any time. Declining a permission only limits that feature; the rest of the Service remains usable.
The commemorative stamps (treasure stamps) shown when you photograph a Namhae landmark are judged and recorded entirely on your device. Which landmarks you have visited is never transmitted anywhere.
1-1. Details on crash logs
The Operator uses Google's Firebase Crashlytics to diagnose app errors. When the app terminates abnormally, the following is collected automatically and sent to Google:
- The stack trace at the point of failure, the error type, and the time it occurred
- Device information: model, CPU architecture, RAM and storage capacity, OS name and version
- App information: package name (app identifier) and app version
- Device / installation identifiers: the Crashlytics installation UUID, Firebase installation ID, and app session identifier (used to avoid double-counting the same error)
Photos, location data (GPS coordinates), notes, and other data you create are not included in crash logs. Nothing that directly identifies you — name, contacts, email — is collected either.
Crash log collection happens automatically while the app runs, to keep the app stable, and the app currently provides no separate setting to opt out. If you do not want it, uninstalling the app stops any further transmission; logs already sent are deleted after the period stated in section 4.
1-2. Details on push notifications
The Operator sends push notifications about new features and service news through Google's Firebase Cloud Messaging. For this, a notification token (registration token) is issued per device when the app is installed and sent to Google.
- The notification token designates "this app on this device." It is not linked to anything that identifies you — name, contacts, email — and becomes invalid when you uninstall the app or reset the device.
- Only if you consent to notifications does the app subscribe to a single topic for this app. The Operator sends only to that topic and never targets an individual user. Withdrawing consent unsubscribes you, so you are excluded from delivery altogether.
- Whether and when you consented is stored only on your device and is never transmitted.
- Photos, location data, and notes have nothing to do with notifications. Notification content is written by the Operator and is not personalized using your data.
Displaying notifications requires your notification permission (Android 13 and above). Declining it leaves every other feature usable, and you can change your choice in device settings at any time (see section 5).
The Operator does not send promotional messages through this channel. Notifications are limited to service news and update announcements; should promotional messages ever be introduced, separate prior consent will be obtained as required by the Act on Promotion of Information and Communications Network Utilization and Information Protection.
2. Transmissions to external APIs
When you use the features below, the data needed for each feature is sent directly from your device to an external API. It is used only to generate that response; the Operator does not collect or store it.
| Recipient | Feature | Data sent |
|---|---|---|
| NAVER Cloud Corp. — Naver Maps API | Map display, coordinate-to-address conversion (reverse geocoding) | Map viewport and photo capture coordinates |
| Korea Tourism Organization — TourAPI | Nearby tourism information such as Namhae attractions and festivals | Current location coordinates |
| Nangman Namhae (Namhae-gun tourism platform) | Checking whether an attraction, restaurant, or lodging is listed on Nangman Namhae, and linking to its detail page | Place name (search term) only — no personal data or location data is sent |
When you open external web pages inside the app — Nangman Namhae, the Namhae Cultural Center, and the like — ordinary web connection data (such as your IP address) reaches that site, as with any browser. Each recipient's handling of personal data is governed by that organization's or site's own privacy policy.
As the Service evolves, external APIs and data sources of the same character (tourism and regional information) may be added or changed, or tourism content may come to be downloaded from a server (cloud) managed by the Operator. As long as no new collection of personal or location data is involved, this policy continues to apply as is; if new processing of personal data arises, this policy will be revised and, where required, separate consent will be obtained.
3. Third-party provision, outsourcing, and cross-border transfer
The Operator does not provide your personal data to third parties. For app error diagnosis, processing is outsourced as set out below, and because the processor's servers are located abroad, the data is transferred abroad.
| Item | Details |
|---|---|
| Processor (recipient) | Google LLC (Firebase Crashlytics) · firebase.google.com/support/privacy |
| Outsourced work | Collecting, storing, and analyzing crash logs; providing error reports |
| Data transferred | The crash log and device / app information and device / installation identifiers of section 1-1 (photos, location, and notes excluded) |
| Destination country | The United States and other countries where Google operates data centers |
| When and how | On abnormal app termination, over HTTPS-encrypted transmission from your device |
| Purpose | Diagnosing app errors and improving stability |
| Retention | 90 days after transmission (then destroyed per Google's deletion procedures) |
In addition, for delivering push notifications, processing is outsourced as set out below and the data is transferred abroad.
| Item | Details |
|---|---|
| Processor (recipient) | Google LLC (Firebase Cloud Messaging) · firebase.google.com/support/privacy |
| Outsourced work | Issuing and managing notification tokens; delivering push notification messages |
| Data transferred | The notification token and device / app information of section 1-2 (photos, location, and notes excluded) |
| Destination country | The United States and other countries where Google operates data centers |
| When and how | When the token is issued at install / launch and when notifications are sent, over HTTPS-encrypted transmission |
| Purpose | Announcing new features and service news |
| Retention | Until the app is uninstalled or the token is renewed / expires |
The transmissions for map display, address conversion, tourism information, and the Nangman Namhae listing check are direct communications from your device to each API; the Operator does not collect or retain that data (see section 2).
4. Retention and destruction
- Your data — photos, location, notes, commemorative stamps: stored only on your device, so deleting a photo or record in the app, or uninstalling the app, destroys it immediately. The Operator keeps no copy.
- Crash logs and device / app information: retained for 90 days after transmission under Google's Firebase Crashlytics policy, then destroyed from live and backup systems per Google's deletion procedures.
- Notification tokens: uninstalling the app invalidates the token, and no further notifications are delivered. Google's stored copies are cleaned up through token expiry and renewal procedures.
5. Your rights
- You can grant or withdraw the camera, location, and photo permissions in device settings at any time.
- You can delete individual photos and records directly in the app.
- Uninstalling the app deletes all data the app stored, and no further crash logs are sent.
- Requests to access, delete, or suspend the processing of crash logs can be made through the contact in section 8. Because crash logs contain nothing that can single you out, it may be impossible to locate a specific user's records; if so, we will explain why.
- You can withdraw notification consent at any time. Turning off Settings → Notifications in the app unsubscribes you from the topic, so no further notifications are sent (you are removed from delivery, not merely muted). Turning notifications off in device Settings → Apps → (app name) → Notifications also stops them from appearing, and uninstalling the app stops delivery as well.
6. Safeguards
- The Service is designed on-device: photos, location, and notes are never placed on an Operator server.
- External API communication and crash log transmission use HTTPS-encrypted channels only.
- Crash logs contain neither your data nor direct identifiers, and collect only the minimum needed for diagnosis.
7. Children's privacy · advertising and analytics
The Service is not directed at children under 14 and does not knowingly collect children's personal data.
The Service shows no ads and collects no advertising identifier (ad ID). It also uses no analytics tool (e.g., Firebase Analytics) that tracks or profiles your usage. The Firebase Crashlytics described in section 1-1 is a stability tool used solely for diagnosing app errors. If advertising or a behavioral analytics tool is ever introduced, this policy will be revised with prior notice.
8. Privacy officer
- Privacy officer: Representative, Romantic Rider
- Contact: romanticrider.app@gmail.com
Please direct privacy questions, complaints, or requests for redress to the contact above. We will respond and act without delay.
9. Remedies for infringement
If you need to report, consult on, or seek mediation for a privacy infringement, the following Korean institutions can help.
- Personal Information Dispute Mediation Committee: kopico.go.kr · +82-1833-6972
- Personal Information Infringement Report Center (KISA): privacy.kisa.or.kr · 118 (in Korea)
- Supreme Prosecutors' Office: spo.go.kr · 1301 (in Korea)
- National Police Agency Cyber Bureau: ecrm.police.go.kr · 182 (in Korea)
10. Changes to this policy
This policy may be revised as laws or the Service change. The Operator may introduce new features — accounts and login (including social login), sharing or posting of photos and other content, advertising, or server-based delivery of tourism content — and where such a feature changes how personal data is processed, this policy will be revised before the feature launches, with separate consent obtained for anything the law requires. Revisions are announced in the app or on this page at least 7 days before taking effect (30 days for material changes).
- v1.0 (2026-08-09) — First enactment. Separated into a dedicated policy for the Namhae edition from the policy that previously covered it together with the nationwide Spacetime Diary (no advertising provisions — this app shows no ads).