BEDLESS FAJR

Privacy Policy

Effective date: November 1, 2026

Bedless Fajr is an alarm clock for the Fajr prayer, published by Zakariya Telitel (France), operating as Telitouch. This policy explains what happens to your data. It is short, because the app handles very little of it, and it is precise, because that little matters.

The Short Version

1. Who Is Responsible

Zakariya Telitel, individual developer, France. Contact: support@telitouch.app

2. What Is Processed, and Why

Location (when in use)

Fajr moves every day and depends on where you are. When you allow location access, the app reads your coordinates about once a day and sends them, with the date and your chosen calculation method, to a prayer-time service: the Aladhan API (Islamic Network, api.aladhan.com). No identifier is sent with them. To show the name of your city and pick the usual calculation angle for your country, the app also asks Apple's geocoding service, built into iOS, to turn your coordinates into a place name and a country code. Your coordinates themselves are not kept: the app keeps only the place name, the time zone and the prayer times it computed, on your device, and iOS remembers your location permission. We do not store your coordinates on our servers, and we never track your movements. Aladhan does not publish a privacy policy; like any web service, it may log the requests it receives, including your IP address. If you prefer, deny location access and choose your city from a list: only that city's fixed coordinates are then used.

Photo verification

To end the alarm you photograph a target object. The photo is sent over an encrypted connection to our server function (hosted on Google Cloud / Firebase, United States), which forwards it to an AI vision service, the OpenAI API, with a single question: does this photo show the target? The verdict comes back; the photo does not stay on our servers, and we build no gallery. On your phone, the photo stays in the app's private storage (never in your camera roll) until you delete the app. According to OpenAI's API data policy, data sent to the API is not used to train its models, and inputs may be retained for up to 30 days in abuse-monitoring logs before deletion. We do not ask OpenAI to store the request beyond that.

Anonymous identifier

The app signs in anonymously (Firebase Authentication): a random identifier is created on your device, with no name, email or Apple ID attached. Our server uses it to limit abuse: each device may request a bounded number of photo verifications per day. For that, one record per identifier is kept on our server, containing the current date and a count. It is deleted automatically 30 days after its last update. Firebase also keeps the anonymous account itself (identifier, creation and last sign-in dates) until it is deleted. Deleting the app deletes the identifier from your device; nothing on our side can link it back to you.

Technical logs

Like any hosted service, our server function produces technical logs, kept by Google Cloud for up to 30 days: IP address, time and response code, and for each photo verification the anonymous identifier described above, the app language, the target that was asked, the verdict and the short description the verification returns (for example "unrolled prayer mat"). We read them only to catch wrong verdicts and improve the check. They contain no photo and no location.

Crash reports

When the app crashes or hits an error, Firebase Crashlytics (Google) receives a crash report: the technical trace of the error, the app version, iPhone model and iOS version, and a random installation identifier. It contains no photo and no location. Google keeps these reports for 90 days.

Notifications about new versions

From version 1.2.6, the app can send you a notification when a new version of Bedless Fajr is out, or when a bug stops the alarm from working and you need to update. It does this only if you have allowed notifications for Bedless Fajr in iOS; it never asks for that permission for this purpose. It is on whenever notifications are allowed; there is no separate switch in the app. To turn it off, turn off notifications for Bedless Fajr in your iPhone settings (Notifications, then Bedless Fajr): the next time you open the app, it removes its registration with Google. This also turns off the app's other notifications: the evening reminder of tomorrow's Fajr time, the end-of-trial reminder if you asked for one, and the alarm's backup notification if Alarms are not allowed for Bedless Fajr. These notifications never contain ads, prices or offers. To send them, we use Firebase Cloud Messaging (Google). We hold no list of devices: the app itself registers with Google on three lists, by the app's language, its version and your time zone, so that each announcement reaches only the versions concerned, in the right language and, as far as possible, during the day where you are. To register, the app sends Google: a push token, a random installation identifier, these three lists, your iPhone model and iOS version, your phone's language and time zone, the versions of the app and of Google's software, and, like any web service, your IP address. Apple's push notification service (APNs) then delivers the notification to your iPhone. While the app is registered, Google's Firebase software also attaches the push token to each photo verification request (see Photo verification); our server function receives it but neither reads nor keeps it. To show you that a new version is available, the app also asks Apple's public App Store lookup service (itunes.apple.com) which version is on sale, sending only the app's identifier and your phone's region. It also reads a short information file on our own website (telitouch.app/annonce.json, hosted by Google Firebase Hosting), used only to display a notice such as an outage. Neither request carries any identifier; like any web server, both see your IP address.

Usage analytics

To see where the app works and where it breaks, the app and our server function send usage events to PostHog, an analytics service hosted in the European Union (Frankfurt, eu.posthog.com): which screens were viewed, whether a plan was chosen or a purchase started, cancelled or failed, whether a mission was started and how its verification ended (with the model used, its duration and its size), and error diagnostics when something crashes or fails. During onboarding we also ask where you heard about Bedless Fajr; your answer is recorded in PostHog and with RevenueCat, so we can see which channels lead to a subscription. Two screens also send the progress kept on your phone: when the app asks you to rate it, how many mornings you have verified; and when it makes you an offer after you have cancelled your free trial, your current streak and your number of verified days. Each event carries the anonymous identifier described above and technical details such as the app version, iPhone model, iOS version, language and time zone. It never contains your photo, the description the verification makes of it, your location or your city. Like any web service, PostHog receives the IP address of each request; we have turned off locating you from it. We use these events only to improve Bedless Fajr. They are never sent to Meta or any other advertiser, and we never sell them.

We use Apple's AdServices framework to learn whether an install came from an Apple Ads campaign (campaign, ad group, keyword). This doesn't identify you and isn't used to track you across apps or websites. RevenueCat (see Subscriptions) retrieves this information from Apple and keeps it with the random identifier of your device. Where AppsFlyer runs, it reads the same information (see Ad measurement with AppsFlyer).

RevenueCat, our subscription provider, also sends our subscription events (trial started, renewal, cancellation, refund) to PostHog, tied to the same anonymous identifier, so we can see which steps lead to a subscription.

Ad measurement with Meta

We advertise Bedless Fajr on Instagram and Facebook. To know which ads bring people to the app, from version 1.2.3 the app includes Meta's software development kit (the Facebook SDK, from Meta Platforms Ireland Ltd). During onboarding, your iPhone asks whether you allow Bedless Fajr to track your activity (App Tracking Transparency). This only happens if you allow tracking.

Because Bedless Fajr is an app for the Fajr prayer, the simple fact that you use it may reveal your religion. This is why the Meta SDK only starts if you explicitly allow tracking, and why this consent is the legal basis for it. You can withdraw it at any time, in your iPhone Settings (Privacy & Security, then Tracking). From the next time the app starts, nothing more is sent to Meta.

Ad measurement with TikTok

We also advertise Bedless Fajr on TikTok. From version 1.2.4, the app includes TikTok's software development kit (the TikTok Business SDK), under the same rule as Meta's: it starts only if you allow tracking when your iPhone asks, in a request that names TikTok.

As with Meta, the simple fact that you use Bedless Fajr may reveal your religion. This is why the TikTok SDK only starts if you explicitly allow tracking, and why this consent is the legal basis for it. You can withdraw it at any time in your iPhone Settings (Privacy & Security, then Tracking). From the next time the app starts, nothing more is sent to TikTok.

Ad measurement with AppsFlyer

From version 1.2.6, the app also includes the software development kit of AppsFlyer, an ad measurement service that works for us (it is one of our providers, see section 4). It tells us which ad, on Meta, TikTok or Apple Ads, led to an install, a free trial or a subscription. From version 1.2.6, the tracking request your iPhone shows during onboarding names AppsFlyer. When AppsFlyer runs depends on where you are:

Where it runs, AppsFlyer receives:

What this tells us:

AppsFlyer processes this data on our behalf. Under its own privacy policy, it may also use it to detect ad fraud and, in anonymous and aggregated form, for statistics. It does not sell it.

Subscriptions

Purchases are handled entirely by Apple through your Apple Account. We never see your payment details. To know whether your subscription is active, the app uses RevenueCat, a subscription-management service: it receives from Apple the transaction identifiers of your purchase, together with a random identifier for your device, and returns the subscription status. No name, email or payment detail is involved. Manage or cancel your subscription at any time in your Apple Account settings.

If you ask Apple for a refund, Apple may ask us about your purchase before deciding. With your agreement, given when you subscribe (see the Terms of Use), RevenueCat answers on our behalf: whether the subscription was delivered, whether a free trial or a description of how the app works was available before purchase, and, where we state one, our preference on the outcome. It sends no usage data, no photo and no location. Apple makes the decision. You can withdraw this agreement at any time by writing to support@telitouch.app: we then stop answering Apple's requests about your purchases. To see or delete the data Apple itself holds about you, go to privacy.apple.com.

On your device only

Your record, your daily history, your alarm days and your alarm sound never leave your phone. Your streak and your number of verified mornings are kept on your phone too; only their current values are sent to PostHog, on the two screens described in Usage analytics. The photos you took for your missions stay in the app's private storage after their check, never in your camera roll. Your chosen city and calculation convention are kept on your phone and sent, without any identifier, only to compute your prayer times (see Location). Deleting the app deletes all of this.

3. What We Do Not Do

We do not sell data. If you allow tracking, the data described above goes to Meta and TikTok for ad measurement and advertising; some laws, such as California's, call this "sharing". We show no ads in the app. The only advertising SDKs in the app are Meta's and TikTok's, and they start only if you allow tracking (see Ad measurement with Meta and Ad measurement with TikTok). The app also includes AppsFlyer, an ad measurement service that works for us: outside the countries listed in Ad measurement with AppsFlyer, it runs whether or not you allow tracking. If you don't allow tracking, AppsFlyer never receives your advertising identifier and passes nothing that identifies you on to Meta or TikTok, and we do not track you across apps or websites. Our other measurement tools are PostHog and Apple's AdServices, both described above and used for this app alone.

4. Who Processes Data for Us, and Where

Transfers outside the European Union rely on the safeguards these providers offer, including standard contractual clauses; see their respective policies.

Meta is not one of our providers. If you allow tracking, Meta Platforms Ireland Limited (Merrion Road, Dublin 4, D04 X2K5, Ireland) and we are joint controllers, under Article 26 GDPR, for collecting this data in the app through Meta's SDK and transmitting it to Meta. Under the Controller Addendum we have accepted with Meta (facebook.com/legal/controller_addendum), we are responsible for giving you this information, and Meta Ireland is responsible for your rights under Articles 15 to 20 GDPR over the data it stores once received. Meta alone decides what happens to the data after it receives it, as an independent controller. Meta's contact details, the legal basis it relies on and how to exercise your rights with Meta are in Meta's Privacy Policy: facebook.com/about/privacy.

TikTok is not one of our providers either. If you allow tracking, TikTok Technology Limited (Ireland), TikTok Information Technologies UK Limited and we are joint controllers, under Article 26 GDPR, for collecting this data in the app through TikTok's SDK, transmitting it to TikTok, and the measurement reports TikTok gives us. Under the TikTok Business Products (Data) Terms we have accepted, we are responsible for giving you this information, and TikTok is responsible for your rights under Articles 15 to 20 GDPR over the data it receives. TikTok alone decides what happens to the data after it receives it, as an independent controller. TikTok's contact details, the legal basis it relies on and how to exercise your rights with TikTok are in TikTok's Privacy Policy: tiktok.com/legal/page/eea/privacy-policy/en (European Economic Area, United Kingdom and Switzerland) and tiktok.com/legal/page/us/privacy-policy/en (United States).

Every provider listed above, and Meta and TikTok for the data they receive through their SDKs, is bound by its terms with us to give that data the same or equal protection as this policy describes and as Apple's App Review Guidelines require.

5. How Long Data Is Kept

6. Your Rights

Under the GDPR you may request access to, correction or deletion of personal data we hold, ask us to restrict or stop processing it, receive it in a portable format, withdraw your consent at any time (this does not affect what was done before), and complain to your supervisory authority (in France, the CNIL). The data we control is tied only to random identifiers, so deleting the app breaks the link to you.

Deleting the app does not delete what Meta received if you allowed tracking. If you have a Facebook or Instagram account, you can review a summary of it, disconnect it from your account and turn off future activity in your Meta settings (Accounts Center or Meta Account, then Your information and permissions, then Your activity off Meta technologies). Disconnecting does not delete the data, and Meta does not show everything it receives there. To ask Meta for access, deletion or anything else, use the options in its Privacy Policy. If you write to us about data Meta received, we forward your request to Meta within 7 days.

Deleting the app does not delete what TikTok received if you allowed tracking either. If you have a TikTok account, you can see and clear your activity from other apps and turn it off in TikTok's settings (Ads, then Your off-TikTok activity). To ask TikTok for access, deletion or anything else, use tiktok.com/legal/report/privacy. If you write to us about data TikTok received, we forward your request to TikTok within 7 days.

Deleting the app stops AppsFlyer, but does not delete what it already received; it keeps it for the period given in section 5. AppsFlyer works for us: to exercise your rights over that data, write to us, and we pass your request on to AppsFlyer within 7 days.

For anything else, write to support@telitouch.app; we answer within 30 days.

7. Children

Bedless Fajr is not directed at children under 13, and we knowingly process no personal data from them.

8. Changes

If a new feature changes what is processed (for example accounts), this policy and its effective date are updated before the feature ships.

9. Contact

support@telitouch.app