Skip to content
Truffleinit
TR

Mim Ayet Privacy Policy

Effective date: [YAYIN TARİHİ]

This policy explains which data the Mim Ayet app processes, where that data goes and how you can control it. The data controller is Mustafa Erdoğan (Truffleinit). Legal bases and how to apply are set out separately in the KVKK Notice. If the two language versions differ, the Turkish version prevails.

In short

  • There is no account. You do not sign up, and you are never asked for your name, email or phone number.
  • Your location never leaves your phone. Only the ID of the city you chose is sent to our server.
  • Your settings and your prayer, missed prayer, fasting, khatm and dhikr records stay on your phone.
  • Special days data is stored encrypted on your phone; it is never sent anywhere and is left out of backups.
  • The app has no ads. We do not track you across other apps or websites.
  • Usage analytics runs only if you allow it. Permission is off by default; you can withdraw it in Settings → Privacy.
  • Essential technical records such as error and crash reports are collected without asking for permission; they contain no IP address, location or worship data.

Data controller

The data controller is Mustafa Erdoğan (Truffleinit). Email: [email protected].

No account, one anonymous ID

Mim Ayet has no sign-up or sign-in. On first launch the app creates a random anonymous ID on your phone. This ID is not linked to your name, email or phone number. Your support code is the first 8 characters of this ID.

The same anonymous ID is written to records sent to PostHog, the purchase service (RevenueCat), requests to our server and the local log on your phone. This lets us find the related records when you report a problem with your support code. Because it can be matched through the support code, this ID counts as personal data, not anonymous data, and the protections in this policy apply to it. If you delete and reinstall the app, a new ID is created.

Location

Location permission is optional. If you do not grant it, you pick your province and district from a list.

If you grant it, your location is used only on your phone: to find the nearest city, and to calculate the qibla direction and the distance to nearby mosques. Your location is not sent to our server, the analytics service or support emails, and it is not written to the local log. Only the ID of the selected city goes to the server; prayer times and the mosque list are downloaded with this ID.

When you ask for directions to a mosque, the maps app on your phone opens. From then on, that app's privacy policy applies.

Data that stays on your phone

The following data is kept on your phone and is not sent to our server:

  • Settings, notification and adhan preferences
  • Prayer, missed prayer, fasting, khatm and dhikr records, and badges
  • Your reading position in the Quran
  • Usage counters (how many different days you opened the app, time spent in the app) and the Supporter badge. Your phone's overall screen time is not read.
  • The name you have written in calligraphy
  • The information your widgets show
  • Share cards and wallpapers: created on your phone. On iPhone, wallpapers are saved to Photos. A card is shared only when you send it through the share menu.
  • Camera image: used only on the camera qibla screen, to draw the qibla arrow over the image. The image is not saved or sent anywhere. If you do not grant camera permission, the regular compass opens.

Special days data

The special days setting is sensitive health information. It is therefore kept in a separate, encrypted store on your phone. It is never sent to the analytics service, our server, the local log or support emails.

It is also left out of iCloud and Android backups and the app's backup file. If you delete the app, it is deleted; it does not move to a new phone.

Which data goes to which service

For Mim Ayet to work, data leaves your phone only for these services:

  • PostHog, essential technical records (no permission asked): app errors and crashes; the last 50 steps before an error (only the names of steps, such as which screen you were on, without usage analytics details); once a day, checks showing the app works properly (for example, that notifications are scheduled and widgets are up to date); along with these, the anonymous ID, app version, device type and operating system. These records contain no IP address, location or worship data.
  • PostHog, usage analytics (only if you allow it): session ID, language and events such as which screen you opened and which button you tapped. If you allow it, PostHog is also used to read per-device settings for rolling out features gradually.
  • PostHog, detailed logging (only if you turn it on): you turn it on in Settings → Help with a separate permission so that we can find a problem; it is independent of the analytics permission. While it is on, only detailed log records are sent; it turns itself off after 24 hours.
  • No record sent to PostHog contains location, city name, name or email; the app strips these fields before sending. Nor do records contain the content of your prayer, fasting, khatm or dhikr records. IP address recording is turned off in PostHog.
  • RevenueCat (purchases): anonymous ID and your purchase, trial, renewal and refund history. Payments are taken by the App Store or Google Play; your card details never reach us or RevenueCat. Purchase events also reach our server from RevenueCat and are kept as sales records: product, store, price, time, status and, if you used one, the influencer code.
  • Cloudflare (our server): prayer times, religious days, mosque lists, Quran audio and app settings are downloaded from our server running on Cloudflare. Quran audio also comes through our server; your phone does not connect to the audio source directly. Requests include the selected city ID, the anonymous ID and a request ID. If you enter an influencer code, it is sent to our server to be verified. Server logs are kept to find errors. To deliver requests, your IP address is processed on Cloudflare's network during the connection, but it is not written to our server logs.
  • App Store and Google Play: downloads, purchases and updates go through these stores and are subject to Apple's and Google's privacy policies. When the app crashes or freezes, a report appears in the store consoles. These reports include the app version and device information, but not your anonymous ID.
  • Support email: when you tap Settings → Help → "Report a problem", your email app opens a ready-made email to [email protected]. It contains your support code, app version, device, operating system, city ID, prayer time source, notification and alarm permissions, battery setting, last sync time and active special settings. It reaches us only if you send it. The local log from your phone is attached only with your approval. Emails you send us are stored on Google (Gmail) servers.

Your permission for usage analytics

Usage analytics runs only with your explicit permission. On first launch the app asks for it on a separate screen, apart from this policy; the option is off by default. If you do not allow it, every feature of the app still works; no usage analytics events are sent and no per-device settings are read. Settings that apply to everyone come from our server.

You can withdraw your permission at any time in Settings → Privacy. Once withdrawn, no new usage analytics data is sent.

Error and crash records and the daily health check do not depend on this permission. They are needed for the app to work properly and for errors to be fixed; their legal bases are performance of the contract and our legitimate interest (KVKK art. 5(2)(c) and 5(2)(f)). Detailed logging does not depend on this permission either; you turn it on yourself with its own permission.

The Personal Data Protection Board has decided that analytics and performance cookies that are not strictly necessary require explicit consent obtained in advance. We apply the same approach to usage analytics in the app and run it only with your permission.

You can withdraw location, notification and camera permissions at any time in your phone's settings.

Where data is processed

  • Your phone: settings, tracking records, special days data, location calculations and the local log.
  • Cloudflare: our server, downloaded files, sales records and server logs, on Cloudflare's global network. Sales records are kept in the EU.
  • PostHog: servers in its EU region.
  • RevenueCat: Amazon Web Services (AWS) data centers in the US.
  • Google: emails you send us (Gmail).
  • Apple and Google: store transactions, crash reports and phone backups on their own infrastructure.

International data transfers

The service providers we use to run the app (Cloudflare, PostHog, RevenueCat and Google) may process data abroad, in the EU and the US. Our server runs on Cloudflare's global network; your requests may be served by a data center near you. This text states which data goes to which service provider.

We keep the data that goes abroad to a minimum: your IP address is not written to PostHog records or our server logs, essential technical records contain no location or worship data, and usage analytics is sent only if you allow it. Your location, worship records and special days data are not sent to us or our service providers; your worship records go only into your phone's own backup (iCloud or Google), and special days data is left out of that too.

Transfers of personal data abroad are governed by Article 9 of KVKK. Your downloads and payments in the App Store and Google Play are subject to Apple's and Google's own privacy policies.

Backup and export

Because your data is on your phone and not with us, its backup is your phone's backup:

  • iPhone: iCloud device backup includes app data. If you set up a new phone from this backup, your data comes with it.
  • Android: automatic backup is on (up to 25 MB per app). When you reinstall the app, your data comes back.
  • Settings → "Export / import backup": your settings, tracking records, badges and usage counters are written to a single file. You save it wherever you like through the share menu; it is not sent to us.

Retention and deletion

Special days data is never included in any backup. If backups are off and you delete the app, your tracking records are deleted too and cannot be recovered. Premium can be restored with "Restore purchases".

  • Data on your phone: deleted when you delete the app; what remains in your phone backup or exported file is yours.
  • Local log: the last 500 lines are kept on the phone; older lines are deleted.
  • Server logs: deleted after 3 days (7 days on Cloudflare's paid plan).
  • PostHog records (technical records, usage analytics and detailed logging): at most 12 months.
  • RevenueCat records: kept so that your Premium can be verified and restored, until you ask for deletion or we stop using RevenueCat. Under RevenueCat's data processing addendum, data is kept while the agreement is in force.
  • Sales records: the period required by tax law.
  • Support emails: at most 2 years.
  • KVKK applications: at most 3 years.

Deletion with your support code

Write to [email protected] with your support code to ask for your PostHog and RevenueCat records to be deleted. Sales records that tax law requires us to keep are not deleted until their retention period ends.

Deleting your RevenueCat record does not cancel your subscription. You cancel it in the App Store or Google Play; the Terms of Use explain how.

Your rights under KVKK

Under Article 11 of the Turkish Personal Data Protection Law No. 6698 (KVKK), you have the right to:

  • learn whether your personal data is processed,
  • request information about the processing,
  • learn the purpose of processing and whether data is used accordingly,
  • know the third parties in Türkiye or abroad to whom data is transferred,
  • request correction of incomplete or inaccurate data,
  • request deletion or destruction under the conditions of KVKK Article 7,
  • request that corrections and deletions be notified to third parties who received the data,
  • object to an adverse outcome resulting solely from automated analysis,
  • claim compensation for damage caused by unlawful processing.

How to apply

You can apply regarding your rights, in Turkish, in one of these ways (Communiqué on the Procedures and Principles of Application to the Data Controller, art. 5):

  • by email to [email protected] from an email address you have previously given us and that is in our records
  • by email signed with a secure electronic signature or mobile signature: [email protected]

What to include and response time

Your application must include your name and surname, your Turkish ID number (for foreigners, your nationality and passport number), your address, your email or phone number if any, and your request.

Because there is no account, we can find your records only with your support code, so please include it. Your support code is already filled in the email that opens from Settings → Help → "Report a problem".

Applications are concluded free of charge within 30 days at the latest. If the process involves an additional cost, the fee in the Board's tariff may be charged (KVKK art. 13).

You can also send questions about your rights to [email protected].

Complaint to the Board

If your application is refused, the answer is insufficient or no answer is given in time, you can complain to the Personal Data Protection Board within 30 days of learning the answer, and in any case within 60 days of your application (KVKK art. 14). You must apply to the data controller before complaining.

Children

Mim Ayet is not directed at children; it is made for users aged 13 and over. Because we create no accounts and do not ask for age, we cannot know whether a user is a child.

If you believe a child's data has reached us, write to [email protected] with the support code.

Changes

We may update this policy. The current version is always published on this page with its effective date.