Privacy policy

How 16kb Checker handles information for this website: local scans in your browser, optional analytics when you opt in, and the Support form.

Last updated: May 11, 2026. Also read our Terms of service. Technical detail: Documentation.

Summary

  • Build files (.apk, .aab, up to 150 MB) are analyzed only in your browser. We do not upload those packages to our servers to run the scan.
  • Scan results are stored in this browser tab in sessionStorage under a key like scan_ plus your scan id. They can disappear if you close the tab, clear site data, use a private window, or hit storage limits.
  • Theme uses localStorage key 16kb-checker-theme (light / dark / system) so your choice persists.
  • Cookie choice for measurement is stored in localStorage as 16kb-checker-cookie-consent (accepted or declined).
  • Support messages go through Web3Forms so we can reply by email, as described below.

1. Who this applies to

This policy covers visitors and users of the public 16kb Checker website (the “Service”) as we host it. If someone else runs their own copy of the software or a fork, the operator of that site is responsible for their own privacy practices; this document describes our deployment of the Service.

2. Scans, results, and exports (your device)

When you scan, the app reads your file in memory, unpacks and inspects it (ZIP layout, native libraries, manifest, size breakdown, and related checks described in our Documentation). Outputs are built on your device. Successful scans are written to sessionStorage using a key that starts with scan_ followed by your scan id, so the results page can load them in the same tab.

Exports (JSON, CSV, HTML, print/PDF) are generated in your browser from the saved scan. Exporting does not upload your package to us; you choose where downloaded files go.

Anyone with access to your device, browser profile, exported files, or screenshots can see what you analyzed. Do not use the Service on a shared machine for confidential builds unless you understand that risk.

3. Support form (Web3Forms)

The Support page sends your name, email, and message to Web3Forms, which delivers the message to us. Web3Forms processes that submission on their systems under their privacy policy. Do not paste signing keys, passwords, or full app source in the form unless you accept the risk of it being stored or forwarded with your ticket.

4. Technical and hosting data

Our hosting and network path may create ordinary server or CDN logs (for example IP address, rough region, user agent, time, and URL) for reliability, security, and abuse prevention. We use that to run the site, not to sell contact lists.

5. Cookies, local storage, and analytics

We use localStorage for theme and cookie-banner choice, and sessionStorage for scan payloads as above. You can clear these in your browser; clearing may remove saved scans and show the cookie banner again.

If you click Accept on the cookie banner and our Firebase config is present in the deployment, we load Google Analytics for Firebase to understand traffic and product usage (for example page views, scan completion, export actions, and support outcomes). Event parameters are coarse—things like file extension, counts, and pass/fail summaries—not your app package name or file contents. We do not use this for ads or third-party profiling. If you click Decline, that measurement code is not loaded until you accept later.

6. Third-party services

The Service loads fonts and icons from Google Fonts / Material Symbols, may use Firebase when analytics is enabled, and uses Web3Forms for Support. Those providers handle technical data under their own terms. We do not control their independent practices.

7. Retention

We do not keep your application packages on our servers as part of the scanning flow. Support messages may be retained as long as needed to respond and keep operational records. Server logs follow our host’s normal retention.

8. Security

We apply reasonable safeguards for the Service and data we handle. No browser or network transmission is perfectly secure; use judgment for highly sensitive builds.

9. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, or restrict personal data, or to object to certain processing. For requests about Support submissions or hosting logs, contact us via Support. We may need to verify your request. EEA/UK users may also complain to a supervisory authority.

10. Children

The Service is a developer tool, not directed at children under 16. If you believe we received a child’s personal data in error, contact us and we will take appropriate steps.

11. International users

If you use the Service from another country, data may be processed where our providers operate. Where required, we rely on appropriate safeguards or legal bases for cross-border processing.

12. Changes

We may update this policy. We will change the “Last updated” date and, for material changes, post a reasonable notice on the site.

13. Contact

Privacy questions: Support.