Privacy Policy | Sadaat
Skip to content

Privacy Policy

Last updated: November 12, 2026

This Privacy Policy explains what information the Sadaat mobile app (Android and iOS) and the website sadaat.pk (together, the “Service”) collect, why we collect it, who we share it with, how long we keep it and the choices you have. We built Sadaat to serve the community, and we treat your information as a trust (amanah).

1. Who we are

The Service is operated by Sadaat (“Sadaat”, “we”, “us”), which is the controller of the personal information described in this policy. You can reach us at support@sadaat.pk.

2. Information we collect

2.1 When you use the app (with or without an account)

  • Device identifier. The app creates an identifier for your device so that it can be recognised without an account. On iOS it is a random identifier stored in your device's Keychain, kept only on that device (it is not synced to your other devices) and kept when the app is reinstalled. On Android it is derived on your device from the identifier Android provides to each app (ANDROID_ID) through a one-way hash, so the original Android value is never sent to us; it stays the same when the app is reinstalled or its data is cleared and changes after a factory reset. If neither is available, the app uses a random identifier that is removed when the app is uninstalled. When you update from an earlier version, the app sends its previous identifier once so that your existing likes move to the new one. We use this identifier to count each like and “I'm joining” once per device, to count event views fairly, to limit spam (for example, how many events can be waiting for review from one device) and to prevent fraud and abuse. It is not an advertising identifier, it is not shared with advertisers and it is not used to track you across other apps or websites.
  • Notification registration. If push notifications are available on your device, the app registers it with us: the Firebase Cloud Messaging token, your device identifier, platform (Android or iOS), app version, app language, the time-zone offset of your device clock (so a notification can arrive at the same local time everywhere), whether notifications are allowed, the city and country the app has determined for you (see “Location” below) and — only if you have given the app location permission — your position rounded to two decimal places (about 1 km). The app sends a new position at most once a day and only after you move more than 5 km. When you are signed in, this registration is linked to your account so that we can send you notifications about your own events, pages and orders. For each announcement we send, we record whether it reached your device and whether you opened it, to count how many people it reached; these records are deleted after 90 days.
  • Location. With your permission, the app reads your device location while you use it. It does not track your location in the background. The location is used on your device to calculate prayer times and adhan reminders, the Qibla direction and the start of the Hijri day at Maghrib. For a quick first estimate the first time the app is opened, whenever location permission is not given, and to find the name of your city (with location permission: once, and again only after you have moved more than about 25 km), the app asks our own location service (geo.sadaat.pk, run on Cloudflare's network) for an approximate city, country and coordinates based on your internet (IP) address. The lookup is answered by Cloudflare from the request itself; your IP address is not passed to any other company and the result is not stored. Location is sent to our servers only (a) with the notification registration described above, rounded to about 1 km, (b) with a search when you look for events or pages near you, and (c) with requests for the Events feed and the home banners: the app sends the city and country it has determined for you and a position rounded to two decimal places (about 1 km), taken from your device location if you have allowed it, otherwise from the IP lookup above. They are used to show the posts nearest to you first and to pick the featured posts and banners of your city and country; and (d) with the usage analytics described below, as long as they are switched on: your precise position (to about 1 metre, with its accuracy) while the app is open, if you have allowed location access, otherwise the approximate city, country and coordinates of the IP lookup. The location in a search or feed request is used only to answer it and is not stored, apart from our web server logs (kept for 14 days). A precise map position is stored only when you choose to pin a location on an event or page you submit.
  • Likes, “I'm joining” and usage counts. When you like a wallpaper, a book, a post or a video, give a Media item a heart, or mark “I'm joining” on an event, we store that mark with your device identifier (and your account, if you are signed in). The app also reports, without your name, when an event card is viewed, an event is opened or shared, or someone taps directions, call or WhatsApp, and when a wallpaper or book is downloaded or a book is opened. We turn these into totals; views and opens are counted at most once per device per day.
  • Usage analytics. To understand how the app is used and where our audience is, the app records, while you use it, which screens you open and for how long, the features you use (for example opening a dua or a surah, completing a tasbeeh, downloading a wallpaper, searching — including the words you search for — bookmarking, sharing, opening a notification), when the app is opened and closed, and with each of these the time and your position (precise, from your device location, if you have allowed location access; otherwise approximate). With them it sends your device identifier, app version, phone model and brand, operating system version, app language, time zone and network type (Wi-Fi or mobile), and, while the app is open, the screen you are on (so that we can see how many people use the app right now and where). The app collects these on your phone and sends them to our own servers in batches about once a minute; they are not shared with any analytics, advertising or other company. Without an account they are linked only to your device identifier. When you sign in, the usage your device recorded before is linked to your account too, so that we see your history as one person. We use them to improve the app and decide what to build, to see which content is used where, and to support you. You can switch them off at any time in Settings → Share usage analytics: the app then stops recording and deletes what it had not sent yet. Turning off location permission stops the position being sent. The usage records are kept for 13 months; after that only totals that do not identify anyone remain. While usage analytics are on, the links you share from the app carry a short code of your installation (for example ?r=k3f9a2bc), so that we can count how many visits, installs and app opens your shares bring; the code does not show the person who opens the link who you are. On Android the app also tells us once, after it is installed, where it was installed from, as Google Play reports it (for example a link shared by another user, our website, a search in Google Play or a campaign).
  • Media feed. When you watch the Media feed, the usage analytics above also record which Media items were shown to you, how long you watched each one and how much of the video you watched, and when you open an item on YouTube, share it, give it a heart or open the page that posted it. We add these up into views and watch time per item; they are kept like the rest of the usage analytics (13 months) and switch off with Share usage analytics. The app remembers on your phone which items you have recently watched (the last 7 days) and sends their numbers with each feed request, so that you see new items first; we do not store that list. A heart you give a Media item is stored like any other like (above): with your device identifier, and with your account if you are signed in, until you take it back or your account is deleted; the number of hearts is public, on the item in the app and on its page on our website, but never who gave them.
  • Technical data. Like any online service, our servers receive your IP address, the address requested, the time and your browser's or app's user agent, and record them in web server logs, kept for 14 days. The address requested can contain what you searched for, the coordinates of a search for events or pages near you and, for Events feed and home banner requests, the city, country and rounded position described under “Location”. The app also tells our servers its language and platform so that content is served correctly. When a request fails with an error, our error monitoring records the request (with passwords, sign-in tokens, store receipts, notification tokens and cookies removed) so that we can fix the problem. We do not add any third-party crash-reporting or analytics SDK to the app (the Google Maps SDK reports its own crashes to Google, as described in section 5); our own usage analytics are described above.

2.2 When you sign in

An account is optional. You sign in with Google (Android and iOS) or Sign in with Apple (iOS); we do not use passwords. The provider sends us, and we store:

  • your name, your email address and your provider's account identifier for you;
  • from Google, the address of your profile picture (we do not copy the image);
  • from Apple, the email you choose to share — this can be an Apple “Hide My Email” relay address — and your name only if you share it the first time you sign in.

We also record when you last signed in, and issue the app a sign-in token (stored on our servers only in hashed form).

2.3 Data synced to your account

While you are signed in, the app stores the following on our servers so that it is kept safe and the same on every device you sign in on. When you are signed out it stays only on your device, as before.

  • Bookmarks of duas, tasbeehs, a'maal, salah guides, Quran ayahs and books (with their titles, so they can be shown offline), and your book favourites.
  • Your likes and “I'm joining” marks (one of each per post per account) and your hearts on Media items. When you sign in, likes made earlier on that device without an account are moved to your account.
  • Tasbeeh counts and progress, your Quran last-read position and the last page you read in each book.
  • Reading and app preferences: font sizes, transliteration and translation languages, app language, your Hijri date adjustment, adhan and prayer-time settings, the jamaat times you entered for your masjid and how prayer times are shown.
  • Khums & Zakat calculator — your saved calculations (history), the calculation you are working on and your chosen currency. These are the amounts you type in (such as savings, gold, crops or livestock); the calculations themselves are done on your device. We do not connect to any bank or financial account.
  • Your event reminders, so they can be set again on a new device if the event is still ahead.

Not synced: your device identifier, location, downloaded book files and temporary caches. When you sign out, the app removes your synced personal data and bookmarks from that device (it keeps only your choice of app language); they remain in your account for your next sign-in.

2.4 Events and pages you submit

If you add an event or create or claim a page (an imambargah, masjid, anjuman or scholar), we store what you enter: title, type, zakir or khateeb, description, date, time, time zone and repetition (for example a series of days), whether it is online, a YouTube link, address, area, city, country, an optional map pin, a poster, logo or cover image, and up to five contact numbers with a name, whether the number uses WhatsApp and whether it may be shown publicly. Contacts you do not mark as public are visible only to you and to our moderation team. We record your account and your device identifier with each event you submit.

If you apply for Verified Member for a page, we keep the application: the member type, the contact phone number you give for our review call and the proof you choose to attach (optional). If you follow a page, we store that you follow it so that we can send you its new posts.

We also keep an in-app notifications inbox for your account (for example “your event was approved”, “your poster is ready” or a reminder), with the read status of each item.

If you contact us through Help & Support in the app, we keep your tickets: the topic, subject, your messages and ours, and the screenshots or documents either side attaches. With each ticket and message the app also sends the details we need to reproduce a problem: the app version and build, the platform and operating system version, the device manufacturer and model, the app language, time zone, screen size and text size, dark mode, whether notifications are on, the city and country the app uses, and the device identifier. Screenshots are stored as WebP images in our cloud storage; they are reached only through the long random link our team and you see in the ticket.

When you delete your account, the app asks (optionally) why you are leaving. We keep the reason you pick and any note you write, and whether you later restored the account, to understand why people leave.

Photos you choose are resized and stored as images in our cloud storage; anything you put in a poster or cover image is public once the event or page is published. The app accesses your camera or photo library only when you choose to add an image or save a wallpaper.

We also store moderation information about your submissions: their status, when they were reviewed and any rejection reason.

2.5 Orders and payments

Event packages and the Verified Member subscription are bought through Google Play or the App Store. The store processes the payment; we never receive your card, bank or billing details. Our server verifies each purchase directly with the store (the Google Play Developer API): the app sends the store's purchase token, and every purchase carries your account's anonymous purchase identifier (a random code, never your name or email) so the store can tell us which account bought it. To apply a purchase to your event or page we keep an order record: the product, the store's order or transaction identifiers, price and currency, purchase, renewal and expiry dates, status (for example paid, refunded or expired) and whether it was a test purchase. Each order is linked to your Sadaat account so that it can be restored on another device.

If you pay manually instead, the order also keeps the name and phone number you gave for the call back, the order's reference code, the payment proof image you upload (for example a screenshot of the transfer), the amount and currency, and notes from our team about the payment.

If you enter a promo code, our server checks it and keeps a redemption record: the code, your account, your device identifier, when you used it, and the purchase, free package or refund it led to. We use it to apply the offer and to enforce each code's limits. It is kept for 24 months, or for as long as the code can still be used (after 24 months without the device identifier), so one account can't use a code more often than allowed.

2.6 When you contact us

If you email us, report content or ask for help, we receive your email address, your message and anything you attach, and we keep the conversation to answer you and to deal with the report.

2.7 The website

sadaat.pk does not use advertising or analytics cookies, and no third-party analytics. It sets only technical cookies needed for the site to work (a session cookie and a security token against forged requests). It counts visits itself: for each page you open, the page sends our server which page it is, the page you came from (for example Google or WhatsApp), campaign tags or a share code in the link, your browser's language, time zone and screen width, how long the page was open and whether you tapped a store button. Your browser keeps a random visit number in its session storage until you close the tab. Our server works out the type of device, operating system and browser from your browser's user agent, and a visitor number from your IP address and user agent mixed with a secret that changes every day, so visits can be counted per day but not followed from one day to the next; the IP address itself is not stored with them. These records are kept for 13 months. When you tap “Get it on Google Play”, the link tells Google Play where your visit came from, so that the app, once installed, can tell us. From Google Search Console we also see which searches showed our pages and how often they were clicked, as totals: Google never tells us who searched. Fonts are loaded from Bunny Fonts (fonts.bunny.net), which receives your IP address to deliver them. Web server logs are kept as described below.

2.8 Data that stays on your device

The app also keeps information only on your phone: your location cache, prayer-time and adhan schedules, downloaded books and wallpapers, cached content for offline reading and notification reminders. We do not receive this, except the items listed in section 2.3 while you are signed in.

3. How we use information and our legal bases

We use information only for the purposes below. If you are in a country whose law requires a legal basis (such as the EU, UK or similar laws), we rely on the basis shown.

Purposes and legal bases
PurposeInformation usedLegal basis
Provide the app and its content, in your languageTechnical data, language, device identifierContract (providing the Service you ask for)
Your account, sign-in and syncing your data across devicesAccount details, synced dataContract
Publish, moderate and manage events and pagesSubmissions, images, contacts, device identifierContract; legitimate interests (keeping the platform safe)
Show local content, such as events and pages near you, and send local notificationsApproximate location: city and country (from your device location or from your IP address)Legitimate interests (showing you what is relevant where you are)
Prayer times, Qibla and Hijri day on your device; events near your exact positionDevice (GPS) location: for local features stored only rounded to ~1 km; precise only with usage analytics (see the usage analytics row)Consent (location permission) — withdraw it at any time
Usage analytics: understand which screens and features are used, how people move through the app, where our audience is and how many use it right now; improve the app and support youUsage records (screens, features, sessions), device identifier, device and app details, precise position (with location permission) or approximate location, account if signed inLegitimate interests (improving the Service); the position from your device location only with your consent (location permission). Switch analytics off in Settings at any time
Website analytics: count visits, see where visitors come from and which pages and shared links bring people to the website and the appPages viewed, referring page, campaign tags and share code in the link, browser language, time zone and screen width, device type, a visitor number that changes every dayLegitimate interests (improving the website and reaching people)
Push notifications and the in-app inbox (announcements, your events and orders, pages you follow, events in your city)Notification token, registration, inbox itemsConsent (notification permission)
Show events with a paid package: featured places in the Events feed and home banners to users in the event’s country, nearest city first; notifications and reminders to users in the event’s cityCity and country the app sends with the request; city from the notification registration; notification tokenLegitimate interests (helping event hosts reach their local community)
Answer your Help & Support tickets and fix the problems you reportTickets, messages, attachments, the app and device details sent with them, accountContract (providing the service); legitimate interests (fixing problems)
Process, verify and restore orders, apply packages and membership, review membership applicationsOrders (including payment proofs), membership applications, accountContract; legal obligation (accounting and tax)
Count likes, joins, views and other interactions; show page owners totalsDevice identifier, interaction eventsLegitimate interests (fair counts and useful statistics)
Prevent spam, fraud and abuse; enforce our rulesDevice identifier, account, IP address, submissionsLegitimate interests
Fix errors and keep the Service secureServer logs, error recordsLegitimate interests
Answer your messages and reportsEmail address, messageLegitimate interests; contract
Comply with law and respond to lawful requestsAny relevant informationLegal obligation

We do not sell your data, use advertising networks or advertising identifiers, or build advertising profiles. Event hosts can buy a package for their events. Such events appear in featured places in the Events feed and, for the highest package, as a banner on the home screen; Featured Plus and Featured Elite events are also sent as a notification and a reminder to app users whose notification registration (described in section 2.1) is in the event’s city. Event hosts never receive the list of people notified. You can turn off notifications at any time in your phone’s settings. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.

4. What other people can see

  • Published events and approved pages are public in the app to everyone: their text, images, place, map pin, the page that posted them and the contact numbers you marked as public. A page shows its number of followers, never who they are.
  • You can make any of your pages private (edit the page in the app). Then only you — and our team — see the page and its posts: they leave the directory, search, feeds, share links and notifications. Its followers stay but see nothing until you make it public again; to post from it you make it public first.
  • Your own name and email are not shown on events you submit; only the page you post as (if any) is shown.
  • Likes and “I'm joining” are shown only as totals, never as a list of people. The number of likes on a post and of hearts on a Media item is public. The number of people joining an event is shown only to the post's owner and to our team, never to other users or on the website.
  • Event hosts and Verified Member pages see statistics for their own events and page — views, opens, likes, joins, shares, follows, direction and call taps — as totals and per-day counts. They never see who viewed, followed or tapped.

5. Service providers and sharing

We do not sell or rent personal information and we do not share it with advertisers or data brokers. We use the following providers to run the Service; each receives only what it needs for its task:

  • Google Cloud — hosts our servers and database.
  • Cloudflare — DNS and network services for our domains, the approximate IP location lookup described above, and Cloudflare R2 storage for images (event posters, page logos and covers) and for payment proofs. Images you add to a public event or page are served from a public address.
  • Google Firebase Cloud Messaging — delivers push notifications to your device using its notification token.
  • Google Sign-In and Sign in with Apple — confirm your identity when you sign in. Apple also tells us when you stop using Sign in with Apple for Sadaat (we then sign you out on every device), when you delete your Apple Account (if Apple was your only way to sign in, your Sadaat account is then deleted exactly as if you had deleted it yourself, with the same 90-day grace period; otherwise only the Apple sign-in is removed) and when you turn email forwarding to your private Apple relay address on or off.
  • Google Play and the Apple App Store — process payments and subscriptions and tell us their status. Google Play also sends our server a notice when a purchase or subscription changes (renewed, cancelled, refunded); we keep these notices for 90 days.
  • Google Maps SDK — shows the map when you pin a location. While the map is shown, the Google Maps SDK sends Google the map requests from your device, along with diagnostic and crash data about the SDK, under Google's privacy policy.
  • YouTube — event videos and the videos of the Media feed (in the app and on the Media pages of our website) are played with YouTube's embedded player, so YouTube (Google) receives information about that playback (for example your IP address and what you watch), and cookies or similar technologies may be used by YouTube. The Media feed uses YouTube API Services: our server reads public video details and counts (title, channel, views, likes, comments) from YouTube; no information about you is sent to YouTube by our server. By watching YouTube videos in the app you also agree to the YouTube Terms of Service, and YouTube's use of information is governed by the Google Privacy Policy.

When you tap Directions, Call, WhatsApp, Share or an email link, the app opens the relevant app (for example Google Maps, your phone dialer, WhatsApp or your email app); what happens there is governed by that app's privacy policy.

We may also disclose information if required by law or a valid legal request, to protect the safety of people (including reporting child sexual abuse material to the authorities — see Child Safety Standards), to enforce our Terms of Use, or as part of a merger or transfer of the Service, in which case this policy continues to apply to your information.

6. How long we keep information

Retention periods
InformationHow long
Account details and synced data (section 2.3)While your account exists. When you delete your account it is deactivated at once and permanently deleted after a 90-day grace period, during which you can restore it by signing in again.
Events, pages and their imagesUntil you delete them, or until your account is permanently deleted. A page with a Verified Member subscription that is still active at that moment is detached from your account instead of deleted and stays published as the imambargah’s or scholar’s page until it asks us to remove it (see Delete Account).
Posts you deleteHidden at once; permanently deleted with their images after 3 days. Until then our team can restore them at your request.
Orders (including call-back details and payment proofs)Kept as required for accounting and tax purposes, for up to 7 years. When your account is deleted, the link to you is removed.
Membership applications (contact phone and optional proof)Kept with the page’s membership history while the page exists. When your account is deleted, the link to you is removed.
In-app notifications inbox90 days
Delivery and opening of each announcement notification90 days
Purchase status notices from Google Play90 days
Promo code redemptions24 months, or for as long as the code can still be used (after 24 months without the device identifier). When your account is permanently deleted, the link to you is removed.
The reason and note you give when deleting your account (optional)12 months from your request. When the account is permanently deleted, the link to you is removed.
Help & Support tickets (messages, attachments, device details)Deleted with their attachments 12 months after the ticket was closed, or when your account is permanently deleted, whichever comes first.
Pages you followUntil you unfollow, or until your account is permanently deleted.
Likes and “I’m joining” marksUntil you remove them or the item is deleted. When your account is deleted they are detached from it and remain only as part of the totals.
Device identifiers used for spam and fraud limitsUp to 12 months (most limits expire within an hour or a day).
Notification registrationWhile the app is in use. Deleted 30 days after Firebase reports the token as no longer valid (for example after you uninstall the app), and deleted after 12 months in which the app was not opened. On account deletion it is unlinked from your account.
Usage analytics (screens, features, sessions, positions, Media items watched and for how long)13 months, then deleted; only totals that do not identify anyone (such as views and watch time per Media item) are kept. Deleted with your account when it is permanently deleted.
Website visit counts (pages, where the visit came from, device type, daily visitor number)13 months, then deleted.
Web server logs14 days
Error recordsUp to 30 days
Database backupsTaken nightly and kept for 14 days, so deleted data disappears from backups within 14 days.
Emails and reports you send usAs long as needed to resolve them, and longer only where a report must be kept for legal reasons.
Aggregate statistics (totals that do not identify anyone)May be kept indefinitely.

7. Your rights and choices

  • Access and portability — you can see most of your data in the app (your events, pages, bookmarks and settings). Email us for a copy of your personal information in a commonly used format.
  • Correction — edit your pages in the app; a post cannot be edited, so delete it and post again, or contact us to correct it or anything else.
  • Deletion — delete individual events, pages, bookmarks and likes in the app, or your whole account (see Delete Account).
  • Withdraw consent — turn off location or notification permission at any time in your phone's settings; the related features stop, the rest of the app keeps working. Turn off usage analytics in the app's Settings (“Share usage analytics”). Turning off notifications also stops notifications about featured events. You can also sign out at any time.
  • Objection and restriction — you can object to processing based on legitimate interests or ask us to restrict it, where the law gives you that right.
  • Complaints — you may complain to your local data protection authority, though we would appreciate the chance to resolve your concern first.

To exercise a right, email support@sadaat.pk from the email address of your account. We may need to confirm it is you, and we respond within 30 days.

8. Children

The content of the app is suitable for all ages and can be read without an account. Accounts and the features that need one (posting events, pages, purchases and syncing) are not directed to children under 13, and we do not knowingly collect personal information from children under 13. If we learn that a child under 13 has created an account, we delete it. If you believe a child has given us personal information, please contact us.

9. International transfers

Sadaat is used around the world. Our servers are hosted by Google Cloud in the Middle East, and our providers (Google, Firebase, Cloudflare, Apple) process data in many countries, including the United States. Where we transfer personal information across borders, we rely on our providers' standard data-protection terms and safeguards, such as standard contractual clauses where required.

10. Security

Communication between the app or website and our servers is encrypted with HTTPS. Sign-in tokens are stored only in hashed form, store receipts are never shown in our responses, and access to our administration tools is limited to authorised team members with role-based permissions. No method of transmission or storage is completely secure, but we work to protect your information and will notify you and the relevant authorities of a breach where the law requires.

11. Changes to this policy

We may update this policy as the Service changes. We will change the “Last updated” date above and, for significant changes, tell you in the app or on this page before they take effect.

12. Contact us

Sadaat
Email: support@sadaat.pk

See also our Terms of Use, Community Guidelines, Payments & Refunds and Child Safety Standards.

سادات کو ساتھ رکھیں

مکمل تجربہ — آف لائن مطالعہ، آڈیو، یاد دہانیاں اور بک مارکس — ایپ میں ہے۔

Get it on Google Playجلد آ رہی ہےDownload on the App Store