Google Play apps, reviews, permissions, and data safety
Play Store apps, reviews, permissions, and data safety as JSON. Not Play Console. Not Play Framework.
Say Google Play, not bare “Play.” googleplay.fetcher.sh returns store listings: search, app details, similar apps, developer catalogs, reviews, permissions, and data safety. Those last two barely exist elsewhere in the catalog, and they are why this host is not just another app search.
This is not Play Console for publishers and not Play Framework the web toolkit. It is not how to publish an app, and it is not the Apple App Store. Official Play Developer API lives in Cloud; this host does not.
Search takes search, optional price (all, free, paid), optional country and lang. An app id from that storefront unlocks details, similar apps, reviews, permissions, and data safety. A developer id unlocks the rest of that publisher’s public catalog.
Listings plus compliance fields
curl -H 'Authorization: Bearer bby_live_…' 'https://googleplay.fetcher.sh/api/apps?search=meditation&price=free'
Then, for an id you kept:
/api/apps/{appId}— the listing/api/apps/{appId}/similar— the neighborhood/api/apps/{appId}/reviews— software ratings, not Maps/api/apps/{appId}/permissions— what the listing claims/api/apps/{appId}/datasafety— the data-safety section as data
ASO uses similar apps and reviews. Reviews as research is the qualitative feed. Storefronts by country is the geo parameter.
Country and price filters are on search; similar apps need an app id from that same storefront. An id you found on the US store is not a promise about the German listing. Search country=de if Germany is the question.
How to read permissions without becoming a lawyer
Permissions and data safety are why security-minded readers land here. They are still the listing’s claims, not a dynamic analysis of the APK you sideload. Treat them as what Google shows on the store page, structured.
A school, a parent, a procurement person: search, shortlist, fetch permissions and data safety before they fall into reviews. Reviews tell you if the meditation timer is annoying. Permissions tell you if it wants the contact list. Those are different questions. Mixing them in one skim is how a “nice reviews” app with a loud permission set sneaks through.
Play Console remains how publishers ship. You cannot submit a build through this host. You cannot read private crashlytics. You can read what everyone else can read, as JSON, without a Cloud project.
A case: a school that only allows certain permissions
An IT lead is reviewing meditation apps for a student program. They search free apps, fetch permissions and data safety on the shortlist, and only then read reviews.
They are not using Play Console. They are not shipping an app. They are answering “what does this APK claim to access?” with JSON instead of screenshots.
They keep a boring allow-list: no contacts, no SMS, data safety that does not look like a tracker farm. Apps that fail that bar never make it to the pedagogical debate. The Apple store is a different host if the same question exists for iOS.
A case: a PM comparing a competitor’s data-safety copy
A PM is rewriting their own data-safety section. They pull the competitor’s /datasafety and their own, and they diff the categories in a spreadsheet. They are not asking Google for an audit. They are reading the public store the way a user would, at a scale screenshots cannot do.
Reviews go in a second pass, under app store reviews as research. Permissions go in this pass. Similar apps tell them who else is in the neighborhood so they are not diffing a random meditation timer against a bank.
Developer catalogs are how you see the rest of a publisher’s public apps without guessing search keywords. A sketchy permission set on one “flashlight” is more interesting if the same developer id ships twelve other flashlights. Fetch /api/developers/{developerId} after you have it from the listing.
price=free was the featured filter because procurement people need it. country=de plus price=paid is the other featured example: storefront and SKU together. Search is not details. Do not skip the app id fetch and trust a search snippet for data safety.
Console vs storefront
Play Console stays the publisher product. This host reads the public store. Docs on googleplay.fetcher.sh. Pay per call or a bby_live_ key from /topup.
If you needed the official Play Developer API, you are in Cloud, and you probably already know that. If you needed iOS, you want appstore.fetcher.sh, not a country flag on Play.