Contents
1. Who we are
VaultAuth is developed and operated by Brix Apps (“Developer”). For privacy requests, contact:
- Email: contact@brixsapps.com
- Website: https://brixsapps.com/
2. Scope
This policy applies to the VaultAuth mobile app for Android (package com.totpapp) and related support channels. It does not cover third-party websites or services you open outside the App.
3. Information we collect
3.1 Account & profile information
When you sign in with Google, we receive:
- Email address
- Display name
- Profile photo URL (if provided by Google)
- A unique user identifier from our authentication provider
3.2 Authenticator account data
To provide the core service, we store:
- Account display name, username/issuer metadata
- TOTP secret keys (protected; see Security)
- Labels/tags you assign
- Emails you choose to share an account with (view-only access)
- Timestamps related to account creation/updates
3.3 Technical & advertising-related data
- Basic app/diagnostic information needed for sync and authentication
- Device platform indicators (for example Android)
- Advertising identifiers and ad interaction data when ads are shown (see Advertising)
3.4 Information we do not intentionally collect
- We do not sell your personal data
- We do not collect precise location for advertising
- We do not store camera recordings or photo libraries from QR scanning
- We do not request microphone / audio recording for app features
| Data | Collected | Purpose |
|---|---|---|
| Email / name | Yes | Sign-in, sync, sharing |
| TOTP secrets | Yes | Generate one-time codes |
| Labels & account metadata | Yes | Organize & filter accounts |
| Shared emails | Yes | Grant view-only access |
| Advertising ID / ad events | Yes (via Google AdMob) | Show ads, measure performance, fraud prevention |
| Payment card data | No | — |
| Contacts / SMS / microphone | No | — |
4. Advertising (Google AdMob)
VaultAuth displays advertisements using Google AdMob to support the free app. Ad formats may include banner, native, interstitial, app-open, and rewarded ads.
- Ads are not placed on the Google Sign-In screen
- Ads are not overlaid on your TOTP codes
- Ads are not shown on the QR camera scanner UI
- You may watch a rewarded ad in Settings to hide ads for 24 hours
Google and its partners may collect and process information such as device identifiers (including Advertising ID), IP address, approximate location derived from IP, and interaction with ads, according to Google’s policies.
Learn more: Google Privacy Policy and AdMob & privacy.
In the European Economic Area (EEA), UK, and Switzerland, Google may require consent for personalized ads. Where required, we (or Google’s consent tooling) may present a consent message. You can also reset or limit ad personalization in your device settings (for example Google → Ads).
5. How we use information
- Authenticate you and keep you signed in
- Sync your authenticator accounts across sessions/devices
- Generate TOTP codes for your saved accounts
- Apply labels, filters, and theme preferences
- Enable private sharing of codes with emails you invite (view-only)
- Show and measure advertisements (AdMob)
- Provide support and improve reliability and security
- Comply with legal obligations where required
6. Sharing & disclosure
6.1 Service providers
- Google — Sign-In / authentication
- Google AdMob / Google advertising services — ad delivery and measurement
- Supabase (or equivalent backend) — account database, auth sessions, and sync
6.2 Sharing you initiate
If you share an authenticator account with another email address, that person can view and copy codes only. They cannot edit, reshare, or delete your account. You can revoke access at any time in the App.
6.3 Legal requirements
We may disclose information if required by law, regulation, legal process, or to protect the rights, safety, and security of users or the public.
We do not sell personal information.
7. Security of secrets & codes
Authenticator secret keys are sensitive. We take reasonable technical and organizational measures to protect them, including:
- Encrypted transport (HTTPS / TLS)
- Access controls so only you (and people you explicitly share with) can access your accounts
- Encryption of secrets at rest where enabled in our backend configuration
- View-only restrictions for shared recipients
No method of transmission or storage is 100% secure. You are responsible for keeping your device lock, Google account, and recovery options secure.
Tip: Treat TOTP secrets like passwords. Only share accounts with people you trust.
8. Device permissions
| Permission | Why we ask |
|---|---|
| Internet | Sign-in, sync, sharing, and advertisements |
| Camera | Scan QR codes when adding 2FA accounts. Optional — you can add accounts manually. We do not save camera recordings. |
| Advertising ID (where applicable) | Used by Google AdMob for ad serving and measurement on Android |
9. Data retention & deletion
We retain your account and authenticator data while your account is active and as needed to provide the service. If you delete accounts in the App, those records are removed from your active dataset subject to normal system processing.
Advertising providers may retain ad-related data according to their own retention policies.
You can delete your account in the App: Settings → Delete account. This permanently removes your VaultAuth account, profile, and synced authenticator data.
You may also request deletion by emailing contact@brixsapps.com from your registered email address. We will verify the request and delete or anonymize data unless we must retain some information for legal or security reasons.
10. Your rights
Depending on your location, you may have rights to:
- Access the personal data we hold about you
- Correct inaccurate information
- Request deletion
- Object to or restrict certain processing
- Withdraw consent where processing is consent-based (including ads consent where applicable)
- Export a copy of your data (where applicable)
Contact contact@brixsapps.com. If you are in the EEA/UK, you may also lodge a complaint with your local supervisory authority.
11. Children’s privacy
VaultAuth is not directed to children under 13 (or the minimum age required in your country). We do not knowingly collect personal information from children. If you believe a child has provided personal data, contact us and we will take appropriate steps to delete it.
12. International transfers
Your information may be processed on servers located in countries other than your own (for example where Google, AdMob, or our database providers operate). Where required, we rely on appropriate safeguards provided by those processors.
13. Changes to this policy
We may update this Privacy Policy from time to time. We will revise the “Last updated” date at the top of this page. Continued use of the App after changes means you accept the updated policy, unless applicable law requires additional notice or consent.
14. Contact us
- Email: contact@brixsapps.com
- Developer: Brix Apps
- App: VaultAuth: TOTP Authenticator (
com.totpapp) - Website: brixsapps.com