2AYE Authenticator
Mobile privacy and account requests
Updated 14 October 2026. Applies to the mobile app; website and customer service processing may have additional terms.
Offline authenticator
Authenticator seeds and generated codes are processed on your device. The app PIN is checked on your device; operating-system biometrics return a confirmation result rather than biometric data. The offline authenticator does not require an organization account.
Organization connection
When you enroll, the configured organization service processes account and organization identifiers, device and session information, approval decisions and delegated intent activity. Mailbox verification requests use the configured organization API. Organization retention and access policies apply to its audit records.
Optional Android notifications
In push-enabled builds, with notification permission, Google Firebase Cloud Messaging processes app installation identifiers, registration tokens and delivery information. 2AYE stores registration tokens encrypted and sends only a generic sign-in hint and opaque request identifier through Firebase. Matching numbers, authenticator seeds, signatures and approval details are not included. Notifications are best effort and never approve a request. Disable them in Android settings; signed-in users can still open Approvals to retrieve requests.
Camera and SDK diagnostics
The camera scans setup and enrollment QR codes on your device. On Android, Google ML Kit collects device and app information, installation identifiers, performance metrics, scan configuration and event/error information for diagnostics and usage analytics over HTTPS. Google documents this collection at developers.google.com/ml-kit/android-data-disclosure. Camera images and decoded authenticator secrets are not uploaded by the scanning feature. The app has no advertising SDK or advertising identifier access and does not request contacts, microphone or precise-location permission. Organization sign-in records can include approximate location derived from network addresses.
Remove device data
Delete authenticator entries in the app to remove their seeds stored on your device. Removing an entry does not disable two-factor authentication at the original service; arrange recovery there first. Removing an enrolled device and signing out are separate operations.
Request account or organization-data deletion
Contact your organization administrator for organization-controlled records. You can also email support@twoaye.com with the subject Mobile privacy request. Provide only your account email and organization name; never send passwords, verification links, authenticator seeds or identity documents. We will route the request and explain any security or legal retention requirements. This is a request channel, not an automatic deletion guarantee.
Support and security
For setup and access assistance: support@twoaye.com. For suspected vulnerabilities or ownership disputes: security@twoaye.com. Enterprise approvals require enrollment, connectivity and appropriate authority; Android notifications require a push-enabled installed build and permission. Physical-phone notification acceptance remains in verification; iOS background push is not available.