BLAZE SPORT

Legal & Privacy

Privacy Policy

This Privacy Policy explains how the Blaze Sport Android application handles information when you use its native sports features or a remotely configured website displayed inside the app.

Effective date: August 12, 2026

No native account requiredThe native sports features do not ask for your name, email address, phone number, or login.
Local by defaultNotes, favorites, stopwatch sessions, and personal analytics remain on your device.
Web content is separateAn activated website may use cookies, request permissions, or process data under its own privacy terms.

1. Scope and developer

This policy applies to Blaze Sport (Android package com.tacktikcwin.app), developed and published by vecerulana-pixel ("we," "us," or "our"). Third-party websites and services available through the app are governed by their own terms and privacy policies.

2. Information handled by native features

The native sports features do not create user accounts and do not directly request your name, email address, phone number, contacts, payment details, advertising identifier, or health data.

The following content is created or stored locally on your device:

  • notes that you write in the app;
  • matches and news items that you mark as favorites;
  • stopwatch durations, lap times, and the time a training session was saved;
  • personal statistics calculated from your locally stored activity;
  • cached match schedules and news items downloaded for offline access; and
  • the latest valid website address opened in the in-app browser.

This locally stored content is not uploaded to us and is not used to identify you.

3. Network access and third-party services

Blaze Sport uses an internet connection to download sports schedules from TheSportsDB and sports headlines from BBC Sport. When you open a news article, the destination website's own terms and privacy policy apply.

The app also reads the url configuration value from Firebase Realtime Database. If that value is a valid web address, the app stores it locally and displays the website in an embedded browser. Google Firebase may process connection and technical information needed to provide this service under the Firebase Privacy and Security documentation.

An activated website may receive information you submit to it, use first-party or third-party cookies, request access to location, camera, or microphone, initiate file uploads or downloads, and process standard network information. That processing occurs directly between your device and the website and is governed by the website operator's privacy policy.

As with any internet request, these service operators and network infrastructure may automatically receive limited technical information such as your IP address, request date and time, and a standard network user-agent value. We do not receive, combine, or retain that technical information.

For more information, review the TheSportsDB Privacy Policy and the BBC Privacy and Cookies Policy.

This policy page is hosted by GitHub Pages. When you visit it, GitHub may process standard connection and usage information under the GitHub General Privacy Statement.

4. How information is used and shared

Local native information is used only to provide the features you request: saving notes and favorites, recording stopwatch sessions, calculating personal analytics, restoring the latest embedded page, and making downloaded content available offline.

We do not sell, rent, monetize, or upload your locally stored native notes, favorites, or stopwatch history. Information entered into an activated website is sent to that website rather than to the native sports data store and may be processed or shared as described by the website operator.

5. Device permissions

Blaze Sport declares internet and network-state access to retrieve native content, Firebase configuration, and web pages. The embedded browser can request approximate or precise location, camera, and microphone access when a website needs those capabilities. Android displays a runtime permission prompt, and access is not granted unless you approve it.

The file chooser can open files you select or capture a new photo. Downloads are handled by Android DownloadManager. A legacy write-storage permission is declared only for Android 9 (API 28) and earlier. The app does not request contacts, call logs, or message access.

6. Security

Blaze Sport stores native local information and the cached website address in the app's private Android storage, which is isolated by the operating system. Supported native service requests use HTTPS. The remote configuration may specify either an HTTPS or HTTP website; traffic to an HTTP website is not encrypted in transit. Website cookies are managed by Android WebView. No security method is perfect, so review the active website before submitting sensitive information.

7. Retention and deletion

Notes, favorites, cached native content, stopwatch sessions, the latest embedded page address, and WebView site data remain on your device until removed through available controls, Android settings, website controls, or by uninstalling the app. Clearing app storage or uninstalling Blaze Sport removes app-managed local information from that device. Data already submitted to an activated website must be deleted through that website operator.

8. Children's privacy

Blaze Sport's native sports features are intended for a general audience and are not directed to children under 13. Any activated website must be evaluated separately by its operator. If you believe a child has provided personal information through a third-party service, please contact that service and notify us using the contact method below.

9. International processing

Firebase, third-party sports and news services, and an activated website may operate servers in different countries. Their handling of information is governed by their own privacy policies and applicable laws.

10. Changes to this policy

We may update this Privacy Policy when Blaze Sport's features, data practices, or legal requirements change. The revised policy will be published at this same URL with an updated effective date. Material changes will be reflected in the app or its store listing when appropriate.

11. Contact and privacy requests

For questions, concerns, or privacy requests, contact the developer through the Blaze Sport privacy inquiry form on GitHub. Please do not include sensitive personal information in a public issue.

Google Play Data Safety summary

This summary is provided for clarity and must remain consistent with the declarations submitted in Google Play Console.

CategoryBlaze Sport practicePurpose
Native sports data collected by the developerNone directlyNative features operate without an account
Firebase configuration lookupFirebase may process connection and technical informationRetrieve the optional website address
Embedded website dataDepends on the active website and user interactionProvide the remotely configured web experience
User-generated contentStored only on the deviceNotes and personal organization
App activityStored only on the deviceStopwatch history and personal analytics
Optional sensitive permissionsLocation, camera, and microphone only after an Android permission promptWebsite-requested functionality
Data encrypted in transitNative services use HTTPS; a configured HTTP website is not encryptedNetwork content retrieval
Account deletionNo account is createdLocal data can be removed in the app, Android settings, or by uninstalling
Note: Google Play Console declarations must also account for the final production build and any SDKs or services added after this policy was published.