XB Controller X
This policy covers XB Controller X for Xbox on Android (eu.hetko.controller.xbox), including the release with Pro and advertising. The earlier 26.10.2 test version is described below. Other products have their own pages, listed on the combined policy.
Last updated 26 October 2026 · Controller: Algorion OÜ, Tallinn, Estonia
Your console and Microsoft sign-in
Local discovery, controller input and text entry communicate with the console you choose. Gamepad sessions use Remote Play and Microsoft services. Microsoft handles authentication; credentials needed to reconnect are kept in protected device storage. We do not receive your Microsoft password or attach your sign-in input, tokens, console names, typed text or gameplay to analytics or crash reports.
Microsoft/Xbox account identifiers are used to sign in, list your consoles and connect to them. There is no separate Hetko account, relay or configuration service. LAN remote control works without signing in. XB Controller X is an independent client and is not affiliated with Microsoft.
Who is responsible
Algorion OÜ (trading as Hetko), Tartu mnt 67/1-13b, 10115 Tallinn, Estonia, is the data controller. Contact: hi@hetko.eu.
What stays on your device
Saved console addresses and identifiers, controller layouts, settings and your selected background photo stay in private app storage. A resized background photo is saved without its original camera and location metadata. These app files are excluded from Android backup and are removed when the app is uninstalled.
Usage analytics and campaign measurement
Google Firebase Analytics receives app usage and session events, generated installation identifiers, app and device details, language, approximate region, purchase events and ad-impression revenue. Events describe screens, connection outcomes and durations, console-search counts, sign-in outcomes, layout changes and purchase steps. They do not contain your console address, account identity, text input or gameplay.
Analytics is enabled by default for new installations. A collection preference saved by an earlier version is respected. The current app has no separate analytics switch. Where permitted by your advertising choices, Firebase also uses the Android advertising identifier and Google Play install referrer to measure campaigns and advertising conversions.
In the EEA, UK and Switzerland, Firebase advertising storage, advertising user data and advertising personalisation follow the consent form, including consent to Google, and remain denied until the relevant consent is available. Elsewhere these advertising categories are enabled when analytics is enabled. Advertising choices do not disable ordinary usage analytics. There is no session replay, Amplitude, PostHog or Meta App Events integration.
Crash reports and diagnostics
Firebase Crashlytics receives crashes and unexpected errors, stack traces, generated installation identifiers, app and device details, and recent app events to help us diagnose failures. For unexpected non-fatal errors, our code removes the exception message and keeps its type and stack. We do not attach Microsoft credentials, console identifiers, text input or gameplay to reports.
Crash reporting is enabled by default for new installations, while preferences saved by earlier versions are respected. The current app has no separate crash-reporting switch. When an earlier preference disables reporting, pending reports are deleted from the device. Data already sent requires a separate deletion request. Advertising SDKs also process technical diagnostics and performance data under their own policies.
Advertising and your choices
The free app uses Appodeal to serve banners on the console list and Settings, and interstitials after eligible completed sessions. The consent flow runs before Appodeal starts. Pro removes these ads and stops ad requests; some bundled SDK components may still initialise before the app has resolved purchase status.
Advertising partners process ad impressions and interactions, IP addresses and approximate location derived from them, generated user and device identifiers, permitted advertising identifiers, purchase or conversion information, and technical diagnostics. These are used to deliver and measure ads, operate SDK services and prevent fraud. Partners may share data with their advertising and measurement providers. The app does not request precise location permission or send your Microsoft account identity to ad networks.
The bundled networks are Google AdMob, Amazon Publisher Services, AppLovin, BidMachine, Bidon, BIGO Ads, Chartboost, DT Exchange, InMobi, ironSource, Meta Audience Network, Mintegral, MobileFuse, Moloco, myTarget (VK Ads), Ogury, PubMatic, Smaato, TaurusX, Unity Ads and Yandex, whose SDK includes AppMetrica. Availability depends on network configuration and your region. Audience Network advertising is separate from Meta App Events, which this app does not use.
Where required, the consent form lets you choose how advertising partners use your data. Reopen it in Settings under Privacy choices. The European regulations message covers the EEA, UK and Switzerland; the US states message offers applicable sale, sharing and targeted-advertising choices. Android settings also let you reset or delete your advertising ID. Restricting that identifier does not prevent all technical SDK data collection.
Pro purchases
Google Play handles payment. RevenueCat processes purchase receipts, purchase history and state, and a generated app-user identifier to provide and restore Pro, validate access and analyse purchases. Purchase state is checked automatically; making a purchase is optional. Firebase also records purchase events for analytics and campaign measurement. We do not receive your payment-card details. Microsoft sign-in does not itself grant Pro.
On the device, the app keeps the time of the first successful console session and counts successful sessions to time introductory offers. Pro removes ads but does not disable analytics or crash reporting.
Data recipients and retention
Microsoft provides Xbox services and authentication; Google provides Play, Firebase and AdMob services; RevenueCat handles purchases; Appodeal and its advertising partners deliver and measure ads. Our mail provider processes support messages and attachments you send. These providers may process data outside the EEA; their privacy information describes their processing, retention and international-transfer safeguards.
Local app data remains until you remove it or uninstall. We retain support correspondence as needed to resolve requests and meet legal obligations. Purchase records may need to be retained for refunds, fraud prevention and accounting obligations. Analytics, crash and advertising records follow the relevant service retention settings and provider policies. Uninstalling the app does not by itself erase records already received by a provider.
Request deletion of your data
We delete data we control and request deletion from service providers where we can identify the records. Some accounting, security or fraud-prevention records may need to be retained; we will explain any applicable exception and its retention period when handling your request. A Microsoft account is managed by Microsoft, and advertising providers may require their own identifier or privacy-request process. We will direct you to the relevant provider when needed. Removing an account or uninstalling locally does not delete the Microsoft account.
To request deletion of XB Controller X data without deleting a Microsoft account, email hi@hetko.eu with the subject “XB Controller X data deletion”. Tell us which data you want removed. For purchase records, include the Google Play order ID if available; do not send passwords, sign-in tokens or payment-card details. We may ask for the minimum information needed to locate the relevant records and verify your request.
Your rights
Under the GDPR you can ask for access, correction, deletion, restriction or portability, and object to processing based on legitimate interest. Mail us and we answer within one month. You may also complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon).
Earlier test version 26.10.2
Version 26.10.2 only ran the advertising consent flow and did not request or show ads. Firebase Analytics and Crashlytics were off until enabled using the separate Usage analytics and Crash reports switches. Firebase advertising-ID collection and advertising personalisation were disabled. Preferences saved by that version are respected when you update.
Children, security and changes
The app is not directed at children under 13. Internet service requests use encrypted transport. No system is completely secure. We update this page when the app changes how it processes data.