Privacy Policy
Revised: October 25, 2026
App and Developer Identity
This Privacy Policy applies to the following app and its associated website. App name (Japanese listing): ずつけあ - 頭痛予報・天気痛対策・気圧と痛み記録 Localized app name: Oh My Headache Developer: molto., kk. Android package: com.molto.ohmyheadeache Website: https://zutsucare.com/
Oh My Headache (the "Service") recognizes the importance of Users' personal information, complies with the Act on the Protection of Personal Information and other related laws and regulations, and strives to handle and protect personal information appropriately based on the following policy.
Update forecasts as you move
Allow location access at all times to update pressure and weather forecasts and notifications while the app is closed. The OS detects movement; a location fix is requested only when needed. The forecast location is saved on your device and sent to forecast providers and the notification server. The notification location and settings are updated on sync and kept until account deletion. Background locations in Japan (excluding simulated locations) and failure diagnostics from any country are linked to your Firebase UID and sent to our server. These records become eligible for automatic deletion 90 days after server receipt; deletion may be delayed. You can turn this off in Settings.
Article 1 (Information We Collect)
The Service may collect the following information: 1. Information you enter ・Email address ・Health-management information you enter, such as condition logs and headache records 2. Information collected automatically ・IP address ・Access date and time ・Device information ・OS information ・Browser information ・App usage ・When location access is allowed, latitude, longitude, accuracy, capture time, acquisition method, attempt count, and acquisition duration when the app starts in Japan, returns to the foreground, or an enabled background movement check runs (linked to the Firebase UID and retained for 90 days) ・The latitude and longitude of the selected location, observation station, time zone, and notification settings used to provide notifications (linked to the Firebase UID, stored on the server, updated at the next settings synchronization, and retained until account deletion) ・When location cannot be obtained at app startup, on return to the foreground, or during an enabled background movement check, the reason (such as permission denied, location services disabled, timeout, or position unavailable), processing context, standardized error code, failure stage, attempt count, duration, and attempt time (linked to the Firebase UID and retained for 90 days) 3. Information collected through technologies such as cookies To diagnose location functionality, we send the automatic-update setting, in-app consent, OS location permissions and accuracy setting, location-service and geofence-registration status, check time, and app version linked to your Firebase UID. This status report contains no coordinates. It is replaced with the latest state on launch, resume, or setting changes and retained until account deletion. Consent-not-given and permission-denied states are also reported for diagnosis.
Article 2 (Purposes of Use)
We use the collected information for the following purposes: 1. To provide and operate the Service, including pressure and weather information and notification features based on the current or selected location 2. For user support and responding to inquiries 3. To improve the Service and develop new features 4. To analyze usage and create statistical data 5. To prevent misuse and for security measures 6. To respond to violations of the Terms of Service 7. Authorized operations personnel may review location data and related acquisition records to the extent necessary to verify the operation of location acquisition and location-based features, investigate the causes of acquisition failures, address defects, and respond to user inquiries.
Storage of Fortune Profiles
The nickname, date of birth, and gender entered for the fortune feature are stored in Firebase (including Google Cloud), linked to the Firebase UID, to display fortunes and restore the profile across devices. The profile is overwritten when it is next saved and retained until account deletion. It can be deleted through the in-app account deletion process or by contacting us.
Article 3 (Handling of Health Information)
1. Condition logs and headache records are normally stored on the User's device. 2. When the User explicitly creates a cloud backup, the records are stored in Firebase (including Google Cloud) under the signed-in account. A new cloud backup replaces the previous one and is retained until the User deletes it. 3. When Smart Notifications is enabled and the User answers symptom or no-symptom after an alert, the answer, alert category, and alert time are stored in Firebase under the account to adjust notification timing and frequency. Unanswered alerts are not treated as symptom-free. Turning Smart Notifications off stops new answers from being sent to the server. 4. We use this information for the User's health-management reference, backup functionality, and notification adjustment. 5. We do not sell health information or provide it to medical institutions, insurers, or advertisers for advertising purposes. 6. If used as statistical data for service improvement or research, it is anonymized so individuals cannot be identified.
Article 4 (Provision to Third Parties)
The Service does not provide Users' personal information to third parties except in the following cases: 1. When the User has consented 2. When required by law 3. When necessary to protect a person's life, body, or property 4. When outsourcing operations for the purpose of running the Service
Article 5 (External Services, Advertising SDKs, and Data Sources)
The Service uses the following external services to provide features, display weather information, analyze access, and deliver ads: ・JMA AMeDAS: current observed pressure in Japan ・Open-Meteo: API data for weather, hourly and future pressure, UV, and air quality at the selected coordinates (Weather data by Open-Meteo, CC BY 4.0) ・CAMS ENSEMBLE: modelled air-quality data, including PM2.5 and dust particles, delivered via Open-Meteo ・Weathernews Open Data: pollen observations in Japan ・Google Analytics, Firebase, Google AdMob, and similar services: analytics, cloud features, and advertising The selected latitude and longitude are sent to weather and air-quality data providers when requesting data. The app processes data for display, including unit conversion, classification, and aggregation. Advertising and analytics services may collect device information, advertising identifiers, and usage. Information is handled under each provider's terms and privacy policy. Advertising consent choices can be reviewed or changed from the in-app ad privacy settings.
Article 6 (Cookies)
The Service may use cookies to improve User convenience and for access analysis. Users can refuse the use of cookies through their browser settings.
Article 7 (Data Management)
The Service takes reasonable security management measures to prevent unauthorized access to, leakage of, alteration of, or loss of personal information.
Article 8 (Disclosure, Correction, and Deletion of Personal Information)
Users can delete on-device data from Data Management. Location records in Japan (excluding simulated locations) at app startup, foreground return or background movement, and failure diagnostics from any country, become eligible for automatic deletion 90 days after server receipt; deletion may be delayed. Any remaining records are also deleted when the account is deleted. The selected location, time zone, and notification settings stored on the server for notifications are updated when settings are synchronized and deleted when the account is deleted. Cloud backups and other account-related data can be deleted through the in-app account deletion process or by contacting us below. Information subject to a legal retention obligation may be retained only for the required period.
Article 9 (Changes to this Privacy Policy)
The Service may revise this Privacy Policy as necessary. The revised policy takes effect when posted on this website.
Article 10 (Contact)
For inquiries regarding this Policy, please contact us at the following URL.