Privacy Policy — PhoneAtlas

Last updated: 12 May 2026

PhoneAtlas (“the app”) is operated as a personal project by the developer of tifu.xyz. This policy describes what data the app accesses, how it is used, and what choices you have.

No personal information is collected by PhoneAtlas itself.
No data is sent to our servers, because PhoneAtlas has no servers.
No analytics SDKs are integrated.
Banner ads are served by Google AdMob and may collect device-level identifiers used by the ad network. Ads can be disabled in app Settings without payment.

1. What information PhoneAtlas reads from your device

PhoneAtlas reads the following information locally on your device in order to display it back to you. None of this information leaves your device.

Category	Data read	Permission required
CPU	`/proc/cpuinfo`, `/sys/devices/system/cpu/*`	none
GPU	OpenGL ES / Vulkan capabilities via `PackageManager` and an `EGL` pbuffer	none
RAM	`ActivityManager.MemoryInfo`, `/proc/meminfo`	none
Storage	`StatFs` on data and external paths	none
Battery	`BatteryManager`, sticky `ACTION_BATTERY_CHANGED` broadcast	none
Display	`Display`, `WindowManager`	none
Network	`WifiManager.connectionInfo`, `TelephonyManager` (operator name, network type — public API only)	`ACCESS_WIFI_STATE`
Sensors	`SensorManager.getSensorList`	none
System	`Build.*` static fields, `/proc/version`	none
Camera	`CameraManager` characteristics	none
Connectivity	`BluetoothAdapter`, `NfcAdapter`, `PackageManager` feature flags	none

In addition, PhoneAtlas declares the following non-data permissions purely for app functionality:

INTERNET — required by the Google AdMob SDK when ads are enabled.
SYSTEM_ALERT_WINDOW — required to draw the optional floating overlay window with live readings.
POST_NOTIFICATIONS (Android 13+) — required to show the persistent notification used by the overlay foreground service.
FOREGROUND_SERVICE and FOREGROUND_SERVICE_SPECIAL_USE — required to keep the optional floating overlay alive in the background, with subtype real_time_device_monitoring.

PhoneAtlas does not request location permission, camera capture, microphone, contacts, calendar, files, phone state (READ_PHONE_STATE), or any other personal-data permission.

2. What Google AdMob collects

When ads are enabled (the default), PhoneAtlas displays a banner ad served by Google AdMob. AdMob may collect:

Advertising ID (resettable by you in Android system settings)
Device language, country, time zone, screen size
Coarse network information used for ad delivery and fraud prevention
Approximate IP-based location

Use of this data by Google is governed by Google’s Privacy Policy: policies.google.com/privacy.

For users in the EEA, the United Kingdom, or Switzerland, PhoneAtlas presents a consent dialog (Google’s User Messaging Platform, IAB TCF v2.2) before any ad is requested. The dialog can be re‑opened at any time from Settings → Privacy options.

You can also:

Disable ads entirely in PhoneAtlas → Settings → Hide ads. When disabled, the AdMob SDK is not initialised and no ad request is made.
Reset your Advertising ID at any time in Android Settings → Privacy → Ads.

3. Data shared with third parties

If ads are enabled, the limited information described above is sent to Google AdMob. No other third party receives data from PhoneAtlas.

If ads are disabled, no third party receives any data.

4. Data retention

PhoneAtlas does not store any data on its servers (it has none). The only data persisted on your device is your app preferences (Hide-ads, theme, overlay options), kept in app-local SharedPreferences and removed when you uninstall the app.

5. Children’s privacy

PhoneAtlas is not directed at children under 13. We do not knowingly collect personal information from children.

6. Changes to this policy

If we make material changes to this policy, the new version will be posted at the same URL with an updated “Last updated” date.

7. Contact

For questions about this policy or the app, contact [email protected].