Pramaan — Privacy Policy
Pramaan is a sign-in companion app: it lets you approve sign-ins to your organisation's applications with a tap, generates authenticator codes, and stores passkeys in your device's secure hardware. It is built so that the most sensitive material — private keys and authenticator secrets — stays on your device, apart from two clearly listed exceptions (encrypted sync data, and the optional offline approval secret). This policy explains what data the service does process, and why.
Data we process, and why
| Data | Purpose | Where it lives |
|---|---|---|
| Account identifiers (name, username, email) from your organisation's identity provider | Signing you in and showing which account is in use | Your identity provider; cached on your device |
| Device enrolment record: a device label (“Pramaan (Android)”), the platform and OS version, the app version, public keys (approval key, post-quantum key, token-binding key), an Android key-attestation certificate chain, and a push-notification token | Delivering sign-in requests to your device, verifying your approvals, and proving the approval key is held in secure hardware | The Pramaan ID Broker operated by your organisation, until the device is revoked |
| Sign-in security metadata (IP address, approximate location derived from it, time, application name) | Shown to you on each approval so you can reject sign-ins that are not yours; risk checks against unusual locations; security audit log | The Pramaan ID Broker, in the audit trail |
| Device integrity verdict (Google Play Integrity), when your organisation enables it | Checking the app and device are genuine at enrolment and when you approve a sign-in | Verified with Google; the verdict is kept on your device’s enrolment record until the device is revoked |
| Device health: screen lock set, storage encryption on, security patch within 120 days, device-admin present, Android version. Sent when you set up the device and when you open “Your devices” | Showing you a device health score and letting your organisation require a healthy device for some apps | The Pramaan ID Broker; the latest report is kept on the device record |
| Offline approval secret (only if you turn on offline approval codes) | Letting the server check a code you read out when your phone has no connection | Your device and the Pramaan ID Broker; cleared when you turn the feature off or revoke the device |
| Encrypted sync data (only if you turn on sync): your authenticator entries, added sign-in sources and theme, encrypted on your device with your passphrase | Keeping your other devices in step | The Pramaan ID Broker, as ciphertext it cannot read |
| Network experience measurements (only if your organisation enables it): reachability and timing of services your organisation chooses, measured from your phone every few minutes while the app is open | Helping your organisation find network problems | The Pramaan ID Broker; the measured services also see your phone’s IP address |
| Private-app access records: which private app you opened and the page path requested | Security and troubleshooting | The Pramaan ID Broker’s logs |
| Telegram link (only if you link Telegram) | Sending you one-time codes through Telegram | The Pramaan ID Broker holds the link; messages are delivered by Telegram |
This website sets no cookies and loads nothing from other sites.
Data that never leaves your device
- Private keys — approval and passkey keys are generated in your device's secure hardware (StrongBox/TEE) and are non-exportable. (The optional offline approval secret is shared with your organisation's server; see the table above.)
- Authenticator (TOTP) secrets — stored only on your device. If you explicitly enable cross-device sync, they are end-to-end encrypted with a passphrase only you know before upload; the server stores ciphertext it cannot read.
- Biometrics — fingerprint/face data is handled entirely by Android; Pramaan only receives a yes/no from the operating system.
What we don't do
- No advertising, and no Firebase Analytics or crash-reporting SDKs.
- We do not sell personal data.
Third parties that process data for the app
- Google.
- Firebase Cloud Messaging delivers sign-in requests. Each notification passes through Google and contains the application name, approximate place, network and requesting browser. Firebase also assigns an installation ID.
- Play Integrity checks device and app integrity.
- The ML Kit barcode scanner, which reads QR codes entirely on your phone, sends Google anonymous diagnostics: device and app information, an identifier, performance and error data.
- Wear OS relays a sign-in request to your paired watch.
- Telegram, only if you link it.
Retention
Enrolment records are kept while the device is enrolled and are deleted when you (or your administrator) revoke the device — revocation is available in the app under "Where you're signed in". Sign-in audit events are retained per your organisation's security policy and then purged.
Your choices and rights
- Revoke any enrolled device at any time from the app; this immediately stops push delivery and invalidates its approval key.
- Uninstalling the app destroys its on-device keys.
- To exercise data access or deletion rights, contact your organisation's administrator or the address below.
Contact
Frontier Labs Private Limited
contact@pramaanid.cloud