Fake Calls Detector & Backup

Fake Call Detector inspects your Android call log for entries that look like they were edited or inserted by third-party call-log-editor apps. It runs entirely on your device — your call history is never transmitted to any server. WHAT IT DOES: Forensic analysis. Each call-log row is examined against a set of metadata signals (last-modified timestamp, contact-cache fields, dual-SIM account identifiers, number-formatting fields, state flags, timeline ordering) and given a severity tier — none, possible, elevated, high, or certain — along with a 0–100 confidence score and the specific reasons that contributed to the score. Backup and restore. Save your full call log to a .bak file in your Downloads folder. Restore it back later if entries are deleted or when you switch devices. Dual-SIM slot information is preserved across the round trip. Export. Generate .bak files you can keep for archival or move to another device. HOW THE DETECTOR WORKS: The detector compares each call-log row against the expected behavior of Android's native telephony stack. When a row's metadata diverges from what the system would normally write — for example, a modification timestamp earlier than the call's end time, an impossibly long duration on a blocked call, or a fingerprint left by a known editor app — the row is flagged with the specific reasons. The analysis is heuristic. Legitimate system events such as contact-name cache refreshes, antispam rescans, voicemail-transcription completion, and OEM dual-stack call routing can occasionally produce signals that resemble editing. Conversely, some sophisticated edits may go undetected. Results are inferential and should not be treated as forensic evidence. PRIVACY: Your call log stays on your device. • Call-log data is read locally through Android's standard CallLog API and is never sent to our servers or to any third party. • Backup .bak files are written to your device's Downloads folder. They do not leave your device unless you choose to share them yourself. • Firebase Analytics is used for anonymous usage statistics (screen views, session counts, basic device info). No call-log content is included. PERMISSIONS: • READ_CALL_LOG / WRITE_CALL_LOG — to read your call history and to restore entries from a backup file. • READ_PHONE_STATE / READ_PHONE_NUMBERS — to identify SIM slots on dual-SIM devices. • READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE (Android 13 and below) — to read and write backup files in the Downloads folder. • INTERNET / ACCESS_NETWORK_STATE — required by Firebase Analytics. COMPATIBILITY: Designed for Android phones with a working call log. Tablets and devices without telephony hardware will have nothing to analyze. SUPPORT: If you encounter an issue or want to report a false positive, contact us at [email protected].