Skip to content
Deprem
Live

Privacy policy

Last updated:

This policy covers the deprem.sayfa.app website, the Deprem iPhone app (including its Apple Watch app and widgets), the Deprem Android app and the deprem-api.sayfa.app server they use.

Deprem has no accounts; we do not ask for your name, email or phone number. We use no ads, no advertising identifier, no cross-site tracking and no third-party analytics, and we do not sell data. Page visits on the website are counted with Yuva Analytics (useyuva.com), our own open-source analytics; see “Usage statistics”.

Device registration and notifications

The app or the browser creates a random device id and a secret key for itself and registers them with the server; the server stores only a hash of the key. The iPhone and Android apps register only when you turn on alerts, save a place or use station mode; the website only when you turn on alerts on the “Alerts” page.

The registration holds:

  • the notification address: on iPhone the Apple Push Notification service (APNs) device token, on Android the Firebase Cloud Messaging (FCM) token, on the web the browser’s Web Push subscription (endpoint and encryption keys); if you use Live Activities, a push-to-start token,
  • language, intensity threshold, critical alert preference, app and operating system version,
  • your saved places: the name you give and coordinates rounded to about 100 m (0.001°),
  • in the app, if “Alerts where I am” is on, your last location rounded to about 1 km (0.01°),
  • when you were last notified and for which earthquakes.

How alerts are computed

For every earthquake the server computes the expected shaking at your saved places and notifies you when it reaches your threshold. Notifications are delivered through Apple (APNs), Google (Firebase Cloud Messaging) or your browser’s push service (for example Google, Mozilla or Apple); these services see only the notification content and address.

“Did you feel it” reports

When you report shaking, the location you send is reduced to an H3 cell (resolution 8) of about 0.7 km², roughly 1 km across, as soon as it reaches the server; the exact coordinates are neither stored nor logged. The cell, the intensity you chose, the time, the platform and a random id your device keeps (to merge repeated reports) are stored. That id is not linked to your device registration.

Per-cell summaries are shown publicly on earthquake pages.

Station mode (phone as a sensor)

Station mode runs only when you turn it on and the phone is charging and still. On Android it runs as a foreground service shown in the notification bar and reads the accelerometer only while the phone is charging; nothing is detected while the phone is moving. Motion data is processed on the phone; raw sensor data is never sent.

Only the following is sent to the server: an H3 cell (resolution 7) of about 5 km², clock offset, sample rate and background noise (regular “I am listening” heartbeats), and, when the phone detects shaking, the trigger time, peak acceleration and classifier values. These records are linked to your device id.

Apple App Attest on iPhone and Google Play Integrity on Android are used to reject fake data: Apple or Google confirms that the app is genuine and unmodified. On iPhone the server keeps the result and the public part of the key on the device; on Android it keeps only that the check passed and when, and Play Integrity tokens are not stored. Community detection is experimental and currently runs in shadow mode; this data is not used to send alerts, only to measure how well the method works.

What stays on your device

The iPhone app asks for your location only while you use it, and uses it to estimate the expected intensity where you are, to find nearby assembly areas and for felt reports. Nearby assembly areas are stored on the phone for offline use. The “I’m safe” message goes through the phone’s share sheet to the people you choose; it is not sent to us. The Android app also asks for location only while you use it and does not request background location.

The website uses one cookie, lang, only to remember the language you picked; no other cookies. Your browser keeps only your theme choice, a random id for felt reports, the device id, key and chosen place if you turned on alerts, and your emergency kit list and family plan if you used the Tools section (local storage); none of these are sent to the server.

Technical data

Requests to the site and the server pass through Cloudflare. Your IP address is used in memory for rate limiting to prevent abuse and is not written to the database. The basemap is served from Cloudflare R2, earthquake data from our own server.

Usage statistics

To know how many people use the app, we keep one record per device per day for each request made with the device key: country (the country code Cloudflare derives from your connection; the IP address is not stored), platform, app version and build, OS version, device model, the device’s region setting, time zone and language. Requests without a device (the website and the app’s public queries) are only counted per day, country, endpoint type and client type. No third-party analytics; the data is not used for advertising and not shared.

Page visits on the deprem.sayfa.app website are counted with Yuva Analytics (useyuva.com), our own open-source analytics, which we run ourselves. It sets no cookie and stores nothing on your device. Your IP address is shortened before anything else uses it and is never stored; the approximate location comes from the shortened address. What is kept: the page and the referring page, campaign (utm) parameters, country, region and city, browser, operating system, device type, screen size class and language. To tell visitors from page views, a hash of the shortened address and the browser is computed under a random key that is deleted within hours of the end of the day, so a visitor cannot be recognised the next day or on another website; no profile and no id per person is kept. Browsers that send Do Not Track or Global Privacy Control are not counted. This is used only to understand and improve the website, not for advertising, and is not shared.

Deprem Pro purchases

Deprem Pro purchases are processed by Apple on iPhone and Google Play on Android; your payment details never reach us. We use RevenueCat to manage the subscription status. The app sends RevenueCat no name, email or our device id; an anonymous user id generated by the RevenueCat SDK and the store’s purchase receipt are sent to RevenueCat to verify the Pro entitlement. Your Pro status is not sent to the Deprem server.

Retention and deletion

  • Device registration, places, last location and the App Attest or Play Integrity attestation: until the device registration is deleted. Deleting the registration deletes them together.
  • The list of notifications sent: 30 days (or until the device registration is deleted, whichever is first).
  • Sensor triggers linked to your device are kept 30 days; after that only platform, time, sample rate, peak values, classifier score and classifier features are kept for 1 year, without your device id or location, to train the detector.
  • Station mode heartbeat history: 90 days (or until the device registration is deleted, whichever is first).
  • On iPhone and Android, Settings → “Delete my data” deletes the device registration from the server immediately and clears the places, last location, offline assembly areas and keys on the phone, and ends Live Activities. “Did you feel it” reports are not deleted because they are anonymous cells.
  • On the web, turning alerts off on the “Alerts” page deletes your device registration immediately. A browser subscription the push service reports as gone is removed automatically.
  • One-time App Attest and Play Integrity challenges are valid for 5 minutes; expired ones are deleted within 10 minutes.
  • Test triggers and drill simulations: 7 days. A drill record contains the device position rounded to about 100 m.
  • Per-device daily usage records: 13 months (or until the device registration is deleted, whichever is first). Daily totals without device ids: kept indefinitely.
  • Website page views counted with Yuva Analytics: individual page views 90 days, daily totals 25 months.
  • “Did you feel it” reports: kept indefinitely at cell level together with the random id the app or browser generated; that id is not linked to your device registration. The IP address of the request is not stored with a report.
  • Database backups are kept encrypted in Cloudflare R2. Because of the 30-day recovery window and the base backup that covers it, data of a deleted device can remain in backups for up to about 31 days.
  • Server logs are kept for 30 days. Some warning lines can contain a device id; coordinates, push tokens and secret keys are never written to the logs.

App Store privacy label summary

The App Store privacy details of the iPhone app match this policy:

  • Precise location: your saved places and, for “Alerts where I am”, your last location; for app functionality, linked to your device id, no tracking. The server rounds places to about 100 m and the last location to about 1 km.
  • Coarse location: “Did you feel it” reports on cells of about 0.7 km² (roughly 1 km across); for app functionality, not linked to you. Also the country code in usage statistics; for analytics, linked to your device id, no tracking.
  • Device ID: the app-generated device id and the push token; for app functionality and analytics, linked to your device registration.
  • Usage Data → Product Interaction: the per-device daily usage record; for analytics, linked to your device id, no tracking.
  • Diagnostics → Other Diagnostic Data: app version and build, OS version, device model; for analytics, linked to your device id, no tracking.
  • Other data: station mode summaries (peak acceleration, a cell of about 5 km²); linked to your device id.
  • Purchases → Purchase History, for App Functionality and Analytics (by RevenueCat, which validates App Store receipts under an anonymous app user ID), not linked to your identity, not used for tracking.
  • Not collected: tracking, contact info.

Google Play data safety summary

The Google Play data safety details of the Android app match this policy. Data is encrypted in transit and none is shared with third parties (Firebase Cloud Messaging, Play Integrity, RevenueCat and Cloudflare act as service providers). Google counts areas under 3 km² as precise location, so places, the last location and felt-report cells are declared as precise:

  • Location → Precise location: saved places (about 100 m), last location (about 1 km), felt-report cells; for app functionality.
  • Location → Approximate location: the station mode cell (about 5 km²) and the country code in the daily usage record; for app functionality and analytics.
  • Financial info → Purchase history: Deprem Pro purchases (RevenueCat and Google Play Billing); for app functionality.
  • App activity → App interactions: the per-device daily usage record; for analytics. Other user-generated content: the intensity in a felt report. Other actions: station mode heartbeats and triggers; for app functionality.
  • App info and performance → Other app performance data: app version and build, Android version, device model, region setting, time zone, language; for analytics.
  • Device or other IDs: the app-generated device id, the FCM token, the RevenueCat anonymous user id, the Play Integrity result for station mode; for app functionality, analytics, and fraud prevention and security.
  • Not collected: personal info (name, email, phone, address), messages, photos and videos, audio, files, calendar, contacts, health and fitness, web browsing, crash logs, advertising ID.
  • All data is optional; you can request deletion in the app with Settings → “Delete my data” or by email.

Data sources

Earthquake data comes from AFAD, Boğaziçi Üniversitesi Kandilli Rasathanesi ve Deprem Araştırma Enstitüsü Bölgesel Deprem-Tsunami İzleme ve Değerlendirme Merkezi, EMSC, USGS, GFZ GEOFON and the National Observatory of Athens (NOA) and is shown with attribution. Assembly areas and map data © OpenStreetMap contributors (ODbL), basemap by Protomaps, faults from GEM Global Active Faults (CC BY-SA 4.0).

Children

Deprem is not directed at children and does not knowingly collect personal data from children.

Contact and your rights

You can delete your data yourself: on iPhone and Android with Settings → “Delete my data”, on the web with “Turn off alerts” on the “Alerts” page. For deletion requests, including reports sent from the web, and for other access or correction requests under GDPR and the Turkish KVKK, write to [email protected]. Including your device id speeds up the request.

If this policy changes, the new version is published on this page with its update date.