Last Updated: 24 September 2026
Account Information: Aurex collects and stores the information provided when you create an account. This may include your email address, first name, and last name.
Account and Usage Information: Aurex also maintains information associated with your account, including the date and time your account was created, your most recent login, your most recent use of the app, and the number of times you have used the app.
Authentication: Aurex allows users to sign in using Apple, Google, or email. When signing in with email, a one-time password (OTP) is sent to the email address provided by the user. Authentication services are provided through Clerk.
Authentication and Account Management: Your email address, first name, and last name are used to create and authenticate your Aurex account and to provide access to the app.
App Functionality: Account and usage information, such as account creation time, last login, last app usage, and usage count, is used to operate, maintain, and improve the functionality of Aurex.
No Third-Party Sharing: Aurex does not sell, share, or distribute your personal information to third parties.
Aurex uses service providers, including Clerk for authentication, Vercel for server-side application infrastructure, and Google Cloud Firestore for data storage. These services process or store information as necessary to provide Aurex's functionality and are not used by Aurex to sell or distribute your personal information to third parties.
Secure Authentication: Aurex uses Clerk to manage user authentication and sessions. Clerk uses short-lived, cryptographically signed JSON Web Tokens (JWTs) to authenticate requests to the application's backend. These tokens have expiration times and are validated before authenticated requests are processed.
Controlled Data Access: The Aurex mobile app does not directly connect to or access the Google Cloud Firestore database. All requests to store or retrieve application data are made through Aurex's server infrastructure hosted on Vercel. The server authenticates each request and accesses data on a per-user basis, so authenticated users can only access the data associated with their own account.
Limited Authentication Tokens: The server receives a short-lived authentication token that is used to authenticate the user's request. The token is validated before the server processes requests to store or retrieve the user's data.
Secure Connections: Communication between the Aurex app, the server, and Google Cloud Firestore is protected using secure, encrypted connections. Data transmitted to and from Firestore is protected using Transport Layer Security (TLS), and data stored in Firestore is encrypted at rest.
While Aurex takes reasonable measures to protect your information, no method of transmitting or storing information electronically can be guaranteed to be completely secure.
Updates: This Privacy Policy may be updated when necessary. Any changes will be reflected in the "Last Updated" date at the top of this page. Checking this policy periodically is recommended.
For any questions or concerns about this Privacy Policy, contact engineering@admtronics.com.
By using Aurex, you acknowledge the practices described in this Privacy Policy.