Skip to content
New: the free AppMetis browser extension puts measured installs and chart places on every Google Play and App Store page →
AppMetis
Removed appsData

Why we keep a removed apps archive

When an app leaves the App Store or Google Play, its public record goes with it. AppMetis keeps last known listing details for due diligence, competitor research, policy trends and fraud work.

AppMetis team Updated 11 Nov 2026 5 min read
Isometric landscape of bar chart towers and app tiles under a magnifying glass
On this page

When an app disappears from the App Store or Google Play, its store page goes with it, and so does the public record of what the app was, who made it and how big it got. AppMetis keeps the last known listing details of removed apps, so you can still look them up for due diligence, competitor research, policy tracking and fraud work. We keep listing details, not app files, and developers can ask for contact data to be masked or corrected through our data removal page.

What the archive is for

Due diligence

If you are investing in a studio, acquiring an app or signing a publishing deal, the developer's past matters as much as its current portfolio. A store page shows what is live today. The archive shows what used to be there: apps that were pulled, how many installs they had reached and when they disappeared. A developer with a run of removed apps in one category is a question worth asking before you sign.

Competitor exits

A competitor's app vanishing is a signal. It may have shut down, been taken down over a policy problem, or been relisted under a new package name after a rebrand. Each case means something different for you, and each can leave users looking for an alternative. With the archive you can see the last known install count and ratings of the app that left, which tells you the size of the opening.

Store policies change, and removals in a category can rise after a policy update or an enforcement sweep. Watching removals by category over time shows where enforcement is heading, which matters if you publish in a category under scrutiny or advise clients who do.

Clone and fraud patterns

Some removed apps come back in another form: the same icon and description under a new package name, or the same developer details under a new account. Trust and safety teams, ad networks and researchers can use last known details to connect a new listing to a removed one, and to spot templates that keep reappearing.

Research

App churn, store policy and market lifecycles are hard to study when the evidence keeps disappearing. A stable archive gives analysts and academics a record that does not depend on what happens to be live today.

How the archive is built

Our catalog syncs check listings on a regular cycle. When a listing that was live comes back as not found, the app is marked as removed and its last known details are kept. If the app returns later, its status goes back to live.

For delisted Google Play apps, we also reconstruct details from public Internet Archive (Wayback Machine) snapshots of the store page. This recovers apps that left before our own syncs recorded them in full. A reconstructed record shows the app as it was on the capture date, not on the day it was removed, and it is dated to that snapshot.

Removal dates follow the evidence. When we saw an app live and then gone, the removal is dated to when we noticed. When an app is known only from an archived snapshot, we record when it was last seen live. Stores do not publish reasons for removals, so the archive records that a listing disappeared, not why.

What we keep and what we do not

We keep the last known listing details:

  • App name, developer, category and store identifier, such as the package name on Google Play
  • Last known install figures, ratings and review counts
  • Last known version and when it was released
  • Developer contact details as they were publicly listed on the store at the time

We do not keep app binaries, so there are no APK or IPA files in the archive. We also do not guess at removal reasons.

Reading a removed app record

  • Removed is a status, not a verdict. Developers unpublish apps for ordinary reasons: a product shuts down, a company rebrands or trims its portfolio, a licence ends. Do not read a removal as proof that an app broke a rule. The guide on why apps get removed from the stores covers the common causes.
  • Check the date basis. A removal date is when we noticed the listing was gone, and a reconstructed record reflects its snapshot date.
  • Look for the other store. If the app belongs to a cross-store app family, check whether it left one store or both.

Putting the archive to work

A few ways to use it in practice:

  • Before a deal, open the developer's profile, which lists removed apps next to live ones, and note when each one disappeared and how far it had grown.
  • When a competitor goes quiet, check whether its app was removed, then look for a new listing with the same name or icon from the same developer.
  • For category research, include removed apps in your search results and compare removals per quarter with new releases in the same category.
  • For ongoing monitoring, watch the apps that matter to you and get an alert if one is removed from its store.

An example with made-up details: a publisher you are assessing shows 14 live apps. The archive shows 9 more removed over two years, 6 of them within a single quarter and all in the same category, and two reappear under new package names with the same icon. None of that proves wrongdoing, but it gives you three specific questions to ask before you sign.

Contact data and removal requests

The archive keeps the developer contact details that were publicly listed on the store, because they are part of the record of who published an app. Those details can go stale, and a developer may not want an old address attached to a removed app. Developers can ask for contact details to be masked or corrected through the data removal page. Contact details are also masked on lower Market Intelligence plans.

Where to find it

The free removed apps page lists recent removals from Google Play with their last known details. In the product, new and removed apps adds the full history, search filters and exports on paid plans.

Frequently asked questions

Why do apps get removed from the App Store and Google Play?

Stores remove apps for policy, security or account problems, and developers also unpublish apps themselves, for example after a shutdown or a rebrand. A removed status on AppMetis records that the listing is gone, not why.

Does AppMetis keep the app files of removed apps?

No. The archive keeps last known listing details, such as name, developer, category, ratings and install figures. It does not keep app binaries.

Where do details of delisted Google Play apps come from?

From our own catalog syncs where we recorded the app while it was live, and otherwise from public Internet Archive (Wayback Machine) snapshots of the store page, dated to the snapshot.

How can a developer correct or mask contact details in the archive?

Through the data removal page at appmetis.com/data-removal, where developers can ask for publicly listed contact details to be masked or corrected.

Related posts

All blog →

Also on our guides

Start with real numbers today

Free forever plan. No card needed. Upgrade when AppMetis earns it.