Privacy Policy
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
- No account, no email, no ads in the app.
- If you allow tracking when your iPhone asks, Meta's SDK tells Meta (Facebook, Instagram) when you install and use the app and whether you start a trial or subscribe, and TikTok's SDK tells TikTok when you install the app and when you start a trial or subscribe, with how you use the app in those sessions only, so we can see which of our ads work. Meta and TikTok may also use it to show you ads. If you say no, the app sends nothing to Meta or TikTok. Your photos, your precise location and your prayer times are never shared with them.
- To know which of our ads bring people to the app, we also use AppsFlyer, an ad measurement service that works for us. In the European Union, Iceland, Liechtenstein, Norway, the United Kingdom and Switzerland, it runs only if you allow tracking. Everywhere else, it runs whether or not you allow tracking: it learns when the app is installed and opened, when you finish the onboarding, when Apple's purchase sheet opens, and whether you start a trial or subscribe. It never receives your photos, your location or your prayer times. Without your permission, it never gets your advertising identifier and passes nothing that identifies you on to Meta or TikTok.
- Anonymous usage analytics (PostHog, hosted in the EU) show us where the app breaks. They never include your photo, what it shows, or your location.
- If you have allowed notifications, the app can tell you when a new version is out. For that, it registers with Google (Firebase Cloud Messaging) under its language, its version and your time zone. To stop them, turn off notifications for Bedless Fajr in your iPhone settings.
- Your location is used to compute your prayer times and to name your city. We do not store it.
- The photo you take to end the alarm is sent for verification. We do not store it on our servers. The verification provider may keep it for up to 30 days in abuse-monitoring logs, then deletes it, and does not train on it.
- Your streak, history and settings live on your phone. Our analytics only see how many mornings you have verified and the length of your streak, on two screens.
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.
- If you say no, or if tracking is turned off in your iPhone settings, the Meta SDK does not start and the app sends nothing to Meta. The app works exactly the same.
- If you allow it, the SDK sends Meta: when the app is installed, opened and closed, and how long each use lasts; your App Store purchase activity (for example starting a trial, subscribing, restoring a purchase or a purchase that fails), with the product, its name, price, currency, subscription period, trial details and the App Store transaction identifiers and dates; your device's advertising identifier; a random identifier the SDK creates on your device; technical details such as the app version, iPhone model, iOS version, language, time zone, screen size and IP address; and, if the SDK itself crashes, a crash report about it.
- Meta collects this information from our app, as it does from other apps and websites that use its tools, and may link it to the information it holds about you. Meta uses it to measure our ads, to target and deliver ads, including the ads it shows you on Facebook and Instagram, and to personalize and improve its own products (see Meta's Privacy Policy, facebook.com/about/privacy). To stop this, turn off tracking (see below).
- We never send Meta your photos, your GPS location or your city, your prayer times, your streak, the days you pause the alarm, your answer about where you heard of the app, or any other event of our own. Like any web service, Meta sees your IP address, from which it can estimate an approximate area.
- The random identifier created by the Meta SDK is also shared with RevenueCat, our subscription provider, along with whether you allowed tracking. RevenueCat uses it to tell Meta, server to server, when your free trial turns into a paid subscription and when your subscription renews, with the product and its price, this identifier and RevenueCat's random identifier for your device (see Subscriptions). RevenueCat sends these events only for people who allowed tracking. The Meta SDK identifier is removed from RevenueCat if you withdraw your permission.
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.
- If you say no, or if tracking is turned off in your iPhone settings, the TikTok SDK does not start and the app sends nothing to TikTok. The app works exactly the same. If you allowed tracking in an earlier version of the app, whose request named only Meta, the TikTok SDK does not start either.
- If you allow it, the TikTok SDK starts only when there is something to report: once, when the app is installed (usually right after you allow tracking), and when you start a free trial or buy a subscription. It does not start otherwise, so TikTok does not see your day-to-day use of the app.
- Each time it starts, and until the app is closed, the SDK sends TikTok: that event (for a trial or a purchase, with the product and, for a purchase, its price and currency); when the app is opened or comes back to the screen and how long it stays open (with a signal every minute while it is open), with a random identifier for each session and when your previous session started; your device's advertising identifier, its identifier for our apps (identifier for vendor) and a random identifier the SDK creates on your device; whether you allowed tracking; technical details such as the app name and version, iPhone model, iOS version, language and region, time zone, screen resolution, memory and processor details, when your device was last restarted (up to three restart times from the past 30 days), and IP address; and technical reports on how the SDK itself is working, which carry the same identifiers.
- TikTok collects this information from our app, as it does from other apps that use its tools, and may link it to the information it holds about you. TikTok uses it to measure our ads and, on its own behalf, to build audiences, to target, deliver and personalize ads, including the ads it shows you on TikTok, for safety and security, and to develop its products (see TikTok's Privacy Policy). To stop this, turn off tracking (see below).
- We never send TikTok your photos, your GPS location or your city, your prayer times, your streak, the days you pause the alarm, your answer about where you heard of the app, or any other event of our own. We have also turned off the SDK features that would record the screens you view, the buttons you tap, images of your screen, or crash reports. Like any web service, TikTok sees your IP address, from which it can estimate an approximate area.
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:
- In the European Union, Iceland, Liechtenstein, Norway, the United Kingdom and Switzerland, AppsFlyer starts only if you allow tracking in a request that names it. We treat you as being in one of these countries if your App Store country, your iPhone's region or its time zone points to one of them, or if we cannot tell your App Store country. If you say no, or if tracking is turned off in your iPhone settings, or if you allowed tracking in an earlier version of the app, whose request did not name AppsFlyer, AppsFlyer does not start and the app sends it nothing. In these countries, your 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 AppsFlyer, and RevenueCat stops sending it your subscription events.
- Everywhere else, AppsFlyer runs whether or not you allow tracking: from the moment you have answered the tracking request during onboarding, then each time you use the app. There is no switch to turn it off in the app; deleting the app stops it.
Where it runs, AppsFlyer receives:
- from the app: the install, and each time the app is opened or comes back to the screen, with the time; two events: when you finish the onboarding (with no detail), and when Apple's purchase sheet opens, with the product, its price and its currency; a random identifier AppsFlyer creates on your device; your device's identifier for our apps (identifier for vendor); technical details such as the app version, iPhone model, iOS version, language and region, battery level, how long the app takes to start (AppsFlyer uses these against ad fraud), and IP address; and, if an Apple Ads ad led to your install, Apple's attribution token (see below). Your device's advertising identifier is sent only if you allow tracking. Because most people open Bedless Fajr when their alarm rings, the times of these openings show roughly when you wake up.
- from RevenueCat, our subscription provider, server to server: your free trial and subscription events (for example a trial started, a trial turned into a paid subscription, a purchase or a renewal), with the product and the net revenue, tied to AppsFlyer's random identifier and to the random identifier RevenueCat uses for your device (see Subscriptions). RevenueCat sends them only if AppsFlyer has run on your iPhone, renewals included, even if you no longer open the app.
- We never send AppsFlyer your photos, your GPS location or your city, your prayer times, your missions or their verdicts, your streak, the days you pause the alarm, your answer to the man or woman question, your answer about where you heard of the app, or any event of our own other than the two above. Like any web service, AppsFlyer sees your IP address, from which it can estimate an approximate area.
What this tells us:
- If you allow tracking, AppsFlyer can use your advertising identifier to ask Meta, TikTok and Apple whether one of their ads led to your install, and may report the installs and subscriptions their ads brought back to them, so we can see which ads work.
- If you don't, AppsFlyer cannot link you to a Meta or TikTok ad, and it passes nothing that identifies you on to them: at most, they get anonymous totals per campaign. For those ads, AppsFlyer itself only gets Apple's anonymous totals (SKAdNetwork and AdAttributionKit), which carry no identifier: wherever you are and whatever your answer, Apple may send AppsFlyer a copy of these reports when an install came from an ad. Where AppsFlyer runs, it sets the value these reports carry, such as whether a trial was started. Where it doesn't (in the countries above, without your permission), the app sets that value itself, on your iPhone, through Apple's SKAdNetwork: only which of four steps you have reached (finishing the onboarding, opening Apple's purchase sheet, starting a trial, subscribing), during your first two days. It leaves your iPhone only inside Apple's anonymous report, never with an identifier, and nothing is sent to AppsFlyer, Meta or TikTok by the app itself.
- Apple Ads is the exception. Apple gives every app a token that says which Apple Ads campaign, ad group and keyword led to an install, without asking for your permission and without identifying you to advertisers (see Usage analytics). AppsFlyer reads this token wherever it runs, so it can tie your install, under its random identifier, to an Apple Ads campaign whatever your answer.
- Our own links work differently. If an install follows one of our own links rather than an ad, for example a link on our website, AppsFlyer may estimate statistically, from technical details and without using any identifier, that this link led to it. Because such links are ours and not another company's ads, AppsFlyer may record this with your install whatever your answer to the tracking request.
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
- Google (Firebase Authentication, Cloud Functions, Firestore, Cloud Logging), United States (us-central1): hosting, anonymous sign-in, the abuse-limit record, technical logs.
- Google (Firebase Crashlytics): crash reports.
- Google (Firebase Cloud Messaging): notifications about new versions (push token, installation identifier and the three lists described above).
- Google (Firebase Hosting): our website telitouch.app, including the information file the app reads.
- OpenAI (API), United States: photo verification.
- Islamic Network (Aladhan API): prayer-time calculation from coordinates.
- Apple: purchases and subscriptions; turning your coordinates into a place name and a country (iOS geocoding); delivering notifications (Apple Push Notification service); telling the app which version is on the App Store (itunes.apple.com).
- RevenueCat (United States): subscription status, from Apple's transaction identifiers and a random device identifier; and, if an Apple Ads campaign led to your install, its campaign, ad group and keyword (Apple AdServices); your answer about where you heard of the app; whether you allowed tracking and, if you did, the identifier created by the Meta SDK, which it uses to tell Meta when your trial turns into a paid subscription and when it renews (see Ad measurement with Meta); if AppsFlyer has run on your iPhone, AppsFlyer's random identifier, so it can send your trial and subscription events to AppsFlyer, together with its own random identifier for your device; it forwards subscription events (trial started, renewal, cancellation, refund) to PostHog; if you ask Apple for a refund, it answers Apple's request for information about the purchase (see Subscriptions).
- PostHog (European Union, Frankfurt): usage analytics, error diagnostics, your answer about where you heard of the app, and the subscription events relayed by RevenueCat, tied to the anonymous identifier.
- AppsFlyer (AppsFlyer Ltd., Israel, and its affiliates, including in the United States; data hosted by Amazon Web Services and Google Cloud in the European Union and the United States): ad measurement, as described in Ad measurement with AppsFlyer: the install and each use of the app, the end of the onboarding and the opening of Apple's purchase sheet (with the product, its price and its currency), its random identifiers, technical details, Apple's Apple Ads token, your advertising identifier if you allow tracking, and the trial and subscription events relayed by RevenueCat with RevenueCat's random identifier for your device.
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
- Photos: not kept on our servers; possibly up to 30 days in OpenAI's abuse-monitoring logs; on your phone, in the app's private storage, until you delete the app.
- Location: not kept by us.
- Abuse-limit record: deleted 30 days after its last update.
- Technical logs, including verification verdicts and their short description: up to 30 days (Google Cloud).
- Crash reports: 90 days (Firebase Crashlytics).
- Registration for notifications about new versions (Firebase Cloud Messaging): until you turn off notifications for Bedless Fajr in your iPhone settings (the registration is then removed the next time you open the app), or until you delete the app. Nothing about it is kept on our servers.
- Subscription status and the details attached to it (Apple Ads campaign, your answer about where you heard of the app, whether you allowed tracking and, if you did, the Meta SDK identifier, and AppsFlyer's identifier if AppsFlyer has run) (RevenueCat): for as long as the subscription exists, then under RevenueCat's own retention policy.
- Data received by AppsFlyer: up to 24 months, under AppsFlyer's privacy policy.
- Usage events and error diagnostics (PostHog): under PostHog's retention policy for our plan.
- Data received by Meta, if you allowed tracking: under Meta's Privacy Policy; we do not control it.
- Data received by TikTok, if you allowed tracking: up to 18 months under TikTok's terms with us, as described in TikTok's Privacy Policy; we do not control it.
- Everything else: on your device, until you delete the app.
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.