Manevi Halka

Privacy Policy

Effective date: May 3, 2026
Last updated: October 17, 2026

Manevi Halka (“the App”, “we”, “us”) values your privacy. This policy explains what information we collect when you use the App, how we use it, and what rights you have.


1. Data Controller

Name: Emirhan Ayaz
Email: privacy@manevihalka.app
App: Manevi Halka


2. Information We Collect

2.1. Information you provide directly

  • Account info: Email address, full name, profile picture (optional)
  • Authentication: If you use Sign in with Apple or Google, the identity token from the respective service
  • Preferences: App language, theme, notification preferences, the circles you hide from your Circles list (only you can see this; it is deleted when you leave the circle) and the circles you remove from My Journey and My Spiritual Memories (only you can see this; your records are not deleted, they are just not counted in these views; kept until you add them back or delete your account)
  • Cross-device backup: The personal worship records and reading preferences you keep while signed in are backed up on our servers so they are not lost when you change devices. This backup includes: your prayer and supererogatory (nafl) tracking records, your prayer tracking preferences, your Qur’an bookmarks, your last reading position in the Qur’an and Jawshan, your reader preferences (secondary translation language, mushaf font style). If you use the same account on more than one device, these records are kept in sync between them; notification and reminder settings are not part of this backup and stay separate on each device. Only you can access this backup; members of your circles, circle admins and other users cannot see it (protected by row-level access rules in the database). The backup is deleted when you delete your account. Your location coordinates are NOT included in this backup and remain only on your device
  • User content: Group descriptions you create, custom dhikr texts, Quran verse notes, book reading notes
  • One-time circle (dedication): The title and dedication text of any one-time circle you create. You are responsible for any third-party information (e.g., a name) you enter in the dedication text
  • Dhikr list sharing: You can share your personal dhikr list with others via a share code/link. When you share, a copy (snapshot) of your list at that moment is stored with the share code; recipients can add the list to their own library. You can revoke a share at any time
  • Report records: When you use the in-app “Report” feature, your report (the reporting account ID, the reported group/member/event, the selected reason, and your optional note) is stored on our servers. These records are used solely to review the report and prevent abuse, are never shared with third parties, and are deleted or anonymized within a reasonable period after the review is completed
  • People you block: When you block someone from the report screen, who you blocked and when are stored on our servers. The person is not notified, and only you can see this record. Their encouragement and gesture notifications no longer reach you, and free texts they write (for example a custom prayer text) are hidden from you; the circle’s shared activity and announcements continue. You can remove a block under Profile → Account & Security → People you’ve blocked

  • Shared practice check-ins: If you join a circle’s shared practice (prayer tracking, memorisation/review, supplication) of your own accord, the day and unit you mark (for example “maghrib, 22 August”) is stored on our servers. By default a task is in “admin only” mode: only that circle’s admin can see this record; other members of the circle and other users cannot. If the admin who created the task chose “Mutual”, everyone who joins the task sees each other’s check-ins by day (the admin too, but only after joining the task); members who have not joined still cannot. The mode that applies is shown on the task screen before you join. A mutual task can later be switched to admin only, not the other way round. Joining is a separate, explicit act: being a member of a circle does NOT enrol you in a shared practice. A newly started task appears in every member’s list, but before your first check-in you read who will see what and confirm; members who have not started are not shown in the tracking at all. You can remove a task you do not want from your list: only which task you removed is stored, and the task no longer appears in your list; if you start the task later, this record is deleted. When you leave the task or leave the circle, these check-ins and records are deleted immediately. When a new shared practice starts in a circle, members receive an in-app notification (one entry per circle a day) and a push notification, which can be turned off in the notification settings. Your personal prayer tracking on the home screen is entirely separate and is never transferred here. The two markings are independent: marking a prayer on your personal card does not mark the circle task, and nobody, including the admin, can see your personal record (see the “Cross-device backup” item above)
  • Gestures between participants in mutual tasks: In a mutual task you can say “May Allah accept it” on another participant’s checked day, or send them “I remembered you in my dua”. For this, the sender, the recipient, the type of gesture and the day concerned are stored on our servers; no free text can be written. Only the sender and the recipient see a gesture. No push notification is sent to the recipient; it appears in the in-app notification list, at most once a day, with the sender’s name
  • Shared counter in “Everyone reads” tasks: When an admin opens a surah as an “everyone reads” task (for example “41 × Yā-Sīn” or “Al-Kahf every Friday”), the day you mark as read and how many times you read it that day are stored on our servers; the circle’s total number of readings and your own total in that task are kept as well. In these tasks nobody, the admin included, can see who read: the circle sees only the total, and only you see your own count. If the circle has at least three members besides you, that day’s number of readings and number of readers are also shown (without names); in a smaller circle these numbers are hidden. When you leave the task or the circle your own records are deleted; the circle’s total is not tied to anyone and does not change
  • Personal targets in memorization tasks: A circle’s admin can give someone who has joined a memorization task a personal memorization target (a surah, for example). For this, the target, who set it and when are stored on our servers; the person receives an in-app notification and a push notification. Only that person and the task’s admin see the target; in mutual tasks the other participants cannot see it either. For the targets that person is working on (a personal target or the task’s own), the admin sees only a coarse state of their Cetele progress (not started, learning, memorized); the places they struggle with, the review schedule and section details stay with the person
  • Memorization voice recordings: In the Hifz Chart you can, if you wish, record yourself reciting what you are memorizing and listen back. Recordings are kept only on your device; they are not sent to our servers and are not shared with anyone. Microphone permission is requested only when you start your first recording. Verses you mark as “got stuck” while listening are saved as part of your Hifz Chart progress (the places you struggle with); the audio itself is not part of that record. If your device’s backup (iCloud or Google) is on, recordings may be included in it; this is your device’s own setting
  • Guest members without the app: A circle’s admin can add someone close to them who does not use the app to the circle as a guest member. For this, only the name the admin enters is stored (no surname needed); the guest’s phone number, email address or any other contact detail is not collected. A guest has no password or way to sign in and does not use the app themselves. A member of the circle (the person looking after the guest) keeps track of the guest’s reading tasks; that member or the admin marks a task as read, and who did so is recorded. The guest’s name and task status are visible to the circle’s members. The member looking after the guest can share a plan of the guest’s upcoming readings as a PDF or an image; this document is created on the device and not uploaded to our servers. To alert that member and the admin when something changes in the circle, only a short summary of the plan (round, number of the section to read and date) is stored. When you add someone close to you as a guest, do so with their knowledge; you are responsible for the information you enter about them

2.2. Automatically collected information

  • Progress data: Quran page progress, completed tasks, hatim count, dhikr counters, Cevshen knot completions, your Cetele (memorization) progress and review schedule
  • Notification token: Device token for push notifications (Apple APNs / Google FCM)
  • Signed-in devices: For each device your account is signed in on, we keep the device model (for example iPhone 15 Pro), the operating system and app version, that device’s notification token and the time of its last activity. This is used only for account security: under Account & Security > My devices you can see where your account is signed in and sign out any device, and when your account is signed in on a new device, your other devices are notified. The name you gave the device, your IP address and your location are not part of this record. It is not kept for guest use (before the account is secured)
  • Location: Only your device’s current location, used to compute prayer times and the qibla direction. Location data is not sent to or stored on our servers — used only on-device for calculation. So that the app can notice you have moved and offer prayer times for your new city, the last known coordinate is stored on your device only; it is deleted when you clear your account data.
  • Prayer time servers: Prayer times are fetched from external servers. With the Diyanet calculation method, only the ID numbers of the country, city and district are sent to the Diyanet prayer time server (ezanvakti.emushaf.net). When Diyanet data cannot be retrieved, or when another calculation method is used, the city’s coordinates, the method and the date are sent to Aladhan; if automatic location is on, these are your device’s location rounded to about 1 km. In countries with more than one time zone (such as the US, Canada or Russia), Aladhan is also asked once for the city’s time zone. To find the city’s name, your device’s operating system looks up the coordinates with Apple’s or Google’s location service. These servers see your IP address; no account information is sent.
  • Subscription info: If you have a Premium subscription: term, plan type, store (App Store / Play Store), subscription status
  • App improvement measurements: To understand where new users get to in the app, a few events that are not linked to your account are sent if analytics is on: the interests you chose in the introduction (category name only, e.g. “Quran” or “Prayer”), that a feature was opened for the first time on this device (e.g. the Quran reader or the dhikr counter; once per feature), the steps of creating a circle and inviting (not whom the invitation went to, only how the share screen was closed), whether you continued at the screen asking for your name (not the name you typed), the outcome of the join-with-code screen, and your answer to the optional one-question survey. These events are sent with a random number unique to this installation; your account ID, email, location and notification token are not included, and location lookup is turned off. The content of your worship (which surah, dua or dhikr) and its amount (pages, counts) are not sent; prayer check-offs are never sent. When you turn analytics off, these events stop too and the random number is deleted from your device.

2.3. Information we do NOT collect

  • Credit card / payment details (handled by Apple/Google — never visible to us)
  • Health data
  • Sensitive personal data (except religion — voluntarily provided through use of the app, given the nature of tracking Islamic practices)

2.4. Joining from the web without an account (manevihalka.app)

On manevihalka.app you can take on a portion or contribute to a shared dhikr without creating an account. There are two ways in: opening a circle’s invitation link when you do not have the app, or visiting the public Shared Reading page (no invitation needed). In both cases we collect only the following:

  • A random identifier generated in your browser. It is kept in your browser’s local storage. The identifier itself is not stored on our servers; only an irreversible digest of it (SHA-256) is kept. It serves one purpose: so that you can see your own portion when you return to the same link
  • Your interface language (to show the page in the right language)
  • The portion you took on (page or chapter range) and whether you marked it finished
  • The count you added to a shared dhikr
  • First-seen and last-seen timestamps
  • A name, if you choose to give one. It is optional and never a condition for anything: taking on a portion, contributing, marking it finished — all of it works without a name. If you leave it blank you appear in the circle as “Guest”. You can remove a name you gave from the same page later
  • To limit abuse: your IP address is never written in raw form; an irreversible digest of it (SHA-256) is kept with a counter, and those records are deleted automatically after 1 hour

Not collected: email, phone number, account, location. A name is taken only if you type one. The page carries no advertising, analytics or tracking tools. While you view or read the page, no request goes to any third party (every file it uses is served from our own servers).

Bot check (Cloudflare Turnstile): Only at the moment you contribute (taking on a portion, marking it complete, adding to a shared dhikr count or entering a name) does the page run Cloudflare’s verification service to tell automated programs apart from real people. Your browser then connects to Cloudflare, which processes your IP address, browser information (such as the User-Agent) and the site on which the check runs. Usually you see nothing; if something looks suspicious, a checkbox may appear. For this purpose Cloudflare may store strictly necessary technical data on its own domain, and it also uses these signals, under its own responsibility, to improve its bot detection. Details: Cloudflare Turnstile privacy addendum.

If you gave no name, the circle’s administrator and members cannot see who you are; they only see that the portion was taken on, or that a contribution was added to the count. If you gave a name, they see that name alongside the portion you took and what you contributed.

Clearing your browser’s site data removes the identifier and severs the link to your portion. If you wish to access or erase this data, simply send us your identifier; without it we have no way to locate the record.

Three things are different on the Shared Reading page: there is no name field and you are never asked for one; the page has no administrator and no members, so nobody sees anything about you, only the shared counter grows; and because the page never ends, your record follows a 90-day retention rule.


3. How We Use Your Information

  • To provide core app functionality (group tracking, task distribution, progress recording)
  • To send reminders (task deadline, streak warning, milestone celebration)
  • To verify Premium subscription status
  • To diagnose errors and performance issues (anonymous technical data)
  • To meet legal obligations
  • To improve user experience (aggregated/anonymous analytics)
  • Inappropriate text check: Texts other people can see (circle name, announcement, custom prayer text, dhikr list name, guest name, profile name) are checked automatically against a word list when they are saved. Text found inappropriate is not saved. The text is not stored separately for this check and is not sent to any third party

We do not use your data for advertising. We do not sell your data to ad networks.


4. Third-Party Services

We use the following third-party services to provide our service:

Service Purpose Data
Supabase (privacy) Database, auth, server functions Account, progress, all app data
Resend (privacy) Account emails (verification, password reset) Email address and email content; sent from EU servers
RevenueCat (privacy) Subscription management User ID, subscription status
Apple Push Notification Service iOS push notifications Device token
Google Firebase Cloud Messaging Android push notifications Device token
Expo (privacy) Push notification infrastructure Device token
Apple Sign In OAuth login Apple ID, email, name
Google Sign In OAuth login Google ID, email, name
Sentry (privacy) Error reporting, crash tracking Anonymous error logs, stack traces, device/OS info
PostHog (privacy) Product analytics (opt-out available) Usage events (no PII); app improvement measurements are not linked to your account (section 2.2). Hosted on EU servers
Quran Foundation (privacy) Recitation audio (reciter list and verse audio files) Audio files download directly to your device from Quran Foundation and quranicaudio.com servers; these servers see your IP address and the requested file. No account information is sent; the reciter list is fetched anonymously through our server
Diyanet prayer time server (ezanvakti.emushaf.net) Prayer times (Diyanet calculation method) ID numbers of the country, city and district; the server sees the IP address. No coordinates or account information are sent
Aladhan (api.aladhan.com) Prayer times when Diyanet data cannot be retrieved and for other calculation methods; the city’s time zone in countries with several time zones The city’s coordinates (the device’s location rounded to about 1 km if automatic location is on), calculation method, date; the server sees the IP address. No account information is sent
Esri (privacy) Satellite view on the Qibla screen (map tiles) The numbers of the map tiles around your location; the server sees your IP address. No account information is sent, and no request is made unless you open the satellite view
Cloudflare Turnstile (privacy) Bot check when contributing on manevihalka.app IP address, browser information (User-Agent, TLS fingerprint), site name; only at the moment you contribute on the website

5. Data Retention

  • Shared practice check-ins: Check-ins are kept for 180 days, then permanently deleted by a daily automated job. If you leave the task or the circle, your check-ins are deleted immediately, without waiting for that period
  • Gestures between participants: Gestures older than 30 days are permanently deleted by a weekly automated job. If you leave the task or the circle, the gestures you sent and received are deleted immediately
  • “Everyone reads” counters: Your day marks follow the same rule as shared practice declarations (180 days). The circle’s total is a single number not tied to anyone; it is kept as long as the task exists and is deleted with it. Your own total in the task is deleted when you leave the task or the circle
  • Personal memorization targets: Deleted immediately when you leave the task or the circle, and when the admin removes the target
  • Signed-in devices: When you sign out of a device or remove it under My devices, its record and notification token are deleted immediately. Records of devices whose session has ended and that have not been seen for 30 days, or that have not been used for 180 days, are deleted by a weekly automated job
  • Active account: Data is retained as long as your account is active
  • Memorization voice recordings: You choose how long they are kept (1 week, 1 month or until you delete them; the default is until you delete them). Expired recordings are deleted automatically on your device. When you sign out or uninstall the app, the recordings on that device are deleted too
  • Account deletion: Your account is first marked as soft-deleted. You can restore your account within 30 days by signing in again. After 30 days, an automated cron job (pg_cron) permanently deletes all your personal data. If you want immediate permanent deletion, contact us by email. Only accounting/subscription records that must legally be retained may be kept (anonymized)
  • Completed one-time circles: When a one-time circle ends, a summary (participant count, work completed) is archived; individual task details are cleared
  • Inactive circles: Circles with no activity for a long time are automatically frozen and later archived (content is kept, active task distribution stops)
  • Empty, abandoned circles: Circles that have been inactive for more than 90 days, have at most one member and contain no reading/task content are permanently deleted by a weekly automated job
  • Unused guest accounts: Guest accounts with no linked identity (email/Google/Apple) that remain unused for 90 days and have no circle memberships, event participation, family plan or subscription are marked for deletion and go through the permanent deletion process above after 30 days
  • Shared dhikr lists: A snapshot created when you share a dhikr list continues to be kept for those who added it to their library, even if you delete your account; however, your name as the sharer is anonymized when your account is deleted
  • Guest members: When a guest is removed from a circle, their name and the shared plan summaries are deleted immediately. The anonymous record of the tasks they read is permanently deleted under the “Unused guest accounts” rule above. If no members other than guests remain in a circle, the guests are removed too
  • Blocks: When you remove a block, the record is deleted immediately. It is also deleted when you or the person you blocked delete the account
  • Removal record: If a circle admin or moderator removes you from a circle or a one-time circle, we record which circle, when and by whom, so that you cannot rejoin the same circle. The record is kept until the admin lifts it, the circle is deleted or your account is deleted. No such record is kept when you leave on your own
  • Abuse-limiting counters: To prevent excessive repetition of reports, shares and similar actions, we count how many times they are done. These counters are kept for at most 7 days. For people who join on the web without an account, daily dhikr and page counts are kept with the guest identity for at most 3 days
  • Notification logs: Auto-deleted after 30 days
  • Audit logs: Retained for 12 months for security and compliance

  • Web participation without an account: A guest record belongs to the circle it was created in. When that circle is deleted after it ends (24 hours after its end date), the guest record, the portion taken and the contributed count are permanently deleted with it. Abuse counters derived from the IP address are deleted after 1 hour, daily dhikr and page counters after at most 3 days. Because the Shared Reading page never ends, records there follow a separate rule: if you make no contribution for 90 days, your guest record, the portion you took and your dhikr contribution are deleted automatically. If a portion is still open in your name at that moment, deletion waits until it closes

6. Your Rights (GDPR / KVKK)

Under GDPR (EU) and KVKK (Turkey), you have these rights:

  • Access: Learn what data we store about you
  • Rectification: Update inaccurate information (via app’s profile screen)
  • Erasure: Delete your account and all data (in-app: Profile → Account & Security → Delete account permanently)
  • Portability: Request a copy of your data. In-app: Profile → Account & Security → Download My Data downloads all your data as a PDF
  • Object: Object to specific processing activities. Analytics opt-out is available anytime: Profile → Account & Security → Anonymous Usage Data (default on)
  • Complaint: File a complaint with your data protection authority

For requests: privacy@manevihalka.app


7. Children

The App is not intended for children under 13. We do not knowingly collect data from users under 13. If you believe your child has provided us data, please contact us — we will delete it immediately.

App Store age rating: 4+ (Islamic content — no aggressive/inappropriate content)


8. Security

  • All data is transmitted over HTTPS/TLS
  • Database access is protected by Row-Level Security (RLS) policies
  • Passwords are hashed with bcrypt (Supabase Auth standard)
  • Auth tokens are short-lived and stored in secure device areas (iOS Keychain / Android Keystore)
  • On Android, your sign-in session and the book files in your Library are excluded from the device backup (Google); on a phone restored from backup you need to sign in again
  • Server access is restricted by 2FA + IP allow-list (developer account)

No system is 100% secure. While we cannot guarantee absolute security, we will notify affected users and authorities within 72 hours of discovering a data breach.


9. Cross-Border Data Transfer

Supabase and our other service providers may host servers in the EU and US. For data transferred outside the European Economic Area, GDPR Article 46 “Standard Contractual Clauses” apply.


10. Cookies / Local Storage

The App is a mobile app and does not use web cookies. However, the following data is stored locally on your device:

  • Session token (for login, in Keychain/Keystore)
  • Preference settings (language, theme, cities you follow for prayer times)
  • Cached data (for offline use)
  • Notification counters
  • Widget data (UserDefaults / SharedPreferences)
  • Recitation files you download (offline listening) and temporary copies of recently played verses. Under the provider’s terms they are kept for at most 6 days and refreshed whenever you are online; you can delete downloads in the app

Deleting your account or uninstalling the app removes this data.

Website (manevihalka.app): The account-free participation page uses no cookies, but stores a single value in your browser’s local storage: the random identifier described above (section 2.4). Nothing is written for analytics or advertising. Clearing your browser’s site data also removes this value. The Cloudflare check that runs when you contribute may store strictly necessary technical data on its own domain (challenges.cloudflare.com) for bot detection (section 2.4).


11. Changes to This Policy

We may update this policy from time to time. For significant changes, we will send an in-app notification. The effective date is shown at the top.


12. Contact

For questions:

Email: privacy@manevihalka.app
Subject: Manevi Halka — Privacy

We respond within 15 days.