Skip to main content
Mindset Dev Solutions

Application privacy

CoverShake privacy policy

This policy explains what data and permissions may be used by CoverShake and its integrated services.

CoverShake

Last updated : August 18, 2026

Back to CoverShake

1. Application publisher

Mindset Dev Solutions, represented by Mardochee Ndjeka, develops and publishes CoverShake.

For questions concerning this policy or application-related data, contact realityking12u@gmail.com.

2. General operation

CoverShake is an Android application that detects a phone shake to quickly display a fake screen.

The application does not require an account and does not directly request a name, email address or phone number to use its main features.

3. Data CoverShake does not access

In the analysed version, CoverShake does not use Android mechanisms that capture or read the real content displayed in other applications.

  • No capture of the real screen.
  • No camera access.
  • No microphone access.
  • No access to personal photos or files.
  • No location access.
  • No contacts access.
  • No accessibility service.
  • No access to application usage history.
  • No reading of the URL actually being viewed.

4. Shake detection

CoverShake uses the phone’s motion sensors to detect a shake.

Raw sensor values are not stored in local history and are not sent by CoverShake to a server owned by Mindset Dev Solutions.

The application only records the information required to identify that an activation occurred.

5. Locally stored history

CoverShake uses a Room database stored locally on the device to keep activation history.

  • Local event identifier.
  • Activation date and time.
  • Displayed fake-screen type.
  • Detected shake type.
  • Technical value “Background Detection”.

6. Information about the URL field

The internal database currently contains a technical field named urlBeingViewed.

Despite its name, this field does not contain the address of a website viewed by the user.

In the analysed version, the stored value is the fixed text “Background Detection”.

CoverShake therefore does not read the URL displayed in another application.

7. Deleting history

Activation history remains stored locally on the phone.

The application technically supports deleting an event or the entire history.

History can also be removed by clearing CoverShake data in Android settings or uninstalling the application.

8. Local preferences

CoverShake uses Android preferences to store settings required for application operation.

  • Premium state.
  • Activation count used by selected features.
  • Favourite fake screen.
  • Application settings.
  • Information related to displaying the review request.

9. Display over other applications

CoverShake may request Android permission to display a fake screen over other applications.

This permission is only used to present the selected cover screen after a shake.

It does not allow CoverShake to automatically read the content beneath the fake screen.

Users can remove this permission from Android settings.

10. Biometric protection

CoverShake may use Android biometric authentication to protect access to selected features.

Biometric verification is managed by Android.

CoverShake does not receive or store fingerprints, facial templates or raw biometric data.

11. Background service and startup

CoverShake uses a foreground service to maintain shake detection when the feature is enabled.

The application may request permission to restart after device reboot and to exclude its service from selected battery optimisations.

A persistent notification may be displayed while the service is operating.

12. Google AdMob advertising

CoverShake uses Google AdMob to display advertisements.

The advertising SDK may process technical and usage-related information to provide, measure and secure advertising.

  • Advertising or installation-related identifiers.
  • IP address and general device information.
  • Interactions with advertisements.
  • Advertising diagnostic and performance information.

13. Firebase services

CoverShake integrates Firebase services to improve application stability, performance and configuration.

  • Firebase Analytics to measure application usage.
  • Firebase Crashlytics to analyse crashes and errors.
  • Firebase Performance Monitoring to analyse technical performance.
  • Firebase Remote Config to receive selected technical configurations.

14. In-app purchases

CoverShake uses Google Play Billing to provide premium features or benefits.

Payments are processed by Google Play. Mindset Dev Solutions does not receive complete payment-card information.

The application may receive technical information required to verify a purchase and activate the corresponding features.

15. Processing purposes

Local and technical information may be used to:

  • Detect a shake.
  • Display the selected fake screen.
  • Keep the protection service active.
  • Store local history.
  • Store user preferences.
  • Manage premium features.
  • Display and measure advertising.
  • Analyse usage and performance.
  • Detect and correct crashes.
  • Provide technical configurations.
  • Prevent abuse and protect the services.

16. Retention and deletion

History, settings and premium information are primarily stored locally on the device.

They can be removed from the application where an option is available, from Android settings or by uninstalling CoverShake.

Clearing data may result in the loss of local history and settings.

Technical information processed by Google is retained according to the configuration and policies of its services.

17. Android backup

Depending on the Android version, device settings and Google Account configuration, some local data may be included in Android backup or device-transfer mechanisms.

Data restoration is not guaranteed after uninstalling the application or changing devices.

18. External services

Selected technical information may be processed by Google through AdMob, Firebase Analytics, Firebase Crashlytics, Firebase Performance Monitoring, Firebase Remote Config and Google Play Billing.

These services apply their own terms, security measures and privacy policies.

Mindset Dev Solutions does not directly sell the names, email addresses or phone numbers of CoverShake users.

19. Security and transfers

Reasonable measures are used to limit requested data and protect CoverShake operations.

Google services may process selected technical information on infrastructure located in different countries according to their policies.

No information system can guarantee absolute security.

20. Choices and rights

Users can disable the service, remove display-over-other-apps permission, manage notifications and clear local data through Android settings.

Subject to applicable law, users may request information, correction, restriction or deletion of data controlled by Mindset Dev Solutions.

21. Policy changes

This policy may be updated when features, permissions, integrated SDKs or Google Play requirements change.

The date displayed at the top identifies the latest published version.

Privacy contact

For questions or requests concerning CoverShake and this privacy policy, contact Mindset Dev Solutions.

realityking12u@gmail.com