Updated 14 November 2026 · translation of the Ukrainian original
Privacy Policy
This policy describes what data the Air Alert Map (“Карта тривог”) app and website process and why.
1. Who is responsible
Air Alert Map is developed and run by İbrahim YAVUZ. Personal data questions: [email protected]; anything else: [email protected].
2. Data we process
- Approximate location — only if you grant permission. It is used on the device to find your district. Coordinates are not sent to our server.
- Settings, places and the regions you follow — stored on the device.
- Push notifications — to deliver alerts while the app is closed we use Firebase Cloud Messaging (Google). The device subscribes to the topics of your district and of the regions you follow; Google processes a device identifier to deliver them. Topics contain no coordinates.
- Advertising — the free version shows Google AdMob ads. AdMob may process the device advertising identifier, IP address and ad interaction data. In the EU, EEA, UK and Switzerland personalised ads are shown only with your consent (Google’s consent form); on iOS tracking requires your permission (App Tracking Transparency). You can change your choice in the app settings.
- Purchases and subscriptions — payments are handled by the App Store or Google Play; we never receive payment details. RevenueCat processes purchase status to unlock paid features.
- Server logs — IP addresses and request times may be processed for security and diagnostics and are kept for a limited time.
- Cloudflare — all traffic of the app and the website, the Community included, passes through Cloudflare (delivery and protection); like any intermediary, Cloudflare sees the IP address and the requests.
The third parties we share data with (Google Firebase Cloud Messaging, Google AdMob, RevenueCat and Cloudflare, and, for the Community only, DeepSeek) process it under their own terms, which provide a level of protection equal to that described in this policy. The list and purposes are in section 8.
3. What we do not do
We do not sell personal data, do not share your location with third parties and do not use it for advertising. No alert is ever behind a subscription or an ad.
4. Alert data sources
Alert and threat data come from public sources; the current sources, with links, are shown next to the map in the app and on the website (currently NEPTUN, https://neptun.in.ua, which collects official signals and open sources). Boundaries come from OpenStreetMap, GADM and Natural Earth open data; temporarily occupied territories follow public DeepState data. The app is not an official channel of the State Emergency Service of Ukraine and does not replace sirens or official warnings.
5. The airalertmap.com website
The website uses no cookies, analytics or ads. It loads alert data from our server.
6. Community: what data and why
From version 1.1, the app has a “Community” section (text only). This section, and everything this policy says about it, applies from version 1.1. Everyone can read; only PRO and Patron subscribers aged 16 or over who have accepted the rules can write.
- Messages. Text (up to 300 characters), room, time and a generated nickname. A message is visible to everyone in the room for 72 hours; anyone can see and copy it. Do not put personal data in it.
- Proof of purchase. To unlock writing, the app sends an anonymous RevenueCat identifier (not your name or e-mail) to our chat server, and the server asks RevenueCat about your subscription. The identifier and the subscription identifiers are written to disk only as irreversible hashes (HMAC) and never reach any log. This is needed so that a block cannot be dodged by reinstalling the app or changing plan.
- Automatic check. The message text and the room name are sent to DeepSeek (China) before publication, and again if the message is reported, and for translation for the moderator if the message lands in the moderation queue (at the moderator’s request, as a separate call). During the check the model also writes a short summary of the message for the moderator. The summary is kept together with the message and deleted with it. We do not send the author, the nickname, the address or any history. The text first passes automatic rules on our own server; if we switch free writing off, DeepSeek receives nothing.
- Reading. Requests to read, to open a session and to accept the rules carry no room, region, district, place or coordinates: all rooms arrive together and the selection happens on your device. The room (all-Ukraine or the region you chose) is sent only with a message, when you press “send”; it is visible to everyone in that room anyway. Reports and deletions carry a message identifier, which indirectly indicates its room.
- Reports and rules. A report (message identifier, reason, time); for a report from a subscriber also a hash of their record until the report is resolved. We also keep the fact that the rules were accepted, session identifiers and warnings.
- IP address. The chat server does not write the IP address to disk: it stays in memory to limit request rates. Your address is not written to any log when reading messages or filing a report. Requests to open a session, to send and to delete messages are logged by the web server with the address, time and path for 12 months (security and legal requirements).
- No promise of anonymity. A nickname hides you from other users but does not guarantee anonymity: the address in the web server log and the purchase data may be used on a lawful request of competent authorities.
7. Community: retention periods
From version 1.1 the following periods apply:
| Data | Period |
|---|---|
| Messages visible in the room | 72 hours; then in the archive for up to 30 days |
| Texts of rejected, held and expired messages | up to 30 days; text rejected by the automatic rules is not stored at all |
| Author record: key hashes, sessions, rules acceptance, warnings | 90 days after the last activity |
| Block and mute keys (hashes) | 2 years; a deletion request does not affect them |
| Reports | 30 days |
| Moderation action log | 1 year; the message text is removed from the lines after 30 days |
| Web server log: IP address, time and path of requests to open a session, send and delete messages | 12 months |
Records marked with a legal hold (section 10) are not deleted when these periods end.
8. Processors and transfers abroad
From version 1.1 the processors are:
| Party | Purpose |
|---|---|
| Google Firebase Cloud Messaging (FCM) | delivery of push alert notifications |
| Google AdMob | ads in the free version |
| RevenueCat | purchase and subscription status; subscription check for the Community |
| DeepSeek (China) | checking messages, a short summary and a translation for the moderator: the message text and the room name |
| Cloudflare | delivery and protection of the app’s and the website’s traffic |
These parties may process data outside Ukraine, and DeepSeek does so in China. By accepting the Community rules you agree that the text of your messages is checked automatically by DeepSeek, which also writes a short summary and a translation for the moderator; you cannot write without this consent.
9. Deleting data and your rights
Data on the device is deleted with the app’s data or when the app is removed. Location, notification and tracking permissions can be withdrawn in the phone settings.
From version 1.1 you delete your Community data yourself: the “Delete my Community data” button in the section’s “⋯” menu and in settings. It works even when your subscription has ended. Your messages and author record are removed from our files within 24 hours at the latest. Only records under a legal hold and the hashed block keys remain (up to 2 years, so that a block cannot be dodged). A single message can be deleted by long-pressing it. For access, correction or deletion requests write to [email protected].
10. Legal hold
From version 1.1, where the law or a request of a competent authority requires it, or to investigate a serious violation (for example harm to children or forbidden information), we may mark individual records with a legal hold. Such records are not deleted when the period ends or on your deletion request for as long as the hold lasts. Each such action is recorded in a log.
11. Children and age
The app is not intended for children under 13 and does not knowingly collect their personal data. From version 1.1 you can write in the Community only from the age of 16: before your first message you confirm your age and accept the rules. This is a confirmation, not an age check. On child safety in the Community see Child safety.
12. Availability of the Community
From version 1.1 the Community (both reading and writing) is unavailable to requests from the EU, the EEA and the United Kingdom. The rest of the app works unchanged. Community rules: Community Rules.
13. Changes
We may update this policy; the current version is always on this page. If the translation and the Ukrainian original differ, the Ukrainian original prevails.