BRUTAL Optimizer for Android — Privacy Policy

Effective 8 July 2026 · Last updated 25 September 2026 · App renamed to BRUTAL Optimizer 2 August 2026 (previously Truepath); the product, the company and these practices are unchanged. This policy is specific to BRUTAL Optimizer for Android. BRUTAL Optimizer for Windows and this website are a different product with different data practices and its own privacy policy, published with that product.

Who we are

BRUTAL Optimizer is operated by ARHAS INDIA (OPC) PRIVATE LIMITED (CIN U62013TS2026OPC220112), a One Person Company incorporated in India under the Companies Act 2013 on 27 July 2026, registered office SY No. 4A & 4/AA, Peeramcheru, Golconda, Hyderabad 500008, Telangana, India. Under India's Digital Personal Data Protection Act, 2023 (DPDP Act), the company is the data fiduciary for the personal data described in this policy — the entity that decides why and how your personal data is processed. Contact: legal@brutaloptimizer.com.

What BRUTAL Optimizer does

BRUTAL Optimizer is a game-connection tool. When you tap Connect, the app establishes a VPN tunnel on your device (using Android's VpnService and the WireGuard protocol) and routes only the game you selected through a BRUTAL Optimizer relay server near your region. The tunnel carries the game's IPv4 traffic; any IPv6 the game uses travels over your normal connection, not the relay. Nothing else on your phone enters the tunnel — no browser, no other apps, no background traffic. Disconnecting (or closing the app) returns the game to your normal connection.

What "the game's traffic" means, precisely

Worth spelling out, because "we only route your game" can be heard as "only the match packets". While a game is routed, all of that game's IPv4 traffic takes the relay path — not just the match server, but every IPv4 host that app talks to, its login, patch, asset, store and telemetry endpoints included. That is deliberate rather than incidental: the tunnel is a full forwarder, and carrying the whole app is what keeps the game working instead of half-broken. It is also why the tunnel is capped at one app in the code itself — a request to route everything is refused if there is no single app to scope it to, rather than quietly becoming a device-wide VPN.

Two consequences follow, and both are yours to know before you connect:

• While a game is routed, its DNS is answered by 1.1.1.1 — Cloudflare's public resolver, which the app sets on the tunnel. The reason is that a relayed connection whose name lookups still go to your carrier's resolver is a split we would rather not create; inside the tunnel, the lookups travel the same path as the traffic they're for. Those lookups reach Cloudflare from the relay's IP address rather than yours, and Cloudflare answers them under its own public-resolver privacy policy. We don't log or inspect them. This applies to the routed game only: every other app on your phone — and BRUTAL Optimizer itself — keeps using your phone's normal resolver, and the override ends when you disconnect.
• The game's IPv6 stays on your own connection. Our relays are IPv4, so rather than blackhole IPv6 (which strands a game on an IPv6 carrier mid-load), we deliberately let it fall through to your carrier. So any IPv6 that game uses is not relayed, is not boosted, and still carries your own IP address.

What the tunnel does and doesn't see

• Carried, not recorded. Relays forward your game's encrypted packets. We don't inspect, record or sell the contents of your traffic, and we don't record which servers it reaches; the only record of the traffic itself is the data count described below.
• Connection metadata. When you connect, our control plane records which relay your device is authorized on and when — a short-lived lease that lapses within about an hour of your app's last check-in, so seats free up. The app also sends the game you selected so the per-title ban-safety rules can be checked; it is not stored with the lease. The relay sees your device's IP address; that is how any VPN works.
• Data counts. Relays report how much data each connection sent and received — a byte count only, with no content and no destinations — against that connection's WireGuard key, which the app generates in memory and discards when the app closes. We keep daily totals for about 100 days to plan relay capacity, then delete them. An unusually heavy day can also be noted in our operations log, with only the first few characters of the key. The key is linked to your account only through the relay lease, which lapses within about an hour.
• Relay locations — and where we have none. Relays are datacenter servers, currently in regions such as India (Chennai, Mumbai, Bangalore, Delhi), Singapore, Jakarta, Tokyo, Seoul, Frankfurt, Dallas, São Paulo and Bahrain. BRUTAL Optimizer only routes you through a relay in your own broad region (e.g. South Asia for Indian players), never across a ban boundary — and titles that are locked to a market (like BGMI in India) only ever use a relay provably in that exact country. Today every South Asia relay is in India. The app is available worldwide but the fleet is not: there is no relay in Oceania or Africa, and none in any region not named above. Where we have no relay in your region the app says so and leaves you on your direct connection — and because that check runs before any relay is asked for a seat, no tunnel is established and there is no session and no connection metadata to record.
• Countries where we do not offer routing. Routing (Smart Route) is not offered in a short list of countries where VPN use is restricted by law or comprehensive sanctions apply. When the app asks for the relay list or a relay seat, our server compares the country Cloudflare reports for your connection with that list. The check starts in an observation mode that refuses nobody. In that mode, if an account with a paid subscription that includes routing (Ultra) asks for a relay seat from one of those countries, we record the account's licence key (the identifier of your subscription), the country, which app the request came from (Android or Windows), when it was first and last seen, and how many times. We use that record only to contact those customers before routing stops in their country and to arrange a refund. It is deleted 90 days after it was last updated, and when you delete your account. Once we stop offering routing in a country, the app says "Smart Route isn't available in your country" and leaves your game on your direct connection; the request is turned away before your account is looked up, so nothing is recorded against it, and we keep only an anonymous count per country.
• Measurements. The app measures latency (ping) from your phone to relays and shows you the real numbers. Session records ("Route Receipts") are stored locally on your phone and are erased when you sign out or delete the app's data.

What the app checks on your phone

Two on-device checks deserve naming plainly rather than being left for you to discover: one because it sounds broader than it is, and one because Android classes it as a special access permission.

• Which games from our catalog you have installed. To build the "My Games" list, to pre-select a sensible title, and to refuse connecting a game you don't actually have, the app asks Android whether each title in the BRUTAL Optimizer catalog is installed and launchable. Being precise about what that involves, because the manifest is public and we would rather you read it from us: the app does not request QUERY_ALL_PACKAGES, the permission Google reviews specifically because it exposes your whole app list. It does declare the ordinary launcher visibility that Android 11+ requires in order to open an app — without it, the "Open Game" button silently does nothing — and that visibility is not narrowed to our catalog, so in principle the app could see which launchable apps you have. What it actually does with it is bounded and checkable: it asks about the game packages in the BRUTAL Optimizer catalog, and nothing else. It builds no inventory, and the answer never leaves your phone — it only draws the picker. The one game package that reaches our servers is the one you boost, sent with the connect request so the ban-safety rules can be checked; it is not stored with the lease.
• "Usage access" (PACKAGE_USAGE_STATS) — optional, off unless you grant it yourself. Connecting while a match is already running would move that game's open connections onto the relay's IP mid-match and drop you out of it. To avoid that, the app can check whether the game you selected is the app currently in the foreground. Android puts that behind a special access you grant yourself in Settings ▸ Usage access. The app never asks you for it and never opens that settings page — the permission is declared only so that the toggle exists for you to find, and unless you go and grant it deliberately, the app simply never has this answer. When it is granted, the app reads recent foreground/background events, discards every event that is not the game you picked, and reduces them to one yes / no / can't-tell answer that stays on the device. We do not build, store, or transmit a record of what you use your phone for, and none of this is sent to us or to anyone else. When it is not granted the answer is "can't tell", which blocks nothing — the app connects exactly as it would otherwise. This is the whole use: it is not used for analytics, advertising, or anything you see in the app.

Your account

• Signing in. You can sign in with your email address (a one-time 6-digit code — no password) or with Google Sign-In. Depending on the build you installed, Discord and Sign in with Apple may also be offered — each is shown only when that provider is configured into that build, so a sign-in button you can see is one that works. However you sign in, your email is your account identity. Google and Apple give us your email and display name; Discord gives us your Discord account's email and username. We store the email to operate your account, your device list, and your subscription. We don't send marketing.
• Name and phone. A display name is collected at signup; a phone number is optional. Both are stored with your account; the app does not display or use the phone number.
• Devices. Your account lists the devices signed into it (for the device cap). We store a device name (your phone's model), platform, and a one-way hashed device identifier (derived from Android's app-scoped SSAID) so a reinstall reuses the same device slot instead of consuming a new one. The raw identifier never leaves your phone.
• Delete your account. Profile → Delete account removes every device on your account and our copy of your email, name and phone. Local receipts are erased too. If you have (or had) a paid subscription, a de-identified billing record (subscription id, plan and dates — no email, name or phone) is retained for accounting and fraud prevention; cancel billing itself separately with the payment provider. Uninstalled the app? Email legal@brutaloptimizer.com with the subject "Delete my account" from your account email and we'll do the same deletion server-side — no reinstall needed. (This page, anchor #delete-account, is the deletion URL for the Google Play Data safety form.)

Deleting some of your data without closing your account

You do not have to delete your whole BRUTAL Optimizer account to get rid of data you would rather we did not hold. There are two routes, and both are free.

• Remove a device yourself, in the app. Profile → Your devices → the bin icon next to any device. That erases our record of that device — its device id and the hashed device fingerprint we use to stop one account being shared across many phones. Any relay lease it still holds lapses within about an hour. Your account, your email and your subscription are untouched. Removing the device you are currently using also signs that device out.
• Ask us to erase something specific. Email legal@brutaloptimizer.com from your account email with the subject "Delete my data", and say what you want removed — for example your name or phone number, a support conversation, or your device history. This is the correction-and-erasure right described under Your rights below. We verify that the request really comes from you (normally by confirming you control the account email) before we act, we acknowledge within 48 hours, and we resolve within 30 days.

What we keep even after a partial-deletion request, and why. Two things do not go, and we would rather say so here than surprise you: if you have ever held a paid subscription we retain a de-identified billing record (subscription id, plan and dates — no email, no name, no phone) for accounting and fraud prevention; and our hosting provider's standard request logs (IP and user agent) age out on Cloudflare's own retention schedule, which we do not extend or export. Deleting data here does not cancel a subscription — on Android, cancel that in Google Play; on the desktop, with the provider you paid.

This section — #delete-data on this page — is the data-deletion URL for BRUTAL Optimizer (published by ARHAS INDIA (OPC) PRIVATE LIMITED) in the Google Play Data safety form. To delete the entire account instead, see Delete your account above.

Support requests

If you use Help → contact support in the app, we receive what you send: your message, the category you picked, your app version, an email address so we can reply — the box is pre-filled with your account email and you can clear or change it before sending — and device diagnostics only if you switch them on, which is off by default. The diagnostics are shown to you in full beforehand and are just this: app version, device model, "Android", and your plan. Nothing else about your device is attached. A second switch, also off by default, attaches this phone's recent connection results: the last 20 Connect results, route endings and app errors the app noted on your phone (what happened, which of our relays, when, and for an error one line with personal details and game names removed). You can read the full text in the form before you send, and copy it without attaching it. Support tickets are kept while we work on them and for a reasonable period afterwards so repeat issues have context; ask us to delete a ticket and we will. If you gave an email, it's used to acknowledge and answer that ticket — nothing else.

Crash reports and connection results (optional, off unless you say yes)

The app can send us two kinds of anonymous report, and only once you have said yes. It asks once, on the Home screen, after the first Connect that failed for a reason other than your own choice ("Help us fix connection problems?"), and you can change your answer at any time in Profile → "Send crash reports and connection diagnostics". Until you say yes, it sends neither.

• Connection results. Counts of how each Connect attempt ended (for example connected, relay full, no answer from the relay, or cancelled by you), how each route ended (for example you disconnected, or the relay stopped answering) with its length in broad bands (under 2 minutes, 2–15, 15–60, over 60 minutes), which of our relays was involved, and how many times the app was started. Each report also carries the app version, the Android version (stored in broad groups) and the phone's maker (one of twelve common brands, otherwise "other"). No account, device identifier or game is sent with them, and no IP address is stored with them. We keep them as daily totals for each combination of those values, for 30 days, to see how often Connect works and to spot a relay that is failing.
• Crash reports. When the app hits an error it cannot handle: the kind of error, its message with email addresses, IP addresses, file paths, web-address queries, tokens and keys, app package names, game names and long numbers removed before the report is built, where in the app's own code it happened, a one-way fingerprint so the same fault on different phones is grouped, a random report id, the app version and the Android version. No account, device identifier or game is sent with it. At most five reports in any 24 hours, and one per kind of error. Kept for 30 days, then deleted.

When a report arrives, our server uses a one-way hash of your connection's IP address only to limit how many reports one connection can send; it is never stored with the report. Because neither kind of report carries an account or device identifier, we cannot pick out yours to delete it; it goes when its 30 days are up. The app also keeps its own last 20 connection results and errors on your phone; they leave it only if you attach them to a support request, as described above.

Why we process your data (legal basis)

Under the DPDP Act we process your personal data on the basis of your consent, given when you sign up and connect, for the specific purposes this policy describes: operating your account and device seats, routing the game you selected, showing you your subscription state, (on the free tier, where applicable) serving a rewarded ad, and, only if you turn it on, sending crash reports and connection results. Certain narrow processing — security, abuse prevention, and complying with Indian law — may rest on the DPDP Act's "legitimate uses".

You can withdraw consent at any time, and each path stops the processing it actually relates to:

• Disconnecting ends routing — the relay lease lapses and no new connection metadata is created.
• Signing out ends processing tied to that device (its session token is invalidated; local receipts are erased).
• Switching off "Send crash reports and connection diagnostics" in Profile stops crash reports and connection results from being sent.
• Deleting your account withdraws consent for account processing altogether and triggers the erasure described in "Your account" above.

Withdrawing consent doesn't undo processing already done, and the service can't work without the minimum data it needs (an account and a relay lease) — withdrawal is as easy as the consent was to give, which is what the DPDP Act requires.

Your rights under the DPDP Act

If you are in India (and as a matter of policy, wherever you are), you have these rights as a data principal:

• Access. Ask us for a summary of the personal data we hold about you and what we've done with it.
• Correction and erasure. Ask us to correct inaccurate data or erase data we no longer need. Account deletion is built into the app (Profile → Delete account) — you don't need to email us, though you can.
• Grievance redressal. Complain to our Grievance Officer (below). If you're not satisfied with our answer, you may approach the Data Protection Board of India.
• Nominate. Nominate another person to exercise these rights for you if you die or become incapacitated. Email us to record a nominee.

Exercising a right costs nothing. We will verify it's really you (usually by confirming control of your account email) before acting on a request.

Grievance Officer

If something goes wrong (data breach)

If a personal data breach affects your data, we will notify the Data Protection Board of India and affected users in the form and within the timelines the DPDP Act and its rules require — plainly, and without burying it. Our internal breach and data-request runbook exists precisely so this isn't improvised.

Ads on the free tier

Free boosts are funded by a short rewarded video ad, served by Google AdMob. For this, the Google Mobile Ads SDK uses your device's advertising ID (Android AD_ID) and shares ad-serving data with Google as described in Google's Privacy Policy. In the EEA/UK the app shows Google's consent form (UMP) before any ad is requested; if you don't consent, the app requests no ads at all — boosting still works, we just don't get paid. BRUTAL Optimizer Ultra removes ads entirely: on an Ultra account the app doesn't request ads.

One more flow worth naming plainly: to confirm you actually finished the ad, the ad request carries your BRUTAL Optimizer device id (the server-assigned identifier from your device list — not your email), and Google echoes it back to our server in a signed receipt ("server-side verification") — that's how the boost unlocks. Google gets the id, not your email, and we don't use this id for ad targeting. When Google confirms you watched a rewarded ad, we store that confirmation against a one-way hash of your device id — when it was granted and when it lapses (currently six hours later). An expired record is cleared the next time it is checked.

Google is a separate company that processes ad data for its own purposes as described in its policy; for the DPDP Act's purposes, AdMob ad serving is disclosed here so your consent to it is informed. If you'd rather no ad data flow at all, Android lets you delete or reset your advertising ID in system settings, and Ultra never requests ads.

What the ads SDK itself collects, in Google's own terms. The advertising ID is not the whole of it, and we would rather list this than have you discover it in a form. For the version of the Google Mobile Ads SDK this app ships, Google publishes what that SDK collects automatically and shares — for advertising, analytics and fraud prevention: your device's IP address, which can be used to estimate the device's general area and is why our Google Play Data safety entry declares approximate location; app interactions such as app launches, taps and video views; diagnostic information about how the app performs; and device and signed-in account identifiers. That is the SDK's own collection, not ours — we do not receive any of it — and none of it is the contents of your traffic, which the tunnel never inspects. It happens only on the free tier, only when an ad is requested, and not at all on Ultra or where you decline the EEA/UK consent form.

Privacy Sandbox on newer Android versions. Bundling that SDK also means the app declares Android's Privacy Sandbox advertising permissions, ACCESS_ADSERVICES_TOPICS and ACCESS_ADSERVICES_ATTRIBUTION. These are Google's replacement for cross-app tracking: Topics lets the system hand an advertiser a coarse interest category worked out on your own device, and Attribution Reporting measures whether an ad led to an install without giving anyone a cross-app identifier. They arrive with the ads SDK rather than from code we wrote, they are administered by Android and Google rather than by us, and we neither read nor store what they produce. Android exposes controls for both under Settings → Privacy → Ads. On Ultra no ad is ever requested, so none of this runs.

Payments

In this Android app, Ultra is purchased through Google Play and nowhere else. Google handles the payment and the billing relationship; we never see or store your card details, and Google charges in the currency of your Google Play account. All we receive from Google is confirmation that a subscription exists and when it runs to, which we store against your account so the app can unlock Ultra.

Ultra is one subscription across your devices. If you already hold Ultra from BRUTAL Optimizer for Windows, signing in here with the same email unlocks it on this phone; that purchase stays with whoever billed it, under the terms published with that product, and we never see card details either way. For a purchase made in this app, cancel or ask for a refund in Google Play — see our refund policy for Android.

Notifications

While a route is active, the app shows an ongoing "route active" notification so the connection is never invisible. Android 13+ asks your permission for this; declining hides the notice but doesn't affect routing (Android always shows the system VPN key icon).

What we don't do

• We don't inspect, log, retain, or sell the contents of your traffic.
• We don't route anything except the game you selected — no other app's traffic ever enters the tunnel — and never through a relay outside your broad region or across a ban boundary. Within that one game we do route all of its IPv4 and set its DNS resolver, as described above; its IPv6 stays on your own connection.
• We don't sell your personal data to anyone.
• We don't collect your contacts, files, or browsing history. We don't collect GPS or precise location — but we do infer your country from your connection's IP address (via Cloudflare), to match you to a same-region relay (the ban-safety rule in our Terms), to check whether routing is offered in your country, and to refuse routing a game that is blocked where you are. We don't store a location history; the one record linked to your account that names a country is the country-check record described under Countries where we do not offer routing. It is no longer used for pricing: Ultra is sold through Google Play, which prices in the currency of your Google Play account, not in one we infer.

When we disclose data

We don't volunteer your data to anyone — but there are three situations where the data described in this policy (account data like your email and device list, and connection metadata like relay lease records) can be handed over:

• Lawful orders. If an Indian court or a government authority acting under law compels us, we comply. What we can hand over is limited to what this policy says we hold: account data, relay lease records while they exist, per-connection data counts, and a country-check record where one exists. We cannot hand over the contents of your game traffic, because relays never record it.
• Protecting the service. We may use and disclose connection metadata as needed to investigate and stop abuse of the relays (for example, unlawful traffic sent through our IP addresses).
• A successor. If ARHAS INDIA (OPC) PRIVATE LIMITED merges, is acquired, or sells the BRUTAL Optimizer business, the account data transfers to the successor bound by this policy (our Terms cover assignment); we'll notify you of any such change.

Where your data is processed (cross-border note)

Two different things travel, and it's worth being precise about which:

• Game traffic in transit passes through the relay you connect to. Relays are datacenter servers in the regions listed above (India, Singapore, Jakarta, Tokyo, Seoul, Frankfurt, Dallas, São Paulo, Bahrain), and BRUTAL Optimizer only routes you through a relay in your own broad region (e.g. South Asia for Indian players); market-locked titles like BGMI only ever use a relay in that exact country. Today every South Asia relay is in India. Where we have no relay in your region — Oceania and Africa today — nothing is routed at all, so no game traffic of yours crosses a border on our account.
• Account data (email, name, device list, subscription state) lives on our control plane, which runs on Cloudflare's global network — so it may be stored or processed outside India. The DPDP Act permits transfers to countries the Indian government has not restricted; if the government notifies a restriction that affects us, we will comply and update this policy.

Data retention & security

Account data lives on our control plane (Cloudflare) for as long as your account exists. Relay authorizations expire automatically (about an hour) and are re-granted while you play. Per-connection data counts are kept for about 100 days, and a rewarded-ad confirmation lapses six hours after it is granted, as described above. Crash reports and connection results you choose to send are kept for 30 days. A country-check record is deleted 90 days after it was last updated, or sooner if you delete your account. Standard request logs (IP, user agent) are kept by our hosting provider (Cloudflare) under its standard log retention policy for security and abuse prevention; we don't extend or export them. Your sign-in session token is stored on your phone in Android Keystore-backed secure storage (with a device-local fallback only if your phone's secure storage is unavailable).

When you delete your account, we erase the personal data it held (as described in "Your account" above) rather than keeping it "just in case". We keep only what the law requires us to keep — like the de-identified billing record described above.

Children — and why this is an 18+ service

India's DPDP Act treats anyone under 18 as a child and requires verifiable parental consent before a child's personal data is processed, and it prohibits tracking, behavioural monitoring and targeted advertising directed at children. BRUTAL Optimizer is not directed at children.

Our single position, stated the same way here and in our Terms: BRUTAL Optimizer is for users 18 and over. The ad-funded free tier, which uses the advertising ID, is not available to anyone under 18 — and neither is any other part of the app. We ask you for no age and store none. Every ad request on the free plan is non-personalized and capped at the mildest content rating Google offers — for every user, as a matter of course rather than as a special case. We do not knowingly maintain an account for anyone under 18; if you believe a child has created one, contact us and we'll delete it.

Changes & contact

If this policy changes materially we'll update this page and the effective date. Questions: support@brutaloptimizer.com. Data requests, deletion and grievances: legal@brutaloptimizer.com.