Hijri First is built local-first. The short version: your calendar lives in your browser, we don't run a server that stores your events, and we don't sell data — there's nothing to sell.
Your events, tasks, settings (location, calendar authority, preferences), and connection tokens are stored locally on your device, in your browser's storage. They are not transmitted to or held on Hijri First servers. Clearing your browser data deletes them; exporting (.ics) is always available in Settings.
If you enter a city for prayer times, the lookup resolves coordinates and timezone; your precise device location is used only if you explicitly grant it, and it is not stored anywhere but your device.
One honest detail about sharing: when you share an event, the link itself encodes the event's title, its Hijri/Gregorian date, and the cities involved — that's how the recipient's view works without a server holding your data. Anyone you give the link to can read those details, so treat share links like the information they carry.
Connecting Google Calendar is optional. When you do, Hijri First requests the minimum scopes needed for two things:
OAuth tokens are stored locally in your browser and sent only to Google's APIs. Google Calendar data obtained through these scopes is used solely to provide the features above, is not stored on our servers, and is never shared with or sold to third parties. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
To understand whether the app is useful and where it needs work, Hijri First records anonymous, aggregate usage events through Aptabase, a privacy-first analytics service. This is the only thing the app reports beyond your device, and it is deliberately minimal.
What is sent: anonymous events like “the app was opened”, “an event was created”, or “the theme was changed” — counts and simple flags only. What is never sent: your event titles, notes, tasks, contacts, prayer or location details, email, or anything you type. There are no cookies, no advertising identifiers, and no profile linking activity to you — we can see that something happened, never what it was or who did it.
The same minimal, anonymous events cover our public surfaces too. On our website (hijrifirst.com) the only thing recorded is an anonymous “open-the-app button was clicked” event — no page-load tracking there; general traffic (page counts, referrers) is measured by Cloudflare Web Analytics, which is cookieless and stores no personal data. On the free public tool pages (for example the date converter or Hijri age calculator) we record only that a tool page was viewed, identified by its public name — never anything you type into the tool, which is computed entirely on your device.
Analytics respects your browser’s Do-Not-Track / Global Privacy Control signal on every surface, and turning it off in Settings → General applies everywhere — the website and tool pages read the same opt-out. Aptabase processes this data in the European Union.
We don't sell or share personal data. We don't show ads. We don't use your calendar content for advertising, profiling, or training models. We don't require an account to use the app.
Disconnect Google at any time in Settings → Import & export, or revoke access from your Google account's security page. Delete all local data by clearing site data in your browser. Export your calendar as .ics whenever you like.
Hijri First is provided as-is during the beta. Hijri dates, prayer times, and provisional month boundaries are computed from the authority and location you choose and may differ from your local community's announcements — always follow your local authority for acts of worship. See the full Terms of Use. We may update these terms and this policy; material changes will be announced in the app.
Questions about privacy or your data: [email protected]
Google Calendar and Google are trademarks of Google LLC. Hijri First is an independent app and is not affiliated with, endorsed by, or sponsored by Google.