RCON Manager privacy policy

RCON Manager is provided by Xelora. It connects your phone directly to game servers you choose. This policy explains the app’s local storage, Google Play subscriptions, advertising and optional support reports.

Your servers and local data

Server profiles, connection settings, commands, history and macros are stored on your device. Saved server passwords use Android secure storage. Profile exports exclude passwords; you control where exported files are saved and shared. RCON Manager does not upload your server passwords, command history or macros to Xelora’s billing service or advertising services.

Connecting to a server sends the credentials and commands required by that server’s protocol directly to that server. Its operator may receive your IP address, commands and other connection data. Some game protocols do not encrypt connections: use trusted networks or a suitable secure tunnel. The server operator’s own privacy practices apply.

Subscriptions and purchase verification

Google Play handles checkout, payment methods and subscription management. Xelora does not receive your card details. Free features do not require a purchase-verification account. In versions that offer Google sign-in, sign-in links paid purchases to your RCON Manager account so you can restore them on another device. Use the same sign-in account when restoring. This may be different from the Google account used to pay in Google Play.

When you sign in, the app temporarily sends a Google identity token to Xelora’s verification service over HTTPS. The service validates it with Google’s signing information and uses your Google account’s stable identifier to derive an app-specific, keyed pseudonymous identifier. It stores that mapping with a random RCON Manager buyer identifier and purchase-account binding. It does not store your Google identity token, name or email address. The email shown in the app is stored only on your phone, encrypted with the local account information.

To verify a purchase, the app sends its package and product identifiers, a Google purchase token, a pseudonymous installation identifier and a verification-session credential over HTTPS. The service checks the purchase with Google and stores encrypted purchase tokens, purchase-token hashes, replacement links, product and billing-period identifiers, subscription status, acknowledgment status and verification/expiry times. A random purchase-account binding is supplied to Google Play to associate a purchase with your RCON Manager account. These billing identifiers are not passed to the advertising service.

The service stores hashes of verification-session credentials, along with their account, installation and validity information. The app stores its session credential encrypted using Android secure storage. Google identity tokens are used only during sign-in; session credentials and purchase tokens are excluded from application request logs. The service returns a signed entitlement, valid for at most 15 minutes in versions using account-based verification, so the app can briefly confirm paid access without contacting the service. The app does not extend that entitlement while offline.

Earlier versions without Google sign-in use an identifier derived from Android’s app-scoped device identifier to verify purchases. Those versions do not create a Google-linked RCON Manager account. Contact support if you need help with records from an earlier version.

Designated app reviewers may receive complimentary access through a review code without Google sign-in or payment. The service stores a hash of that code, random reviewer and grant identifiers, the app identifier and access level separately from customer and purchase records. The app holds the entered code only in memory; it is cleared when you end review access or restart the app. Short-lived signed access is bound to the installation and is renewed online while the code remains authorized. Codes and signed access are excluded from application request logs. Earlier account-based review access uses an app-specific buyer identifier. Complimentary access is not a purchased subscription.

Advertising and privacy choices

The Free plan is supported by Google AdMob banner advertising. Pro and Unlimited remove the app’s banner ads. Builds with advertising disabled do not request ads.

When advertising is enabled and eligible to run, Google’s advertising SDK may collect and share IP addresses and approximate location derived from them, advertising or app-set identifiers, app and ad interactions, and diagnostic/performance information. Google and its advertising partners use this information for advertising, measurement, analytics and fraud prevention. The app does not request GPS location, contacts, camera or microphone access for advertising.

Where required, Google’s consent form provides consent, refusal and options to manage purposes and partners. You can revisit available choices in the app’s advertising privacy settings. Android settings also let you reset or delete your advertising ID. Advertising requests follow the consent SDK’s eligibility decision; refusing personalized advertising does not necessarily remove every form of advertising.

Support and feature requests

The app prepares an email draft or text you can copy. You decide whether to send it. Optional diagnostic details are limited to the app version, device model, Android version and plan; the app does not automatically attach server credentials, command history or purchase tokens. If you send a report, Xelora receives your email address, sender name if included by your email app, message and any information you choose to include, and uses them to investigate and reply. Support correspondence is retained as needed to handle the request and maintain support records.

Security and your choices

Billing and advertising services use HTTPS. Access to Xelora’s verification credentials and purchase records is restricted. Hosting infrastructure may process IP addresses and request/security metadata to operate and protect the service; request bodies and purchase tokens are excluded from application request logs.

You can remove saved profiles in the app. Clearing Android app storage or uninstalling removes local app data; exported files must be deleted separately. Removing the app does not cancel a Google Play subscription. Manage or cancel your subscription in Google Play.

Delete your account and account data

You can delete your purchase-verification account from the account controls in RCON Manager, or use our RCON Manager account-deletion page without reinstalling the app. Sign in with the same Google account used inside RCON Manager and separately confirm deletion. For help accessing the account or requesting deletion, email support@xelora.host. We may need to verify that the request relates to your data.

Confirmed deletion removes the active verification account, its sign-in sessions and encrypted purchase tokens. Limited pseudonymous purchase-ownership records remain as described below. Signing in again with the same Google account creates a new RCON Manager account identifier and lets you restore a valid subscription when Google Play returns the purchase and our service verifies it again. Recreation alone does not grant paid access or restore deleted sessions and account data. A previously issued signed entitlement on another device may remain usable until its short validity period ends. Your saved game servers and other local app data remain on your devices until you remove them.

Account deletion does not cancel a Google Play subscription, stop future charges, delete your Google account or remove records held by Google. Cancel any subscription in Google Play if you want future billing to stop.

We retain limited pseudonymous purchase-ownership records after account deletion: the app-specific keyed Google-account identifier, an opaque former buyer identifier and purchase-account binding, purchase-token hashes, product/billing-period and verification metadata, and replacement links. This is pseudonymous personal data, not anonymous data. It prevents a stolen or deleted purchase being claimed by another account and allows secure recovery by the same Google sign-in. It includes no raw Google account identifier, email, Google identity token or usable purchase token. These records have no fixed automatic deletion schedule. Other verification records are retained while needed to operate purchase verification and restoration, prevent fraud, resolve disputes or meet legal obligations. Removing data from the active database does not guarantee immediate physical removal from database recovery files or backups; those copies may persist through their retention lifecycle. Contact support for information about a specific request.

The account-deletion webpage uses Google Identity Services to confirm your identity. Google receives information needed to provide its sign-in service, such as your IP address and browser information. The page uses a randomly generated verification identifier and holds sign-in/session credentials only in page memory. It attempts to revoke its verification session when you cancel or leave; closing a browser or losing connectivity can prevent that request from completing. No advertising is displayed on that page.

For access, correction or deletion of other information held by Xelora, contact support@xelora.host. Do not send passwords, private keys, payment details or purchase tokens in support messages. Google handles requests concerning information it holds under its own policies.

Third-party policies and changes

See Google’s privacy policy and Google’s advertising information for Google’s practices and controls. Data may be processed in countries where Xelora’s infrastructure, Google or their service providers operate. We may update this policy when the app or its services change; the effective date above identifies the current version.