← AppFactory Studio

AppFactory Studio

Privacy Policy

Qiblah Path

Effective: 25 September 2026 · 한국어

1. What we collect

We collect and keep no personal data ourselves. There is no sign-up, no login and no account. The only thing the app sends to our server is the anonymous usage events described below, which contain no personal data. The advertising SDKs bundled in the app do collect data in order to serve ads (see section 4).

• Your location never leaves your device. The coordinates, country and time zone of the city you pick or of your device location are stored on your device only and used solely to calculate the Qibla direction and prayer times on the device. No external API is called to calculate prayer times, and no online geocoding is used.
• The app does not pass your location to our server or to the ad SDKs. The InMobi advertising SDK, which we found collects coordinates automatically when an app has location permission, is not included in this app.
• City search runs against an offline city list built into the app (GeoNames, CC BY 4.0); search terms are not sent anywhere.
• Compass sensor readings are used only to draw the direction on screen; they are neither stored nor sent.
• Calculation method, school, minute adjustments, per-prayer reminder settings, theme and the reminder schedule are stored on your device only. Home-screen widgets are drawn from the same on-device data.
• The app is excluded from Android's automatic backup.
• The advertising identifier (GAID) is used by the ad SDKs. Our own app code neither reads nor stores it.
• Anonymous usage events — the app sends a small, fixed set of anonymous events (first launch, first prayer timetable shown, the "Remove ads" screen being shown and where it was opened from (Settings or next to the banner), purchase started, completed, cancelled or failed, restore attempted, an interstitial ad being shown, and whether the app was reopened on day 1 and day 7) to a server we operate. Each event carries only an install identifier the app generates at random, an app tag, the event name and a timestamp; no advertising ID, device identifier, name, coordinates, city or sensor reading is included. We use it solely to see where people drop off, and raw events are deleted within 90 days, leaving only aggregate counts.
• Counters such as Qibla screen opened, direction aligned, location set and reminder enabled are numbers on your device and are never transmitted anywhere.
• There is no third-party analytics or crash-reporting SDK in the app.

2. Where data lives

Data	Purpose	Location
Location (city or device coordinates), country, time zone	Calculating Qibla direction and prayer times	On device — never sent
Calculation method, school, minute and Hijri adjustments, theme	Running the app	On device
Per-prayer reminder settings and reminder schedule	Prayer reminders	On device
Whether "Remove ads" was purchased	Unlocking and restoring the purchase	On device + Google Play
On-device usage counters	In-app decisions (e.g. when to ask for a review)	On device — never sent
Anonymous usage events (random install identifier only)	Seeing where people drop off	Our server — raw events for up to 90 days, then aggregates only

3. App permissions

Permission	Used for
Approximate and precise location	Requested only when you tap "Improve location accuracy" (approximate) or "Use precise location" (precise) on the Location screen. The app takes a single fix while you are using it and then stops; background location is never used. If you decline, you can pick a city from the list.
Notifications (Android 13 and later)	Requested when you turn on a prayer reminder.
Exact alarms	Delivering reminders on time. You turn this on yourself via "Allow exact alarms" in Settings; without it, reminders may arrive somewhat late.
Run at startup	Re-scheduling prayer reminders and widget updates after the device restarts.
Internet, network state	Showing ads, in-app purchase, sending anonymous usage events

The compass (orientation) sensors need no permission.

4. Third-Party Services

Google Play Billing — in-app purchases are processed by Google, and the app only checks whether you own an item. We never see your payment details. Google's handling is covered by the Google Privacy Policy.

Unity LevelPlay & Unity Ads (Unity Technologies / ironSource) — to serve banner and interstitial ads via mediation, it collects and uses the advertising identifier (GAID), IP address, device information (model, OS version, language, etc.) and ad-interaction data, which may be passed to advertising partners during ad bidding. Unity's handling is covered by the Unity Privacy Policy, and you can opt out of personalized ads via the information icon shown on ads.

Ad mediation partners — ads are selected through Unity LevelPlay mediation, which runs a real-time auction among the networks below. Each network's SDK is included in the app and, when it takes part in an auction, may process the advertising identifier (GAID), IP address (used to estimate an approximate region), device information, ad-interaction data and SDK diagnostic/crash information for ad delivery, measurement and fraud prevention. Each partner's handling is covered by its own policy. (Unlike our other apps, this app does not include the InMobi advertising SDK — see section 1.)

Partner	Privacy policy
Unity LevelPlay · Unity Ads · ironSource Ads (Unity Technologies)	unity.com
Liftoff Monetize (Vungle)	liftoff.io
Mintegral	www.mintegral.com
Pangle (ByteDance)	www.pangleglobal.com
AppLovin	www.applovin.com
Meta Audience Network	www.facebook.com
DT Exchange (Digital Turbine)	www.digitalturbine.com
Moloco	www.moloco.com

5. Consent in Europe (GDPR / EEA, UK, Switzerland)

On devices that appear to be in the EEA, the UK or Switzerland, the app shows the InMobi Choice consent dialog (CMP) before anything else. It follows the IAB TCF standard.

• If you do not consent, or you dismiss the dialog, the ad SDKs are not initialised at all — no ad request is sent.
• You can reopen it and withdraw consent any time from Settings → "Ad privacy choices". After withdrawal, any already-loaded ad is discarded rather than shown.
• Outside those regions the dialog does not appear; you can still limit personalised ads by resetting or deleting the advertising ID in your device settings.

6. International transfers

We transfer no personal data ourselves. The anonymous usage events in section 1 are processed on Cloudflare infrastructure (which may be located abroad) and contain no personal data. The advertising partners listed in section 4 may process data on servers abroad (including the United States) while serving ads, under their own policies. In Europe this only happens after the consent described in section 5.

7. Ad formats

• The app shows banner and interstitial ads. There are no rewarded ads.
• Banners appear only on the "Today" and "Monthly" screens. The Qibla (compass) screen never shows any ad.
• Interstitials can appear only when you go from "Monthly" back to "Today", and never within 20 minutes before or after a prayer time. They never appear in the first session after install, and at least 300 seconds (5 minutes) pass between them.
• The one-time in-app purchase "Remove ads" removes all of them. No other feature is locked.

8. Children

This app is for a general audience and is not directed at children under 13.

9. Your rights

• Change or withdraw ad consent — Settings → Ad privacy choices (devices in Europe).
• Reset or delete the advertising ID — device Settings → Privacy → Ads.
• Revoke location or notification access — device Settings → Apps → Qiblah Path → Permissions. You can keep using the app by picking a city.
• Delete everything — removing the app erases all of its on-device data (including your location) and its scheduled reminders.
• Questions — email us at the address below.

10. Contact

Email: leehywo@gmail.com

Privacy contact: AppFactory Studio Privacy  |  leehywo@gmail.com

City data: GeoNames, CC BY 4.0.

11. Change history

Date	Change
2026-09-25	First published (launch preparation)