Privacy
This section describes how Aurex handles user data across web and mobile interfaces and outlines privacy-related responsibilities and limitations.
Aurex is designed to minimize data exposure while maintaining the functionality required to operate account, wallet, and card features.
Data scope
Aurex processes only the data required to operate the platform:
account identifiers and authentication data,
card-related information,
transaction and activity metadata.
No unnecessary personal data is collected.
Note Aurex does not collect behavioral or tracking data unrelated to platform functionality.
Web and mobile data consistency
The mobile application uses the same backend and data model as the web platform.
This means:
no separate mobile-only user profiles,
no duplicated data storage,
consistent privacy rules across platforms.
All privacy-related actions apply globally to the account, regardless of device.
Mobile-specific considerations
While the mobile app does not introduce new data collection mechanisms, users should be aware that:
data is displayed on a personal device,
device-level security (PIN, biometrics, OS protections) plays a role in privacy,
notifications may expose limited information on the device screen.
Important Aurex cannot control the security or privacy settings of a user’s mobile device.
Third-party platforms
The mobile application may be distributed through:
App Store (iOS) — coming soon
Google Play (Android) — coming soon
These platforms operate under their own privacy policies.
Note Beta access and installation instructions are communicated via official Aurex channels (X).
User responsibility
Users are responsible for:
securing their devices,
avoiding the use of shared or compromised environments,
reviewing platform updates that may affect privacy behavior.
Important Aurex does not share account data with third parties outside what is required for platform operation.
Privacy limitations
Aurex cannot prevent data exposure caused by compromised user devices
Actions performed by an authenticated user are considered authorized
Privacy protections do not override account security rules
Last updated