Trust & transparency
Privacy Policy
Last updated: September 2026. Destiny Map is built on a simple promise — your spiritual journey is private.
1. The short version
Destiny Map is built on a simple promise: your spiritual journey is private. In the current version, your journal entries, prayers, habits and reflections are stored in your own browser's local storage — nothing you write is uploaded to any server in the default (guest) experience. This policy explains the details, including what happens if we later enable accounts, analytics or advertising.
2. Local-first by design
In the default experience, Destiny Map stores your data — Names studied, habits, prayer records, journal entries, reflections and preferences — in your own browser's local storage under a versioned key. This data does not leave your device. Clearing your browser's site data, or using the 'Reset all data' control in Settings, removes it.
3. Data we do not collect
In the current local-first version we do not collect names, email addresses, or location data, and we do not upload your journal or personal progress anywhere. Your journal is stored on your device and is not readable by us.
4. Cookies and local storage
Destiny Map uses localStorage (a form of browser storage) to persist your app state, and a theme preference may be held in browser storage as well. These are essential to the app's function: without storage, your habits, prayers and journal would reset each visit. We do not use cookies for cross-site tracking in the current version.
5. Optional future accounts (Supabase)
A future release reserves a slot for accounts and cloud sync via Supabase/PostgreSQL. If you connect an account, your data would be stored in that backend under your account, protected by row-level security policies so that only you (and, for content tables, administrators) can access it. This page will be updated with full details before that ships, and account creation will always be optional.
6. Advertising (Google AdSense)
Destiny Map currently serves no advertising and shows no ad placeholders, and it will never display ads that interrupt or mislead you. If we later enable advertising through Google AdSense or a similar network, Google and its partners may use cookies or device identifiers to serve ads based on your visits to this and other websites. Where required, we will clearly disclose this, link to Google's advertising privacy practices, and give you a way to opt out (for example, via Google's Ads Settings). We will never allow advertising that conflicts with the content of this platform — editorial content and religious material will never be influenced by advertisers.
7. Analytics and anonymous telemetry
We do not currently run analytics. The 'anonymous analytics' preference visible in Settings is a placeholder for future, aggregated, opt-in telemetry and sends nothing today. If we enable it later, it will be aggregated, non-personalised, opt-in, and described here before activation.
8. Third-party services
Current dependencies of the platform (such as the Google Fonts self-hosted at build time and the Supabase client library, which is only initialised when credentials exist) do not transmit your personal data. Any future third-party services — analytics, advertising, hosting or sync — will be listed in this policy and in the platform's Settings.
9. Notifications and service workers
If you enable optional reminders (such as gentle habit or prayer-time notifications), they are scheduled on your device by your browser. We do not receive or store notification content. If offline support is enabled through a service worker, it caches application files on your device only.
10. Calculated dates and religious content
Hijri dates and occasions on this platform are calculated estimates using the Umm al-Qura or tabular calendars and are labelled as such. Official lunar months depend on confirmed moon sighting. Where scholars differ — on dates, narrations or rulings — we present the difference transparently and encourage consulting qualified scholars. Religious content here is educational and is not a substitute for scholarship.
11. Children's privacy
We do not knowingly collect personal information from children. The journal is designed for personal reflection; if you share a device with children, we recommend using the journal-lock reminder in Settings and securing the device itself, since local data cannot be encrypted by the app alone. If you believe a child has provided us personal data, contact us and we will delete it.
12. Your rights and controls
In Settings you can edit notifications, privacy toggles and preferences, export your data, and reset all local data with one action. Because your data lives on your device, you control it fully: export or delete it anytime. Where account data is stored later, applicable data-protection laws give you rights of access, correction and erasure, which you can exercise by contacting us.
13. Data retention and deletion
Local data is retained on your device until you clear it, reset it in Settings, or it expires with the storage key version. Future server-side account data would be retained only while needed to provide the service and deleted on request.
14. Changes to this policy
We may update this policy as features evolve. Material changes will be announced on this page and, where possible, in the app. The 'Last updated' date at the top of this page always reflects the latest version.
Questions about privacy? See the jamdevs97@gmail.com, or the docs/database.md schema plan in the project repository.