MARAMOA

Privacy Policy

Effective date
Last updated

The language follows your browser preferences. You can also choose a language above.

MARAMOA (the “Service”), operated by DevRyner, respects your privacy and follows applicable privacy laws, including the Korean Personal Information Protection Act. This Policy explains information processed by our website and iOS and Android apps.

1. Information we process

The Service does not require an account. The main categories of information are described below. You can use basic information features without granting optional permissions.

1.1. Information you provide

InformationWhen processedPurposeStorage
Error report text, report category, event identifier and a snapshot of event informationWhen you submit an information error reportReview reports and correct event informationOur server, as needed for review and follow-up. Please do not include unnecessary personal information.
Email address and information you include in an inquiryWhen you contact us by email or SupportRespond to inquiries and requestsAs needed to handle the inquiry and related disputes
Firebase Cloud Messaging (FCM) registration tokenOnly if you enable push notificationsSend notifications, such as newly added eventsOur server; deleted when you unsubscribe

1.2. Optional location information

InformationWhen processedPurposeProcessing
Latitude and longitude (approximate or precise, depending on device permissions)Only if you allow location access on the map screenShow nearby eventsUsed on your device; search center coordinates are sent to our server for nearby searches. We do not maintain a separate location history database. Request URLs may appear in access and diagnostic logs.

Network requests for displaying maps may be sent to the map provider and are subject to its privacy policy. You can withdraw location permission in device or browser settings.

1.3. Information collected automatically

InformationCollected byPurpose
IP address and User-AgentOur serverTemporary access logs for security and error handling; retained for up to 30 days
Traces, metrics and logs: HTTP requests and responses, interactions (clicks and page navigation), device and browser information, response timesOur OpenTelemetry collector (otel.devryner.com)Performance analysis and error diagnosis
App instance ID, advertising identifiers (GAID/IDFA), events, screen views, device details (OS/model/language) and approximate location derived from IPGoogle Firebase AnalyticsUsage analysis and service improvement
Crash stack traces, device details (OS/model/memory state) and screens or events associated with a crashGoogle Firebase CrashlyticsDiagnose and fix app crashes
Advertising identifiers (IDFA/GAID, subject to permissions and platform settings), device details, ad impressions and clicksGoogle AdMob (iOS and Android apps)Ad delivery and measurement

Analytics information is used to understand usage trends and improve quality. Individual diagnostic records may be reviewed when investigating errors or security issues. Advertising and analytics identifiers are processed according to permissions and SDK settings. Google Analytics retention follows property settings; Google states that Crashlytics retains crash records and related identifiers for 90 days before beginning deletion.

You can restrict advertising identifiers and tracking in device settings:

  • Android: Settings → Google → Ads → Delete advertising ID.
  • iOS: Settings → Privacy & Security → Tracking → turn off “Allow Apps to Request to Track”, or decline the app’s tracking permission request.

2. Why we use information

  • Provide event information and map features.
  • Send push notifications if you subscribe.
  • Maintain service stability and prevent abuse.
  • Deliver and measure advertising in iOS and Android apps.
  • Review information error reports and handle inquiries and privacy requests.

3. Retention

InformationRetention period
FCM registration tokenDeleted from our server when you unsubscribe
Location and nearby search coordinatesProcessed to provide the feature; no separate location history database. If request URLs appear in logs, the log retention period applies.
Server access logsUp to 30 days from collection
OpenTelemetry traces, metrics and logsUp to 30 days from collection
Reports and inquiriesAs needed for review, handling and related disputes. Contact Support to request deletion.
Google Analytics and AdMob informationAccording to service-specific retention settings and Google’s applicable policies
Firebase Crashlytics informationDeletion begins after 90 days, according to Google’s policy

4. Disclosure to third parties and public data

We do not sell your personal information. Except for the service, analytics and advertising processing described here or as required by law, we do not disclose it for other purposes without a lawful basis.

We separately collect public event and results information from sources such as roadrun.co.kr, World Athletics and its GraphQL API, and Wikipedia. This is distinct from collecting information about Service users. You can contact Support to request correction or removal of public event data, including athlete names, affiliations and results.

5. External providers and international processing

We use the Google services below. Firebase, Google Analytics and AdMob have their respective data processing terms and policies. Information processed can vary by feature and platform.

ProviderServices
Google LLCFirebase Analytics, Firebase Crashlytics, Firebase Cloud Messaging and AdMob

Related information may be transferred to and processed in the United States and other countries where Google operates its processing infrastructure. See Sections 1 and 2 for information and purposes, and Section 3 for retention. Use the contact details in Section 10 for questions and rights requests.

Firebase Privacy and SecurityGoogle Privacy Policy

6. Your rights and choices

You may request access, correction, deletion or suspension of processing of your personal information, subject to applicable law.

The Service does not require an account. To exercise rights relating to push tokens, reports, inquiries and associated logs:

  • Unsubscribe from push notifications using the app or website notification control.
  • Withdraw location access in device or browser privacy settings.
  • For other requests, contact Support using Section 10.

7. Deletion methods

  • Electronic records are permanently deleted using methods intended to prevent recovery.
  • Printed materials, if any, are shredded or destroyed.

8. Security measures

  • Encrypted communications over HTTPS.
  • Restricted server access and administrator authentication.
  • Restricted access to logs and periodic checks.

9. Children’s privacy

We do not intentionally collect personal information from children under 14. If such collection is identified, we delete the information promptly.

10. Privacy contact

Contact DevRyner, the operator of MARAMOA, for privacy questions, complaints, rights requests and assistance:

Email: [email protected]
Support: cs.devryner.com/apps/maramoa

11. Privacy complaints

You may also seek assistance from these Korean authorities or an applicable privacy authority in your jurisdiction:

12. Changes to this Policy

This Policy may be revised to reflect legal or service policy changes. Changes will be announced in the Service at least 7 days in advance.

Original effective date: April 28, 2026. Latest notice: November 5, 2026.

November 5, 2026: added Korean and English versions and clarified existing location searches, error reports, support, Android advertising and external SDK processing. This document update does not introduce new data collection features.