Privacy Policy

Safa is an alarm app that helps you wake for the Fajr prayer. It also shows prayer times, points to the qibla, counts dhikr and offers short readings. This policy covers the Safa app for iPhone and Android, the website alarm.mysafa.uz and the Safa Telegram bot.

Safa is operated by Safa. For anything in this policy, write to devasqarov@gmail.com or use Help inside the app.

• The alarm, prayer times, wake-up missions, the qibla compass and the dhikr counter all work without an account and without an internet connection.
• Your precise location never leaves your phone.
• Safa never receives, records or stores sound from your microphone.
• There is no advertising and there are no third-party analytics or advertising trackers. Your data is never sold.
• Safa counts how its own screens and missions are used, on its own server, to decide what to improve — and you can turn that off.
• Other people never see how much you gave, unless you choose to show your total.
• You can delete your data yourself, from inside the app, at any time.

An anonymous account. The first time the app connects to our server, it creates an account identified only by a random code. It holds no name, email address or phone number. Your streak, badges and dhikr counts are attached to it.

On iPhone, this account's sign-in is kept in the iOS Keychain of that phone only (it is not synced to iCloud), so reinstalling Safa on the same iPhone returns you to the same account. On Android, reinstalling starts a new anonymous account unless you sign in.

Signing in (optional). You can sign in with Telegram, Apple or Google to keep your account on a new phone. Safa never sees or stores a password. What we receive depends on the service:

• Telegram: your numeric Telegram ID, your @username and your first and last name.
• Apple: an identifier for your Apple Account and, if you choose to share them, your name and email address (which may be an Apple private relay address).
• Google: an identifier for your Google Account, your name and your email address.

The name you sign in with becomes your display name, which you can change. You can link more than one service and unlink any of them, as long as one remains.

Profile — only what you enter. Display name, full name, gender, date of birth and profile photo. We use them to show your profile; which of them other people can see is described below.

Country and time zone. The app works out your country from your phone's time-zone setting — not from your location — and sends the country and time zone to the server. They are used to recommend a prayer-time method, to deliver notifications at a sensible local hour and to show a flag on the boards.

Your wake-up record. For each morning: whether you woke for Fajr, which mission you completed, how many attempts and how long it took, snoozes, an early "I'm awake", your answer to the morning check-in ("did you wake up for Fajr today?"), a skipped morning, an emergency dismiss, a missed day, your evening intention, the local date and your time zone. The record is kept on your phone first; a copy on the server keeps your streak when you change phones and powers badges and the boards.

Dhikr. How many times you said each phrase on each day, your goals, and any phrase you write for yourself. The individual counts are deleted after 60 days; the daily totals stay with your account.

Your activity in the app. Badges you earn, articles you save, the duas you send (chosen from a fixed list of phrases), "JazakAllahu khayran" taps on the supporters wall, whether you accepted or dismissed a request to support Safa, and how many of the kind words hidden on the Home screen you have opened (a running count the app sends when it fetches new ones, so we can see how the feature is used).

How you use the app (usage statistics). Which screens you open and for how long; when the app is opened and put away; each alarm's ring and what followed — the missions started and finished, how long each took, wrong answers and hints, snoozes, an emergency dismiss; opening the hidden word on the Home screen (by a shake, by tapping the greeting or from the daily gift, and which line); visits to the zikr counter; articles and cards opened; the steps of the support and Safa Tong screens; widget taps; which of the app's own reminders came due on your phone and which you opened, counted by kind, and a morning check-in answered from its buttons; settings you change; the controls you use — which tabs, buttons, sheets, pickers and prompts, and the choice made in them (a sound or mission by its name, a setting's value, an amount's size — never a word you typed); the daily gift on the Home screen, whether it was opened or left to fly away; and, about once a day, a summary of how the app is set up — how many alarms there are, their times, repeats, missions and levels, your theme, language, prayer-time and notification settings, which permissions are granted and which widgets are placed. Never what you type (not even an alarm's name — only whether it has one), audio, photos, contacts or your location. Safa collects this itself and keeps it on its own server — there is no third-party analytics — linked to your account, for 13 months. We use it to see which features help people wake for Fajr and what to improve next. Turn it off in Profile → Settings → Privacy → Usage statistics: nothing more is recorded, and anything not yet sent is deleted.

Messages to us. Questions, feature requests and reports you send through Help, our replies, and the app version, platform and language they were sent from. A report also records which account you reported and the reason you chose.

Device information. Each install of the app sends: an install identifier (on iPhone a random code kept in the Keychain; on Android the system's Android ID), the platform, operating-system version, device model and manufacturer, app version and build, app language, country, time zone, whether each permission is granted (location, notifications, alarms, microphone, camera, photos, battery optimisation), your notification settings, and when the app was last opened. We use this to see which versions and devices are in use, to find out why an alarm fails on a particular phone, to respect your notification choices, and to recognise accounts created on the same phone (for example, to help you recover an account or to stop abuse).

Notifications. A push token for your device, and for each notification we send, whether it was delivered and whether you opened it.

Error reports. When the app runs into an error, it sends a technical report: the error message and the program's stack trace, the screen it happened on, whether an alarm was ringing, and the platform, OS version, device model, app version and language. Reports are linked to your account and deleted after 45 days. They contain no screenshots, and nothing you have written is added to them.

Server records. Like any online service, our server sees your IP address when the app connects. The IP address and the device's user-agent string are stored with each sign-in session (and deleted with your account); server logs are overwritten automatically on a short rolling basis. We use them only for security and troubleshooting.

Payments. See "Donations and purchases" below.

• Location. Used to calculate prayer times and the qibla direction. The app matches it to the nearest city in a list built into the app and keeps the result on the phone. Your coordinates and your city are never sent to us.
• Microphone. Used only on the "Read a verse" mission screen, to check that you are reading aloud. Safa never receives, records or saves audio. On iPhone, speech recognition runs on the device only. On Android, Safa asks the phone to recognise speech on the device; a phone that cannot do that uses its own speech service (usually Google's), under that provider's terms.
• Motion sensors. The accelerometer is read by the Walk and Shake missions while they are on screen, and by the Home screen to notice a shake gesture while it is open. The sensor readings themselves are never recorded or sent.
• Camera and photos. Used for the QR code mission and for a profile photo. The code you register for the mission is stored only on your phone. From your photos, only the one picture you choose as your profile photo is uploaded.
• Your alarms, sounds, settings, the reading cache and the list of people you have blocked.

Safa never accesses your contacts, messages, calls, calendar or health data.

Safa has no comments, no likes and no direct messages.

Your public profile. New accounts start with a public profile, which anyone who taps your name can open. It shows your display name, your full name (if you entered one), photo, country, badges, the date you joined and how many "JazakAllahu khayran" taps you have given. It shows the following only if you switch them on: your streak (when you join the leaderboards), today's dhikr total, your total support and number of donations, and how many duas you have received. It never shows your gender, date of birth, email address or how you sign in. You can make your profile private at any time: Profile → Edit profile.

Leaderboards. You appear on them only if you choose to. They show your name, photo, country, featured badge, the Safa Tong mark and your streak or this week's wake-ups. An account that has not signed in appears as "Anonymous".

The supporters wall and boards. When a donation or purchase succeeds, it appears on the supporters wall, and you appear on the supporters boards with your name, photo, country and supporter level. A level stands for a range of amounts; the exact amount is never shown unless you switch on "Show my support total". If you would rather be listed without your name and photo, write to us and we will make your support anonymous.

Payme (in Uzbekistan). You pay on Payme's own page, in your browser. Safa never sees or stores your card details. We store the order number, the amount in soʻm, its status and Payme's transaction number and times. Payme issues the fiscal receipt and processes the payment under its own terms.

Click (in Uzbekistan). You pay on Click's own page, or in the Click app if it is installed. Safa never sees or stores your card details. We store the order number, the amount in soʻm and its status, and for each payment attempt Click's payment numbers (including the number in Click's SMS), the times, Click's error if the attempt failed, a refund if one was made, and the link to the fiscal receipt. Click issues the fiscal receipt and processes the payment under its own terms.

App Store and Google Play. A Safa Tong purchase is handled entirely by Apple or Google. We receive the transaction and verify it with them, and store its reference number and amount — never your payment details.

Payments require a signed-in account. Payment records are kept for accounting; if you delete your account, they are kept without any link to you.

Notifications from the phone itself — the alarm, the notice 15 minutes before it, prayer-time bells, the morning check-in, the evening intention, reminders and dhikr reminders — are scheduled on your phone and are shown without any server. How many of them came due and how many you opened is counted as part of usage statistics (above), which you can turn off.

Push notifications — daily inspiration, Safa news, replies to your messages and gifts — are delivered through Firebase Cloud Messaging (Google) and, on iPhone, Apple's push service. They receive your device's push token and the text of the notification. Safa uses Firebase for push delivery only, not for analytics or crash reporting. Non-urgent pushes are held overnight, between 22:00 and 06:30.

Telegram. If you signed in with Telegram, the Safa bot can message you when a new article or inspiration is published. Turn this off in Profile → Settings → Notifications. Telegram processes those messages under its own privacy policy.

We do not sell or rent your data, show advertising or share data with data brokers. It is handled only by the services Safa needs in order to work:

• Hetzner Online — hosts our own server in Helsinki, Finland (European Union). The database, accounts, files and website run on that server.
• Google — push delivery (Firebase Cloud Messaging), Google sign-in, Google Play purchases and, on some Android phones, speech recognition.
• Apple — Sign in with Apple, App Store purchases and push delivery on iPhone.
• Telegram — only if you sign in with Telegram.
• Payme — only if you donate through Payme.
• Click — only if you donate through Click.

A small team — the operator and the moderators — can see account data in Safa's admin panel in order to answer your messages, handle reports and fix faults. Their actions are logged.

We may disclose data if the law requires it or if it is necessary to protect someone's safety, and in no other case.

Our server is in Finland, in the European Union. If you live elsewhere, including Uzbekistan, your data is transferred to and stored in Finland, and the services listed above may process it in other countries under their own safeguards.

• Account, profile, wake-up record, badges and dhikr totals: until you delete your account.
• Individual dhikr counts: 60 days.
• Error reports: 45 days.
• Usage statistics: 13 months.
• Sign-in hand-off codes: a few minutes.
• Messages to us: until you delete your account.
• Payment records: as long as accounting requires; after account deletion, without any link to you.
• Backups: database backups are kept for 14 days and file backups for up to 8 weeks, so deleted data disappears from them within that time.
• Server logs: overwritten automatically.

See your data. Ask through Help or by email and we will send you a copy of what the server holds about you.

Correct it. Change your profile at any time in Profile → Edit profile.

Delete it. Profile → Settings → Account → Delete account removes everything held on the server. If you have not signed in, the same screen offers "Delete my data on this phone". Details: https://alarm.mysafa.uz/delete-account/en

Switch things off. Your public profile, the leaderboards, showing your support total, dhikr or received duas, push notifications, Telegram messages and usage statistics can each be turned off in the app.

Withdraw a permission. Location, microphone, camera and notifications can be revoked in your phone's settings at any time. Features that depend on a permission stop; the alarm keeps working.

Object or complain. Write to us and we will reply within 30 days. You also have the right to complain to the data-protection authority in your country.

All traffic between the app and our server is encrypted (HTTPS). The database enforces per-account access rules, so an account can read only its own private data. No passwords are stored. Admin access is limited to the team and logged. No system is perfectly secure, but we work to protect your data and will tell you if a breach affects it.

Safa is not directed at children under 13, and we do not knowingly collect their data. If you believe a child under 13 has given us personal data, write to us and we will delete it.

When this policy changes, the date at the top changes with it. If a change affects what we collect or who can see it, we will tell you in the app before it takes effect.

Contact: devasqarov@gmail.com, or Help inside the app.