This policy explains what information the METLA Cleaner app for Android (“METLA”) reads and sends: why, who keeps it and for how long. It describes METLA versions newer than 1.3.0.
Your files, your list of apps, usage statistics and other apps’ permissions never leave your device. METLA does not share your list of apps with anyone — not with us and not with other companies. The only exception is the error text in a crash report, if you agreed to crash reports (section 3).
Little leaves the device: an anonymous account and service data that plans, server protection and METLA’s switches in case of a failure cannot work without. Analytics and crash reports are sent only after you agree. All of it is listed in section 3.
We do not sell information about you. METLA currently shows no ads and does not collect the advertising ID.
1. Who we are and how to contact us
METLA is developed by Al Badu team, the trading name of Александр Бодунов, a private individual. We are responsible for the information described in this policy. Send questions about it, about your data or about deleting your account here:
Address: on METLA’s Google Play page (“App support” → “About the developer”); we can also email it to you on request.
We usually reply within 24 hours. METLA news is posted in the @metla_cleaner_en channel (it is not a support channel).
2. What stays on your device
METLA reads and processes the following only on your device. The app has no way to send any of it over the network. The only exception is the error text in a crash report (section 3).
Files. To find junk, duplicates, thumbnails, empty folders, old and large files and to move what you delete to Quarantine, METLA needs file access: on Android 11 and above — All files access; on Android 8–10 — the Storage permission and the folders you choose. The files themselves and the scan results never leave the device. METLA does not read other apps’ private folders (Android/data and Android/obb).
List of installed apps: app names, icons, sizes and permissions — for the Apps and Activity screens, Anti-Spy and Radar.
Usage statistics — a special access you grant yourself in Android settings: how often and how long apps run and when they ran in the background — for Apps, Activity, Radar and tips; the size of other apps’ cache — for Storage, Messengers and the daily tip.
Other apps’ permissions (Anti-Spy): which of seven kinds of data — camera, microphone, location, contacts, phone, SMS, storage — an app has access to and which it only requests.
The QR scanner for Family invites is a Google Play service on the device: it controls the camera, and METLA receives only the scanned code. METLA has no camera permission. The service itself may send Google information about how it works — under Google’s rules.
Profile: your “About me” text and profile photo.
Cleaning history, Quarantine and METLA settings.
METLA reads the list of apps, usage statistics and other apps’ permissions only after you tap “Agree and continue” on the Before You Continue screen. If you chose “Not now”, those screens show a placeholder, and you can agree later. Two things work without this consent: Messengers checks whether the five messengers on its list (WhatsApp, WhatsApp Business, Telegram, TikTok, Instagram) are installed, to show their files; and METLA shows the size of other apps’ cache if you yourself granted it usage access in Android settings — a total for the whole device plus the messengers’ sizes. None of this leaves the device. Exception: if Radar was turned on in METLA 1.3 or earlier and you chose “Not now” on the Before You Continue screen, Radar keeps checking the apps on its list until you turn it off.
3. What leaves your device
METLA runs on Google cloud services. Below is everything that leaves your device: when, why, who keeps it and for how long. Google Firebase and Google Cloud process this information for us as a service provider; Google Play, the backup in your Google account and Telegram are independent services that work under their own rules. Everything is sent over a secure connection (HTTPS). We do not sell this information and do not use it for advertising.
Anonymous METLA account
When
From the first launch — even before the Before You Continue screen.
What
An account ID in the Firebase sign-in service. Such an account has no name and no email. With every request to our server METLA also sends the app language — so the server replies in your language — and, from version 1.5, its build number.
Why
Plans, Family, tester access and sign-in recovery.
Kept by
Google (Firebase sign-in service) and our server.
How long
Until you delete the account.
Sign-in recovery key (Android 9 and above)
When
From the first launch.
What
The key itself is kept on the device and — if the device has a screen lock and backup to your Google account is on — also in that backup; without it, the key does not move to a new device. Our server keeps its public part: the account ID, the public key, the key type, whether a cloud copy exists, a use counter and dates. For each sign-in the server creates a one-time service code that lives for 5 minutes.
Why
To return to the same METLA account after reinstalling or on a new device.
Kept by
Google and our server.
How long
Until you delete the account.
App integrity check
When
With every request to our server — also before the Before You Continue screen.
What
A Google Play Integrity token confirming that the request comes from the genuine METLA app (App Check), and the device ID in Google’s push notification service (an Instance ID token — for it the Firebase library registers an installation ID and attaches the token to the request).
Why
To protect the server from fake apps and abuse.
Kept by
Google (Google Play, Firebase).
How long
Per Google’s retention periods.
Purchases
When
At launch and when you buy.
What
METLA asks Google Play which METLA purchases your Google account has. The Individual subscription and Lifetime are checked on the device — nothing about them is sent to our server. Google Play itself sends our server notifications about all purchases; for purchases not related to Family, the server writes only a fingerprint of the purchase token to its log. In METLA 1.5 and later, with a purchase METLA gives Google Play an irreversible fingerprint of your METLA account number and a technical payment-window number; Google keeps them with the purchase, and our server does not read the window number. For a Family owner, after checking the purchase the server keeps a “fingerprint → account” record so it can find the family if Google reports a purchase the server has not seen yet; the record is kept until the account is deleted. Only Google sees your payment card details — we never receive them.
Kept by
Google Play; the log — Google Cloud.
How long
The log — up to 30 days.
Family plans (Family 3, Family 5, Lifetime Family)
When
When you buy a Family plan or join a family; once a day the server checks the purchase with Google Play.
What
The Google Play purchase token, the plan, subscription period and status, members, the dates the family was created and members joined, the invite code, family payment history, and the nicknames of the owner and members (“METLA User” if the nickname was not changed); for the account — the family ID, the role (owner or member) and the time of the last purchase check. The family owner sees members’ nicknames; the owner’s nickname is stored but shown to no one. If Google reports a family purchase that the server could not link to any family — a record of it: the token fingerprint, the plan, dates and the account-number fingerprint from the purchase.
Why
To confirm the purchase with Google Play and give members Pro.
Kept by
Our server (Cloud Firestore).
How long
The family — until the owner deletes the account; a member’s membership and nickname — while they are in the family or until they delete their account; the record of a purchase without a family — until the purchase finds its family or the account from the purchase is deleted; if the subscription was not cancelled, after the account is deleted each renewal briefly creates such a record again — the server removes it within two days.
Linking a Google account (optional)
When
Only if you link a Google account yourself in Profile.
What
The email, name, profile photo and ID of that Google account.
Why
To restore access to Family and your subscription after reinstalling.
Kept by
Google (Firebase sign-in service).
How long
Until you delete the account; in the sign-in service’s backups — up to 180 days after deletion.
Tester email
When
If you take part in METLA testing, we add the email you gave Google Play for testing to the tester list on our server ourselves — even if you never enter it in METLA. In METLA the email is sent to the server when you enter the email or the code and on every launch while it is saved — including in the background (Radar, auto-clean).
What
The email; the IDs of the accounts that confirmed it with a code; the dates of the last confirmation and the last check; our internal note. The confirmation code arrives by email via Gmail; a copy of that email with your address and the code stays in our mailbox’s sent folder.
Why
To give testers Pro: check that you are on the list and send you the code.
Kept by
Our server; Google (Gmail; the closed-testing list — in Google Play).
How long
The record of the entered email — up to a day; the wrong-attempt counter — up to two days; the email on the tester list — while testing goes on or until you ask us to remove it; the emails — until you ask us to delete them.
Activation code
When
If you enter an activation code in Profile (Subscription → Activation code).
What
The code itself — the server checks it and does not store it; if the code is accepted — your account ID on the list of confirmed accounts and the date.
Why
To unlock Pro with a code. For now there is one code — for Google Play reviewers.
Kept by
Our server.
How long
The account ID — until you delete your account or we revoke the code.
IP address
When
With every request to our server and the sign-in service, and when you open these documents in METLA (the pages are hosted on GitHub Pages) — this is how the internet works.
What
The address itself — in Google’s and GitHub’s logs. To protect against code guessing, our server keeps a fingerprint of the address (a SHA-256 hash — it does not make the address anonymous) in six counters: Family purchase check, invite code, tester code, activation code, account deletion, sign-in recovery on first launch.
Why
To deliver the response and protect the server from abuse.
Kept by
Google Cloud, the Firebase sign-in service, our server; GitHub — for the document pages.
How long
Google Cloud logs — up to 30 days; the sign-in service — a few weeks; the fingerprint — about a day; GitHub — under its own rules.
METLA settings (Firebase Remote Config)
When
In METLA 1.5 and later — from the first launch, even before the Before You Continue screen: at launch and when you return to METLA (at most once an hour), before Quarantine clean-up by period, night-time auto-clean, a Radar check and the payment window.
What
The Firebase installation ID and its token, country and language from your device settings, time zone, Android and METLA versions, the app package name and signing certificate fingerprint; if you agreed to analytics, also the first-open time from it.
Why
To switch a feature off quickly — for example, if a bug is found: Quarantine clean-up by period, auto-clean, Radar, sales, the new-version banner, creating the sign-in recovery key; to make METLA call our server less often if it is overloaded; and to suggest an update if your version is out of date. Some settings apply only in certain countries — Google determines the country from the IP address of the request.
Kept by
Google.
How long
The installation ID — until we ask Google to delete it, then up to 180 days.
Analytics (Google Analytics for Firebase)
When
Only after “Agree and continue” and while the “Analytics and crash reports” switch in METLA Settings is on.
What
The installation ID, device model, Android and METLA versions, device language, approximate location (from the IP address), where the app was installed from, sessions (when and how long the app is open), in-app purchases, and service events that Analytics records by itself: first launch, METLA and Android updates, METLA removal and clearing its data. METLA does not send which screens you open and has no events of its own. The advertising ID is not collected, and advertising consents default to “no”.
Why
To find bugs and see how the app is used.
Kept by
Google.
How long
Detailed data — 2 months; Google Analytics keeps aggregated reports without device IDs longer.
Crash reports (Firebase Crashlytics and Firebase Sessions)
When
Only after you agree and while the same switch is on. Reports collected before you agree are deleted without being sent.
What
The error trace and its text (it occasionally contains the name or path of a file, or the name of an app, that METLA was working with at the moment of the crash), the app state, device information, the installation ID; and our own reports of errors in the purchase flow (METLA 1.5 and later; for example, Google did not confirm a purchase or the payment window did not open): the event, the plan and its period, the subscription state, and the Google Play or server response code and text — without the purchase token, order or account numbers, email or nickname; these labels also stay on later crash reports until METLA restarts. In METLA 1.4 — two such errors: the response code and text.
Why
To find and fix bugs.
Kept by
Google.
How long
90 days.
Support requests
When
When you write to us; a record of your bot language only if you changed it.
What
Email — your message and address. The @METLA_support_bot bot and its mini app — your Telegram ID, name, username and language; requests — text, category, priority, status and dates; attachments (photos, videos, voice messages and files; up to 20 MB through the mini app); reviews and a support rating from 1 to 5.
Why
To reply to you.
Kept by
Emails — our mailbox (Gmail). The bot — its database (Supabase) and the bot server hosted on Railway, including server logs with your Telegram ID; messages are forwarded to our internal Telegram chat and internal alert channel (access for METLA support only), and the first message of a request is also copied to our mailbox through our server; attachments are kept by Telegram. Telegram itself works under its own rules. The mini app page is served by GitHub Pages: GitHub logs the IP address of whoever opens it for security purposes (under GitHub’s rules).
How long
Emails — as long as needed to reply. The bot deletes closed requests from its database 12 months after they are closed; your bot language record and the copies in our mailbox and internal chat and channel stay until you ask us to delete them. At your request we delete them sooner — within 30 days: from the bot database, our mailbox and the internal chat and channel. Hosting logs — per Railway’s retention periods.
Google windows on your device — payment, rating METLA on Google Play, signing in with a Google account, the QR scanner and, in METLA 1.5 and later, in-app updates (METLA asks Google Play whether a new version is available; Google Play receives device information, the METLA version and the list of its modules; Google Play handles the download and installation) — work under Google’s rules: what you enter in them is processed by Google. METLA receives only the result — the purchase, the linked account’s data, the scanned code; METLA does not see your rating or review.
4. Permissions
There are no permission prompts at launch: METLA asks for each permission when you tap a button where it is needed. If you decline twice, METLA offers to open Android settings. Below is the full list of METLA’s permissions, including the service permissions added by Google and Android libraries.
METLA’s permissions
All files access (MANAGE_EXTERNAL_STORAGE), Android 11 and above: finding junk, duplicates and empty folders, moving what you delete to Quarantine and restoring files. Without it METLA cannot see photos, videos, music and documents and cannot delete files. METLA has no separate photo, video or music permissions.
Storage (READ_EXTERNAL_STORAGE), Android 8–10: the same tasks in the folders you chose; METLA deletes only inside them.
List of installed apps (QUERY_ALL_PACKAGES): Apps, Activity, Anti-Spy and Radar (section 2).
Usage statistics (PACKAGE_USAGE_STATS) — a special access in Android settings (section 2).
Uninstalling apps (REQUEST_DELETE_PACKAGES): uninstall an app you picked — you confirm it in the Android dialog.
Stopping background work (KILL_BACKGROUND_PROCESSES): ask Android to stop an app’s background work; works on Android 8–13.
Notifications (POST_NOTIFICATIONS), Android 13 and above: auto-clean results, junk and trial reminders, Radar alerts. You can turn them off in METLA Settings.
Network state (ACCESS_WIFI_STATE, ACCESS_NETWORK_STATE): Device Pulse shows whether Wi-Fi is on and whether there is a network; libraries check for a connection.
Bluetooth (BLUETOOTH), Android 8–11: Device Pulse shows whether Bluetooth is on.
Library service permissions
Internet (INTERNET): our server, Firebase, Google Play and the pages of these documents.
Purchases (BILLING): payments through Google Play.
Task scheduler (WAKE_LOCK, RECEIVE_BOOT_COMPLETED, FOREGROUND_SERVICE): scheduled auto-clean, Radar and reminders, including after a restart.
Google push notification service (RECEIVE): the device ID that Firebase libraries attach to requests (section 3, “App integrity check”).
Install source (BIND_GET_INSTALL_REFERRER_SERVICE): analytics learns where the app was installed from — only after you agree.
Google service permission (READ_GSERVICES): added by the protection of the Firebase sign-in service (reCAPTCHA).
Biometrics (USE_BIOMETRIC, USE_FINGERPRINT): added by an Android library; METLA does not use biometrics.
Internal permission (DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION): a service permission of the AndroidX library that works only inside METLA.
What METLA does not have: the advertising ID and the related Android ad services permissions, camera permission, photo, video and music permissions, write-to-storage, Bluetooth device connection and location permissions.
5. Quarantine, history and backup
Files you delete in METLA go to Quarantine first. On Android 11 and above a file is moved without copying into the hidden .METLA_Trash folder at the root of the same storage (device storage or memory card); on Android 8–10 Quarantine keeps a copy in METLA’s internal storage. Quarantine exists only on your device. Space is freed when a file leaves Quarantine.
On Android 11 and above the Quarantine folder is in the device’s shared storage: file managers and other apps with All files access can see it.
The default retention period is 30 days; for free you can choose 7, 14 or 30 days, and with Pro also 60 days or “No time limit”. “Auto-clean Quarantine” is on by default: when the period ends, the file is deleted permanently. The default Quarantine size is 1 GB (from 256 MB to 10 GB). When it runs out of space, METLA warns you and asks before permanently deleting the oldest files.
A file can be restored while it is in Quarantine and METLA has file access (on Android 11 and above — All files access). On Android 8–9 a file can be restored only to the folders you chose.
If you uninstall METLA on Android 11 and above, the .METLA_Trash folder remains — you can delete it with any file manager; after reinstalling, METLA does not see the earlier files in it. On Android 8–10 Quarantine is erased together with METLA, and also by “Clear storage” in Android settings.
Cleaning history is stored only on the device; you can clear it in Profile. METLA does not make an Android backup at all — neither to the cloud nor when moving to a new device: history, Quarantine, settings and the profile photo do not move over. Your previous METLA account comes back on a new device through the recovery key, if it got into the cloud backup, or through a linked Google account (section 3).
6. Retention and account deletion
How long we keep it
The account, the public part of the recovery key, the family and its payment history — until you delete the account.
The record of an entered tester email — up to a day; the wrong-attempt counter — up to two days; the email on the tester list — while testing goes on or until you ask us to remove it.
The IP address fingerprint — about a day.
Google Cloud server logs — up to 30 days. They may contain the account and family IDs, the IP address, a purchase token fingerprint, the plan’s product ID, a support request number, and — if sending the code email fails — a masked tester email (first letter and domain).
Backups of our database: daily backups — up to 30 days; point-in-time recovery — up to 7 days. Data of a deleted account disappears from them when these periods end.
Firebase sign-in service: IP addresses — a few weeks; linked Google account data after deletion — in backups for up to 180 days.
Emails to support — as long as needed to reply; closed requests in the bot database — 12 months after closing; your bot language record and the copies in our mailbox and internal chat and channel — until you ask us to delete them; at your request we delete them sooner — within 30 days. Bot hosting logs — per Railway’s retention periods.
The “account deleted, when” marker — indefinitely (see below).
How to delete your account
In the app: Profile → Account & data → Delete account. Or write to us (section 1) — we will delete it within 5 business days; the steps are on the account deletion page.
Erased on the server: the family (if it has no members — together with its payment history and invite code) or your family membership, nicknames, purchase links, tester confirmation (the account ID is removed from the list of confirmed accounts together with the last-check entry) and records of emails entered from this account, the public part of the recovery key, sign-in, the “fingerprint → account” record (for a Family owner).
Erased on the device: the recovery key (also from the cloud copy), the nickname (back to “METLA User”), “About me” and the profile photo, the saved tester email, family information, analytics data and the installation ID. After deletion METLA creates a new anonymous account by itself; a Family purchase is not attached to it automatically — only if you tap “Restore purchases” or buy again. If we delete the account at your request by email, nothing changes on the device: this data stays there until you uninstall METLA; the recovery key may remain, but it no longer works.
What remains: a deletion marker — under the random ID of the deleted account, only “deleted” and “when”, with no name, email, device or purchase data; it is kept indefinitely so that a copy of the app still signed in with the deleted account cannot restore it, rejoin a family or claim a purchase. Google Cloud logs — up to 30 days. Backups of our database — up to 30 days (point-in-time recovery — up to 7 days). Tester code emails — until you ask us to delete them; support requests — per the periods in section 3. Analytics and crash reports already sent are not linked to the account and are kept for their own periods. On the device, the cleaning history, Quarantine and the Radar list remain.
A family owner whose family still has members first removes them in Family (they immediately lose Pro from that family) or writes to us, and then deletes the account. Deleting the account does not cancel a Google Play subscription: cancel it in Google Play. Uninstalling METLA does not delete the account, and the server does not remove abandoned accounts by itself — so if you want the data erased, delete the account first and then uninstall METLA, or write to us.
7. Your rights and choices
Analytics and crash reports: tap “Not now” on the Before You Continue screen or turn off the “Analytics and crash reports” switch in METLA Settings — at any time. What has already been sent is kept for the periods in section 3.
Access: you can revoke each access in Android settings.
Information about you: write to us to find out what we keep about you, correct it or delete it. You can also delete your account in the app (section 6). We answer such requests within one month.
8. For residents of the EU, EEA, UK and Switzerland
The data controller is Александр Бодунов (Al Badu team; contacts — section 1). Legal bases:
performance of a contract — plans, Family, tester access, support replies;
legitimate interest — the anonymous account and recovery key (to keep your plan and access), protecting the server and purchases from abuse: app integrity checks, IP address fingerprints, server logs; METLA’s settings (Remote Config): switches in case of a failure and country-specific settings — the country from the IP address of the request;
consent — analytics and crash reports: turned on by “Agree and continue” (the “Analytics and crash reports” switch is on by default); you can withdraw consent at any time with that switch.
Right to object. You can object at any time, on grounds relating to your particular situation, to processing based on our legitimate interest (above): write to us (section 1). We will then stop that processing unless we have compelling legitimate grounds to continue it.
If you are younger than the age at which you can consent to data processing yourself in your country (in EU countries — from 13 to 16), only a parent or guardian can consent to analytics and crash reports; without that consent, tap “Not now”.
Data may be processed outside your country, including in the United States and Japan. Google (Firebase, Google Cloud, Gmail) processes it for us under its data processing terms, which include the European Commission’s Standard Contractual Clauses (write to us for a copy); Supabase and Railway — under their own data processing terms; Google Play, Telegram and GitHub are independent services that work under their own rules.
You have the right to access your data, to have it corrected or erased, to restrict processing, to data portability, to object to processing and to withdraw consent, as well as the right to lodge a complaint with the data protection authority in your country.
9. Children
METLA is intended for adults aged 18 and over and is not intended for children under 13; we do not knowingly collect information about children under 13. If you learn that such a child has sent us information, write to us — we will delete it.
10. Security
Everything that leaves the device is sent over a secure connection (HTTPS). The app never accesses our database directly — only through our server functions, and requests pass the app integrity check — except two: entering an activation code and deleting an account (deletion only erases the caller’s own account and is rate-limited per hour). On the device, METLA’s data is protected by your screen lock and Android encryption; on Android 11 and above Quarantine is in shared storage (section 5).
11. Changes to this policy
A new version is published on this page with a new “Last updated” date at the top. If what METLA collects changes, we publish a new version; if a change needs your consent, the app will ask for it again. The version of September 30, 2026 described METLA up to and including version 1.3.0: in those versions analytics started right away, without consent, and the advertising ID was collected.
12. Terms of Use
The rules for using METLA, the license, subscriptions and refunds are in the Terms of Use.