Legal
Cookie notice
This page summarises the cookies and storage used in the web experience, and the equivalent local storage mechanisms in the mobile app.
- Last updated
- 3 September 2026
- Operator
- Little Lion Labs
- Contact
- [email protected]
This English version is provided for convenience. If there is any difference, the Turkish version prevails.
Our approach to cookies
We do not use advertising or third-party marketing cookies. Storage is used mainly for sessions, preferences and offline use.
The web app uses cookies for session continuity and secure authentication. It also uses browser storage for fast start-up, keeping your preferences and the offline experience. In the mobile app, the equivalent functions are provided by SecureStore, MMKV and a local cache.
Web cookies
auth_token
HttpOnly session cookie
Carries your authorisation to access the server. The cookie itself can be long-lived; the access token inside it is refreshed more often.
refresh_token
HttpOnly refresh cookie
Supports refreshing the access token and reduces the need to sign in again.
pt_session
HttpOnly session continuity cookie
Makes it easier to restore the session, especially in PWA and iOS return scenarios.
auth_token_client
Client-side helper cookie
Helps the web client detect that a session exists; it grants no security authorisation on its own.
_ga, _ga_<ID>
Analytics cookie (Google Analytics, only with consent)
Distinguishes visitors for anonymous usage statistics. It is set only if you accept analytics consent and is not used for advertising or targeting.
Local storage and offline records
localStorage
Account mirrors: auth:token, auth:user
Notification and security preferences: pref.notify.*, pref.security.loginAlerts
Profile and invitation preferences: pref.visibility.profile, pref.invites.who, pref.notify.cadence
Prayer time and city cache: the selected city and prayer time records
Quran bookmarks, offline queues, PWA installation and interface preferences
Consent keys: consent.analytics and consent.special
Other local storage
sessionStorage may be used to hold a temporary nonce/value, especially in some sign-in flows.
IndexedDB may be used for Quran content and offline reading data.
In the mobile app, similar functions are provided by SecureStore, MMKV and local cache layers instead of cookies.
How can you manage it?
You can clear or block cookies in your browser settings; you may then need to sign in again.
You can change notification, visibility and security preferences on the Settings screen in the app.
If you manually clear offline records or the local cache, some personalisation preferences may be reset.
Google Analytics runs only if you choose "Accept" in the notice on your first visit or turn on analytics consent in Settings; you can withdraw consent in the same place. No marketing or ad-targeting cookies are used.