Guide
Setup and Security Guide
Configure core anti-theft modules correctly so incident capture and alarms remain reliable on real Android devices.
1) Permissions and why they matter
The app requests only permissions needed for features you enable. If a permission is denied, revoked, or restricted, the related module may stop detecting incidents.
- Camera for optional intruder evidence photos.
- Overlay for alarm and lock-style warning screens.
- Usage access for timeline and session context.
- Notifications and system capabilities for reliability.
2) Data storage and retention
Evidence and event records stay local, encrypted, and are automatically cleaned by retention policy.
- Event logs and photos are stored in app-private storage only.
- Captured photos are encrypted with Android Keystore-backed AES-GCM file encryption.
- WorkManager cleanup removes old photos automatically (default 2 days).
- Retention can be set to 1, 2, 3, or 7 days.
3) Android reliability checklist
Some devices aggressively suspend background processes. Excluding this app from battery optimization improves real-world alarm reliability.
- Disable battery optimization for the app.
- Keep lock settings and critical permissions enabled.
- Run at least one unlock/motion simulation test after setup.
4) Alarm stop and troubleshooting
Alarm stop behavior follows your configured lock method. If alarms seem unstable, verify permissions and rerun quick tests.
- PIN mode: stop via PIN confirmation.
- PIN + biometric mode: stop via biometric or fallback PIN.
- No lock mode: stop by the configured timeout path.