Effective date: 14 October 2026 · Last updated: 2 November 2026
The short version
- PhoneLab asks for no account or sign-in and has no server of its own. We, the developer, do not receive your test results, readings, photos or recordings.
- Every test runs on your phone, and results are kept in the app's private storage until you delete them.
- A report leaves your phone only when you share it, to the app or person you pick.
- The app is free and shows ads from Google AdMob. Google collects some device data to show and measure ads, as described below. Where the law requires it, you are asked first.
- To fix bugs and improve the app, it sends crash reports and basic usage events through Google Firebase, never your results. Where the law requires it, this happens only if you agree. We do not sell your data.
1. Who we are
PhoneLab ("PhoneLab", "we", "us") is an Android app for testing phone hardware, published on Google Play under the package name com.phonelab.app. This policy covers the app and this website. For any question about privacy, write to phonelabtools@gmail.com.
For the data that stays on your phone, nobody but you controls it. For the data collected by Google's advertising service, Google acts as an independent controller (or, for some purposes, a processor) under its own terms and privacy policy.
2. Data that stays on your phone
To test the hardware, the app reads from the phone's parts and keeps the results. All of this is stored in the app's private storage, which other apps cannot read, and is never sent to us.
- Test results and readings: whether each test passed, and what it measured, such as battery health and charge cycles, screen refresh rate, storage speed, sensor rates, signal strength, or the number of GPS satellites in view.
- Device details: brand, model, Android version, security patch date, chipset, number of processor cores, memory and storage size, and screen resolution. They are shown in the app and printed on reports.
- Network details: for the connectivity tests, the type of mobile network, the operator's name, whether a SIM is present, and the number of nearby Wi-Fi networks or Bluetooth devices. The Wi-Fi analyzer shows nearby network names on screen; they are not stored.
- IMEI: the IMEI test keeps only the last four digits, to compare with the box or the seller's listing. You choose whether they appear on a report.
- Touch map: a picture of which parts of the screen answered your touch, saved with the check.
- Condition photos: if you take photos of the phone's body during a check, they are saved with that check only, in the app's private storage.
- Camera and video tests: the photo or short video taken to test a camera is written to the app's temporary cache and deleted again; it is not kept with your results.
- Microphone tests and the sound meter: sound is measured in memory while the test runs. Nothing is recorded to a file or uploaded.
- Location: the GPS test counts satellites and times the first fix. Your coordinates are not stored, shown or sent anywhere by PhoneLab.
- Fingerprint test: uses Android's own fingerprint prompt. The app is told only whether a finger was recognised; it never sees fingerprint data.
- Settings and battery history: your app preferences, and, only if you switch it on, one battery reading a day so you can see how the battery ages.
3. Permissions and why they are needed
Each permission is asked for when its test comes up, with the reason on screen. You can refuse any of them; only the tests that need it are skipped, and they don't count against the score.
| Permission | Used for |
|---|---|
| Camera | Testing each camera, autofocus, flash, video, zoom and lens spots; condition photos if you take them. |
| Microphone | Testing the microphones, the earpiece and loudspeaker loop-back, and the sound level meter. |
| Location | The GPS test, and listing nearby Wi-Fi networks, which Android only allows with location. |
| Nearby devices | The Bluetooth test and Bluetooth audio. |
| Physical activity | The step counter test. |
| Phone | Reading the SIM state, network type and the IMEI's last four digits. |
| NFC, vibration, biometrics | The NFC test, the vibration motor test and haptics, and the fingerprint test. |
| Change audio settings | Sending a test tone to the earpiece or loudspeaker and setting the volume for that moment. The volume is put back afterwards. |
| Wi-Fi and network state | The Wi-Fi and internet tests. |
| Internet | Loading ads, sending crash reports and usage events through Firebase, checking for updates, and the test that checks your internet connection. No test sends your results anywhere. |
| Advertising ID | Used by Google AdMob, as described in section 5. |
4. Reports you share
You can save or share a check as a PDF or an image. When you do, Android's share sheet opens and you choose where it goes: a messaging app, email, your files or a printer. The report contains the device details, the score, and each test's result. Condition photos and the last four IMEI digits are left out unless you switch them on for that report. What happens to a report after you share it depends on the app or person you sent it to.
Reports carry two QR codes: one holds a short summary of the result (score, date, report number), and one links to PhoneLab on Google Play. Neither links to any data of yours online.
5. Advertising (Google AdMob)
PhoneLab is free because it shows ads. Ads are provided by Google AdMob, a service of Google LLC (and, for users in the European Economic Area, the UK and Switzerland, Google Ireland Limited). The app shows two kinds:
- a full-screen ad after a finished check, at most three a day, never after your first check, and never while a test is running;
- an optional short ad you choose to watch to save or share a report. Once watched, that report stays unlocked.
To show, limit, measure and protect these ads, the Google Mobile Ads SDK in the app collects and sends to Google:
- the phone's advertising ID;
- the IP address, which Google may use to estimate an approximate location (such as the country or city);
- device and app information, such as the model, operating system version, language and app version;
- ad interactions, such as which ads were shown or tapped, and diagnostic data about ad performance and crashes in the ad SDK.
Google uses this data to deliver ads, to cap how often you see them, to measure them, to prevent fraud and abuse, and, only if you allow it where consent is required, to personalise ads. PhoneLab never passes your test results, readings, photos or recordings to Google or to any advertiser.
The highest content rating allowed for ads in PhoneLab is "Teen". Learn more about how Google uses data in How Google uses information from sites or apps that use our services and in Google's Privacy Policy.
6. Crash reports and usage (Google Firebase)
PhoneLab uses three services from Google Firebase to keep the app working and to learn which parts are used. They need an internet connection, and no test depends on them.
- Firebase Crashlytics: if the app crashes, it sends a crash report: where in the code it failed, the time, the app and Android versions, the phone model, whether the app was in the foreground, and an ID for this install of the app.
- Google Analytics for Firebase: basic usage events: that a check was started or finished and its type, which tool was opened, and that a report was saved or shared and in which format. It also records app opens, time in the app, app version, phone model, Android version, language, and an approximate region. It runs without the advertising ID, and its data is not used for advertising.
- Firebase Authentication: creates a random anonymous ID for this install of the app. It is not tied to your name, email, or phone number, and you never sign in or see it. Nothing in the app needs it today; it is there so that features using an account can be added later.
None of these services receives your scores, verdicts, test readings, photos, sound, reports, or the IMEI. Google processes this data for us under the Firebase privacy terms.
In the European Economic Area, the UK and Switzerland, these services stay off until you agree to storing information on your device and measuring performance in the consent message, and they stop if you later withdraw it. Elsewhere they are on from the first launch. Debug builds used for development never send anything.
7. Consent and your choices
- Europe, the UK and Switzerland: before any ad is requested, the app shows Google's consent message (Google's User Messaging Platform). You can accept, refuse, or choose purposes one by one. If you refuse, Google shows only non-personalised or limited ads, or none.
- United States: where state privacy laws give you the right to opt out of the "sale" or "sharing" of personal information for targeted advertising, the app offers that choice through the same message.
- Changing your mind: open PhoneLab, go to Settings → Privacy choices to see the message again and change your answer. The option is shown where it applies.
- Advertising ID: on Android you can reset or delete your advertising ID at any time in the phone's Settings → Privacy → Ads (or Settings → Google → Ads on some phones). Personalised ads then stop using it.
- No internet, no ads: tests work with the phone offline. Ads, and the data AdMob collects, need a connection.
8. Google Play
You install PhoneLab from Google Play, which processes data under Google's Privacy Policy. As the developer we may see aggregated statistics in the Google Play Console, such as the number of installs by country and device type, ratings and reviews, and crash and "not responding" reports from Android vitals. These do not identify you to us. If you write a review or contact us, we see what you choose to send. When the app opens, it asks Google Play whether a newer version exists. Updates can be required, and Google Play installs them.
9. Keeping and deleting data
- Checks and their files stay on your phone until you delete them. Delete one check from Reports (the ⋮ menu), or everything at once from Settings → Delete all data.
- Delete all data also resets the Analytics ID, drops crash reports not yet sent, and deletes the anonymous ID from Firebase. If the phone is offline at that moment, the app stops using that ID, and the record left on Firebase is no longer linked to your phone. A new ID is made the next time the app starts, unless you have refused consent.
- Uninstalling the app deletes all of its data from the phone.
- Temporary photos, videos and report files are kept in the app's cache and removed after use.
- Data collected by Google for ads is kept according to Google's retention policies, described in How Google retains data.
- Crash reports are kept by Firebase for 90 days. Analytics data is kept for up to 2 months, and anonymous IDs until they are deleted.
- If you email us, we keep your message only as long as needed to answer it, and delete it on request.
10. Security
Your results are stored in the app's private storage, which Android keeps apart from other apps, and they are left out of backups. The Results and Report screens can't be captured by screenshots or screen recordings, so a check leaves the phone only as a report you choose to share. Connections made by the ad SDK use encryption (HTTPS). No method of storage or transfer is perfectly secure, but nothing we hold could expose your results, because we hold none.
11. Children
PhoneLab is a general-audience tool and is not directed at children under 13 (or the minimum age of digital consent in your country, such as 16 in parts of the EEA). We do not knowingly collect personal information from children. Ads are limited to content rated for teens and older. If you believe a child has used the app and want data removed, contact us and we will help, including by asking Google where ad data is concerned.
12. Your rights
Depending on where you live, for example under the EU and UK GDPR or US state laws such as the CCPA/CPRA, you may have rights to access, correct, delete or move your personal data, to object to or restrict its use, to withdraw consent, and to opt out of targeted advertising. Because PhoneLab keeps your results only on your phone, you can see and delete them yourself in the app. For crash reports, usage data, and the anonymous ID, use Delete all data in Settings. For ad data, use the choices in section 7 or Google's tools at My Ad Center. You can also write to us and we will answer within 30 days. You have the right to complain to your local data protection authority.
Where the GDPR applies, the legal basis for ad processing is your consent (for personalised ads and storing information on your device) or Google's and our legitimate interest in showing non-personalised ads, measuring them and preventing fraud, so that the app can stay free. Processing on your phone to run the tests you start is needed to provide the service you asked for.
13. International transfers
Google may process ad data in the United States and other countries where it has facilities. Google relies on safeguards such as the EU–US Data Privacy Framework and the European Commission's standard contractual clauses for these transfers.
14. Changes to this policy
If the app starts handling data differently, we will update this page and its date before the change reaches you, and for important changes we will say so in the app or in the Google Play release notes.
15. Contact
Questions, requests or concerns about privacy: phonelabtools@gmail.com. You can also use the contact page.