SaifLab · All app privacy policies
Brickfight Privacy Policy
This policy explains how the Android game Brickfight (“the app”) handles information and the choices available to you. The developer is Bendev soft., which operates the SaifLab studio brand. “We” and “us” refer to Bendev soft. This policy covers Brickfight; other SaifLab games may use different services.
1. Developer and contact
Bendev soft. (SaifLab), Morocco. For privacy questions or requests, email bendevsoft@gmail.com or contact@saiflab.com. Please identify Brickfight in your message.
2. Gameplay and information stored on your device
Brickfight is a single-player game. Playing does not require an account, a player name or an internet connection. The game stores campaign progress, scores, stars, game statistics, saved runs and preferences on your device, together with a local recovery copy. High scores are local; they are not uploaded to an online leaderboard. Brickfight does not offer cloud saves, online multiplayer or chat.
You can remove game progress and preferences through Settings → RESET ALL DATA and its confirmation. Clearing the app’s storage in Android settings also removes its local data, including locally stored advertising and consent preferences. Clearing game data does not delete information already processed by advertising providers.
3. Advertising and information processed by Google
Brickfight uses Google AdMob for banner, app-open, interstitial and optional rewarded ads. Interstitials may appear after a round ends. Choosing WATCH AD in the game-over revive offer can restore three hearts and restart the current round when the ad reward is earned; this is available once per run. You can decline the offer and continue using the game. Ads and rewards depend on an internet connection and ad availability.
Google’s advertising SDK may process:
- IP address, which can indicate approximate location;
- advertising ID, app set ID and, where applicable, identifiers associated with accounts signed in on the device;
- interactions such as app launches, ad taps and video views;
- device, app and diagnostic information, including performance information.
This information supports ad delivery, measurement, analytics and fraud prevention, and personalization where applicable and permitted. Advertising partners identified in Google’s consent form may also process information under the choices and purposes shown there. See how Google uses information from apps that use its services and the Google Privacy Policy.
4. Consent and advertising choices
The app uses Google’s User Messaging Platform (UMP) to check whether a consent message is needed before requesting ads. Where applicable, the message explains the available purposes, partners and choices. Consent information is stored so the SDK can apply your choices.
When Google requires a privacy-options entry point, Settings → AD PRIVACY OPTIONS lets you review or change your choices. This button appears when applicable to your region and consent status. Settings → PRIVACY POLICY remains available in all regions. You can also use Android’s advertising settings to reset or delete your advertising ID, depending on your Android version.
Declining personalized advertising does not necessarily remove all ads or all advertising-related processing. Limited or non-personalized ads may still be available according to your choices and Google’s requirements.
5. Analytics, permissions and app protection
The current Brickfight release does not enable a separate Firebase Analytics or Crashlytics reporting service, Firebase player accounts or cloud gameplay services. AdMob’s own measurement and diagnostics are described above. Brickfight does not ask you to grant access to your contacts, camera, microphone, photos or precise device location.
The app also checks its package identity and debugger state locally to help prevent modified copies from running. These checks do not create an online player account or send a device-integrity report to our servers.
6. Sharing and service providers
Advertising and consent information is processed by Google AdMob, UMP and the applicable advertising partners described in the consent message. Local game saves are not sent to a developer-operated gameplay server. If you email us, we receive your email address and whatever information you include so we can respond. Please avoid sending sensitive information that is not needed for your request.
7. Retention and deletion
Game saves remain on your device until you reset them or remove the app’s local data. Google and applicable advertising partners retain advertising and consent information under their own policies; we do not set a single retention period for that information. Removing local data does not erase records already held by those providers.
We retain support correspondence only as needed to handle your request and meet applicable obligations. To request access or deletion of information you have sent us, email either contact above with the subject “Brickfight privacy request”. We may need enough information to verify and locate the request. For information held by Google, consult its privacy controls and deletion options.
8. Security and international processing
Local saves are stored in the app’s device storage. Google states that data transmitted by its Mobile Ads SDK is encrypted in transit using TLS. No storage or transmission method can guarantee absolute security. Google and advertising partners may process information outside your country under the safeguards described in their policies.
9. Children’s privacy
Brickfight does not offer accounts or chat or ask players to submit their names, ages or contact details. Advertising-related processing is described above. If you are a parent or guardian with a concern about a child’s information in connection with Brickfight, please contact us so we can investigate and address the request with the relevant provider where appropriate.
10. Your rights
Depending on your location, you may have rights to access, correct, delete or restrict the processing of personal information, withdraw consent, object to processing or complain to your local data-protection authority. Use the in-app and Android choices described above or contact us for help. Withdrawing consent does not undo processing that occurred before withdrawal.
11. Changes to this policy
We may update this policy when Brickfight or its services change. The date above identifies the latest version. This page is available at saiflab.com/brickfight/privacy.html.