BetFlag Privacy Policy

BetFlag Privacy Policy

hazeljohn177@gmail.com

1. General provisions

1.1. This Privacy Policy (hereinafter referred to as the Policy) applies to the BetFlag mobile application (hereinafter referred to as the Application), which provides users with information about sports matches, news and records.

1.2. Using the Application means the user's unconditional consent to this Policy and the conditions specified therein.

1.3. In case of disagreement with the terms of this Policy, the user must stop using the Application.

2. Data collection and processing

2.1. The Application DOES NOT collect personal data of users, including but not limited to:

  • First name, last name, patronymic
  • Email address
  • Phone number
  • Geolocation data
  • Device Information
  • Application Usage History
  • Users' sports preferences

2.2. The application does NOT require registration and does not create user accounts.

3. Working with external APIs

3.1. The application interacts exclusively with external APIs to obtain:

  • Schedules of sports matches
  • Current sports news
  • Updates about sports events

3.2. All API requests are made on behalf of the Application, not on behalf of a specific user.

3.3. User data is NOT transmitted to external API services as part of receiving sports information.

3.4. Third-party API data collection:

The Application uses external services that automatically collect technical information with every API request made by the Application:

SStats API (api.sstats.net):

With each request for sports data, SStats servers automatically collect:

  • IP address of the Application server making the request
  • Request timestamp with exact date and time
  • HTTP headers including:
  • User-Agent (identifying the Application and system information)
  • Accept-Language (language preferences)
  • Accept-Encoding (supported compression methods)
  • Host header and connection details
  • Request details: specific endpoints accessed, query parameters used
  • Response metrics: processing time, data volume transferred, HTTP status codes
  • Geographic location determined from IP address
  • Request frequency and usage patterns

NewsAPI (newsapi.org):

With each request for news content, NewsAPI servers automatically log:

  • IP address and network routing information
  • Complete HTTP request headers containing:
  • User-Agent string (application/browser details, operating system)
  • Referrer information
  • Accept headers (supported content types and languages)
  • Request timestamp and session duration
  • API endpoint usage: which news categories, search queries, date ranges requested
  • Response data: article count retrieved, processing time
  • Device fingerprinting data derived from headers
  • Geolocation inferred from IP address
  • Request volume and rate limiting metrics

3.5. Frequency and scope of external data collection:

  • This technical data is collected with every single API request made by the Application
  • Collection occurs automatically without additional user consent or notification
  • Data is processed in real-time and stored in external service logs
  • No user interaction is required for this data collection to occur

3.6. Important clarifications about external data collection:

  • These external services collect technical data about API requests automatically with each call
  • The data collection happens at the HTTP protocol level and cannot be prevented
  • Users' personal information is not transmitted, but technical device/network data is inherently collected
  • The Application acts as an intermediary, but request metadata is still logged by external services
  • This data collection occurs regardless of user actions - simply using the Application triggers it

3.7. The Application may temporarily cache information received from the API solely to improve performance and provide offline access to content.

4. Transfer of information to third parties

4.1. Since the Application does not collect users' personal data, such data is not transferred to third parties.

4.2. The application can interact with the following types of external services:

  • SStats API (api.sstats.net) for sports match information and statistics
  • NewsAPI (newsapi.org) for getting sports news
  • Content delivery services to optimize data loading

4.3. All interactions with external services are of a technical nature and do not include the transfer of user data.

4.4. External service data practices:

While the Application does not share user data, the external API providers have their own privacy policies regarding technical data they collect from API requests. Users are encouraged to review:

5. Information storage

5.1. Users' personal data is not stored because it is not collected.

5.2. The application may temporarily store on the user's device:

  • Cached information about sports matches
  • Sports news for offline viewing
  • Information about sports records
  • Application Interface Settings
  • Technical information for the correct operation of the application

5.3. All stored information is of a technical nature and does not allow identification of the user.

6. Security measures

6.1. Since personal data is not collected, no special protection measures are required.

6.2. The application uses standard security protocols to interact with external sports data APIs.

6.3. All requests to external services are made via secure communication channels (HTTPS).

6.4. API security:

  • All API communications use encrypted HTTPS connections
  • API keys and credentials are securely stored and not exposed to users
  • Request frequency is managed to comply with API rate limiting policies

7. User Rights

7.1. Since personal data is not collected, users do not need to:

  • Request access to your data
  • Request data deletion
  • Perform data porting

7.2. The User can delete the Application from the device at any time, which will automatically delete all technical information related to the operation of the Application.

8. User Contact

8.1. The Application does not send notifications, letters or other forms of communication with users.

8.2. Push notifications are not used to contact users or collect information.

9. Sports content

9.1. All sports data is obtained from public sources and does not contain confidential information about athletes or teams.

9.2. The application does not track users' sports preferences and does not create personal recommendations.

9.3. Information about watched matches or news is not saved or analyzed to create a user profile.

10. Policy Changes

10.1. This Policy may be changed unilaterally by the developer.

10.2. Users will be notified of significant changes via an App update.

10.3. Continued use of the Application after making changes means acceptance of the new version of the Policy.

11. Contact Information

11.1. For all questions regarding this Privacy Policy, users can contact the developer at the following email address: hazeljohn177@gmail.com

11.2. The Developer undertakes to review all requests within a reasonable time and provide an exhaustive response.

12. Additional Disclosures

12.1. This Application is designed with privacy-by-design principles, minimizing data collection and processing.

12.2. External API providers may update their data collection practices independently of this Application.

12.3. The Application developer does not have access to or control over data collection practices of third-party API services.

12.4. By using this Application, users acknowledge that while the Application itself does not collect personal data, the technical nature of internet communications means that external API services will automatically receive and log certain technical information with each request made by the Application on behalf of users seeking sports and news content.


Report Page