Embedded Files
Simple Alarm ("the App") is an Android alarm clock developed by KairyLab. This page describes what information the App handles, why it is needed, where (if anywhere) it is sent, and what control you have over it.
The App is designed to keep personal information on your device. Apart from the limited cases listed below, nothing the App reads from your device is transmitted to any server.
1. Alarms, sound and notifications
1. Alarms, sound and notifications
To ring alarms reliably the App uses Android permissions for exact alarms, notifications, foreground services, vibration, wake lock, full-screen intents, system overlays, and exemption from battery optimization. It also re-registers your alarms after device reboot, time changes, or app updates.
If you choose a ringtone from your device, the App reads audio files using READ_MEDIA_AUDIO (Android 13+) or READ_EXTERNAL_STORAGE (Android 12 and earlier). The selected file is played locally and is never uploaded.
No data from this section leaves your device.
2. Calendar
2. Calendar
If you grant the calendar permission (READ_CALENDAR), the App reads today's events from your device's calendar and shows them on the screen that appears after an alarm rings. Calendar data is read on demand, kept only in memory for display, and is never transmitted off the device. You may revoke this permission at any time in Android system settings; the schedule section will simply stay empty.
3. News headlines
3. News headlines
The post-alarm screen can show a short list of news headlines. To do so the App downloads a single static JSON file hosted at https://news-hosting-common.web.app/ . The request contains only information that any web request contains (your IP address and standard HTTP headers chosen by Android). No identifier, account, location, reading history, or other personal information is sent with the request. The downloaded headlines are not stored permanently and are discarded when the screen closes.
4. Weather forecast (location)
4. Weather forecast (location)
The App offers an optional weather forecast on the post-alarm screen. The forecast is shown only on devices whose system language is Japanese (ja_JP) and whose location lies within Japan. On all other devices the feature is hidden and no location is requested.
· Permission requested
Only ACCESS_COARSE_LOCATION (approximate location, about 10 km accuracy). ACCESS_FINE_LOCATION (precise location) is never requested.
· Purpose
Solely to decide which 10 km mesh cell of Japan your forecast should be fetched for. Location is not used for advertising, analytics, profiling, or any other purpose.
· How the location is handled
Your raw latitude and longitude are never transmitted to any server. On your device, the coordinates are converted into a 10 km mesh ID (for example "396_1270") and that mesh ID is further transformed into an opaque HMAC-SHA256 hash. Only the hash appears in the URL used to download the pre-generated forecast file. The hosting server therefore cannot recover your location from the request.
· Where forecasts come from
Forecast files are static JSON files hosted on GitHub Pages (public repository "monmonapps/weather-cache"). The forecast contents are produced server-side from data provided by Open-Meteo (https://open-meteo.com). No request from your device ever reaches Open-Meteo directly.
· Frequency and background access
Location is read only while the weather card is visible, and only when the local cache (lifetime: 30 minutes) has expired. The App does not read your location in the background.
· Local storage
The most recent latitude/longitude, the derived mesh ID, and the cached forecast JSON are stored in Android SharedPreferences on your device. They never leave the device and are removed when the App is uninstalled or when its data is cleared from system settings.
· Disabling the feature
To stop the App from using your location, revoke the location permission for Simple Alarm under Settings → Apps → Simple Alarm → Permissions → Location. Once revoked, the weather card falls back to a placeholder and no further location access is performed.
5. Advertising
5. Advertising
The App shows advertisements supplied by Google AdMob (part of Google Mobile Ads). To request and display ads, AdMob uses your device's advertising identifier (AD_ID) and a network connection (INTERNET, ACCESS_NETWORK_STATE). AdMob may use information about your activity on the web to personalize the ads it shows.
· You can reset or limit your advertising identifier at any time under Settings → Privacy → Ads on your device.
· Users in the EU / EEA / UK are presented with a consent form on first launch where personalized ads can be declined.
· For details of what Google collects through AdMob, see Google's own privacy policy: https://policies.google.com/privacy
6. Crash and error reports
6. Crash and error reports
To improve stability, the App may send anonymous crash and error reports through Google Play services when the App terminates abnormally. These reports contain technical information such as stack traces, the App version, device model, and Android version. They are aggregated by Google Play Console and are not used to identify you. You can opt out of automatic sending under Settings → Google → Usage & diagnostics on your device.
7. Children's privacy
7. Children's privacy
The App is not directed to children under the age of 13 and does not knowingly collect personal information from them.
8. Third-party services
8. Third-party services
· Google AdMob — advertising
https://policies.google.com/privacy
· Google Play services — crash reporting, advertising ID
https://policies.google.com/privacy
· GitHub Pages — static hosting of pre-generated weather JSON
https://docs.github.com/site-policy/privacy-policies/github-general-privacy-statement
· Open-Meteo — source of the weather data (accessed server-side only, never directly from your device)
https://open-meteo.com/en/terms
· The geographic mesh used by the weather feature is derived from "Location Reference Information" (位置参照情報) published by the Ministry of Land, Infrastructure, Transport and Tourism of Japan, used under the Government of Japan Standard Terms of Use 2.0.
9. Changes to this policy
9. Changes to this policy
This policy may be revised when new features are added or when applicable law changes. Material changes will be reflected by updating the "Last updated" date at the top of this page.
10. Contact
10. Contact
For questions about this policy, please contact: kairy.lab@gmail.com
Credits
Credits
Image by pch.vector on Freepik
Google Sites
Report abuse