PUSH OTP
User Service Agreement
This Agreement is between you and JKEY LIMITED, a company incorporated in Hong Kong (“JKEY”, “we”, “us”). Please also read the Privacy Policy before using PUSH OTP.
1. Acceptance and eligibility
By using PUSH OTP, you confirm that you have read and accepted this Agreement and the Privacy Policy. If you do not agree, stop using the service. You must be at least 18 years old and legally permitted to use the service where you live.
2. Service scope
PUSH OTP provides standard one-time passwords, enterprise device binding, display of enterprise operation requests, approval or rejection, and verification records.
- Standard one-time passwords are generated locally. We cannot recover an OTP secret that you have not backed up.
- Enterprise verification requests originate from the relevant enterprise system. PUSH OTP displays the request and returns your decision; it does not perform the sign-in, transfer, or other enterprise operation.
- An approval does not guarantee that an operation completes. The result depends on the enterprise system, network conditions, and enterprise rules.
3. Your responsibilities
- Protect your device, QR codes, verification codes, enterprise binding data, and device unlock credentials;
- Review the application, user, event, IP address, time, and description before approval;
- Reject requests that you did not initiate, that contain incorrect information, or that appear suspicious, and contact the enterprise administrator;
- Remove an old device binding when a device is replaced, lost, or no longer used.
4. Prohibited conduct
You must not use PUSH OTP for unlawful conduct, unauthorised access to another account or device, fraud or impersonation, malware distribution, probing or bypassing security measures, API abuse, or interference with the service.
5. Enterprise and external services
Enterprise verification relies on the relevant enterprise system, network connectivity, cloud infrastructure, and Apple push services. Enterprise customers are responsible for the requests they create, their business rules, and their processing results. External services may also be subject to their own terms, privacy practices, and availability.
6. Availability and risks
To the extent permitted by applicable law, the service is provided on an “as is” and “as available” basis. Network interruptions, incorrect device time, disabled notifications, enterprise outages, or expired QR codes may make a code or request unavailable. We do not exclude liability or statutory rights that cannot lawfully be excluded.
7. Deletion and stopping use
PUSH OTP does not create a user account that requires registration or sign-in, so there is no PUSH OTP account to close. You may delete an individual authenticator entry or use Clear All Data. We cannot restore the secret after a standard OTP entry is deleted. For an enterprise authenticator, the app first requests removal of the server-side binding and deletes local data after that succeeds. Contact support if you need further deletion of server-side information.
8. Changes and contact
We may update this Agreement for functional, security, operational, or legal reasons and will provide reasonable notice of material changes. This Agreement and related disputes are subject to applicable law and any mandatory rights or jurisdiction rules that apply to you.
Email: bd@jkey.org