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.

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 on your device by default. The exceptions are: (1) account information, if you sign in for photo sharing; (2) photos you mark as "public" yourself and their accompanying information; and (3) report and block records — these are stored on the Operator's server — and (4) crash logs and (5) push notification tokens, which are sent to Google. See the table below and sections 1-3, 1-4 and 3.

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.

1-3. Details on accounts (social login)

Using photo sharing requires signing in with a Google or Kakao account. Signing in is optional: without signing in you can still use every other feature, including viewing and reporting shared photos.

• What we receive — from the social login provider (Google LLC or Kakao Corp.): your email address, nickname, profile image (if you consented to provide it), and the provider's user identifier. We never receive or store your password.
• Purpose — granting you rights to view, manage and delete "photos I posted"; preventing abuse such as exceeding upload limits; handling reports and blocks; responding to inquiries.
• Where it is stored — the Operator's server (Supabase, Seoul region, Republic of Korea), retained until account deletion.
• Account deletion — you can delete your account at any time from Settings → Account → Delete account. Deleting it also deletes your account information and the photos you shared with that account. If you cannot access the app, see the account deletion guide.

For Kakao accounts, an email address may not be provided depending on Kakao-side settings. This does not affect signing in or using sharing.

1-4. Details on photo sharing

Sharing happens only for photos you mark as "public" yourself, right after capture. Photos you do not mark never leave your device.

• What is uploaded — the image with metadata (EXIF), including location coordinates, removed; the capture time; the landmark (place) you linked; and the displayed nickname described below. The GPS coordinates in the original file are not uploaded; which landmark a photo belongs to is expressed solely by the place link you chose.
• Who can see it — a shared photo can be viewed in that landmark's album by every user of the Service, including users who are not signed in.
• The nickname that is made public — a shared photo is displayed together with the nickname you choose. If you have not chosen one, a nickname generated automatically by the Service (for example, "붕장어338") is displayed. You can change it at any time in Settings → Profile; after you change it, the new nickname is also shown on photos you shared earlier. Your email address, profile image and account identifier are not made public.
• Retention — up to 50 photos are kept per place; when a new photo arrives, the oldest is pushed out of the list and deleted. You can delete photos you posted at any time.
• Reporting and action — anyone (even without signing in) can report an inappropriate photo. The Operator reviews reported photos and may hide or delete them, and may retain a reported photo for up to 30 days for that review.
• Blocking — a signed-in user can block a poster so that their photos are not shown to them. The block list shows the nickname as it was at the time of blocking.

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.

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.

Namhae tourism information is currently served through a server managed by the Operator (Supabase). The coordinates needed for a lookup (the map viewport or your current position) are sent to that server, but the Operator does not store the coordinates used for lookups. This routing exists to share the daily call quota of the Korea Tourism Organization's TourAPI; the information provided is the same.

As the Service evolves, external APIs and data sources of the same character (tourism and regional information) may be added or changed. 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. However, photos you mark as "public" yourself are made viewable to other users as described in section 1-4 (this is disclosure by your own choice, not provision by the Operator to a third party).

To provide the Service and diagnose errors, processing is outsourced as set out below; some processors' servers are located abroad, so that data is transferred abroad.

3-1. Storage of account and sharing records (Supabase — stored in Korea)

3-2. Storage of shared photo images (Cloudflare — cross-border transfer)

3-3. Crash logs (Google — cross-border transfer)

In addition, for delivering push notifications, processing is outsourced as set out below and the data is transferred abroad.

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).

How to refuse an overseas transfer, the procedure, and its effect

You may refuse the overseas transfers above. You refuse by not using the feature that causes the transfer; this takes effect immediately and requires no application procedure.

Even after you refuse, information already transferred and held by a processor is destroyed according to the retention period stated for each item.

4. Retention and destruction

• Your data — photos, location, notes, commemorative stamps: stored only on your device unless you share a photo, so deleting a photo or record in the app, or uninstalling the app, destroys it immediately. The Operator keeps no copy of unshared content.
• Account information: destroyed upon account deletion. Deleting your account also deletes the photos you shared with it.
• Shared photos and accompanying information (including nicknames): destroyed when you delete them or when they are pushed out of the per-place limit (50 photos per place, newest first). A photo under report review may be retained for up to 30 days for that purpose.
• Report and block records: destroyed upon account deletion or after handling, per internal standards.
• Location use and provision records: retained for 6 months from the time of recording under Article 16(2) of the Act on the Protection and Use of Location Information, then destroyed. They contain no coordinates or addresses.
• 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 the data stored on your device, and no further crash logs are sent. Photos you shared and your account information remain on the Operator's server, so delete the photos in the app or use Settings → Account → Delete account.
• You can delete a photo you made public at any time; once deleted it is no longer visible to other users and is destroyed from storage.
• You can change your nickname at any time (Settings → Profile). After you change it, the new nickname is also shown on photos you shared earlier.
• You can delete your account at any time (Settings → Account → Delete account). If you cannot access the app, see the account deletion guide.
• You can review your location use and provision records (Settings → Location use history · Article 24 of the Act on the Protection and Use of Location Information).
• 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. Accounts, login and photo sharing were reflected in version 2.0 of this policy (September 2, 2026). The Operator may introduce further features — 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).

• v2.0 (2026-09-02) — accounts and photo sharing reflected. Updated "At a glance" and the section 1 table (three rows added: account information, shared photos and accompanying information, report/block records); added sections 1-3 (accounts) and 1-4 (photo sharing, including the nickname that is made public); added Supabase (stored in Korea) and Cloudflare R2 (cross-border) processors in section 3; added server-side items, deletion and access routes to sections 4 and 5; corrected the description of where lookup coordinates are sent (external APIs or the Operator's server; lookup coordinates are not stored); replaced the "planned features" notice in section 10 with the realised description.
  The nickname that is made public also applies to photos shared before this revision. This revision fulfils the "revised before the feature launches" commitment in section 10 of v1.0; consent required by law is obtained through the consent step shown the first time you use sharing in the app. At the time of this revision the Service is unreleased and no user has used sharing, so the prior-notice period is satisfied, without disadvantage to users, by the publication of this document.
• 2026-08-28 overseas-transfer disclosure expanded — added the transferee's contact details and how to refuse a transfer, the procedure and its effect, and corrected the description of Cloudflare's destination countries to match what was measured (Personal Information Protection Act, Article 28-8(1)3(a) and 28-8(2); no change adverse to users)
• 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).