Privacy policy
Коли світло. Developer: Ihor Herasimov. Updated: 29 October 2026. Contact: [email protected].
The app displays electricity outage schedules and reports from public sources. No account registration is required. It does not request GPS, contacts, camera or microphone access. Beginning with Android 0.2.26, the Google Play version includes Google AdMob banners.
Saved towns and groups, schedule cache, language, theme, icon, widget appearance and reminder preferences are stored locally on your device until app data is cleared or the app is uninstalled. Removing a card removes it from the saved schedule list.
For search and schedules, the app sends your search query, selected settlement path, group and requested date over HTTPS to app.otvet04ka.com. Your selected town is not determined through GPS and does not necessarily represent your physical location. These requests serve schedule functionality; no user profile is created.
The backend caches public source pages to retrieve schedules efficiently; this cache does not contain a user account or user identifier. Standard HTTP access logging for schedule and website routes is disabled in the app service. Technical errors may include a source path without a user profile.
Emergency reports are retrieved from public Telegram pages. Network recipients, including Cloudflare, necessarily process IP addresses and request metadata. Independent services process these under their own privacy policies (Cloudflare, Telegram and Bez Svitla). We do not set their independent retention periods.
Reminders and widgets use Android services. Notifications can be disabled and exact reminders require a separate system setting. Android restrictions may delay background checks.
Feedback buttons open your external email app or Telegram. Messages are sent only through your action. If you contact the developer, your address and message are used to respond; correspondence is retained until the request is resolved or a deletion request is received, except where retention is legally required.
To remove local data, clear app data in Android settings or uninstall the app. Contact [email protected] for questions or requests concerning correspondence. Changes to this policy are published here with a revised date.
Global minigame ranking: participation is optional. When you choose a nickname, the app sends your nickname, random player ID, game session ID, score, level and duration to the server over HTTPS. The public ranking displays nickname, score and level. A new monthly ranking starts on the first day of each month in Kyiv time. Results are kept for up to 100 days and unfinished sessions for up to 7 days. The nickname profile remains until deletion. Delete your profile and results using the button in the global ranking or contact [email protected]. Clearing Android app data does not delete server results. The game works offline without ranking participation.
Statistics and diagnostics
Technical statistics are optional. The random ID counts unique installations separately even on two phones of the same model. Reinstalling may create a new ID, so this is not an exact count of physical phones. Settings let you allow sending a random installation ID, model, Android/app versions, installer, language and first launch and last contact times to app.otvet04ka.com. IP is not stored in the statistics database; location, Google email, hardware identifiers and saved cities/groups are not sent. Network provider Cloudflare technically processes IP for request delivery and protection. Individual records are accessible only to the developer and retained up to 90 days after last contact (cleanup on service access). Disabling statistics requests deletion; offline requests retry on the next launch. The public website shows cumulative new users from the Google Play report with its reporting date; the developer updates this metric separately from technical statistics. The nonpersonal aggregate remains after deletion. No additional Android permissions are requested. Version 0.2.19 and later send permitted statistics on opening and at most once every five minutes while the app is open; without network access, delivery is delayed. Support email lets you review technical diagnostics and separately include cities/groups before sending the email yourself.
Technical statistics are enabled in the first-run notice, but transmission starts only after Continue. They can be switched off immediately or later in Settings. Required minimal crash reports contain only Android API version, app version and technical exception class, without exception text, stack trace, installation ID, model, IP, location or saved data. The last crash is stored locally until successfully submitted on a later launch after the initial notice. The server retains only aggregate counts by UTC day, versions and error code for 90 days without a user association. Network retries can cause duplicate counts.
First-launch counting is required independently of the technical statistics switch. After the initial notice the app sends an independent random activation code, without model, versions, IP or saved data in that request. The server retains only a keyed hash and acceptance time for up to 90 days to prevent duplicate counting; it does not link this hash with optional statistics. After a successful response the app does not register again. Reinstallation or a very late retry after a failed request may count again. The aggregate is not an exact count of people or store downloads and is retained indefinitely without individual records. Network infrastructure technically uses IP for delivery, but it is not stored in these databases.
Advertising and privacy choices
Starting with Android 0.2.26, the Google Play version uses Google AdMob for a bottom banner. Only non-personalized ads are requested, after the Google User Messaging Platform consent check. Where required, you can consent, refuse or manage choices, and reopen the form from Settings → Advertising privacy.
Non-personalized ads may still send Google the IP address for approximate location, device identifiers (advertising ID and app set ID), app/ad interactions, and crash/performance diagnostics for advertising, analytics and fraud prevention. Data is encrypted in transit. Google's privacy policy covers its handling, retention and data controls. Saved addresses, cities, groups and game nickname are not sent to the ad SDK; precise GPS is not requested. Reset or delete the advertising ID in Android settings. The optional first-party statistics switch does not control AdMob. If no banner is available, the app's functions remain accessible.