Yumble Privacy Policy

Magsmi, represented by Magne Saetran, provides Yumble from the Republic of Korea and controls the information described in this policy. Business registration number: 482-28-02053.

Privacy requests can be sent to support@magsmi.com or by post to 2F, 214-S128, 46 Apgujeong-ro 2-gil, Gangnam-gu, Seoul 06034, Republic of Korea.

Yumble stores your theme, language, haptic and onboarding choices, location-centering preference, search radius and category, favorite restaurants, and up to 20 recent draw results in app storage on your device. Saved restaurant records can include a venue name, category, address, coordinates, distance, source, and provider detail link. Android cloud backup is disabled. Platform backups that you control may apply on other devices or platforms.

If you grant location permission, Yumble can read your location while you are using the app to center the map, find nearby restaurants, and determine a locality for search. Yumble requests foreground or when-in-use permission only. It does not request background location, continuously track your movements, or create a location history.

To determine the locality used for restaurant search, Yumble passes the selected center coordinates to the operating system's reverse-geocoding service through Expo Location. Depending on your device, Apple, Google, or another platform location provider can process those coordinates and routine technical information under its own privacy practices.

You can deny or revoke location permission and choose a map area manually. If automatic centering is enabled, Yumble checks for already granted foreground permission when the explore screen becomes active; it does not use that preference to request permission silently.

When you search, the app sends the selected map-center latitude and longitude, a radius from 100 to 1,000 meters, food category, locality, and app language to Magsmi's Yumble API on Cloudflare. Cloudflare also receives routine request and security information such as IP address, time, network headers, and requested path. The service uses the connecting IP address as a rate-limit key to prevent abuse.

The Yumble API searches available restaurant sources. Kakao Local receives the exact search center, radius, and category or cuisine keyword. The Small Enterprise and Market Service (SEMAS) receives a search center rounded to a small geographic cell, a slightly enlarged radius, and the restaurant-industry category. A SEMAS response for that rounded search cell can be cached in Cloudflare for up to 15 minutes so nearby requests can reuse it. Naver Local receives the locality and food-category search terms; the Yumble API uses the requested center and radius to filter returned places.

Restaurant providers can return venue and branch names, categories, addresses, coordinates, distance or provider links. The Yumble API combines, filters, and returns those results to the app. Search responses are marked not to be stored as a general response cache, and the application does not create a cloud profile from your searches.

Cloudflare, SEMAS, Kakao, and Naver process their service information under their own terms and privacy practices and may process it outside your country. Their availability and records can change independently of Yumble.

Yumble uses the Naver Map SDK to present the map, map center, and restaurant markers. The app supplies the coordinates and labels needed for that presentation. The map SDK does not replace Yumble's foreground location permission flow.

When you choose directions, Yumble gives the selected restaurant name and destination coordinates to Naver Maps or, depending on your device, Apple Maps or Google Maps. The selected map provider then controls that request under its own privacy policy. Yumble does not open a direction provider until you choose one.

Yumble currently has no user account, authentication, cloud sync, advertising, behavioral analytics, cross-app tracking, subscription, or in-app purchase. It does not embed RevenueCat or an advertising SDK. Magsmi does not sell location, search, favorite, or history information or disclose it for targeted advertising.

Yumble can check for and download authorized app updates from Expo's EAS Update service. Expo and its delivery infrastructure can receive the app or project identifier, app version and runtime version, platform, device and operating-system information, IP address, request time, and network headers needed to check compatibility, deliver an update, and secure the service. This update processing is not behavioral analytics.

If these capabilities change, Magsmi will update the app's notices, store disclosures, and this policy as required before or when the change takes effect.

Local preferences, favorites, and draw history remain until you change or delete them, reset relevant app data, or uninstall the app, subject to a platform backup you control. Clearing draw history does not remove favorites. Because Magsmi has no Yumble account or cloud favorites database, it cannot remotely retrieve or delete this local information for you.

The SEMAS cache expires after up to 15 minutes. Cloudflare and the search providers retain routine technical, security, and provider records under their own policies. Magsmi keeps support records only as long as reasonably needed for support, security, legal rights, and legal obligations.

Cloudflare hosts and delivers Yumble's support and legal pages. If you email support@magsmi.com, Cloudflare Email Routing forwards your sender and recipient addresses, message headers, content, and attachments to a consumer Gmail account operated by Google LLC so Magsmi can receive and answer the request. Cloudflare and Google may process this information in the United States or through global infrastructure under their own privacy practices. Do not send precise location history, passwords, full payment-card details, or other information not needed for support.

Magsmi normally deletes support correspondence within 24 months after the request is closed. Where applicable, consumer complaint or dispute-handling records may be kept for three years, and a legal hold or other legal obligation can require longer retention. Deletion from Gmail follows Google's deletion and backup cycle after Magsmi removes the controlled message.

Depending on applicable law, you may request access, correction, deletion, restriction, objection, portability, or withdrawal of consent for information Magsmi controls by contacting support@magsmi.com. These rights do not override records that must be kept by law or information controlled only by your device or another provider.

Protect access to your device and any information you send to support. Yumble and its providers use operational and technical measures intended to protect service information, but no storage or transmission method is completely secure.

Yumble is a general restaurant-decision tool and is not directed to children. If you believe a child submitted personal information to Magsmi through support, contact Magsmi so the request can be reviewed.

Magsmi may update this policy when the app, providers, or law changes. The updated policy will show a new effective date and additional notice where required.