PRIVACY POLICY
Overview
nfcGuard is a digital wellbeing app that blocks access to distracting applications on your Android device. This policy explains what data nfcGuard accesses and how it is handled.
Data Collection
nfcGuard does not collect, transmit, or share any personal data.
All data stays on your device. There are no servers, no analytics, no tracking, and no network requests made by nfcGuard.
Data Stored on Device
nfcGuard stores the following data locally on your device using Android SharedPreferences:
| Mode configurations | Names, selected apps, block mode type |
| Schedule configurations | Names, days, times, linked modes |
| NFC tag identifiers | Hardware IDs of registered NFC tags |
| Runtime state | Which modes and schedules are currently active |
This data never leaves your device unless you explicitly export it using the Export Config feature.
Permissions
| Permission | Purpose |
|---|---|
| Accessibility Service | Reliably detect which app is currently in the foreground on devices where UsageStatsManager is insufficient (see detailed disclosure below) |
| Usage Access | Detect which app is currently in the foreground to determine if it should be blocked |
| Display Over Apps | Show a full-screen overlay when a blocked app is opened |
| Battery Optimization Exemption | Ensure the blocking service runs reliably in the background |
| NFC | Read NFC tag hardware IDs for mode activation/deactivation |
| Foreground Service | Keep the app blocking service running persistently |
| Boot Completed | Restart the blocking service and reschedule alarms after device reboot |
| Exact Alarm | Fire schedule start/end events at precise times |
nfcGuard does not request internet access for its own functionality. The INTERNET permission in the manifest is inherited from dependencies and is not actively used by the app.
Accessibility Service (AccessibilityService API) Disclosure
nfcGuard uses the Android AccessibilityService API solely to detect which application is currently in the foreground. This is required because the standard UsageStatsManager API does not reliably report foreground app transitions on certain devices, including Google Pixel and Samsung Galaxy phones.
What the Accessibility Service does:
| Listens for TYPE_WINDOW_STATE_CHANGED events | To detect when the user switches to a different app |
| Stores the package name of the foreground app | To determine whether the current app should be blocked based on the user's configured modes |
What the Accessibility Service does NOT do:
| Does not read screen content, text fields, or UI elements |
| Does not read or intercept user input, passwords, or keystrokes |
| Does not access, collect, or transmit any personal or sensitive user data |
| Does not perform any actions on behalf of the user |
| Does not interact with any other app's interface |
| Does not send any data over the network |
The Accessibility Service runs with the minimum required configuration: flags = 0 (no content access flags enabled), feedback type set to FEEDBACK_GENERIC, and the only event type monitored is TYPE_WINDOW_STATE_CHANGED. The service exists exclusively to support nfcGuard's core app-blocking functionality and is not used for any other purpose.
Third-Party Services
nfcGuard does not integrate any third-party services, SDKs, analytics platforms, or advertising networks.
Data Export
When you use the Export Config feature, a JSON or YAML file is created and saved to a location you choose on your device. This file contains your mode, schedule, and NFC tag configurations. nfcGuard does not upload this file anywhere.
Children's Privacy
nfcGuard does not knowingly collect any data from children. The app does not collect data from anyone.
Changes to This Policy
If this policy is updated, the changes will be reflected in this document with an updated date.
Contact
If you have questions about this privacy policy, please open an issue on the GitHub repository.