1. Information We Process
Naqsh Widgets is developed and operated by Happy advert Limited, incorporated in Hong Kong. The app requires no account, displays no third-party ads, and does not sell personal information.
- Widget content: text, dates, goals, cities, and selected photos or videos are used to create and display widgets, primarily in local storage shared by the app and its widgets. Recitation counts, reading settings, and completion markers also stay locally.
- Location and Health: with permission, location supports weather, prayer times, and direction features. We read daily steps for the last 7 days, including today, and today’s walking/running distance. We do not write to Health or upload health data to our analytics, logging, or attribution servers.
- Device, purchase, and usage information: after the main app opens, analytics, logging, and attribution may process a randomly generated stable business device ID stored in Keychain, IDFV, IP address and network state, device model, OS and app version, language and time zone, membership state, launches and interactions, widget template identifiers/types/sizes/counts, purchased products and transaction identifiers, amounts and currency, purchase and expiry dates, refund or revocation state, and errors. ASA attribution also processes an attribution token and campaign result supplied by Apple. We do not send widget instance identifiers, text you enter, photos or videos, location, Health data, device-status snapshots, or recitation history to those services.
Legal bases: we process local settings and purchase records to provide the app and membership you request; process location, Health, and selected photos under your system permission; and process necessary device and usage information for security, troubleshooting, product improvement, and marketing measurement. Where applicable law requires consent, we rely on consent; you may withdraw it or object as described in Section 6.
2. System Permissions
When needed, location features request When In Use access; you can also select a city manually. The system photo picker reads only items you choose, without requesting access to browse the entire library. Health access requires permission. Device panels use Bluetooth permission only to display radio state, without scanning for or connecting to nearby devices.
Manage permissions in system Settings or Health. Revoking access affects the relevant features only; widgets may show placeholders or the latest cached information.
3. Membership and Purchase Records
Apple App Store handles purchases, renewals, and restoration. We receive and record products, transaction identifiers, amounts and currency, purchase and expiry dates, refund or revocation status, and transaction verification information from Apple. We use these device-linked records to reconcile purchases, identify membership benefits, troubleshoot, and analyze the purchase flow.
We do not receive your bank card number or Apple Account password. Uninstalling does not cancel a subscription. Manage subscriptions and request refunds through Apple’s procedures.
4. Analytics, Attribution, and Third-Party Services
The main app may use the following services. Umeng analytics and advertising attribution start only after ATT authorization.
- Umeng mobile analytics (Umeng Tongxin (Beijing) Technology Co., Ltd.): processes device and app information, launches/sessions, and the product interactions listed in Section 1 for usage analytics and marketing measurement. Our integration is described in How We Use the Umeng SDK.
- Apple AdServices / Apple Search Ads: generates an ASA attribution token, which the operator’s server exchanges with Apple for Apple Ads campaign attribution results.
- Operator attribution server:
naqsh-api.happyadvert.com receives the stable business device ID, app identifier, app/iOS version, and Apple Ads (ASA) attribution token after ATT authorization to measure Apple Ads campaign results. This endpoint does not receive the IDFA, IDFV, or widget-usage summaries. - Alibaba Cloud Simple Log Service (SLS): processes device identifiers, membership state, launch, interaction, error, and purchase events in Singapore for operations monitoring, troubleshooting, purchase reconciliation, and product analytics.
After the initial network request completes and the app is active, the app requests App Tracking Transparency (ATT) authorization. It starts Umeng analytics, Adjust, and ASA attribution only after authorization. Declining does not affect widgets or in-app purchases, and the app does not obtain a usable IDFA without authorization. You can change your choice in device settings. Importantly, the privacy manifest supplied with the currently integrated Umeng SDK declares “Advertising Data” as potentially used for Apple-defined tracking and third-party advertising; the app itself does not display third-party ads.
Apple location, geocoding, WeatherKit, HealthKit, photo-picker, and App Store services support the corresponding features. We require processors to use only necessary information for agreed purposes and apply appropriate protection; we do not sell or provide data to data brokers. Data may be transferred from your country or region to Hong Kong, Singapore, or locations used by a provider’s global infrastructure, with contractual, access-control, encryption-in-transit, and other safeguards required by applicable law.
After you authorize ATT, we read the advertising identifier (IDFA) and send it with the startup event to Alibaba Cloud SLS for identifier association and analytics. This field is omitted when permission is absent or the identifier is unavailable. The app does not keep a separate IDFA cache; uploaded logs are handled under this policy’s retention rules. This field is not sent to the ASA attribution endpoint.
Adjust installation attribution and conversion events
After ATT authorization, we use Adjust (Adjust GmbH) to measure installations, sessions, and marketing conversions. The SDK may process IDFA, IDFV, IP address, device model, OS and app version, language, timestamps, and installation and session information. We additionally send two events: Apple-verified subscription purchases (including trial starts, excluding automatic renewals, restored purchases, and lifetime purchases), and successful widget saves (including creation and edits). Subscription events use a transaction identifier for deduplication. These two events do not include additional price, currency, receipts, signed transactions, widget instance identifiers, entered text, or photos. We do not send Health data, location, or recitation records to Adjust.
Without ATT authorization, we do not initialize Adjust or report these events. After authorization is withdrawn, we disable Adjust when the app next enters the foreground; it may resume after authorization is granted again. Declining does not affect subscriptions or widgets. Adjust’s AdServices/ASA token collection is disabled in this app; existing ASA reporting remains with the operator’s server. See the Adjust Privacy Policy. Previously reported data remains subject to the retention and deletion rules below.
The app requests ATT authorization after the initial network request completes and the app is active, without waiting for the home screen. Declining does not block onboarding, purchases, or widgets. Without authorization, subscription and widget-save events are not sent to Adjust or cached for later reporting.
5. Storage, Security, and Deletion
Widget settings, photos, health snapshots, and recitation state are primarily stored on your device. There is no account-based cloud sync. Photo cropping and vehicle-subject processing run locally. Deleting widgets or assets in the app does not delete the originals in Photos.
Server records are retained as needed for the purposes stated in this policy and applicable legal obligations. When the retention period ends or the information is no longer needed, we will delete or anonymize it, unless continued retention is required by law. Local caches are updated through refresh or cleanup, and pending logs are cleared after successful transmission. We use system permissions, device storage protections, and encrypted transmission to protect data.
Uninstalling can clear local app data but does not delete server records; a device identifier may remain in Keychain. Device backups depend on your system settings. Contact us below to request access to or deletion of server records, subject to legally required retention.
6. Your Rights and Children
You can manage system permissions, edit or delete local widget content, and, under applicable law, ask to be informed of the basis and purpose of processing, access or obtain a copy, correct, delete, restrict processing, withdraw consent, or object. Withdrawal does not affect prior lawful processing. The app currently has no separate switch to disable Umeng analytics or reset the stable business device ID; contact us using the address below. We will request only information necessary to verify a request and will not ask for Health details, precise location, or unrelated identity documents. You may also complain to the competent data-protection authority where you live.
The app is not directed specifically at children. Minors should use it with guardian guidance. Contact us if you believe a minor’s information has been collected inappropriately.
7. Policy Updates
We update this policy and its date when features or data practices change. We provide an in-app or other reasonable notice of material changes and obtain renewed consent where required.