Terminal
Connecting…
Connecting…
View all

Gapybara & Maru App Privacy Policy

How the Gapybara and Maru mobile apps (the “apps”) handle information. This policy does not cover the theddari website. Effective November 13, 2026For the website, see the theddari Privacy Policy.

1. Information we collect

The apps work without sign-up. They do not collect your name or phone number. Your email address is not collected unless you enter it in a feedback form.

When you send feedback from the app’s Settings, the feedback text, an optional reply email address, a randomly generated app install identifier, and the app version, OS and device model are sent to the developer’s support system, TheSeeker CRM. This system is operated by (주)더씨커 (Theseeker). The information is used only to answer your feedback and improve the apps. When you open What’s new or react to it (like or dislike), the same install identifier and your view and reaction are also sent to TheSeeker CRM and used only to count reactions.

Google AdMob, the advertising SDK built into the apps, may collect the following while serving ads.

  • Advertising identifiers: device identifiers such as the iOS Identifier for Advertisers (IDFA) and the Android Advertising ID (AAID)
  • Approximate location inferred from your IP address
  • App interaction data (such as ad views and clicks) and diagnostics (errors and performance records)

To load prices and news, the apps connect to Theddari servers and public exchange APIs. The IP address of the connecting device and the request time may be kept in server access logs for security and incident response; they are not used to identify you.

Payments, renewals and refunds for the monthly Remove Ads subscription are handled by Apple (App Store) or Google (Google Play), depending on the store you use. TheSeeker does not receive your payment method information; the app stores the subscription status only on your device.

The apps check for small updates from the developer’s update server. A randomly generated update client identifier, your IP address and the request time may be recorded in server access logs.

2. How the information is used

The information in section 1 is used only to:

  • Serve ads and measure ad performance
  • Prevent fraud such as invalid clicks
  • Keep the service stable, for example by investigating errors
  • Answer feedback, count What’s new reactions and improve the apps (feedback and reaction information only)

3. Retention and deletion

  • Your watchlist, coin holdings and app settings are stored only on your device.
  • Deleting an app also deletes the information it stored on your device.
  • A backup file exists only when you export one from the app yourself, and you manage it wherever you saved it.

Information collected by Google AdMob is retained according to the Google Privacy Policy.

4. Sharing and processing by third parties

Information sent with feedback is processed in the developer’s support system described in section 1. To serve ads, the SDK of the company below collects and processes information inside the apps.

Company
Google LLC
Service
Google AdMob (ad serving and measurement)
Data processed
The advertising identifiers, approximate location, and app interaction and diagnostic data listed in section 1

5. Your choices and how to use them

You can turn off personalized ads based on advertising identifiers, or change your advertising ID, in your device settings. Menu names can differ by OS version and manufacturer.

  • iOS: the app asks for permission before tracking (App Tracking Transparency). If you decline, it requests non-personalized ads only. You can change this anytime in Settings > Privacy & Security > Tracking.
  • Android: in Settings > Privacy (or Google) > Ads, you can reset or delete your advertising ID.

Your watchlist, coin holdings and settings on the device are removed when you delete the app. Send any other privacy questions or requests to the email address in section 6.

6. Privacy contact

Privacy questions are handled at the email address below.

Email [email protected]

7. Effective date and changes

This policy takes effect on November 13, 2026.

If it changes, we will post the changes and the new effective date on this page.