Privacy
Permission stays personal.
This notice describes RHINO POP app data handling and supplements the 2RHINO privacy policy.
RHINO POP processes your RHINO ID account identifier, enrolled-device identifier and name, platform, push token, public signing key, trust status, and last-active time. Approval requests can include the requesting service, browser, device, approximate location, expiration time, and decision audit event.
The private signing key remains in Android Keystore or the iOS Keychain and is not sent to RHINO POP. Passwords are not stored. Approval and device-management traffic uses encrypted HTTPS connections.
The camera is used only when you choose Scan QR. QR images are processed on the phone. A RHINO POP enrollment ticket is sent to the RHINO POP service to enroll your device. Third-party one-time-code secrets are not retained in compatibility history or uploaded by the scanner.
Apple Push Notification service or Firebase Cloud Messaging carries the minimum data needed to notify the enrolled phone of a pending approval. Their handling is also governed by Apple or Google privacy terms.
You can deny a request, revoke the device, disable camera or notification permission in phone settings, or contact support about account data.
Email RHINO POP privacy support from the address associated with your RHINO ID and ask us to delete your RHINO POP data. After verifying the request, we remove active device enrollments, push tokens, and public-key associations, and delete or de-identify associated app activity where it is not required for security.
Security events and request records may be retained for up to 90 days after fulfillment to prevent abuse and preserve an audit trail, or longer only when required by law.