Spacetime Diary Privacy Policy

Romantic Rider (the "Operator") respects the privacy of users of the Spacetime Diary app (the "Service") and complies with applicable laws, including the Personal Information Protection Act of Korea and the Act on the Protection and Use of Location Information. This policy explains what information the Service handles and how.

Scope — This policy covers Spacetime Diary (the nationwide edition) published by the Operator. The Namhae edition, Namhae: Spacetime Diary, is governed by a separate privacy policy.

1. Information we process and why

The Service processes the following information on your device only, and the Operator does not collect it. The one exception is crash logs for diagnosing app errors, which are sent to Google as described in the last row below and in section 3.

Each permission (camera, location, photos) is requested with your consent when you first use the related feature, and can be revoked anytime in your device settings. Denying a permission only disables that feature.

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 name, CPU architecture, amount of RAM and disk space, operating system name and version
• App information: package name (app identifier) and app version
• Device and installation identifiers: Crashlytics Installation UUID, Firebase installation ID, and app session identifier (used to deduplicate reports of the same crash)

Your photos, location data (GPS coordinates), and notes are not included in crash logs. No directly identifying information such as your name, phone number, or email address is collected. Crash logs contain no advertising identifier; advertising identifiers are covered separately in section 1-2.

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 advertising and the advertising identifier

To cover the cost of running the Service, the Operator displays a banner ad at the bottom of the diary list screen. Ads are served by Google AdMob (Google LLC). When an ad is requested and displayed, the following is sent from your device to Google:

• Advertising identifier (Android Advertising ID, AAID) — a resettable, per-device identifier
• Device and app information: device model, OS version, app identifier and version, screen size, language and country settings
• IP address and the approximate location (city level) inferred from it
• Ad interaction records such as impressions and clicks

For this purpose the app includes the advertising ID permission (com.google.android.gms.permission.AD_ID).

Your photos, precise GPS coordinates, and notes are not included in ad requests. The Operator does not use the location data recorded by the app for advertising, nor pass it to the ad provider. What the Operator receives from Google is aggregate statistics such as impression and click counts — never information identifying an individual user.

Google's handling of data for advertising purposes is governed by How Google uses information from sites or apps that use our services and the Google advertising policies. You may reset or delete your ad ID and opt out of personalized ads in your device settings (see section 5).

1-3. Details on push notifications

To announce new features and service news, the Operator sends push notifications 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 identifies "this app on this device". It is not linked to your name, phone number, or email, and it 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.
• Your consent state and the time it changed are stored only on your device and are never transmitted.
• Your photos, locations, 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 does not affect any other feature of the app, and you can change the setting on your device at any time (see section 5).

The Operator does not send advertising or promotional messages through this channel — only service news and update announcements. Should promotional messages ever be sent, separate prior consent will be obtained as required by the Korean Act on Promotion of Information and Communications Network Utilization and Information Protection.

2. Coordinates sent to external APIs

When you use the features below, the coordinates needed for the feature are sent directly from your device to external APIs. They are used only to generate the response; the Operator does not collect or store them.

Each recipient's handling of data is governed by its own privacy policy.

3. Third-party sharing, outsourcing, cross-border transfer

The Operator does not share your personal data with third parties. For app error diagnosis, processing is outsourced as set out below, and because the processor's servers are located outside Korea, that information is transferred abroad.

In addition, for banner advertising, processing is outsourced as set out below and the data is transferred abroad.

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

The coordinates sent for map display, address lookup, and nearby attractions travel directly from your device to each API; the Operator neither collects nor retains them (see section 2).

4. Retention and deletion

• Your photos, locations, and notes: stored only on your device. Deleting a photo or record in the app, or uninstalling the app, removes it immediately. The Operator retains none of it.
• Crash logs and device/app information: retained for 90 days after transmission under Google's Firebase Crashlytics policy, after which Google's deletion process removes it from live and backup systems.
• Notification token: uninstalling the app invalidates the token, after which no notification is delivered. Google's stored copy is cleared through its token expiry and refresh process.
• Advertising identifier and ad request data: retained and deleted by Google under Google's advertising data policy. The Operator retains none of it separately, and once you delete your ad ID in device settings, that identifier is no longer sent with subsequent requests.

5. Your rights

• Grant or revoke camera, location, and photo permissions anytime in device settings.
• Delete individual photos and records inside the app.
• Uninstalling the app deletes all data the app stored and stops any further crash log transmission.
• You may submit requests to access, delete, or suspend the processing of crash logs to the contact in section 9. Note that crash logs contain no information identifying you individually, so it may not be possible to pinpoint a specific user's records; in that case we will explain why.
• You may withdraw your consent at any time. Turning off Settings → Notifications inside the app unsubscribes you from the topic, so no notification is sent to you at all (delivery stops, not just display). Turning them off in your device settings (Settings → Apps → (app name) → Notifications) also stops them appearing, and uninstalling the app stops delivery.
• You may reset or delete your advertising identifier. On Android, go to Settings → Privacy → Ads (or Settings → Google → Ads, depending on your device and version) to reset the ad ID or choose Delete advertising ID. After deletion, no ad ID is sent with the ads the app requests, and you will see non-personalized ads instead. The app provides no setting to turn off ads themselves.

6. Security

• The Service is designed on-device — no Operator server holds your photos, locations, or notes.
• All external API communication and crash log transmission uses HTTPS encryption.
• Crash logs carry no user content and no directly identifying information — only the minimum needed to diagnose errors.

7. Children's privacy

The Service is not directed at children under 14 and does not knowingly collect children's personal information.

8. Advertising and analytics

The Service displays Google AdMob banner ads, which send your advertising identifier and related data to Google (see sections 1-2 and 3).

The Service uses no behavioral analytics tool (e.g., Firebase Analytics) to track or profile your usage. The Firebase Crashlytics described in section 1-1 is a stability tool used solely for diagnosing app errors; it is not used for usage analytics or advertising.

Ads appear in an area clearly separated from app content. They are not placed so as to interfere with your actions or to be mistaken for content. If a behavioral analytics tool is introduced, or the form or extent of advertising is expanded, this policy will be revised with prior notice.

9. Privacy contact

• Data protection officer: Representative, Romantic Rider
• Contact: romanticrider.app@gmail.com

10. Remedies for privacy violations

For reporting, counseling, or dispute mediation regarding privacy infringement in Korea, you may contact:

• Personal Information Dispute Mediation Committee: kopico.go.kr · +82-1833-6972
• Privacy Violation Report Center (KISA): privacy.kisa.or.kr · 118
• Supreme Prosecutors' Office: spo.go.kr · 1301
• National Police Agency Cyber Bureau: ecrm.police.go.kr · 182

11. Changes to this policy

This policy may be revised due to legal or service changes (e.g., introducing photo sharing). Revisions are announced in the app or on this page at least 7 days before taking effect (30 days for material changes).

• 2026-08-09 wording alignment — Namhae: Spacetime Diary is now governed by a separate policy; the scope of this policy is narrowed to Spacetime Diary alone (no change in data processing)
• v3.1 (effective 2026-08-14 · announced 2026-08-07) — Revised for the introduction of push notifications: added the notification token as collected data (sections 1 and 1-3), disclosed outsourcing to and cross-border transfer to Google LLC (Firebase Cloud Messaging) (section 3), added the token retention period (section 4) and the right to turn notifications off (section 5), and stated that no promotional messages are sent without separate consent. Takes effect on the same day as v3.0.
• v3.0 (effective 2026-08-14 · announced 2026-08-07) — Revised for the introduction of banner advertising (Google AdMob) in Spacetime Diary: added the advertising identifier and ad request data as collected data (sections 1 and 1-2), disclosed outsourcing to and cross-border transfer to Google LLC (AdMob) (section 3), added the retention basis for advertising data (section 4), added the right to reset and delete the ad ID (section 5), rewrote the advertising and analytics section (section 8), and stated the scope covering both editions.
• v2.0 (effective 2026-07-30) — Revised for the introduction of an app error diagnosis tool (Firebase Crashlytics): added crash log and device/app information as collected data (sections 1 and 1-1), disclosed outsourcing to and cross-border transfer to Google LLC (section 3), added the 90-day crash log retention period (section 4), and clarified the advertising and analytics section (section 8).
• v1.0 (2026-07-07) — Initial version