privacy-policy.mdPrivacy policy
Drafted from the data your code actually touches, to a GDPR baseline.
Manifest Match reads your app, drafts the documents Google Play asks you to file, and points at the places where those documents and your code do not agree.
Run it on your repositoryPoint at any node to see what that agent produced
0 rules
evaluated deterministically against your code, not guessed at
Every fact cited
a file and a line number behind each statement
Gaps stated
what the scan could not reach, in every report
Every mismatch it reports is exactly this: a line in your code, and a declaration that disagrees with it.
<uses-permission android:name="android.permission.INTERNET"/><uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/><uses-permission android:name="com.google.android.gms.permission.AD_ID"/>RULE-LOC-001
collected: nocollected: yesThe manifest declares precise location. The form says none is collected.
privacy-policy.mdPrivacy policy
Drafted from the data your code actually touches, to a GDPR baseline.
terms.mdTerms of service
A matching draft, with the same disclaimers attached.
data-safety.tsvData Safety answers
One row per data type, each carrying the code line it rests on.
findings.jsonReview risks
Every rule that fired, with the official Play policy beside it.
store-listing.txtStore listing
Title, description and keywords that claim only what the code supports.
Read-only
A shallow clone, read, then deleted when the run ends. Nothing is written back.
One destination
Source excerpts go to Google's Gemini models to produce the drafts. Nowhere else.
Nothing is filed
It submits nothing on your behalf. Every output is a draft you review and file yourself.
Deleted after 30 days
A Firestore retention policy on the data itself, not a promise. Nothing trains on it.
Unguessable URL
Your report lives at a random address. Anyone holding it can read it, so treat it as private.
Android and Google Play. Flutter and native Android are parsed deterministically; React Native and web are best effort. iOS is under consideration — the rule catalogue is a separate, swappable file, so an App Store edition means adding one catalogue rather than rebuilding the engine.
This is a drafting tool, not a lawyer and not a compliance guarantee. It will not tell you that your app is compliant or that it will pass review, because no tool can honestly say either. What it will do is show you the facts in your own code, cite the official policy beside them, and be explicit about the parts it could not check.