Privacy Policy

Last updated: 22 September 2026

This page explains what Store Watcher (ストア在庫ウォッチャー) stores on your device, what it sends to other services, and how you can have it deleted. Store Watcher is not an official Apple app, and is not provided, endorsed or sponsored by Apple Inc.

On your device

The app stores product names and part numbers, country or region, postal code or city, selected stores, alert preferences and the last availability results. A random installation identifier and an authentication credential are stored in the Keychain.

When you upgrade from an older version, the app reads the previous version's saved products on the device. The original file is preserved.

Availability checks

The app sends the country or region, product part number and postal code or city to Apple, either directly or through our API, to retrieve in-store pickup availability. Connections to Apple include the ordinary network information that comes with any internet request, such as the source IP address. No name, email address or precise GPS location is required.

Apple's handling of this information is described in the Apple Privacy Policy.

Adding products from a URL

When you paste an Apple product page URL, it is sent to Apple directly or to our API. Tracking query parameters and the fragment are removed. The product name, part number, sales region and source URL are retrieved and saved in your device catalog and, when the API is used, in the shared server product catalog. The shared product catalog is shown to other users as common data. Importing a product URL alone does not enable restock alerts.

Restock alerts

When you enable restock alerts, the notification server stores the random installation identifier, the Apple push token, the products you watch, the country or region, the postal code or city, the selected stores and your alert preferences. The same part number and region are sent to Apple in order to monitor availability.

The notification server keeps records of availability transitions and of delivery processing. Alerts are delivered through the Apple Push Notification service. Notification permission can be changed in your device settings. In the app you can stop monitoring for a single product or for all products.

Current status: the app is being prepared for re-release. The restock alert server is not yet running in production. This section describes how the data will be handled once restock alerts become available.

Browser notifications

Once web alerts launch, a necessary cookie identifies this browser with a random identifier and authentication secret. The cookie is restricted to HTTPS and cannot be read by page JavaScript. The server stores a hash of the secret. It expires 180 days after the last visit and is not used for advertising or tracking across sites.

Saving a watch stores the product name and part number, country or region, postal code or city, selected stores and alert preferences on our API server. Allowing notifications also stores the browser's push endpoint, public encryption key, authentication value and display language. Notifications are encrypted using Web Push and sent through Apple, Google or Mozilla's push service, depending on the browser. These providers process delivery information such as the destination and transmission time.

Permission is requested only when you press the notification button. Stopping alerts stops monitoring and pending delivery on the server. Notifications already sent to a push service cannot be recalled. Monitoring stops after 180 days without a visit; this expiry does not automatically erase server records.

Deleting a product removes it from the list and stops monitoring, while retaining records such as delivery history. The delete-all button under Registration and data for this browser removes its subscription, products, monitoring preferences, delivery history and authentication from the live server database, and clears the cookie. Use this before clearing cookies, otherwise you cannot manage the old registration. Copies in backups are subject to their retention period and are not erased by this screen. The backup retention period will be set and published here before production service begins.

Purposes

Data supports availability checks, restock monitoring, notification delivery, saved preferences, abuse prevention and troubleshooting. The API uses source IP addresses to limit the number of requests over short periods.

Advertising

The iOS app watch list displays Google AdMob banner ads. Banner ads are the only ad format used. Google may process IP addresses, device identifiers, ad interactions and diagnostic information for ad delivery, measurement and fraud prevention. We do not pass your watched products, postal code or selected stores to ad requests as targeting information.

Before ads are displayed, consent status is checked with the Google User Messaging Platform (UMP), and a choice screen is presented in regions where one is required. Where applicable, the app's Settings screen includes an ad privacy options entry so you can change your choices later. Use of the iOS advertising identifier (IDFA) requires iOS tracking permission. Declining tracking permission does not prevent you from using the core availability features.

Google's handling and retention of this information are described in the Google Privacy Policy and in How Google uses information from sites or apps that use our services.

This website

This website is served through Google's Firebase Hosting. Firebase Hosting processes visitors' IP addresses to detect abuse and analyze usage. Google states that Hosting retains IP data for a few months. See Privacy and Security in Firebase for details. This website does not include analytics tags or advertising tags.

Storage and deletion

You can delete saved products from within the app. Stopping alerts stops the corresponding monitoring and any pending notifications. Removing a local product or stopping alerts does not erase all server records. The product catalog remains as shared product metadata that is not linked to an individual user.

No single retention period has been fixed for server-side records at this time. This page will be updated once one is set.

To request deletion of information stored on the server, contact us at the address below. After confirming which records are yours, we delete the device notification registration, the monitoring settings and the delivery processing records. Do not include private keys or authentication secrets in email.

Contact

For questions about Store Watcher data: info@cavemen.jp

For deletion requests, please tell us your country or region and what you would like removed, so that we can identify the records.

Changes

We update this page, and its last-updated date, whenever the app's features or data handling change.