Data Processed by the App
To provide app access control, voucher redemption, and account recovery, AntiStatic uses Firebase services.
Data that may be processed includes:
- Firebase Authentication account identifiers (anonymous UID by default; optionally email/Google account if you link or sign in).
- Voucher/access status data in Firestore (for example:
accessExpiresAt, redemption timestamps, and related access metadata). - Device-binding metadata used to enforce device-switch rules (hashed device identifier and a human-readable device label).
- App telemetry events via Firebase Analytics related to setup/removal selections (for example selected package count and selected package names).
- If you voluntarily create or link an account, your email address may be stored for account recovery and access restoration.
Data Stored Locally on Your Device
AntiStatic also stores operational app data locally, such as setup preferences, selected removal lists, temporary access cache values, and pairing/state information needed for app functionality.
You can remove locally stored app data by clearing app storage or uninstalling the app.
Third-Party Services
AntiStatic integrates Google/Firebase services including:
- Firebase Authentication
- Cloud Firestore
- Cloud Functions
- Firebase Analytics
- Google Sign-In (when used)
Explanation of Permissions Requested in the App
The current permission list is defined in
app/src/main/AndroidManifest.xml.
| Permission | Why it is required |
|---|---|
| android.permission.INTERNET | Required for Firebase authentication, Firestore reads/writes, Cloud Functions calls, and other online app services. |
| android.permission.POST_NOTIFICATIONS | Lets the app show progress/completion and setup-related notifications. |
| android.permission.WAKE_LOCK | Keeps required work active during long-running optimization flows and background processing. |
| android.permission.WRITE_SECURE_SETTINGS | Used by the app’s optimization workflow that applies certain device settings through privileged ADB-based operations. |
| android.permission.ACCESS_WIFI_STATE | Needed to detect network state for wireless debugging and pairing flows. |
| android.permission.CHANGE_WIFI_STATE | Used by connected-device foreground-service behavior on newer Android versions during pairing/connectivity flows. |
| android.permission.ACCESS_NETWORK_STATE | Allows the app to detect whether network connectivity is available before network-dependent actions. |
| android.permission.FOREGROUND_SERVICE | Allows long-running foreground operations (such as optimization/pairing services) with user-visible notifications. |
| android.permission.FOREGROUND_SERVICE_DATA_SYNC | Declares data-sync foreground-service type used by app background work. |
| android.permission.FOREGROUND_SERVICE_CONNECTED_DEVICE | Declares connected-device foreground-service type used by the pairing service. |
Your Choices
- You may use AntiStatic anonymously (default flow).
- You may optionally link/sign in with Google or email for recovery/transfer features.
- You can clear local app data at any time from Android settings.
Contact
If you have privacy questions or discover a security issue, contact support: [email protected]
Yours sincerely,
Eigen Holdings LLC