Privacy Policy — SD Card Test

Last updated: 18 September 2026

SD Card Test (package com.bok.sdcheck) checks whether a memory card or USB drive really holds the amount of storage it reports. This page explains what the app does with information.

Information the app collects

The app uses Google Analytics for Firebase and Firebase Crashlytics to understand how it is used and to find crashes. There is no account and no sign-in. What is sent is a short record of what kind of test was run and how it came out.

Specifically, the app sends:

• How many storage volumes were found, and how many of them were removable.
• Which test you started (quick or full), whether the volume was internal or removable, and the size of the volume as a range rather than an exact figure (for example "8_32", "128_512").
• The verdict — genuine, false capacity, damaged, or did not finish — and roughly how long the test took.
• If you stopped a test, at which stage and roughly how far it had got.
• Whether you saved or sent a report, and whether that succeeded.
• If something went wrong, a fixed error code and a shortened error message with any file path removed.

The app does not send:

• The path of the card or drive. That path contains an identifier for your card, so it is deliberately left out.
• The card's serial number, manufacturer or exact capacity.
• The contents of any report you produce.
• Anything at all about the files already on your card — the app never reads them.

Firebase itself adds some technical information to every record: an app instance identifier, your device model, Android version, app version, session timing, and an approximate region worked out from your IP address. Crashlytics adds a crash stack and device details when the app crashes.

Advertising

The app shows a banner at the bottom of the screen and, occasionally, a full-screen ad. Ads are served by Google AdMob. To serve and measure them, AdMob may use your device's advertising ID and an approximate location worked out from your IP address. This is the one place where your advertising ID is read; it never appears in a report you produce.

The banner stays at the bottom while a test runs. It does not touch the card and does not affect the result: the test measures storage, while the ad uses the network. Nothing is written to your card on behalf of advertising.

A full-screen ad appears only when you finish a test and leave the result screen with Done, and not every time. It never appears when you start a test, when you stop one part way through, or when you save or send a report. If an ad fails to load or is blocked, every test still works exactly the same.

In the European Economic Area and the UK, a consent form is shown before any ad is requested, using Google's User Messaging Platform (UMP). You can reopen it at any time from Ad privacy settings at the bottom of the home screen. Outside those regions the form is not shown and the link is hidden.

Permissions

The app asks you for no permissions. Writing to a card uses the private folder Android gives every app on each storage volume, which needs no storage permission, and saving a report uses Android's own file picker.

Firebase and the advertising SDK add a small number of background permissions that Android does not prompt you about: internet access, network state, a wake lock, an attribution permission used by analytics, and the advertising ID permission used by AdMob to serve and measure ads. None of these show a permission prompt, and none of them give the app access to the files already on your card.

What the app writes to your card

To test a card the app has to write to it. It writes only inside its own folder, which Android gives every app on each storage volume, and it deletes those files when the test finishes or is interrupted. Your photos, videos and other files are never read, moved or deleted.

The app reads the reported capacity and free space of each volume so it knows how much to test. That information is used while you are looking at it and is not stored or sent anywhere.

Reports you create

The app can produce a plain text report of the result. Nothing happens to it unless you choose:

• Save as file asks Android to let you pick a location. The app writes the file where you point it and has no other access to your storage.
• Send hands the text to whichever app you choose. What happens next is governed by that app's own privacy policy, not this one.

The report contains no serial number and no account details. It identifies the phone only by model name and Android version, because the report is meant to be handed to a stranger such as a seller or a marketplace.

Children

The app is not directed at children. Beyond the anonymous usage records and the advertising identifier described above, it collects no information from anyone, including children.

Your choices

You can reset or delete your advertising ID under Device Settings → Google → Ads, and opt out of personalised ads with the ad personalisation option in your device settings. In the European Economic Area and the UK you can reopen the ad consent form from Ad privacy settings at the bottom of the home screen. You can ask for the analytics records associated with your installation to be deleted by emailing the address below. Uninstalling the app also stops all further collection.

Changes to this policy

If a future version adds anything further that touches your information, this page will be updated before that version is published, and the date at the top will change.

Contact

Questions about this policy: leeedaebok@gmail.com