Privacy & Data Policy
Last updated: 9/25/2026
What we store, and for how long
When you upload a patch or rollback archive, we extract and (where applicable) decompile it on our server so you can view the diff. That content — the uploaded archives, extracted files, and decompiled source — is deleted automatically as soon as you download a report or navigate away from the results page, and in any case no later than 24 hours after upload, whichever comes first. We do not keep a copy of your code beyond that.
What we do keep
We keep a lightweight, permanent record of each comparison for reliability and abuse-prevention purposes: the file names and sizes you uploaded, your IP address and approximate location (city/region/ country, derived from that IP), whether the job succeeded or failed, and — if you're signed in — your account email. This record never includes the contents of your files.
Sign-in
You are never required to sign in to compare or decompile files — an anonymous session is created automatically. Signing in with Google is optional and only meaningfully matters for the small number of accounts with administrative access to the aggregate usage dashboard described above; that dashboard never exposes file contents either.
Third parties
Uploads are processed on Google Cloud (Cloud Run, Cloud Storage, Firestore). IP geolocation is resolved via a third-party lookup service using only your IP address, not any file content.
Questions
See something wrong, or have a question about your data? Send us feedback.