Officers Time has no account, no login and no user database. Almost everything it holds never leaves your phone. This page says plainly which parts do, where they go, and why.
Officers Time is published by Akshay Kotish & Co. (Akshay Lakshay Kotish Private Limited, Kaithal, Haryana, India), and this policy covers the Android and iOS apps of that name. Questions about it go to connect@akshaykotish.com.
You are never asked to register, sign in, or give an email address or phone number. There is no server holding a profile of you. The one identifier the app creates is a random install token for the referral programme (section 7): it is minted on your phone, it is not derived from your name, your device or your advertising identifier, and it goes when the app does.
The dossier you fill in — your name, service, designation, cadre, posting and so on — is stored in the app's own storage on your device. It is used to shape the answers you get, and it is not uploaded anywhere as a profile.
The distinction that matters most:
Nothing on the left is ever transmitted on its own. The dossier appears on the right only because it travels with a question you chose to ask — that is what makes the answer fit your charge instead of being generic.
When you ask a question, the app sends it — along with your dossier as context — to a server we operate, which forwards it to Google's Gemini API and returns the answer. The app holds no model credential of its own; that is why the server exists.
Treat it as you would any external service. Do not put anything into it that you would not put in an email leaving your department — no case that is sub judice, no personal data about a citizen, nothing classified.
The daily dispatch, the recruitment feed and the day's questions are fetched from our database. Those are ordinary reads of published material — anonymous, identical for every reader, and carrying nothing about you. Once fetched they are cached on your phone so the app works without a signal.
The free version shows ads supplied by Google AdMob. To do that, AdMob receives your device's advertising identifier along with technical information such as device type, coarse location derived from your IP address, and which ads you saw. This is governed by Google's own privacy policy, not ours — we never see it.
One advertisement is shown only because you asked for it: the rewarded video under ENROLMENT, which, watched through, turns advertising off for an hour. Closing it early earns nothing, and that ruling is the SDK's, not ours.
Enrolling turns advertising off completely. While an enrolment is active — or a referral month, or a rewarded hour — the app does not load an ad, request one, or contact AdMob at all.
Every install can hand out a six-character code. When a friend enters it in their own copy of the app, advertising goes off for you for thirty days, and every further friend adds a month. To keep that honest a small ledger lives on our server, and this is everything in it:
The friend who uses your code is not told anything about you beyond the code itself, and you are told only a count. The ledger is not readable by the app or by anyone else: only our own service writes to it. Deleting the app discards the token on your phone, which severs the link; to have the ledger entry itself removed, email us your code.
The app uses Google Analytics for Firebase to count what is used: which tabs are opened, which drills are sat and how they went, whether the referral and the enrolment are taken up. This is what tells us which parts of the paper are read. Along with each count Google receives an app-instance identifier it generates, and technical information such as device model, operating system version and country.
The yearly enrolment is sold and charged by the App Store or Google Play. Payment happens entirely inside the store — this app never sees your card, and never receives your name or billing address. All we are told is whether an entitlement is active, and that answer is kept on your device.
Cancel or manage it in your store account, not here. Refunds are the store's to give.
Deadline reminders and Ziddi study alarms are scheduled by your phone, locally. Nothing is sent to a server to make them fire, and they work with no connection. Refusing notification permission costs you the alarms and nothing else.
This is a tool for civil-service aspirants and serving officers. It is not directed at children under 13, and we do not knowingly collect anything from them.
Because the app holds your data on your device rather than on a server, you control it directly:
Published material — dispatches, job notifications, questions — stays on our server because it is the same for everyone and is not about you.
If a release changes what the app sends, this page is updated before that release ships, and the version and date in the folio above change with it.