Privacy Policy for Cacher
This policy describes what the Android app Cacher (package com.gante.cacher) does with information. Every description below of what the app and the server that checks Cacher+ purchases do is a statement about the code that ships, not a statement of intent; where we make a commitment, the text says so.
Who is responsible
The controller of the personal data that we process as described in this policy is Gi-Gante s. r. o. In this policy "the developer", "we" and "us" mean Gi-Gante s. r. o. Contact: cacher@gi-gante.com.
Overview
Cacher is a storage cleaner. It shows what is taking up space on your device and removes the files and app caches you choose to remove. It does not claim to speed up your phone, free RAM or save battery — no app can do that. It frees storage space, and that is what it says.
Cacher works without an account: there is no sign-in, and the app does not ask for your name, email address, contacts or where you are. The only place it reads is the one recorded inside a photo or video, and only to keep it in a copy of that file that Cacher writes on the phone (see "Permissions the app uses"). The current version contains no analytics, crash-reporting or advertising SDK. The third-party components that use the network are Google's: the Google Play Billing library and, for the Cacher+ purchase check only, the Google Play Integrity library, both described below.
Scans, measurements and deletions run on your device, and their results are kept in the app's private storage there. Without Cacher+, the app's own code makes no network requests. With Cacher+, it makes one kind of request: the Cacher+ purchase check, which sends the developer's server the purchase details and identifiers described under "Cacher+ purchase check" and nothing from your storage. Either way, your files, your file names and the list of apps you have installed stay on the phone, or on the memory card or USB drive you move files to yourself. The one exception is the exclusion list you make yourself, which Android's own backup can carry, as described below.
What is stored on your device
To do its job the app keeps the following in its own private storage, which other apps cannot read:
- your settings: theme, palette, app icon, language, the age and size thresholds the scans use and the "Clean every cache" switch — and, next to them, when the app last asked Google Play to show its rating card and when it last showed the Cacher+ line after a cleanup, so that neither comes back too soon;
- your exclusion list — the paths and packages you asked Cacher never to touch;
- your schedule and smart rules: how often to scan, quiet hours, the screenshot age and cache threshold you set, and when each rule last notified you;
- app groups you create, stored as group names and package names;
- one snapshot per day of how much storage is used, kept for 60 days, so the app can show a trend and a 30-day chart and estimate when storage runs out;
- once a day, the size of each app — its app, data and cache bytes — with its package name, kept for 120 days, so the app can show whose data is growing. These figures come from the storage statistics that usage access opens; they record how big apps are, not when or how you use them;
- for each app whose cache a cleanup cleared, its package name, the time and the cache size before and after; and after each cleanup, the free space measured one, three and seven days later. Both are kept for 120 days, so the app can show how much of the freed space stayed free and which caches come back;
- a cleanup journal: time, source, number of items, how many bytes were freed and whether the files are still in the system trash — no file names and no package names;
- on Android 11 and newer, a list of the files Cacher sent to the system trash: for each file its name, its address in Android's media library, its size and how much of it counts as freed space, the storage volume it is on, when it was sent, when the system will remove it, which feature sent it and the journal entry it belongs to. It exists so that the Trash screen can show what Cacher put there and restore or delete exactly those files, and so that space counts as freed only once a file has left the trash. Cacher compares the list with Android's media library when you open the Trash screen, when the app starts and once a day, and drops a file from it once it sees that the file has left the trash — restored, deleted, or removed by the system when its time ran out. Files that other apps put in the trash are not listed;
- measurements of your photos, used to spot similar shots, blank frames and the series in Photos by month: for each picture its media address, size and date, a perceptual hash, and figures for brightness, detail and colour balance. They are kept so that the next scan does not have to read every photo again, they hold no copy of the picture itself, and rows for photos that are gone are dropped;
- whether you agreed to the accessibility service, and the verdict of the self-test that measured whether automatic cleaning works on this firmware, with when that check ran, which version of Cacher ran it and which firmware build it ran on;
- a history of Cacher's own accessibility service: when it was last created, connected, unbound, destroyed or interrupted, when it was last started in the restricted process Android uses for backup, and when it last switched itself off for lack of your consent — one time per kind of event, overwritten by the next one — plus two counters since the last app update: how many times the service connected, and how many times a cleanup you asked for could not start, with the reason and time of the last such refusal. It is about Cacher's service only and holds no names of other apps. It is kept across restarts of the app because the support report shows it (see "Writing to support");
- a recent-cleanup memory: for each app a cleanup has just been through with one of three outcomes — the cache was cleared (or had almost nothing left to clear), the "Clear cache" button was greyed out, or the settings screen showed an empty cache while the storage statistics did not — its package name, which of the three it was, the time, and the cache size from the storage statistics; apps with any other outcome are not kept. It exists so that an app cleaned a minute ago is not offered for cleaning again. An entry is meant to live ten minutes: while Cacher is running, a timer removes entries as they expire (the phone's deep sleep, or Android pausing Cacher in the background, can delay that); if the app's process ended before then, they stay in the file until Cacher next starts and are removed then. This memory is not part of the support report;
- the squeeze estimate: how much space re-encoding your photos and videos could free and when that was measured, shown on the home screen and in Cacher+ while it is no more than 14 days old; and a list of files on which squeezing failed in a way that would fail again, kept as the number Android's media library gives each file, its size and the time of the attempt — no file names and no paths — so that those files are left out of the estimate and out of the squeeze hint next to large files. An entry is dropped at the next estimate once that file's size has changed or the entry is more than 30 days old, and the list keeps at most 500 entries;
- a list of live photos from which removing the video failed in a way that would fail again, kept like the squeeze failures — the number Android's media library gives the file, its size and the time, no names — and dropped once that file's size changes or the entry is more than 30 days old;
- if you use the Cacher+ setting that keeps a minimum of space free: whether it is on, the amount you chose, and when it last notified you and how much space was missing then;
- the outcome of the last search for dark stretches in videos: when it ran, how many videos it checked, how many had dark stretches and how many dark seconds they held in total — numbers only. The list of videos it finds is kept only while that screen is open;
- for Photos by month: which months you marked as reviewed, kept as year and month only, and the order you chose for the list of months — no photos and no file names;
- the pace of the last five automatic cleanups — how many apps each went through and how long it took, with no names and no dates — so that the cleanup screen can estimate how long the next run will take on this phone;
- which steps of the before-selling checklist you ticked as done, kept as the names of the steps only;
- which version's "What's new" sheet you have already seen, so that it appears once after an update and not again;
- if you move files to a memory card or USB drive through a folder you pick: Android's permission to that folder, which Android keeps until you take it back or the folder is gone. The list of the files moved is kept on that drive, not on the phone, as described under "What Cacher deletes";
- for each access the app can ask for, whether it has asked already and whether Android has stopped showing that dialog, so that the Access screen can tell a dialog you closed from a refusal;
- whether Google Play reports an active Cacher+ purchase, and the few details about it listed under "Purchases and Google Play Billing"; for Cacher+ owners, what the purchase check keeps on the phone, listed under "Cacher+ purchase check"; and, for everyone, the latest time the app has read from the phone's clock, so that setting the clock back cannot stretch a Cacher+ confirmation;
- the diagnostics text described under "Writing to support": it is put together when the support screen opens, and written into the app's own cache folder when you compose the email with it attached, where it stays until the next report replaces it or Android clears the app's cache.
Cacher's own code sends none of this anywhere, with one exception: for Cacher+ owners, the purchase check sends the purchase tokens with their product identifiers and the installation identifier, as described under "Cacher+ purchase check". Android's backup can carry part of it, as the next section describes, and some of it appears in the support report, which Cacher hands only to the mail app you choose, as a draft that you send yourself. Uninstalling the app deletes all of it from the phone.
Android backup and phone-to-phone transfer
Cacher takes part in Android's own backup and device transfer, which is run by the system under your Google account, not by the developer. What travels is what you chose and would not want to choose twice: settings, exclusions, schedule and smart rules, and your consent to the accessibility service. With them go three small notes: when the rating card was last asked for and the Cacher+ line last shown, so that a new phone does not bring them back too soon; which permission dialogs the app has already asked for and whether Android has stopped showing them; and which "What's new" sheet you have already seen.
Several things are deliberately left out. The cached Cacher+ status, with what the Cacher+ purchase check keeps in the same file, because the entitlement lives in Google Play, a copied flag would be a lie on another phone, and the installation identifier belongs to this installation. The automation verdict, because it describes one firmware and would also cancel the fresh check on the new device. The cacher.db database with the storage history, the cleanup journal, the daily sizes of apps, the records of cleared caches and the measurements after cleanups, because those are measurements of one device and would merge two phones into one chart; your app groups, the photo measurements and the list of files sent to the trash live in that same database and stay behind with it. The history of the accessibility service, because it describes the service on one phone. The recent-cleanup memory, because a copy would neither expire on time nor mean anything on another phone. The squeeze estimate with its list of files that failed, and the list of live photos that failed, because they measure one phone's media library, and the same file numbers would point to different files on another. The setting that keeps a minimum of space free, with its last notification, because an amount in gigabytes means something different on a phone with different storage. The outcome of the last search for dark stretches, because it describes this phone's videos. The months you marked as reviewed in Photos by month, with the order of that list, because they describe this phone's gallery: on another phone the same months hold other photos. The pace of past automatic cleanups, because it describes how long a cleanup takes on this phone. And the ticks in the before-selling checklist, because they describe getting this phone ready for sale. The same exclusions apply to cloud backup and to direct phone-to-phone transfer.
Permissions the app uses
Cacher asks step by step, only when a feature actually needs something. The first scan works with no special access at all.
- Photos and media (READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, READ_MEDIA_AUDIO, READ_MEDIA_VISUAL_USER_SELECTED; READ_EXTERNAL_STORAGE on Android 12 and older) — to find large files, old downloads, old screenshots, duplicates, similar photos and blank shots. For most of that the app reads names, sizes and dates only. It opens file contents in two cases: to confirm a duplicate, where it reads the first 256 KB of files that already match in size; and to compare photos with one another, where it decodes the picture at a small size to work out a perceptual hash and figures for brightness, detail and colour balance. Both happen on the device, and what is kept afterwards is the measurements, not a copy of the picture. On Android 14 and newer you can grant access to selected photos only; Cacher works with what it was given and tells you that the picture is partial. The same access serves six more screens, each only when you open it. To show which apps fill the storage, Cacher reads which app saved each media file, which Android records with the file, counts the files by app, and adds how much the system trash holds. Photos by month reads your photos (not videos) with their names, dates, sizes, dimensions and orientation, groups them by the month they were taken, and decodes them to show them in the month's grid and full screen; to fold shots taken seconds apart that look alike into one series, it uses the same measurements as the search for similar photos. The Trash screen, on Android 11 and newer, reads whether each file Cacher sent to the trash is still there and when the system will remove it, and shows its thumbnail; when Cacher can see all your photos, videos and audio, it also adds up the sizes of the rest of the trash — what other apps put there — to show one total, without reading which files those are. To find videos with dark stretches, it decodes a few small frames from the start and the end of each video longer than 20 seconds from the last twelve months. To move files to a memory card or USB drive, it reads the files you choose in full, to copy them and check the copy. For the before-selling checklist it counts your files by type, and, where Android lets it read WhatsApp's own folders (with All files access, or with the storage permission on Android 9 and older), it reads the names and dates of the backup files there to tell you how old the newest backup is. None of this leaves the phone, and none of it is kept except as listed under "What is stored on your device".
- Location in photos and videos (ACCESS_MEDIA_LOCATION) — asked for only when Cacher is about to write a copy of a photo or video: squeezing, removing the video from a live photo, trimming dark stretches, moving files to a card or drive and back, and putting back the place in photos that earlier versions of Cacher squeezed without it. Android hides the place where a picture was taken from apps that do not have this permission, and a copy made without it would lose that place. Cacher reads the place from the file only to write it into the copy, on the phone. It does not read where the phone is, and it sends no place anywhere. If you refuse, the files that would lose their place are left as they are.
- Writing to storage (WRITE_EXTERNAL_STORAGE, Android 9 and older only) — to delete a file you selected. Those versions of Android came before scoped storage and have no confirmation dialog of their own, so deletion is possible only through this permission. Cacher uses it for one operation: removing the items you ticked on the review screen or marked for removal in Photos by month. On Android 10 the system asks you about each file itself, and on Android 11 and newer it asks about the whole batch in one dialog — so on those versions the app does not request this permission at all.
- All files access (MANAGE_EXTERNAL_STORAGE) — optional, for the deep part of the scan: empty folders, leftovers of apps you already uninstalled, APK installer files, litter from other systems such as .DS_Store, thumbs.db and LOST.DIR, older backup copies, and the photos, videos and voice messages that messengers left on the phone. On Android 11 and newer the contents of the Downloads folder are also shown only to apps that hold this access, so sorting Downloads out needs it too. Android exposes none of that in any other way. Cacher reads names and sizes; the only files it opens are APK installers, to read the app name and version out of their manifest and tell you whether that app is already installed. Everything else in the app works without this access.
- Usage access (PACKAGE_USAGE_STATS) — optional, a special access you switch on in system settings. Android reports how much space each app occupies only to apps that have it. Cacher uses it for three things: the size of each app's cache, when an app was last opened, so you can find apps you no longer use, and a daily record of each app's size, so it can show whose data is growing (see "What is stored on your device"). That record holds sizes, not times: Cacher keeps no history of how you use your apps.
- Notifications (POST_NOTIFICATIONS) — optional, for the quiet scheduled report and smart-rule reminders. The background scan measures and reports; deleting is a step you take in the app. Below 50 MB it stays silent rather than nagging you, and it respects the quiet hours you set.
- Uninstall requests (REQUEST_DELETE_PACKAGES) — to open the system uninstall dialog when you choose to remove an unused app, and, on Android 15 and newer, the system archive dialog when you choose to archive one: archiving removes the app's installation files but keeps its data and its icon, and tapping the icon brings the app back from the store. Android performs both, and you confirm each app.
- Internet (INTERNET) — declared by Cacher itself for one purpose: the Cacher+ purchase check, which the app makes only when Cacher+ is on (see "Cacher+ purchase check"). Google's data-transport component, which comes with the Google Play Billing library, needs it as well, to send Google the library's technical logs described under "Network access and data sharing". Thumbnails are loaded only from files that are already on your device.
- Accessibility service (BIND_ACCESSIBILITY_SERVICE) — optional and off by default. The next section describes it in full.
Nothing else is asked of you. The installed app also declares a few permissions that Android grants at installation without a dialog and that open none of your data: com.android.vending.BILLING, for the Google Play Billing library; WAKE_LOCK, RECEIVE_BOOT_COMPLETED, FOREGROUND_SERVICE and ACCESS_NETWORK_STATE, which arrive with Android's library for scheduled background work, used by the scheduled scan and the daily storage snapshot, and with the video library used for squeezing; and one that keeps Cacher's internal broadcasts private to the app. There is no access to the phone's location, contacts, camera, microphone, call log or messages. The app also does not ask for permission to enumerate every installed package: the list it shows is built from apps that have an icon in your launcher. The list of unused apps asks Android which keyboards are switched on, only to leave them out: a keyboard never comes to the front, so it would always look unused. The before-selling checklist asks Android about a fixed list of apps by name — WhatsApp, WhatsApp Business and common authenticator apps — only to say whether they are installed, because chats and sign-in codes kept in them need moving before a phone is reset.
The accessibility service
Android does not let any app clear another app's cache directly. The only way is to open that app's own system settings screen and tap "Clear cache". Cacher can use an accessibility service to reach that button — only after you have read the disclosure screen and agreed, and only during a cleanup you started yourself.
It follows one fixed sequence and nothing else: open an app's settings, find "Storage and cache", find "Clear cache", tap it. If a settings page does not scroll when asked to, Cacher scrolls it with a swipe, and if a settings page does not open the "Storage and cache" row when asked to, as happens on some phones whose settings pages are built differently, Cacher taps that row. That is why Android lists "perform gestures" among the service's abilities when you switch it on: the swipe on a settings page and the tap on that one row are the only gestures Cacher makes, only on settings pages and only while a cleanup or a check you started is running. The tap opens the storage page and nothing more; the "Clear cache" button itself is always pressed by its name, never by its position on the screen. The one button it presses to clear anything is "Clear cache". If a confirmation prompt appears — "Clear storage" and "Clear data" ask one, "Clear cache" on most phones does not — Cacher takes it as a sign of the wrong screen and leaves that app without confirming. On some firmwares, such as MIUI and HyperOS, the storage page has no "Clear cache" button: its "Clear data" button opens a menu instead of erasing anything. There Cacher presses that button by its name to open the menu, picks the "Clear cache" entry by name, and confirms the question that follows only if that question is about clearing the cache; if there is no such entry, or the question is about anything else, it backs out without confirming. It never presses an entry that erases an app's data. The button names you are shown are read from the screen itself rather than translated by us, because the language of the app and the language of the system settings are not always the same.
Besides these taps and the swipe, Cacher uses two actions that Android offers every accessibility service: Back, to close a menu or a dialog it is not sure about and, at the end of a run, to leave the Settings screens it opened and return to Cacher (Home, only if it cannot get back that way); and, on Android 12 and newer, closing the notification shade, which it does when it cannot find the row or the button it is looking for, in case the shade covers them. During an automatic cleanup, if a window of the system's own interface — the notification shade, quick settings or a similar system window — stays in front of Settings for a second while Cacher waits for an app's page, Cacher closes the shade (on Android 12 and newer) and, if that window is still in front a second later, presses Back. It does each at most once per app and taps nothing in that window; if Settings stays covered like this for three apps in a row, the run stops. Cacher also asks Android whether the screen is on and whether the phone is locked, which any app can ask without a permission. It asks before each app and while it waits for and searches a page, and if the screen has gone off or the phone is locked, the run stops at once and asks you to unlock the phone and try again, because Settings would otherwise open behind the lock screen. Cacher never tries to unlock the phone.
On some phones the service can do the tapping for you. On others the system marks that button as sensitive: it disappears from the accessibility tree and rejects synthetic taps. That is more common on newer versions of Android, but the version number alone does not decide it, so Cacher does not guess — it measures on your phone, says plainly what it found, and where the tapping is not available it switches to a guided mode: it opens each app's storage screen and steps aside so that you tap the system button yourself.
While a cleanup runs, the service reads the text of the settings screen it opened. That is how the button is found, and also how Cacher can tell that an app has nothing left to clear — the screen shows the current cache size, and the system's own statistics can lag behind it by more than a minute. Reading the size is what keeps a second cleanup from reporting failure over apps the first one already emptied. The screen alone does not make a cleanup count, though: a running app can show "0" there and keep the space, so Cacher credits a cache as cleared only when the storage statistics drop too. What it reads is used to find the button and the row with the cache size; the text of the screen itself is not saved. What a run leaves on the device is its result: for the apps it cleared, found with a greyed-out button or found showing an empty cache, the outcome with their package names, kept for about ten minutes (or, if Cacher's process ended first, until Cacher next starts) in the recent-cleanup memory described under "What is stored on your device", and the totals in the cleanup journal, which hold no names. The service also records when it is created, connects, disconnects and is destroyed, in the service history described there. Cacher's own code sends none of this anywhere; the service history appears in the support report, the recent-cleanup memory does not. The one exception to "not saved" is the self-test described under "Writing to support": it keeps the layout of Cacher's own two settings pages in memory for the diagnostics file. Between cleanups it is subscribed to no events and carries no flags, and the flags are set only for the duration of a run and removed straight after. It is declared to receive events from the device's settings apps only, and before every tap Cacher checks for itself that it is standing on the right screen.
During an automatic run Cacher covers the screen with its own progress panel, so that a stray tap cannot land on a system button. In the guided mode a panel of its own also covers each storage page while Cacher opens and reads it, and an app whose cache already reads zero, or whose button is greyed out, is passed over without asking you to tap. Where there is something to tap, the panel goes and Cacher leaves the row of buttons uncovered — you have to be able to read the system labels — and it removes its hints the moment another screen or a system dialog appears on top.
Cacher is not declared as an accessibility tool, because it is not one: it is a cleaner, and Google Play's policy is explicit that cleaners must not claim that status.
You can withdraw your consent in one tap, and the service switches itself off. If it is ever enabled without going through the consent screen, it disables itself on the spot. Turning it off changes nothing else in the app. The screen-dumping tool used while adding support for new firmwares exists only in developer builds and is not part of the version published on Google Play.
What Cacher deletes
Nothing is pre-selected for deletion: you tick what goes and confirm before anything is deleted. In a group of duplicates the original is protected and cannot be selected.
On Android 11 and newer, the photos, videos and audio you delete go to the system trash through Android's own request instead of being erased: the system keeps them for about thirty days and then removes them, and until then they still take up space. Right after a deletion, "Undo" brings them back, and the Trash screen lists what Cacher sent there, with "Restore", "Delete now" and "Empty trash". Restoring is done by Android through its own request. "Delete now" and "Empty trash" delete those files permanently through Android's own delete request, after Cacher has asked you, and "Empty trash" touches only what Cacher sent there, never what other apps put in the trash. Space counts as freed, in the app's totals and in the cleanup journal, only once the files have left the trash. Other files, and all files on Android 10 and older, have no system trash and are deleted permanently, and the confirmation counts the two apart before you agree to anything: so many items to the trash, so many gone for good.
In Photos by month nothing is marked for removal in advance either, and nothing is removed until you confirm on the month's summary. The photos you marked then go to the trash on Android 11 and newer; on older versions they are deleted permanently, after Cacher asks you first.
Cacher writes to your own files, rather than only removing them, in a few features of Cacher+, and all of them follow one order. Squeezing media writes a re-encoded copy; removing the video from a live photo writes a copy that keeps the photo and drops the hidden video; trimming dark stretches writes a copy without the dark start and end, cut at a key frame so that no frame of the video is re-encoded. Each copy is written next to the original and checked first; only if it is sound and really smaller does the original move to the system trash, where the Trash screen lists it among the originals, and the copy take its name, and refusing the system dialog leaves everything exactly as it was. These work on Android 11 and newer, because below that there is no trash to fall back on. The whole of it happens on the device.
Two repairs go the other way. Live photos that earlier versions of Cacher squeezed without their video can be brought back while their originals are still in the system trash: the original returns from the trash and Cacher's copy is then deleted permanently, each through a system dialog. Photos that earlier versions squeezed without the place they were taken can get it back: Cacher reads the place from the original in the trash, which it does not change, and writes it into its own copy.
Moving photos and videos to a memory card or USB drive copies each file you chose to the drive, reads the copy back and checks it against the checksum of the original. Only then are the originals of the files whose copies match removed from the phone, permanently and through Android's own delete request: they do not go to the trash, because a checked copy lies on the drive. The list of what was moved — each file's name, folder, size, dates, type and checksum, and where its copy lies — is written to the drive itself, in a folder named .cacher-offload, so that "Return" can put every file back where it was and check it again. That list is as readable as the files next to it to anyone who holds the drive. Archiving an app, on Android 15 and newer, is done by Android after you confirm it, and keeps the app's data.
A cleanup counts as successful only when the system confirms that the space was actually freed; files in the trash count once they have left it. Scheduled background scans measure and report; deleting is done by you in the app.
Purchases and Google Play Billing
Cacher+ is an optional subscription or a one-time purchase. Payment is handled entirely by Google Play Billing. Your card number, billing address and other payment details stay with Google Play; Cacher does not receive them. What the app keeps from Play on your device is whether Cacher+ is active, whether it came from the one-time purchase or from a subscription, when Google Play last confirmed it, and the purchase token of the subscription that confirmed it — an identifier Google Play issues for that purchase, kept so that Cacher can recognise the same subscription later. The date, the token and the one-time mark are removed when Google Play reports no active Cacher+ purchase. For the purchase check described next, the app also keeps the purchase tokens of the Cacher+ purchases that turn Cacher+ on, the one-time purchase included. If Google Play has not confirmed a subscription for 38 days, Cacher+ pauses until Play answers again; the one-time purchase has no such limit.
Every purchase is checked against Google's signature before Cacher+ turns on. Subscriptions are managed and cancelled in Google Play, not in the app. Cacher+ purchases are also confirmed with the developer's server, as the next section describes.
Cacher+ purchase check
If you have Cacher+, the app confirms the purchase with a server operated for the developer. Without Cacher+ the app does not make this check, sends that server nothing and creates no installation identifier.
- Who. The check runs on an installation where Cacher+ is on: a subscription that Google Play reports as active, including a free trial if one was offered and the grace period Google Play gives after a failed payment, or the one-time purchase.
- What is sent. Over an encrypted (HTTPS) connection: a random installation identifier that the app creates the first time it makes the check (it is not derived from your device, your Google account or your purchase); the Google Play purchase token of each Cacher+ purchase on this phone, with its product identifier (the subscription, the one-time purchase or both); the result of a Google Play Integrity check or, if the phone could not produce one, a short error code; and the app's version number. The request carries no files, file names, scan results, settings, list of apps, name or email address.
- The Google Play Integrity check. Right before each request the app asks Google Play on the phone for an integrity result made for that request. It tells whether this copy of Cacher is the one Google Play distributes and is unmodified, whether the Google account on the phone got the app from Google Play, and it includes a check of the device that Google performs. To make it, Google receives a hash that the app makes for this request from the installation identifier and the purchases, the app's package name, version and signing certificate, the app's Google Play licence status for the accounts signed in on the device and an attestation of the device, as Google describes for Play Integrity. The developer's server sends the result to Google to have it read.
- When. The app looks at whether a check is due each time it rechecks your purchases with Google Play: when you open Cacher or come back to it, when you open the Cacher+ screen, when you tap "Restore purchases", right after a purchase, when Google Play reports that a payment problem with your subscription was fixed, and when its connection to Google Play comes back while it is running. A check is due when the app holds no valid confirmation from the server (the first time, or after a confirmation has run out), when Google Play shows a Cacher+ purchase the server has not confirmed yet, such as a new purchase, and otherwise about once a week, when the last confirmation is a week old. If the server could not be reached or gave no answer, the app waits before the next attempt at least 15 minutes, then an hour, six hours and a day; a busy server can ask for a longer pause, up to a day; a purchase or a tap on "Restore purchases" skips that wait. If the answer was that no active purchase was found, the app asks again at most once a day, or sooner after a purchase or a tap on "Restore purchases".
- Why. To confirm with Google Play that Cacher+ was really bought for this installation, and to detect unauthorised copies of the app and misuse of purchases, such as one purchase used on an unusually large number of installations. If the check starts to limit Cacher+, for example by keeping it off in a copy that Google Play does not recognise or for a purchase that is being misused, this policy will be updated before that.
- What the server does. It asks Google Play about the purchase with its purchase token and reads from the answer only what it needs: the state of the purchase, its product, expiry and renewal, whether it was refunded and whether it replaced an earlier purchase. It asks Google to read the Integrity result. If the purchase is active, it returns a signed confirmation for this installation, which the app keeps on the phone and renews about once a week. The server does not store the purchase token, the Integrity result or the installation identifier as they are: it keeps only a keyed hash of the installation identifier and one-way hashes of the tokens, as listed next.
- What the server keeps, and for how long. For a purchase Google Play confirmed: a record of the purchase-token hash, the installation hash and the date of the last check, deleted automatically within 36 days after the last check. For each request: daily counts per installation hash and per purchase-token hash, deleted within three days after their day ends, and daily totals for the app with no identifier. If Google Play does not know a purchase token: the token's hash with that answer, for at most one hour. From an Integrity result: the facts the check needs (the app's package and the package named in the request, the time, the hash that ties the result to this request, whether Google Play recognises the app and its licence, and a one-word summary of the device check), under a hash of the result, for at most 15 minutes. Purchase records, daily counts and daily totals are deleted by a daily clean-up, which keeps to these terms when it runs normally; if a run fails or does not finish, the next day's run tries again. The other two expire on their own after the times given. After deletion, purchase records and daily counts can still be restored from the database's recovery history for up to 30 days, after which they are gone.
- Server logs keep, for at most seven days, one entry per request: the time, the request path and a request identifier, and our own fields: the first characters of the installation hash, the result or error code with its reason, whether the purchase is the subscription or the one-time purchase and its state as Google Play reports it, the outcome of the Integrity check with the one-word summary of the device check, short technical labels of how the request was handled, and how long the steps took. The log entries contain no IP address, no request headers, no tokens and no installation identifier as it is.
- Your IP address. As with any request over the internet, the request comes from your IP address and carries standard technical data, such as the time and the request headers that Android adds, which usually name the Android version and the phone model. Our hosting provider sees the IP address, as the operator of the network, to deliver the request and to protect the service from overload and abuse. To protect the service from overload, our server also counts requests per IP address: it keeps only a keyed hash of the address or of its network prefix, in memory, for a short time (usually about an hour), and never writes it to disk or to logs. The provider keeps records of requests, which include the IP address, for security and traffic statistics, for the period its own terms set; that period can be longer than the seven days of our server logs.
- Who receives it. The server runs with a hosting provider, which processes the data above on our behalf, as our processor. It may process this data outside your country, including in the United States, under its data processing terms with us, which include the EU standard contractual clauses. Google receives the purchase token and the Integrity result when the server asks it to check them, and handles them under Google's Privacy Policy. We do not pass the data above to anyone else, except where the law requires it, and we do not use it for advertising or to build a profile of you.
- On your phone. The app keeps, in the same private file as the Cacher+ status: the installation identifier; the product identifiers and purchase tokens of the purchases that turn Cacher+ on, as Google Play last reported them; the server's latest confirmation and short hashes of the purchases it covers; its last negative answer, with its time and short hashes of the purchases it concerned; when the next attempt is due and how many attempts failed in a row; since when the app has been waiting for a confirmation from the server; and when a new purchase was first seen. Android's backup and phone-to-phone transfer leave this file out. When Google Play reports no Cacher+ purchase, all of it is removed except the installation identifier and the clock note listed under "What is stored on your device". Clearing the app's storage or uninstalling removes all of it.
- Legal basis. Confirming the purchase for this installation is part of providing Cacher+, which you bought (performance of a contract, Article 6(1)(b) GDPR). Detecting unauthorised copies and misuse of purchases is our legitimate interest in protecting the app and the people who pay for it (Article 6(1)(f) GDPR); you can object to it, as described under "Your rights". The check does not rely on consent.
- Stopping it. The check runs only while Cacher+ is on this installation, at the moments listed above; it cannot be switched off on its own inside the app. Uninstalling Cacher stops it, and the server's records then expire on the terms above. Clearing Cacher's storage removes the identifier and the tokens from the phone; when the app next finds Cacher+ in Google Play, it creates a new identifier and checks again. A new identifier is not derived from the old one, but its check carries the same purchase token, so the server sees the same purchase on a new installation.
Writing to support
The support form lives in Settings, and is also one tap away from every step of a cache cleanup and from the report at the end. It composes an email for you: the address, the subject (which names the Cacher version) and your message are filled in, followed by one line with the Cacher version, the phone's manufacturer and model and the Android version. That line is there even with the diagnostics file switched off, and you can edit or delete it in the draft. Unless you switch it off, a diagnostics file is attached. The email is sent by your own mail app: it opens with the draft, and you press Send there.
The report describes the phone and the app, not you. About the app: version, install source, whether the build is debuggable, the language the app is set to and the languages the system is set to. About the phone: manufacturer, model, Android version and build, screen size and density, total and free storage, the amount of memory (RAM) and whether Android treats the phone as a low-memory device, and how Android treats Cacher in the background: whether battery optimisation applies to it, whether its background activity is restricted, and which standby bucket Android has put it in. About access: which permissions and special accesses are granted, whether the accessibility service has your consent, is enabled and is connected, whether Android itself is running the service, in which form Cacher's own entry appears in the system's list of enabled accessibility services, the system's record of Cacher's service (running or waiting to restart, how many clients and crashes, how long it has been running), and whether the app was installed from outside Google Play.
Then it describes how cleaning went: the verdict for this firmware, with how long ago its check ran, which version of Cacher ran it and whether the firmware build has changed since; whether a cleanup could start right now and, if not, why; the outcome of the last self-test, the step it stopped at and how many swipes and taps it made, and, if it ended up on a page that was not Cacher's, only whether that was another app or another Settings page, without naming it; the labels Cacher looks for on system screens (the system's own words, such as "Storage" or "Clear cache") and where they came from, which settings apps exist on this firmware, whether "Clean every cache" is on and how many apps are on your exclusion list — the number, not the apps. For the runs made since the app was last started it lists how many times a cleanup you asked for could not start and why, and for each run the mode, how long ago, duration, how many apps were in the list, how many caches were cleared and how many bytes that freed, how many were already empty, how many were tapped without the system giving anything back (and, for those, how many had under 100 kB, up to 1 MB or more of cache before the tap, and on how many the system screen itself showed the cache as cleared), counts and reasons for skips and failures, how long Cacher waited for Settings pages (the starting and the final wait, the median time a page took to open and how many opened, how many timed out and how many of those looked like a slow phone, and how many opened only after Cacher closed the shade or pressed Back over a System UI window), and how the run ended — for a run stopped by one of its rules, which rule in fixed words, such as "12 apps in a row did not reach the button", and for a run stopped by a locked phone, whether the screen was on and whether the lock screen was up. When an app's settings page did not open, the report adds what was on screen instead, only as a kind — Settings without the app's title, the home screen, a system dialog, the app itself, another app — and how many characters the title on screen and the app's name had, never which app it was; whether the screen was on and the phone locked at that moment; whether a Settings window had opened behind another window; for a system window in front, only its type as Android reports it, such as a system window or a keyboard; and whether Cacher closed the shade or pressed Back and whether Settings opened after that. It lists the first three and the last three of these per run, with the number left out in between. When the "Storage" row could not be found in some apps' settings, the run adds one line of counts about those apps together: how many were system apps, updated system apps or apps you installed, how many were disabled or on a memory card, on how many pages the row was seen but could not be tapped, the page did not open, the list ended or would not scroll, the page was covered by another window, the sizes were still being computed or the size was written inside the row's text, and the smallest and largest number of rows, size texts, scroll attempts and swipes on those pages — never which apps they were, and nothing per app. Finally the total ever freed and a few recent cleanups, where a cleanup whose files are still in the system trash is marked "[in trash]" and is not counted in that total.
If a scan failed since the app was last started, the report says how long ago, how the scan before it ended and how many scans in a row failed, and names the type of the error and the places in the program code it passed through, as class, method and line number. It never includes the error's message, because such messages can contain file names and paths. This part also lives in memory only.
Besides the verdict and the cleanup totals, four sections reach beyond the current session. TRASH shows, on Android 11 and newer, how many files Cacher has sent to the system trash that are still there and how much space they take, and how much the rest of the trash, which other apps put there, takes when Cacher can see it — numbers only, never which files. POCKET VIDEOS shows the outcome of the last search for dark stretches in videos, if there was one: how long ago it ran, how many videos it checked, how many had dark stretches and how many dark seconds they held in total — numbers only, never which videos. SERVICE HISTORY is read from the file described under "What is stored on your device", which is kept across restarts of the app: how long ago Cacher's own accessibility service was last created, connected, unbound, destroyed or interrupted, last started in the restricted backup process and last switched itself off for lack of consent, with a note on events that belong to an earlier run of the app, and the two counters since the last update. PROCESS describes Cacher's own process: how long it has been running, how long the phone has been on, whether this start followed a force stop, and, where Android keeps such records, why Cacher's last five processes ended — for example a crash, low memory or an app update, with the exit code or signal where there is one, how important the process was to Android at that moment, and whether the service was attached — and why its last three processes were started. To tell whether the service was attached, Cacher leaves Android a one-byte mark on its own process with two flags: service attached, and restricted process. From the system's records the report takes only reason codes, numbers and ages — not the system's free-text descriptions, process names or traces.
If a self-test ran since the app was last started, the report also shows how Cacher's own pages in Android Settings looked to it: the App info page and the storage page of Cacher itself. For each element on those pages it lists its type, its identifier, where it sits on the screen and its text, such as "Storage", "Clear cache" or "32 MB". These pages are about Cacher, not about you. The self-test visits only Cacher's own pages, and if a different app is on screen when it looks, that screen is not written down. This part also lives in memory only.
What is not in it: no names or package names of your other apps, no file names, no paths, and nothing you typed anywhere else in the app. The only package names it contains are those of the store or installer that put Cacher on the phone (the install source), of the system settings apps listed above, and of the settings app shown on the self-test pages. Lists the system keeps with other apps' entries in them — the enabled accessibility services, the running services — are reduced to one answer about Cacher's own service, without the other entries and without their number. The recent-cleanup memory, which holds package names, is not read into the report, and neither is the squeeze estimate with its media-library numbers, the list of files sent to the trash, which holds file names, or the months marked in Photos by month. Times are written as relative ages such as "2 h ago", not as exact timestamps, because a list of exact times across months would describe your daily routine. The per-run counters and the last scan failure live in memory only and disappear when the app process ends. What the report carries across restarts is the SERVICE HISTORY, PROCESS, TRASH and POCKET VIDEOS sections described above and the long-term facts listed earlier: the firmware verdict, the total ever freed and the recent cleanups.
The whole file is shown on screen before you send anything, and you can read every line of it. It is written into the app's own cache folder, and the mail app you pick receives a one-time read grant for that single file. Mail sent this way reaches cacher@gi-gante.com and is used only to answer you and to fix what you described. It is kept in our mailbox, which an email provider hosts for us as our processor. That provider may process it outside your country, including in the United States, under its data processing terms with us, which include the EU standard contractual clauses.
Network access and data sharing
Cacher has no account system. Without Cacher+, the app's own code makes no requests to any server; with Cacher+, it makes one, the purchase check described under "Cacher+ purchase check". What the app works with — scan results, measurements, your settings and history — is not sent by the app to the developer or to third parties. It leaves the phone only through Android's own backup, if that is switched on, through a support email, if you send one, and through the store links described below, when you tap them.
Two Google components inside the app work with Google over the network. The Google Play Billing library contacts Google Play about purchases. It comes with Google's data-transport component, which the library can use to send Google its own technical logs about the purchase flow; Cacher does not receive them. The Google Play Integrity library is asked for a result only for the Cacher+ purchase check; what Google receives for it is described there. Your use of Google Play, including those logs, is covered by Google's own privacy policy. The support screen is no exception to any of this: it prepares a draft, and your mail app sends it.
A few places hand you over to Google Play instead. After a large cleanup Cacher may ask Google Play to show its rating card, through Google's In-App Review library: the card is drawn by the Play Store app, what you enter there goes to Google Play, and the library does not tell Cacher whether you rated the app or what you wrote. "Rate on Google Play" and "Other apps by us" in Settings open a page in the Play Store when you tap them, or in your browser if there is no Play Store. The "Play Store" button on an app's detail screen opens that app's page in the Play Store, or in whichever store app handles such links on your phone. "Manage subscription in Google Play" on the Cacher+ screen opens your subscriptions there. The links in "Other apps by us" carry a tag naming Cacher and that list as their source, so that Google Play Console can show the developer how many installs came from it. The one link that leads elsewhere is "Privacy policy" in Settings, which opens this page in your browser.
Analytics and advertising
The current version of Cacher contains no analytics, crash-reporting or advertising SDK, in the free version and with Cacher+ alike. It does not read the advertising ID and does not build a profile of how you use your phone. The Cacher+ purchase check is not analytics: it is used only for the purposes given in its section.
How this appears in Google Play's Data safety section
Google Play counts data that leaves the phone through any library inside an app, as well as through the app's own requests, so the Data safety section for Cacher lists four data types. Diagnostics: the technical logs the Google Play Billing library sends to Google (described under "Network access and data sharing"), which Cacher cannot switch off; the diagnostics file of a support email, which you can leave out; and, for Cacher+ owners, the app version and the Integrity result or error code sent with the purchase check. Email address: only when you write to support, because the developer receives it with your message. Purchase history: the purchase tokens and product identifiers that the Cacher+ purchase check sends. Device or other IDs: the random installation identifier and the device check inside the Integrity result, sent by the same check. Purchase history and Device or other IDs are marked as required: without Cacher+ the app sends neither, but a Cacher+ owner cannot turn the check off. Email address is marked as optional. For the data of the purchase check the purposes given are app functionality and fraud prevention, security and compliance; Diagnostics is also declared for analytics, because of the Billing library's logs. Under Google Play's definitions none of this counts as shared: our hosting provider and the provider that hosts our mailbox process it on our behalf, and Google receives the purchase and Integrity data to check them for us. The form states that data is encrypted in transit: the app's own connections, including the purchase check, use HTTPS only, the Billing library's logs travel over an encrypted connection, and a support email is sent by your own email app. You can ask at cacher@gi-gante.com for your correspondence to be deleted, and for the records of the purchase check to be deleted before they expire on their own (see "Data retention and deletion").
Data retention and deletion
Everything listed under "What is stored on your device" is stored on your device, and the part listed under "Android backup" also in your Android backup if that is switched on. Some of it removes itself: the recent-cleanup memory after about ten minutes (or, if the app's process ended first, at its next start), a squeeze failure at the next estimate once it is more than 30 days old, a live-photo failure once it is more than 30 days old, an entry in the list of files sent to the trash once Cacher sees that the file has left the trash, a daily storage snapshot after 60 days, and the daily sizes of apps, the records of cleared caches and the measurements after cleanups after 120 days. The list of files moved to a memory card or USB drive lives on that drive and stays there until you delete it, along with the copies it describes. You can erase all of it from the phone at any time through Android's "Clear storage" for Cacher, or by uninstalling the app. Neither removes the copy in Android's backup: that copy is kept by Google under your account and is managed in your phone's or Google account's backup settings. Apart from what you send in a support email, the developer holds no copy of what is stored on your device and therefore cannot delete it on your behalf.
For Cacher+ owners, the developer's server keeps the records of the purchase check described under "Cacher+ purchase check", and deletes them automatically: the record of a confirmed purchase within 36 days after the last check, daily counts within three days after their day ends, the note that Google Play did not know a purchase token after at most one hour, the facts read from an Integrity result after at most 15 minutes, the keyed hash of an IP address or its network prefix, which exists only in the server's memory, after a short time, usually about an hour, and log entries after at most seven days. The daily clean-up of purchase records and daily counts keeps to these terms when it runs normally; if a run fails or does not finish, the next day's run tries again. Deleted purchase records and daily counts can still be restored from the database's recovery history for up to 30 days. Our hosting provider keeps its own records of requests, with the IP address, for the period its own terms set (see "Cacher+ purchase check"). The server's records hold no name, email address or account, and we do not link them to you ourselves. If you send us the order number from your Google Play receipt, we can look up the purchase token of that order in Google Play and delete the records of that purchase, which our server keeps under the token's hash, before they expire; otherwise they expire on their own on these terms. Uninstalling Cacher stops the check, and its records on the server then expire on these terms.
What the developer also holds is support email. A message you send to cacher@gi-gante.com, with your email address and any diagnostics file you attached, is kept in the developer's mailbox, which an email provider hosts for us as our processor, until you ask for it to be deleted. To have it deleted:
- write to cacher@gi-gante.com from the same address, with "Delete my data" in the subject;
- your messages, the replies and any attachments are deleted within 30 days, and you get one email saying it is done;
- there is no account; the records of the Cacher+ purchase check hold no name or email address and are deleted automatically on the terms above. To have them deleted sooner, add the order number from your Google Play receipt, and we delete the records of that purchase too.
The technical logs that the Google Play Billing library sends to Google go to Google, not to the developer, so the developer can neither see nor delete them; they fall under Google's privacy policy. So do what Google receives to make a Play Integrity check and the record of your purchase in your Google Play account.
Children
The app is a general-purpose utility and is not directed at children. The app itself asks no one, of any age, for personal information. What reaches the developer is a support email that someone chooses to send and, for Cacher+ owners, the purchase check described above, which carries no name, email address or age.
Legal bases
Most of what this policy describes stays on your device and is not processed by the developer at all. Where the developer does process personal data, the legal bases under the EU and UK GDPR are these:
- The Cacher+ purchase check: performance of the contract for Cacher+ (Article 6(1)(b)), to confirm your purchase for this installation, and our legitimate interest in preventing unauthorised copies of the app and misuse of purchases (Article 6(1)(f)). The handling of your IP address by our hosting provider, and the count of requests per IP address on our server, serve the same purposes and the security of the service.
- Support email: you wrote to us, and answering you and fixing what you describe is our legitimate interest (Article 6(1)(f)), or part of the contract when it concerns Cacher+ (Article 6(1)(b)).
Android's backup, Google Play Billing, the Play Integrity check on your phone and the Google Play rating card are run by Google under its own terms and privacy policy.
Your rights
Data protection laws such as the EU and UK GDPR give you rights over your personal data, including access, correction, deletion, restriction of processing, portability and the right to object. Most of what Cacher works with never reaches the developer: it stays on your phone, where Android's "Clear storage" for Cacher or uninstalling the app deletes it. For support email, write to cacher@gi-gante.com and we will answer, send you a copy or delete it. The records of the Cacher+ purchase check hold no name, email address or account, and we do not link them to you ourselves; they are deleted automatically on the terms under "Cacher+ purchase check". If you send us the order number from your Google Play receipt, we can find the records of that purchase, tell you what they hold and delete them sooner.
You can object at any time to the part of the purchase check that rests on our legitimate interest. Write to cacher@gi-gante.com, and we will look at your situation and answer within 30 days. The check itself cannot be switched off inside the app: it stops when Cacher+ is no longer on the installation or when you uninstall Cacher.
You can also lodge a complaint with the data protection authority where you live.
Changes to this policy
This policy may be updated as the app changes. Material updates are reflected on this page, and the "Last updated" date changes with them.
Contact
Cacher is published by Gi-Gante s. r. o., a company established in the European Union.
Write to cacher@gi-gante.com — the same address the in-app support form uses — with privacy questions or anything else about the app.
The Google Play listing for Cacher carries the current support contact. If it ever changes, that listing is the authoritative source.