MAXX Auth Privacy Policy
Effective date: November 9, 2026
This policy describes personal data processed by MAXX Auth, its API, and the MAXX Auth Flutter SDK. It does not cover the separate MAXX platform, an integrating developer's app, or other services linked from them; those services may have their own privacy notices.
Operator and contact
MAXX Auth was founded and is published by Aryan Singh “SP” and is operated by Aryan Singh, an individual operator. For privacy questions or requests, email choudharysatyveer02@gmail.com. Please do not email passwords, session tokens, or verification/reset codes.
Roles and the app you use
MAXX Auth provides authentication infrastructure to developers whose apps are integrated with a MAXX project. The developer chooses whether to request an account and is responsible for telling its users about that app's data practices and obtaining any permissions or consent required for its use. The developer's app may collect data beyond the information described here. Contact that developer about data it separately collects.
MAXX Auth identity accounts are separate from Firebase Authentication accounts.
Information processed
- Account information: email address, a generated internal user identifier, account status, verification state, and account timestamps.
- Authentication information: a salted password hash (the plaintext password is not stored), hashed session and recovery tokens, token/session expiry data, and a session-version value used to invalidate sessions.
- Security and rate-limit information: request counts, endpoint/application identifiers, time windows, and a one-way hash derived from the request IP address for rate limiting. The API does not store the raw IP in its rate-limit document; Google Cloud infrastructure may separately process network and request metadata in service logs.
- Email delivery: the recipient email address and the verification or password-reset message/code are sent through Brevo SMTP so the requested action can be completed.
- Developer integration information: public application ID and project/integration records required to route a request to the correct tenant.
The SDK stores a session token on the user's device through the platform storage plugin. Storage protections depend on the target platform and its configuration. The SDK does not send passwords or session tokens to analytics services.
Purposes and legal basis
Data is used to create and secure accounts, verify email addresses, authenticate sessions, deliver password recovery, prevent abuse, operate and troubleshoot the service, and meet legal obligations. Developers integrating MAXX Auth must provide their own appropriate notice and establish a valid basis for asking MAXX Auth to process end-user account data.
Service providers and location
MAXX Auth uses Google Cloud/Firebase for functions, database, secret storage, networking, and hosting, and Brevo for SMTP email delivery. These providers process data to provide their services under their own terms and privacy documentation. Core Firestore data for the current deployment is configured in Google Cloud region asia-south2 (India). Email and provider operations may involve processing in other regions or countries; do not assume all data remains in India.
MAXX Auth does not sell personal information or use it for targeted advertising. Information may be disclosed when legally required, to protect users/service integrity, or as part of a business transfer subject to applicable law.
Retention and deletion
Account records are kept while the account remains active. Session records have a 30-day validity period; verification codes expire after 24 hours and password-reset codes after 30 minutes. Used or replaced recovery tokens are deleted from the active database. Firestore automatic expiration is enabled for expired sessions and recovery-token records. API rate-limit records are eligible for automatic deletion after one day without an update. These deletions are asynchronous and may occur later than the expiry time. Provider logs and backups follow the providers' retention processes and may remain longer.
MAXX Auth currently has no self-service account-deletion endpoint. To request account deletion or exercise a privacy right, email the address above from the account email and identify the integrating app/project if known. We may ask for information reasonably needed to verify the request. We will review and process eligible requests, subject to applicable law, security needs, and data that must be retained. Deleting a MAXX Auth account does not delete information held separately by the developer's app.
Security
MAXX Auth uses safeguards including salted scrypt password hashes, one-way hashes for stored session/recovery tokens, HTTPS, tenant-scoped records, server-only Firestore rules, and request rate limits. No internet service or storage method can be guaranteed completely secure. Keep your email account and device secure, do not share codes or tokens, and tell us promptly if you suspect account misuse.
Children
MAXX Auth is not designed specifically for children. Developers must not use it to create or manage a child's account where prohibited or without any legally required parent/guardian authorization. Contact us if you believe a child's information was submitted improperly.
Rights, changes, and complaints
Depending on applicable law, you may have rights to access, correct, erase, or object to certain processing. Contact us at the email above to make a request or complaint. We may update this policy as the service changes; the current version and effective date will be posted here. Material changes will be communicated through the MAXX platform or an integrating developer where reasonably practicable.
This policy is intended to explain current MAXX Auth practices and is not legal advice. Integrating developers should publish their own app-specific privacy notices and obtain independent advice about their obligations.