Introduction and mission
Guardian helps recognize suspicious phone calls and dangerous scam scenarios in real time. This Policy explains what data Guardian uses, why it is needed, and how it is handled. Please read it before using the app.
Fundamental principle
Guardian processes 100% of data locally on your device. There are no external servers, cloud databases, or personal data transfers. All processing takes place in RAM and is erased after the call ends.
What data Guardian uses
All data is processed in RAM and is not stored on disk.
| Data | How it is used | Storage |
|---|---|---|
| Call state (IDLE, RINGING, OFFHOOK) | Detects that a call is taking place so protection works in real time | Not stored |
| Caller\'s phone number | Checks whether the number is in contacts and whether the call is recent | Not stored |
| Call duration | Helps recognize suspicious long conversations | In memory only; erased when the app is closed |
| Contact list (search only) | Checks whether the number belongs to a trusted contact | Not stored; no contact export |
| Call log (search only) | Checks call recency to identify a familiar caller | Not stored; no call log export |
| App usage statistics | Helps recognize suspicious scenarios during a call | Not stored |
| App installation events | Helps recognize recently installed apps | Not stored |
| Protection readiness flags | Remember whether onboarding and permission setup are complete | Locally on the device (SharedPreferences) |
| Language preferences | Remember the selected language (Russian, Romanian, or system) | Locally on the device (SharedPreferences) |
What Guardian NEVER does
These principles are immutable and form the foundation of trust in the app.
- ✓Does NOT read SMS text or banking confirmation codes (OTP)
- ✓Does NOT listen to or record phone conversations
- ✓Does NOT transmit data to external servers (no INTERNET permission)
- ✓Does NOT require creating an account, entering an email, or passwords
- ✓Does NOT share data with third parties
- ✓Does NOT track location
- ✓Does NOT access the camera
- ✓Does NOT contain ads, trackers, or analytics SDKs
Android permissions and their purpose
Each permission is explained in plain language.
Detects the incoming call state to activate protection during the conversation
Checks whether the number has called recently to identify a familiar caller
Checks whether the caller is a known contact to reduce false alerts
Helps recognize suspicious app usage scenarios (requires manual approval in system settings)
Keeps Guardian\'s protection active for continuous responsiveness
Automatically restarts protection after the device reboots
Data storage and deletion
All data is processed on your device. Guardian does not use a server database or cloud storage. In-memory data (call state, numbers, duration) is erased when the app is closed. Local settings (onboarding, language, protection readiness) are stored in SharedPreferences and can be cleared through system settings or by uninstalling the app.
Developer contacts
If you have questions about the Privacy Policy, please contact us:
[email protected]Last updated: 2026-06-23