AGDM Root Checker data deletion
No AGDM account
AGDM Root Checker does not create an AGDM user account. There is therefore no AGDM account or cloud profile to close.
Delete data stored on your device
- Delete individual history entries through the App where that action is available.
- To remove all App-private settings, consent state, history, aggregate installed-app scan metrics, reports, and pending verification state, open Android Settings → Apps → AGDM Root Checker → Storage → Clear data.
- Uninstalling AGDM Root Checker also removes its App-private data because Android backup and device transfer are disabled for this data.
- Delete exported or shared reports from the folder, cloud service, email, or messaging app where you saved or sent them.
AGDM server data
Successful Play Integrity and subscription-entitlement request bodies and results are not retained as AGDM records by either the Google Cloud Run primary service or the independent Hostinger fallback. Raw tokens, nonces and request bodies are processed in memory and are not written to AGDM application logs or databases. The backend's abuse-prevention state for the raw connection IP is held in process memory without geolocation. Request records expire after 24 hours plus approximately one minute for cleanup; the IP entry disappears when no current records remain, or earlier if the process restarts. Continued requests can keep the entry active.
Technical security logs and IP addresses
The memory-only rule above applies to the backend's raw-IP abuse-prevention state, not to all infrastructure logs. Minimized application security logs can contain the event time and type, method, category or reason, a masked network address and a per-process HMAC fingerprint of the IP. These are pseudonymous identifiers, not a guarantee of anonymity. Hostinger application logs are limited to seven days; Google Cloud application logs to 30 days. VPS operating-system security logs can contain full source IP addresses for network events. The system journal is configured for seven-day retention with daily file rotation. UFW firewall and rsyslog text logs rotate weekly and keep the current file plus four archives. Older copies of these files can remain in provider backups until backup rotation removes them.
Minimized Hostinger application logs expire within seven days. Minimized Google Cloud application logs expire after 30 days; Cloud Run infrastructure request logs are excluded so that raw request IPs and URLs are not retained in the _Default log bucket. Mandatory Google Cloud administration and system-event records are retained in the locked _Required bucket for 400 days and do not contain AGDM request bodies or Play tokens.
An unacknowledged Google Play Real-time Developer Notification can be retained by Google Cloud Pub/Sub for no more than 24 hours. Hostinger rotates full daily and weekly VPS backups according to the provider's schedule. These copies can contain files already deleted from the live server; that content remains until the provider removes the particular backup during rotation. A fixed calendar deadline for removal from all provider backups is not guaranteed here.
Request assistance
Email agdmsoft@gmail.com with the subject “AGDM Root Checker data deletion”. Do not send a Play Integrity token, purchase token, password, payment data, or full device report. AGDM will respond within 30 calendar days and explain whether any data capable of being associated with the request exists. Because successful requests are not retained as AGDM records, there is normally no server record that can later be located by install ID, request ID, package name or purchase token; temporary protection state and retained provider logs expire automatically under the periods above.
See the Privacy Policy for the complete processing and retention description.
Deleting data or uninstalling does not cancel your subscription. Manage or cancel it separately in Google Play.