← Back to home

Privacy Policy — Apex Booster+

Last updated: August 10, 2026 (v4 — documents the actual behavior of Android Auto Backup, physically confirmed: library, history, GFX Profile, language, onboarding and preferences can be restored by the system backup; Apex Studio media is excluded)

1. Data Controller Identification

App name: Apex Booster+

Developer / Controller: AllAppsEngineer

Official contact: allappsengineer@gmail.com

2. Data Stored Locally on the Device

Apex Booster+ does not have its own server. The data below is stored on your device, through Android's SharedPreferences, and Apex Booster+ does not transmit it to any server of its own operated by AllAppsEngineer. Certain preferences and operational data may, however, be copied or transferred by Android's own backup, restore, and device-transfer mechanisms — see section 2.1:

Data	Purpose
Library of added games	Display and manage the user's game library
Game identifier (`packageName`)	Identify and launch the corresponding app
Local GFX profile per game	Save the visual preference chosen by the user
Session history	Display previous sessions and local metrics
Selected language	Keep the language preference between sessions
Onboarding completed flag	Avoid showing the tutorial again when reopening the app
Low Distraction Mode preference	Reduce animations, brightness and haptics when enabled by the user
Apex Floating Button state (on/off)	Remember whether the user chose to keep the capture shortcut active

This data is not synced, sold, or shared with third parties by Apex Booster+.

2.1 Backup, Restore, and Device Transfer (Android)

Apex Booster+ has Android Auto Backup enabled, with a selective (allowlist) backup policy defined within the app itself. These rules cover two behaviors provided by the Android platform: backup/restore and device transfer (used, for example, when setting up a new device from an old one).

May be included in these processes, when available on the device or in the user's account: game library, session history, GFX Profile, language, onboarding and preferences/settings — exactly the data listed in the table above.
Not included: screenshots, video clips, or any Apex Studio media.

This behavior was physically confirmed: after uninstalling and reinstalling the same app on a test device, the library, history, GFX Profile, language, onboarding, and preferences were restored; screenshots and video clips were not.

Who administers this process: the backup, restore, and transfer are not performed by an AllAppsEngineer server or by Apex Booster+'s own code. This process is administered by the Android system and by the backup mechanism/provider configured on the device or in the user's account — not by AllAppsEngineer's servers. When available, the user can manage backup, restore, or transfer options in the system/device settings.

3. Local Device Readings

The app performs the following local readings for informational purposes:

Available and total RAM: reads the device's memory to display the session snapshot. Never leaves the device.
Basic network latency (Apex Ping): the app sends a simple network request (HTTP HEAD) to a public Google connectivity-check endpoint (clients3.google.com/generate_204, with connectivitycheck.gstatic.com/generate_204 as a fallback) solely to measure response time. No personal data is sent in this request beyond standard system HTTP headers, and the result (a number in milliseconds) is used only for on-screen display — it does not represent or promise the actual ping of external game servers. No video, audio, screen capture, clip, preference, game library data, or user-entered content is sent in this request. As with any network connection, the IP address and standard connection metadata may be observed by the destination infrastructure; retention of that data by the third party (Google) is not controlled or confirmed by Apex Booster+.
Focus Mode / Do Not Disturb (DND) status: checked only when the user grants notification policy access permission. It is not enabled automatically.

These readings do not generate any personal data sent to a server — the app's only network communication is the latency check above.

4. Installed Apps

To allow the user to select games from their library of installed apps, Apex Booster+ may list launchable apps available on the device.

No unrestricted access: the app does not request permission for unrestricted access to the full system app list (no QUERY_ALL_PACKAGES).
No external transmission: the list of installed apps is never sent to servers.
User control: the user decides which apps to add to the library. The app does not perform automatic scans or export this data.

5. Apex Studio — Screen Capture, Video Clips and Gallery Media

Apex Studio is the app's social content creation feature. It offers three ways to obtain media, all explicitly triggered by the user:

5.1 Gallery import

The user can voluntarily select an existing image or video on the device through Android's native media picker (image_picker). The file is read only in memory, during the session, for preview and card composition — it is never sent to servers and is not saved in the app's preferences.

5.2 Screen capture and video clips (Apex Floating Button)

With the Apex Floating Button enabled (optional — see section 7), the user can capture a screenshot or record a short video clip (10 to 60 seconds) of their own gaming session. This feature uses Android's MediaProjection API, which requires explicit user confirmation on the operating system's own consent screen before any capture starts, and keeps a persistent notification while capture is active.

In-game internal audio (optional, video only): when available, the app may capture the audio played by the game/app itself during recording (AudioPlaybackCaptureConfiguration API, Android 10 or higher). This is not the device's microphone — no voice or ambient sound is captured. The RECORD_AUDIO permission is required by the Android API for this feature even though it is internal app audio, due to a platform quirk; the physical microphone is never read in this configuration.
When audio is unavailable: some games block internal audio capture by their own policy. In these cases, the video is saved normally without audio, and the app shows a notice guiding the user to record externally (with the device's own screen recorder) and import the video via the gallery (section 5.1), if they want a clip with audio.
Storage: captures and clips are saved in a folder specific to Apex Booster+ inside the app's own storage (not a shared public gallery), with a local index (index.json) used only to list files inside Apex Studio.
Transmission: none. No screenshot, clip, or audio is ever sent to servers under any circumstance.

6. Export and Sharing

Apex Studio lets the user compose a visual card (image or video with an Apex frame) from selected or captured media. All composition — including video export — happens locally on the device, with no server-side processing step.

Always manual sharing: publishing only happens when the user taps "Share" and chooses a destination in Android's native share sheet. Apex Booster+ never automatically posts or publishes to any social network.
Temporary, restricted access: the exported file is made available to the destination app chosen by the user through a FileProvider with temporary permission — no other app has access to it.

7. Apex Floating Button (SYSTEM_ALERT_WINDOW)

The Apex Floating Button is an optional visual shortcut shown over other apps during a gaming session, used exclusively to quickly open the screen/video capture described in section 5.

Explicit opt-in: off by default. Only requested when the user enables the feature in Settings, with an in-app explanation shown before the system's own permission screen opens.
Reversible at any time: the user can disable the button in Settings, which removes the on-screen shortcut immediately.
No data collection: the button does not read, log, or transmit anything by itself — it only opens the capture flow described above.

8. Commercial Model — Paid App for Download

Apex Booster+ is a paid app for download on Google Play: a single purchase of the app, with all features available from the first install. There is no subscription, no ads, and no in-app purchase, paywall, or unlock processed by the app's own code.

Payment is processed entirely by Google Play during the app's installation/purchase step, outside of Apex Booster+'s code — the app does not integrate any Billing library, and does not process, see, or store card numbers, bank details, payment information, or any local "purchased/unlocked" state. Apex Booster+ keeps no record of amounts, billing dates, or payment method — that history lives exclusively in the user's Google Play account, in the store, outside the app.

9. Data Not Collected

Apex Booster+ does not collect any of the following data:

Name, e-mail, or any personal identifier of the user.
Precise or approximate location.
Contacts, messages, calls, or communication data.
Physical microphone audio or conversations.
Card numbers, bank details, or payment information.
Biometric data or advertising identifiers.

Photos, videos, and in-game internal audio are only accessed when the user explicitly triggers gallery import or the capture described in section 5 — never automatically, and never sent outside the device by Apex Booster+. This media is also explicitly excluded from Android's backup, restore, and device-transfer mechanisms (section 2.1).

10. Data Sharing with Third Parties

Apex Booster+ does not sell, rent, or share personal data with advertisers, partners, or third parties. There is no:

Advertising SDK.
Third-party analytics or attribution SDK.
Behavioral tracking for advertising purposes.
Cookies or tracking technologies.

Apex Booster+ does not integrate the Google Play Billing library or any other in-app purchase SDK — the app is distributed as a paid app for download, with no Billing components in the code or dependencies (confirmed via gradlew :app:dependencies: no reference to com.android.billingclient:billing or the transitive Google Play Services components it used to bring in).

11. Permissions Used

Permission	Purpose
Internet	Basic latency and connectivity test (Apex Ping)
Focus Mode / Do Not Disturb access	Gamer Focus Mode — only when the user grants permission
Display over other apps (SYSTEM_ALERT_WINDOW)	Apex Floating Button — only after explicit activation in Settings (section 7)
Foreground service / screen capture (FOREGROUND_SERVICE, FOREGROUND_SERVICE_MEDIA_PROJECTION)	Keeps screen/video capture visible to the user via a persistent notification while active
Foreground service — microphone (FOREGROUND_SERVICE_MICROPHONE)	Declared only during a video recording with in-game internal audio (section 5.2) — never to capture the physical microphone
Record audio (RECORD_AUDIO)	Required by the Android API for in-game internal audio capture (section 5.2); the physical microphone is never read
Network state / Wake lock (ACCESS_NETWORK_STATE, WAKE_LOCK)	Brought in by the `androidx.media3` library (Apex Studio video playback) — not used directly by the app's own code

No other sensitive permission is requested in this version. The app does not request permanent access to the gallery, location, contacts, or camera.

12. Data Retention and Deletion

Library, history and preferences: "Clear history" in Settings removes saved sessions; uninstalling the app deletes all local SharedPreferences data.
Screenshots and video clips: can be deleted individually by the user inside Apex Studio; uninstalling the app removes the entire associated folder.
Media imported from the gallery: discarded from the app's memory as soon as the Studio screen is closed; the original file remains only where the user had already saved it (system gallery), outside Apex Booster+'s control.

Since Apex Booster+ has no server of its own, there is no data retention by AllAppsEngineer's infrastructure outside the user's device. Certain preferences and operational data (section 2.1) may be copied or transferred by the Android system's backup, restore, and device-transfer mechanisms, administered by the device or the user's account — not by AllAppsEngineer's servers. When available, the user can manage these options in the system/device settings, independently of Apex Booster+. The app is paid for download — there is no in-app purchase status, unlock, or local entitlement to retain or restore.

13. Limitations and Important Notices

Apex Booster+ does not automatically modify third-party games.
The app does not promise actual improvement in FPS, GPU, resolution, ping, or performance of external games.
The displayed metrics (RAM, Apex latency) are local and informational — they do not represent automatic changes to the device or to the games.
Gamer Focus Mode enables Android's Do Not Disturb only when the user explicitly grants permission.
Screen capture, internal audio, and the floating button are gamer self-expression and personal organization features — not a competitive in-game advantage.

14. Data Security

Preferences and history data are protected by Android's app sandbox and the device's file system encryption. Screenshots and clips live in a folder specific to the app, not accessible to other apps without the user's explicit permission. The app's only network communication — the latency test (section 3) — uses the operating system's standard encrypted connection (HTTPS/TLS).

15. Children

Apex Booster+ is not directed at children under 13 and does not knowingly collect data from minors.

16. Contact

For questions, requests related to data stored locally on your device, or any privacy-related matter, please get in touch:

E-mail: allappsengineer@gmail.com

17. Changes to this Policy

Version	Date	Change
v1	June 4, 2026	Initial publication
v2	July 28, 2026	Added sections on screen capture, in-game internal audio, floating button, video export, and one-time unlock; corrected outdated references that described these features as "future" when they were already implemented; updated permissions table.
v3	July 30, 2026	Removed internal Billing (Google Play Billing / `in_app_purchase`) from the code. Apex Booster+ is now a paid app for download, with no in-app purchases, no paywall, and no local unlock state. Section 8 rewritten; removed references to `com.android.vending.BILLING`, the purchase status cache, and the "Restore purchase" button.
v4	August 10, 2026	Documented the actual behavior of Android Auto Backup, physically confirmed. Added section 2.1: library, history, GFX Profile, language, onboarding and preferences can be copied, restored, or transferred by the system's backup and device-transfer mechanisms; Apex Studio screenshots and video clips are explicitly excluded from that copy. Sections 2, 9, and 12 adjusted to no longer state absolutely that data "never leaves the device" — precision added: it is not sent to a server operated by AllAppsEngineer; this process is administered by the Android system and by the backup mechanism/provider configured on the device or in the user's account, manageable by the user when available.

This policy may be updated periodically to reflect changes in the application. The "Last updated" date at the top of this document will always indicate the version in effect.