Privacy policy

1. Who we are

Sajda is an app for calculating and tracking qada (missed) prayers. It is made and maintained by Muhammadumar Davlatov, an independent developer. In this policy, “we” means this developer.

This policy covers the Android version of Sajda on Google Play (package name uz.sajda.app) and the Sajda server the app connects to.

If you have questions, write to support@qazo-namoz.uz.

2. Data that stays on your phone

Everything you enter is kept on your phone, in the app’s private storage (an SQLite database). Other apps cannot read it. The database is not encrypted separately; Android’s separation of apps protects it. The app needs neither an account nor the internet to work.

Kept on the phone:

• what you enter for the qada calculation: method, gender, date of reaching puberty (or date of birth and age of puberty), the date you started praying regularly, periods without prayer, and for women the days of hayd and nifas and the number of births;
• the qada you have prayed: +1 taps, calendar marks, daily counts and statistics;
• daily goal, reminders, language and appearance;
• zikrs, the names of your own zikrs, and their counts;
• the city you chose for the qibla, or the place found by GPS;
• a small copy of today’s numbers for the home screen widget;
• if backup is on: the server account number, the time of the last copy and the sign-in token (section 8).

The database, the widget copy and the scheduled reminders (their times and texts, for example the daily goal number) are not included in the phone’s automatic Google cloud backup.

If you move to a new Android phone directly by cable or Wi‑Fi, the database and the widget copy may move to the new phone. The sign-in token does not.

Uninstalling the app, or tapping Profile → Delete all data, deletes it from the phone.

Export. In Profile → Export and import you can save your data as a file (JSON) or a PDF report. You choose where the file goes in the system “Share” window; nothing comes to us. The app deletes the temporary copies it made for sharing.

3. Cloud backup (optional)

Backup is off by default. It starts only when you tap Profile → Turn on backup → Continue with Google, or when you choose Restore from backup on a new phone and sign in with your Google account. Without backup, the app sends no qada, zikr or settings data to the server.

What the server keeps while backup is on

The backup is one copy of the data on your phone. The server keeps it tied to your account:

• Account: a random server account number, the date the account was created, the first day of use, the time of the last copy and the copy’s sequence number.
• Google link: the permanent number (identifier) of your Google account and the date it was linked (section 4).
• Settings: your phone’s time zone (for example, Asia/Tashkent), language, appearance, daily goal, reminders (on or off, times, sound, vibration), and whether automatic backup is on.
• What you entered for the qada calculation: method; gender; date of reaching puberty, or date of birth and age of puberty; the date you started praying regularly; the dates of periods without prayer; the numbers for the “I know the number” method; for women, hayd days per month, the number of births and the number of nifas days per birth.
• Results: owed and prayed counts for each prayer, calendar marks, and the history of daily counts (date and numbers).
• Zikrs: names (including your own), goal and daily counts.
• Plan history: each uploaded copy adds a short record of the calculation inputs (the dates and numbers above) and the totals at that time. Old records are not removed: they build up until the account is deleted and are deleted together with it.
• Session: to keep you signed in, the server keeps not the sign-in token itself but only its hash (SHA-256), and when it was issued, expires and was revoked.

Not sent to the server: qibla location, widget data, export files, phone model, phone number, contacts, advertising ID.

When data is sent

• when you turn backup on (the first copy);
• when you tap Back up now;
• if Automatic backup is on: at most once a day, only over Wi‑Fi or Ethernet, and only if the data has changed. The app checks this when it is opened or you return to it; it sends nothing in the background;
• if the server holds a different copy saved by another phone and you choose Replace (this phone’s copy replaces the one on the server);
• with Restore from backup, the copy is downloaded from the server to the phone.

When the backup screen is opened, the app only asks the server for the state of the copy (its sequence number and time); it sends no data.

Who can see it

Other users cannot see your backup: the server limits every request to that account’s own data. The developer (the server administrator) runs the server database and can technically read it. We look at data only to run the service, fix errors, or carry out your request.

The Sajda server runs on a virtual server (VPS) rented from the hosting company Contabo, and the data is stored on that server’s disk. The hosting company runs the hardware. We do not give it your data for any other purpose. The server may be in a country other than the one you live in.

4. Sign-in with Google

In the Android version, backup works only with a Google account. Sign in with Apple is not available in this version.

• Google itself shows the sign-in window. You choose the account; we never see your password. Google’s privacy policy applies to this step.
• Google gives the app a signed sign-in token (ID token). It contains the permanent number of your Google account, and usually also your email address, name and a link to your profile photo.
• The app does not save this token, and does not show or remember your email, name or photo. The token is sent only to the Sajda server, to verify the account.
• The server checks Google’s signature and takes only the account’s permanent number from the token. The server keeps only this number, the label “google” and the date it was linked. Your email, name and photo are not stored on the server.
• The app does not ask Google for access to your contacts, Google Drive or any other extra permissions.
• Deleting your account on the website (qazo-namoz.uz/hisobni-ochirish/en) also uses Google sign-in. The sign-in button is loaded from Google’s own servers. The website sends the token only to the Sajda server and stores nothing in your browser. For this request the server opens a temporary session: it is deleted together with the account, or closed at once if you cancel. As usual, the server log records the IP address and the browser name (section 7).

5. “Ask a question”

A question you write in Profile → Questions and answers → Ask a question (3–120 characters) is sent to the Sajda server and kept with the time it was sent.

• The question is sent without an account or token: in the database it is tied to no account and no backup. So we cannot reply to you personally.
• Do not put your name, phone number or other personal details in the question.
• We read the questions and use them to improve the app (for example, the Questions and answers section).
• Questions are not deleted automatically; they are kept until we delete them. They are not tied to an account, so deleting an account does not delete them. To have one of your questions deleted, send us its text and the approximate date.
• Like any other request, it is written to the server log with the IP address and time; the question text is not logged (section 7).

6. Other network requests

• The first time Profile or Questions and answers is opened, the app asks the server for the “Contact us” links (once per app start). This request carries no identifier or token.
• The “Contact us” links open Telegram, Instagram or the website in their own app or in the browser. Those services’ own rules apply there.
• Google Play installs and updates the app. Google’s privacy policy applies to that.

7. Server logs

A web server (Caddy) sits in front of the Sajda server. It writes a log line for every request:

• IP address;
• date and time;
• request method and path (for example, /v1/support/questions), response code, size and duration;
• request headers, including User-Agent. For the app this is a generic value (for example, Dart/3.13 (dart:io)) without the phone model.

The sign-in token (the Authorization header) is hidden in the log. Request bodies (your data, question text, the Google token) are not logged.

The Sajda server program’s own log holds only the request method, path, response code, time and, for backup requests, the random server account number. IP addresses, headers, tokens and your data are not written there. When a server error happens, a technical description of the error is written too.

The database (PostgreSQL) writes its own technical log as well. It mostly holds errors; in rare cases the value that caused an error (for example, an account number) may be written too.

Retention. No fixed retention period is set for logs. They rotate by size: up to about 30 MB per service (web server, server program, database; 3 files of 10 MB), and older lines are deleted automatically. When there are few requests, log lines may stay for several weeks or months.

If installing a new version of the server program fails, the last lines of its log (up to 100) also go into the developer’s deployment log on GitHub. GitHub keeps such logs under its own rules (usually up to 90 days).

We use logs only for security (for example, to stop abuse) and to fix errors. They are not used for advertising or profiling.

To limit too many requests, the IP address is kept briefly (at most one hour) in the server’s memory and is not written to disk.

On the phone, the app logs only system errors (without personal data) and sends them nowhere.

8. Security

• The app connects to the server only over HTTPS (an encrypted connection).
• The backup session token is kept on the phone in storage encrypted with an Android Keystore key, not in the app database. It is not included in phone backups and does not move to another phone, so you sign in again on a new phone. The short-lived access token (15 minutes) is kept only in memory.
• The server keeps only the hash of the long-lived sign-in token, not the token itself. The token changes on every refresh. If an old token is used again later, the server ends that sign-in.
• The database is not open to the internet; it is reached only over the server’s internal network.

No system is completely secure, but we take the measures above to protect your data.

9. Retention

Backups of the server database are made to restore data if the server fails. So deleted data may stay in those backups for up to 15 more days.

10. Deleting your data

• Delete only the server backup: Profile → Manage → Turn off backup → Delete. The account and copy on the server are deleted at once; the data on the phone stays.
• If the app asks you to sign in again, choose exactly the Google account that has backup turned on. With another account, the server backup may not be deleted.
• Delete everything: Profile → Delete all data → Delete. If backup is on, the server account is deleted first, then the data on the phone.
• Uninstalling the app does not delete the server backup. Turn off backup in the app first.

Full steps, including when you no longer have the old phone or want to ask by email without the app: Delete your account and data.

11. Location (qibla)

• The app asks for location permission only when you tap Find my current location in the Qibla tab.
• Only approximate location (ACCESS_COARSE_LOCATION) is requested; precise location is not.
• The location is used on the phone itself to work out the qibla direction and the nearest city. It is saved in the database on the phone so it can be shown next time.
• The location is not sent to the server and is not included in the backup or the export file.
• Without the permission you can pick a city from the list. You can revoke the permission in Android settings at any time.
• Android finds the location. Your phone’s settings and Google’s location services rules may apply to that.
• The phone’s sensors for the compass (magnetometer, accelerometer) are used only on the phone.

12. Reminders

• Reminders are scheduled on the phone itself (local notifications). No push service is used and no messages come from the server.
• On Android 13 and newer, notification permission is requested.
• Turn reminders off in Profile → Reminders or in Android settings.

13. App permissions

• Internet and network state — for backup, “Ask a question” and the contact links; the network type is checked on the phone so that automatic backup runs only over Wi‑Fi.
• Notifications, run at startup, vibration — for reminders; after the phone restarts, reminders are scheduled again.
• Approximate location — only for the qibla (section 11).

The app does not ask for access to the camera, microphone, contacts, SMS or your files. For an import, you pick the file yourself in the system window.

The permission list on Google Play may also show technical permissions added by the app’s libraries (for example, background work, Google Play billing service, biometric hardware). In this version the app makes no purchases and does not use biometric checks.

14. Ads, analytics and selling

• The app has no ads.
• The app has no third-party services (SDKs) for analytics, tracking or crash reporting.
• Sign-in with Google works through Google Play services, and they usually also find the location. Google’s own rules apply to them.
• No advertising ID is used.
• We do not sell or rent your data, and we do not give it to others for advertising.
• This version has no in-app purchases or subscriptions.
• We may disclose data only where the law requires it, on a lawful request from a competent authority.

15. Children

Sajda is not directed at children under 13. We do not knowingly collect data from children. If you know that your child turned on backup, you can delete it in the app (section 10) or write to us and we will help delete it.

16. Your rights

• Access: you can see your main data (calculation, results, daily counts, settings, zikrs) in an export file. The server backup consists of the same data plus the extra records listed in section 3 (time zone, plan history, account and session records).
• Correction: you change data in the app, and the next copy updates the server.
• Deletion: section 10 and the deletion page.
• Withdrawing consent: you turn backup on yourself. Turn off backup deletes the server copy, and the app keeps working on the phone.

If you have a question or an objection, write to us. You may also have the right to complain to the data protection authority in your country.

If you email us, we receive your email address and your message. We use them only to reply.

17. Changes to this policy

If we change this policy, the new text will appear on this page and the date at the top will change. If the app starts sending more data to the server, we will describe it in this policy first.

18. Contact

Developer: Muhammadumar Davlatov
Email: support@qazo-namoz.uz