Frequently asked questions

No. ekhasra is a third-party tool that automates the same form-filling you would otherwise do by hand on rccms.up.gov.in. It uses your normal eKhasra login and posts the same data to the same official API. No data is altered or sent elsewhere.

So your credit balance and history follow you across phones. If you only use the app on one phone forever, the Google sign-in is overhead — but for power users who hop between an office desktop session and a field phone, it's what makes credit-sync possible. We use only the openid + email + profile OAuth scopes.

You type your password inside an embedded browser that goes directly to rccms.up.gov.in, and it is never sent to our servers. If you explicitly enable “Remember my password”, the app reads it from that login form and stores it only on your phone in Android Keystore-backed secure storage. After sign-in, the app reads the portal session token needed to make API calls on your behalf.

Yes — every new account gets 10 free gatas on first sign-in. That's enough to run a real survey end-to-end (lock a few gatas, watch them sync) before you pay anything. After that, top up via UPI in packs starting at ₹100; bigger packs cost less per gata, and credits never expire.

Per-gata charging means the survey pauses gracefully — the gata you tried to lock returns "insufficient credits" and stays unlocked, and you can top up + retry that specific gata. Already-locked gatas stay locked.

Yes. Sign in with the same Google account on each phone. Credits and lock history sync. Locking the same gata from two phones (e.g. accidentally) is detected as a duplicate and charged only once.

We have a kill switch — if the portal changes in a way that would corrupt records, we disable the app server-side immediately and ship a JS update within hours. The app polls the kill switch on launch.

In the app: Settings → Delete account. This soft-deletes your user record per the DPDP Act; your historical lock-event entries are retained for audit but the email + Google ID are anonymised. Future sign-ins from the same Google account create a new record.

No, intentionally. Distribution is via signed APK from the Download page. This avoids Play Store policy review of an app that scrapes a government portal, which would be a takedown risk. The signing cert SHA-1 + APK SHA-256 are published on the Download page so you can verify the install.

The eKhasra portal rate-limits its API after a certain request rate. The app respects this with built-in delays (~1 request/second) and exponential backoff on 429 responses. If the message appears repeatedly, give it 60s and resume — the rate-limit window will reset.