PUSH OTP
Privacy Policy
This policy explains how JKEY LIMITED (“we”, “us”) processes information when providing PUSH OTP one-time passwords, enterprise device binding, and operation approval services.
1. Information we process
Local authenticator information
A standard authenticator account may contain the issuer, account name, OTP secret, algorithm, digit count, and refresh period. This information is stored in the device Keychain and is not uploaded to our servers merely by using the standard OTP function.
Enterprise binding and device information
When you bind an enterprise authenticator, we may process the enterprise application name and ID, enterprise user identifier, binding credential, device identifier, device model, system version, APNs push token, device public key, timestamp, and signature. The device private key remains local and is not uploaded.
Verification and operational information
To display, process, and record enterprise verification requests, we may process the request ID, application name, user identifier, event, description, IP address, creation and expiry times, approval result, and necessary network, security, and error logs.
Camera, notifications, and biometrics
With your permission, the camera is used only to recognise QR codes; we do not proactively upload camera frames. Notification permission is used for enterprise verification requests. Face ID or Touch ID is handled by iOS, and we do not receive or upload biometric templates.
2. Why we use information
- Generate and display local one-time passwords;
- Bind enterprise devices, deliver notifications, display requests, and return approval or rejection decisions;
- Display verification records, maintain service security, and troubleshoot failures;
- Meet applicable legal obligations and protect users, enterprise customers, and our legitimate interests.
3. Sharing and external services
We do not sell personal information or use it for advertising, marketing, or cross-app tracking. We use cloud infrastructure and Apple Push Notification service to provide necessary functions. Enterprise verification requests and decisions are exchanged between our service and the enterprise customer that generated the request. Relevant providers are expected to process only the information needed for their function and apply protections consistent with this policy and applicable law.
4. Retention and deletion
Local authenticator accounts remain until you delete them or clear app data. Enterprise bindings, verification records, and security logs are retained only as needed to provide the service, perform security audits, resolve disputes, or comply with law.
PUSH OTP does not create a user account that requires registration or sign-in, so there is no PUSH OTP account to close. Standard authenticator entries are deleted only from the device. For an enterprise authenticator, the app first requests removal of the server-side binding and deletes local data after that succeeds. Clear All Data requests deletion of verification records. You may also use the email below to request access, correction, or deletion of server-side information. After verifying a request, we delete or de-identify the relevant device binding, push token, and verification records within 7 calendar days, except records that applicable law requires us to retain.
5. Information security
We use measures including Keychain storage, local encryption, protected transport, and device signatures. No transmission or storage method is completely secure. Protect your device, QR codes, and verification codes, and promptly address unfamiliar bindings or requests.
6. Your rights and choices
You can manage camera, notification, and biometric permissions in system settings. Disabling a permission does not affect unrelated functions, but the corresponding feature may be unavailable. You may delete individual accounts or clear data in the app, and may contact us to exercise access, correction, deletion, withdrawal of consent, or other rights available under applicable law.
7. Minors
PUSH OTP is not intended for persons under 18 years of age. If we learn that information was provided in a manner inconsistent with applicable law, we will handle it as required by law.
8. Cross-border processing
Because the service may be available in multiple countries or regions, information may be processed outside your location. We take reasonable measures required by applicable law to protect it.
9. Policy updates
We may update this policy for functional, operational, or legal reasons. We will notify you of material changes through the app, website, or another reasonable method. Changes apply from the stated effective date.
10. Contact us
Email: bd@jkey.org