Privacy policy

App versions

The 1.0 rewrite uses Sentry for diagnostics on Android and iOS. Version 1.0.6 added the favorites sync and notification handling described below. Version 1.0.7 adds calendar export. Older Android 0.x versions can still be in use and have different Firebase integrations, described below. Check your installed version when you read this policy.

The app does not require an app account or sign-in credentials. The current rewrite has no in-app advertising SDK or in-app purchases.

Data on your device

The app saves your favorites, settings and cached public esports data in a local database and operating system preferences. These records let the app remember your choices and display saved content.

Favorites also determine which teams and matches the app requests from remote services. Native widgets can make these requests during background refresh. Team or match identifiers can therefore leave your device as part of these requests.

Android backup is enabled. Depending on your operating system settings, backups may retain app data outside the device. Your operating system provider controls that backup service.

Favorites sync and notifications

The app generates and stores a UUID, an app identifier used to associate requests and saved favorites. It is not a verified identity for a person. It can change or be restored from a backup, so it does not reliably identify one person or one physical device. The app still stores this identifier and sends it to the backend with related requests.

On iOS, the app also saves the UUID in Apple's iCloud key-value storage when available and may reuse a cached iCloud UUID after installation. This does not require a separate app sign-in, and restoring the same UUID is not guaranteed.

The app sends the identifiers of your favorite teams, matches, players and events to the backend under this UUID. The backend stores them to provide favorite match results and support notifications. Favorites sync runs independently of notification permission and the live updates setting.

For supported notification features, the backend receives a push token, platform and live updates setting associated with the UUID. iOS Live Activities use Apple Push Notification service. Android uses Firebase Cloud Messaging, including notification tokens and topic subscriptions based on favorites. A token can be registered or retained with live updates disabled; disabling live updates does not delete all related records or stop favorites sync.

Apple and Google process the data needed to provide these services. See Apple's privacy policy, Firebase's privacy and security information and Google's privacy policy.

Calendar export

You can export a single match or an event's scheduled matches to your calendar. On iOS, the app requests full calendar access when you choose to export. It uses this access to save matches and read previously exported match events so repeated exports can update them and avoid duplicates. Full access permits reading other calendar events too. When recovering a saved match entry, the app can read nearby events to find the saved match's link.

The iOS app keeps event identifiers and previously saved match start times in local operating system preferences. The calendar export feature does not upload calendar contents to our backend. On Android, the app creates a temporary .ics file and shares it with the app you choose. It does not request permission to read or write your calendars directly.

Your calendar provider or the app you choose may sync exported events according to its own settings and privacy policy. You can deny or revoke iOS calendar permission in your device settings and continue browsing the app. Exported events remain in your calendar until you delete them. Revoking permission or uninstalling Valorant Esports does not delete those events.

Network requests

The app uses HTTPS for its esports API and diagnostic services. Content and image addresses can also be supplied by remote services; older Android versions permit unencrypted HTTP requests, so HTTPS is not guaranteed for every externally supplied image or link. API and image servers receive the information needed to handle each request. This can include your IP address, network and device request metadata, the public content you request, and search terms you submit.

These requests provide match scores, events, rankings and other app content. The remote services apply their own data handling policies. Opening an external link takes you to a service that has its own privacy policy.

Diagnostics and feedback in the 1.0 rewrite

Sentry receives crash, error, app hang and performance reports to help find faults and improve reliability. Reports can include app, device and operating system details, installation and session identifiers, technical logs, and breadcrumbs that record events before a fault.

The app also sends sampled session replays. A replay records parts of an app session to help reproduce a problem. Replay text and images are masked. Automatic screenshot attachments are disabled, but view hierarchy information is enabled. Default personal information collection is disabled in the Sentry configuration. These safeguards reduce exposure; they do not guarantee that reports contain no personal information or that reports are anonymous.

Network diagnostic descriptions use templates. Database tracing records operation identifiers and whether an operation reads or writes data. It does not include raw SQL statements or their bound values.

If you send feedback in the app, Sentry processes the feedback you submit. If you send email, the email service processes your message and contact details. Only include information needed to explain the issue. Do not send passwords or other sensitive information.

See Sentry's privacy policy for information about the provider.

Older Android versions

Older Android 0.x versions include Google Firebase Analytics, Performance Monitoring and Cloud Messaging. Analytics collects app usage events and app-instance identifiers, can collect advertising identifiers where available, and derives approximate location from IP addresses. Cloud Messaging uses installation and notification identifiers and subscription information to deliver notifications.

Firebase Performance collection is enabled when the older app starts, overriding its manifest setting. It collects performance measurements and device metadata and uses IP addresses to associate performance events with countries. Firebase Crashlytics collection remains disabled in the older app configuration. The 1.0 rewrite uses Sentry for diagnostics. Current Android versions also use Firebase Cloud Messaging for notifications, as described above. See Firebase's privacy and security information and Google's privacy policy for details of their services.

This website

This website does not add analytics trackers or cookies. Fonts and site assets are hosted with the website.

If you join the iOS TestFlight list, we store the email address you submit, the signup time and whether an invitation has been sent. We use this information only to manage TestFlight invitations. When we invite you, we share your email address with Apple so it can deliver the invitation. We do not use the list for marketing.

If you send a support request through this website, we store your email address, request category and platform, subject, message, any app version or device details and optional attachment you provide, the submission time and the request status. We use these details to investigate the request and reply to you. Support requests and the TestFlight list are available to the developer through a private management page; they are not published on the website. We do not use support email addresses for marketing.

The hosting and network infrastructure still processes ordinary connection and request metadata, such as IP addresses, requested paths and browser request information, to deliver and protect the site. Technical logs may contain connection or error metadata. This policy does not treat a website visit as anonymous.

Providers and data handling

Data goes to the providers needed for the functions described above, including content and image services, Sentry, Firebase Cloud Messaging, Google services used by older versions, Apple iCloud, Apple Push Notification service, Apple TestFlight, hosting infrastructure and email services. Providers may process data in countries other than your own.

HTTPS protects traffic sent to the app’s API and diagnostic services in transit. Older versions can also load externally supplied content over HTTP, which does not provide that protection. Masking and limited diagnostic detail help reduce the information sent. No storage or transmission method can guarantee complete security.

Retention and your choices

Local favorites and settings remain until you change or remove them, clear app data, or uninstall the app. Cached content can be replaced as the app refreshes. Operating system backups have separate retention and deletion controls.

Removing a favorite asks the backend to remove that favorite during sync. Changes may wait for a successful connection. Turning off live updates changes notification delivery; it does not erase the UUID, synced favorites or every push registration. Uninstalling the app does not itself send a request to delete backend records or remove an iCloud UUID. Contact us to request deletion of backend information; your email address alone may not identify records stored under an app UUID.

Diagnostics and support messages are retained for the purposes described in this policy, subject to the configured limits of the services used. There is no single fixed retention period for all records. Removing the app does not itself delete reports already sent to a provider or copies in an operating system backup.

We retain website support requests while needed to handle the request and follow up on related problems. You can ask us to delete your request by emailing shreyansh@valesports.app.

We keep TestFlight signups while the invitation list is active. You can ask us to remove your email address at any time by writing to shreyansh@valesports.app.

You can remove favorites, change settings, clear app data or uninstall the app. Manage backups and notification permissions through your operating system settings. The current app does not provide a diagnostics consent toggle.

Email shreyansh@valesports.app to ask about access, correction or deletion of information, or to raise a privacy concern. State your app version and enough detail to locate the relevant information. Reports with session or installation identifiers may not be identifiable from your email address alone. We may need further information to identify a record and confirm your request. Your rights depend on the law that applies to you.

Changes and contact

This page will be updated when the app or its data practices change. The date at the top shows the latest revision.

Developer: Shreyansh Lodha, staticvar.dev, India.
Support and privacy: shreyansh@valesports.app.

Read the terms of service or return to the app website.