JhaankiYour day stays yours.
Jhaanki helps you review your own phone activity and keep a private journal. This policy explains what the app reads, where it stays, and what happens when you choose an external action.
Effective 24 September 2026
What Jhaanki can access
Only sources you enable are read. Depending on your choices, Jhaanki can read notification app names, senders, titles and message content; foreground app usage and screen events; calendar accounts, titles and times; media titles and artists; and movement observations such as walking and still periods.
Optional Health Connect access reads approved steps, distance, exercise, sleep and mindfulness records. Jhaanki is not a medical service and does not diagnose or treat conditions.
No location
Jhaanki does not request or collect your location. It has no location permission.
Storage and sharing
Captured records, saved moments, notes and journals are stored in the app's private storage on your device. The Play edition does not upload them to a developer server, classify them remotely on its own, read SMS directly, sell data or share data for advertising. If you agree, Google Analytics counts the install; see Install counts.
Android app backup is disabled. Android, Google Play services and Health Connect have their own privacy practices.
When information leaves the phone
If you deliberately choose Find source, the selected title becomes a browser search query. That search is outside Jhaanki and is handled by the destination you choose.
Reading (experimental) is the one exception, and it is off unless you turn it on. It is hidden until you find it, it does nothing until you supply an API key of your own, and it sends nothing until you press Summarise with AI. You choose a day or a range of up to seven days and the depth of data: notification excerpts from apps you explicitly select, their expanded text and captured message history only if separately enabled, and usage and calendar only if you switch them on. Sharing starts off, new apps are unselected, and restore resets these choices. Preparing gathers that data on your phone; you can read all of it, or export it as a Markdown file you keep, before anything is sent. When you summarise, the data goes to the AI service you chose, under your key — fitted to what that service can take, as the screen states — and that service's privacy terms then apply. Redaction removes obvious codes and identifiers but cannot guarantee removal of every sensitive detail. No location or address-book data is included. A summary you save is kept on your phone with your other saved moments and travels in a records export. Turning the feature off deletes the stored key.
Asking your saved data is part of the Reading and works only once it is on and has your key. When you ask a question on Saved, Jhaanki first sends your question and the names of the tags on what you saved (for example a person's first name, an app, a topic or a month) to your chosen AI service, which picks the ones that could hold the answer. It then sends only the saved items those tags select: moments with your notes, readings you kept and journal entries, redacted as for a reading and limited to about 40,000 characters. You can read what each step sends before it is sent, and remove tags to send less. Raw notifications and usage are not included. An answer you save stays on your phone.
Install counts (optional)
When you accept these terms on first run, an optional box asks whether Jhaanki may count this install. It starts unticked; unless you tick it, nothing is sent. If you tick it, Google Analytics for Firebase receives the events Firebase records on its own: that the app was installed, opened, updated or removed, how long it was in use, the app version, the device model, Android version and language, the store it was installed from, and the country or region Google estimates from your connection. These are tied to a random identifier for this installation, not to you by name.
Nothing Jhaanki reads or you write is sent: no notifications, app names or usage, calendar, health records, saved items or journals. Jhaanki logs no events of its own. The advertising ID is not collected, every advertising consent signal is denied, and the data is not used for advertising or shared for it.
Google processes this under its own terms and keeps it for the retention period set on Jhaanki's Analytics property. Turn it off at any time in Settings → Share install counts; that stops collection and resets the identifier on the phone. Switching off does not delete counts already sent.
This website and its waitlist
This page and the Jhaanki homepage are served by the developer's own server. If you join the waitlist, the email address you enter is stored on that server with the date you joined and which button you used, and nothing else: no IP address is kept or logged with it. It is used only to tell you when Jhaanki is available, and it is not shared or sold. When you join, the developer is sent an email with your address so they know someone signed up; that email passes through the developer's Gmail account, which Google operates under its own terms. To have it removed, reply to that email or contact the developer at the address on the Google Play listing, and it will be deleted.
The homepage loads its fonts from Google Fonts, which receives your browser's request for them under Google's own privacy terms. The site sets no cookies and uses no analytics.
Your choices and deletion
You can skip permission requests, revoke access in Android settings, stop optional recording, and delete records for individual raw-data sources. Revoking a permission stops future access but does not erase earlier records. To remove all captured records, saved items and journals, use Android Settings → Apps → Jhaanki → Storage → Clear storage, or uninstall the app.
There is no developer-hosted account or remote copy of your records to delete. Install counts, if you allowed them, are held by Google Analytics as described above. A reading you chose to send is held under the terms of the AI service you sent it to; Jhaanki cannot delete it there.
Security and limits
Data is protected by Android app-private storage and device security. Jhaanki does not promise additional database encryption or immunity from device compromise. Foreground time is an estimate of app presence, not attention. Media titles do not prove consumption. Calendar plans are not proof of attendance. Missing observations do not prove inactivity.
Contact
For privacy questions, contact the developer using the support email shown on the Jhaanki Google Play listing. The listing and this page should be kept current together.