Home (Türkçe)

Mihriva

Privacy policy

Mihriva works without an account. This policy explains the current app and website, your choices, and services that have not been activated.

Scope and contact

This policy covers the Mihriva mobile app and website. Using the app does not require your name, email, phone number or password. Voluntarily emailing support is a separate interaction.

Mihriva is operated by Görkem Çiçekdağ. Contact info@mihriva.com with privacy questions or data requests.

Location: optional and on-device

You can manually select a supported locality for prayer times without GPS permission. Qibla and the optional sunlight calculation request foreground location when you start the relevant feature.

Precise coordinates for these features are used for on-device calculations, not included in Mihriva API requests or used to build a location history on Mihriva servers. The current app does not track GPS in the background. Revoke location permission in device settings; location-dependent features may then be unavailable.

Locality and network requests

Your selected locality identifier and requested date range are sent to the Mihriva API to retrieve prayer schedules. Daily content is also fetched online. The selected locality replaces precise GPS coordinates in these requests, but can still indicate your approximate area.

The web and API infrastructure is hosted with Hetzner in Germany. Network requests expose connection information such as IP address and request time to the serving infrastructure. Access-log scope and retention periods have not yet been confirmed. No account does not mean no data processing or that all data stays on your device.

Device storage and notifications

The selected locality, cached schedules and content, appearance/language preferences, notification settings and deduplication plans are stored on your device. They support displaying saved data and scheduling local notifications according to your choices.

Notifications are scheduled locally through your operating system. Permission is optional; change preferences in the app and permission in device settings. Lock-screen previews may reveal content to others; limit previews in device settings. This flow does not require a cloud account or remote-push registration.

For widget/live activity views on supported iOS versions, a schedule summary may be shared through on-device app-group storage. This summary contains no precise GPS coordinates. Consider that a home or lock screen, including any locality label you display, may be visible to others.

Advertising: test-only for now

The app includes Google Mobile Ads and Google User Messaging Platform (UMP) SDKs. Ad requests are available only in explicitly enabled developer test builds, using sample ads in Settings. Live ads are disabled in the current version. The linked SDKs mean that zero network traffic or zero data processing cannot be guaranteed.

Google describes SDK processing that may include IP address, approximate location, device identifiers, interactions and diagnostics for ad delivery, measurement and fraud prevention. Test ads also use a third-party service. Mihriva does not add precise coordinates or religious content to ad requests; a non-personalized request does not mean no processing.

If live ads are enabled later, this policy and store disclosures must be updated, with required notices and privacy choices. In the active test flow, the advertising privacy options in Settings let you change choices when required.

Purchases: not active

Core features are free. Paid checkout for annual and lifetime ad-free options is not enabled in the public release. Draft store products are not available offers; this statement does not imply that technical integration is complete or that purchase/restore acceptance tests have passed.

When enabled, payment is handled through Apple App Store or Google Play with store verification, using prices and conditions from live store offers. Transaction data used for verification and restore, recipients and retention must be disclosed before activation. This website takes no payment and does not request card details.

Website and support email

These web pages include no account, signup form, analytics tag, advertising code or application-set cookies. Pages and images are served from this site. Hosting infrastructure may process connection and access logs; its practices require separate confirmation.

If you email us, your email address, message and attachments are processed to respond to your request. Email providers participate in delivery and storage. Do not send passwords, precise location, card details or purchase tokens; redact personal information in screenshots. External services have their own policies when you follow their links.

Retention, deletion and choices

Local caches and preferences remain in app storage, without a cloud user profile sync. Android app-storage clearing or deleting the iOS app can remove local data. Offloading an iOS app may keep its data. Operating-system backups and restores have separate settings.

A retention and deletion schedule for support correspondence and server logs has not yet been established. Automatic deletion after a particular period is therefore not guaranteed. This policy will be updated when retention periods are defined. Email info@mihriva.com for information or deletion requests about existing records. Third parties also apply their own retention practices.

Send information, correction or deletion requests to info@mihriva.com. There is no Mihriva account-deletion screen because no account is created. Describe the request and any relevant support correspondence, without sending sensitive documents or secrets. This contact route does not replace or limit your rights under applicable law.

Changes

The date on this page records the latest review of the described behavior. New data uses and activated third-party services require updates, with additional in-app notices and permission where needed.