Tabememo

Tabememo Privacy Policy

This Privacy Policy explains how Tabememo (the “App”) handles information.

1. Information stored on your device

The App primarily stores the following information that you enter or select on your device:

The App may access your current location when you select a current-location action or, if permission has already been granted, to start the Find map at a useful position. Merely accessing your location does not save it as the place where you ate. A map location is stored only when you select a location and save the record.

Backups you create may include meal records, photos, saved places, and some app settings, including the introductory ad grace period. Files are saved to the destination you choose using the operating system. The App does not automatically upload these backups to the operator’s server. Please choose a trusted location and manage who can access your files.

2. Information processed by external services

The App may use the following external services to provide its features.

Google Maps Platform

The App uses Google Maps SDK to display maps and let you choose a location. Information required to display the map may be sent to Google. Locations you save remain in the App’s on-device data.

On iOS, the Find map uses Apple Local Search to move to an address or station. When you perform a search, the search text and, when you have moved the map, its visible region are sent to Apple to obtain results. The App does not save the search text or results as a meal record or place; it uses them only to move the map.

RevenueCat

The App uses RevenueCat to check, purchase, and restore Tabememo Pro. Purchase status, store transaction information, an app-specific anonymous identifier, and other information needed to manage purchases may be sent to RevenueCat.

Google AdMob and User Messaging Platform

The free version may use Google AdMob to provide ads. Device information, identifiers limited to the app or developer, usage information, and other information needed to provide and measure ads may be sent to Google.

The App does not request access to the iOS advertising identifier (IDFA) and does not show the App Tracking Transparency prompt. All ad requests are limited to non-personalized ads. Non-personalized ads may still use information such as device data or identifiers for purposes including delivery, frequency capping, reporting, security, and fraud prevention.

Starting with the App Store release of iOS version 1.1.3, before the free version initializes ads, the App uses Google User Messaging Platform (UMP) to update advertising consent information. The App does not automatically open a consent form at startup. If UMP does not allow ad requests, the App does not show ads. You can open “Ad privacy choices” in Settings to make a required choice or change an earlier choice. Pro users may also communicate with UMP to review their choices when they explicitly open this setting. Earlier versions may automatically display a consent form depending on regional settings.

Before initializing ads on iOS, the App also disables Google Mobile Ads publisher first-party ID and publisher personalization. If consent information cannot be updated and no valid previous consent state allows ads, or if privacy configuration or SDK initialization fails, the App does not request ads during that launch.

Ads are not shown while Tabememo Pro is active. If Pro is confirmed during startup, the App does not explicitly initialize Google AdMob or request ads. It also does not request ads while the purchase status is still being checked or cannot be confirmed. If you purchase Pro after ads were used during the same launch, the App removes ads immediately and stops later ad requests, although an SDK that was already initialized cannot be unloaded during that launch.

Apple age assurance and update permissions

Starting with iOS version 1.1.3, depending on the region and Apple Account requirements, the App temporarily receives an age range from Apple to check applicable access requirements. It does not store a birthdate, raw age range, or age declaration method in meal records or backups, or send those values as advertising attributes. Where an update requires permission, Apple’s interfaces are used to request parental approval or an adult acknowledgement.

To prevent applying permission to a different account, the App stores a hash derived from an app transaction identifier and update-permission state on the device. This verification data is excluded from the App’s meal-record backups and is not sent to the operator’s server. Meal records and photos remain stored on the device if verification cannot be completed.

App Store and Google Play

Distribution, payment, restoration, and refund processing are handled through Apple or Google systems and policies.

3. Photos and location information

The App handles photos only when you select them. Selected photos are copied into storage managed by the App on your device. If a photo includes location metadata and the App can read it, that location may be shown as a candidate for your map pin. It is not saved as the place where you ate until you save the record, and you can remove the candidate first.

4. Sharing with third parties

The operator does not sell or provide the contents of your meal records to third parties except when required by law. The external services listed above may process information only as needed to provide their respective services.

5. Deleting data

You can delete records within the App. Deleting the App from your device also deletes the App’s on-device data. App Store or Google Play purchase history remains subject to each store’s systems and policies.

6. Children

The App is not intended to collect personal information from children. Children should not enter personal information without permission from a parent or guardian.

7. Changes to this policy

This policy may be updated when features, external services, or legal requirements change. Important changes will be communicated on this page or within the App.

8. Contact

For questions, email ryo.yamamoto@silentbirdgames.com.

Effective: July 8, 2026
Last updated: October 28, 2026