LockLoom — Device Policy Disclosure

What Data is Accessed

LockLoom's optional AccessibilityService monitors app launch events (window state changes) to:

• Pause or hide protected apps until authentication succeeds
• Log policy bypass attempts for local security telemetry
• Detect distress PIN entry on the system lock screen for covert SOS triggers

Data stays on-device: Launch events are processed transiently and never transmitted off-device.

In-App Consent Implementation

Disclosure Location:	Dedicated "Launch Monitoring Disclosure" screen shown during normal app usage
Consent Mechanism:	Checkbox ("I understand and consent to LockLoom monitoring app launches for enforcement") + "Continue to Android settings" button
Persistence:	Consent timestamp immutably recorded in device-protected storage (SharedPreferences)
Feature Gating:	AccessibilityService cannot be enabled until consent is recorded; distress PIN setup is blocked without accessibility consent

Google Play Policy Compliance

Requirement	Implementation
Comprehensively discloses data collection, use, and sharing	✅ Screen explains what is monitored, why, and that data never leaves device
Within the app itself, displayed in normal usage	✅ Dedicated in-app screen, not buried in settings
Cannot only be in privacy policy or ToS	✅ Standalone in-app disclosure, separate from external policies
Cannot be combined with unrelated disclosures	✅ Dedicated to accessibility monitoring only
Requires affirmative user action	✅ Checkbox must be checked + button must be tapped
Navigation away is NOT consent	✅ Feature remains disabled if user navigates away
No auto-dismiss or expiring messages	✅ Disclosure persists until explicit user action
Must be obtained BEFORE data collection	✅ Service cannot be enabled until consent recorded

What Data is Collected

LockLoom collects phone numbers you provide as emergency contacts to enable the Distress Flare feature:

• Phone numbers you enter as emergency contacts (stored locally on device only)
• SMS messages sent directly to these contacts when you trigger a distress PIN
• Your device's phone number may be included in alerts to identify the sender
• GPS location (if available) included in distress alerts to help contacts locate you

Direct to contacts only: Alerts are sent directly to your configured emergency contacts via SMS/email — never through any LockLoom server or third-party relay.

In-App Consent Implementation

LockLoom implements two layered consent mechanisms for phone number data:

A. Phone Data Disclosure Dialog (Build 313+)

Disclosure Location:	Modal dialog shown when user attempts to save phone numbers as emergency contacts
Consent Mechanism:	Checkbox ("I understand and consent to this data collection") + "I Agree" button
Modal Properties:	dismissOnBackPress=false, dismissOnClickOutside=false — cannot be dismissed without explicit action
Persistence:	Consent timestamp stored in PhoneDataConsentStore (device-protected storage) with version tracking
Feature Gating:	Phone numbers cannot be saved until consent is recorded

B. Distress PIN Data Sharing Consent (Build 347+)

Disclosure Location:	Inline card displayed directly above distress PIN entry fields
Consent Mechanism:	Checkbox ("I understand my phone number will be shared with my emergency contacts when I trigger a distress alert") + "I Acknowledge" button
Persistence:	Separate consent timestamp recorded with date display ("Acknowledged: YYYY-MM-DD HH:MM")
Feature Gating:	Distress PIN cannot be set until BOTH accessibility consent AND data sharing consent are granted

Google Play Policy Compliance

Requirement	Implementation
Comprehensively discloses data collection, use, and sharing	✅ Explains what data is collected, how it's used (SMS alerts), and who receives it (your emergency contacts only)
Within the app itself, displayed in normal usage	✅ Modal dialog + inline card on Distress PIN screen
Cannot only be in privacy policy or ToS	✅ In-app disclosure components, separate from this external document
Cannot be combined with unrelated disclosures	✅ Dedicated to phone number data only (separate from accessibility consent)
Requires affirmative user action	✅ Checkbox must be checked + button must be tapped
Navigation away is NOT consent	✅ Modal cannot be dismissed; features remain disabled if user declines
No auto-dismiss or expiring messages	✅ Disclosures persist until explicit user action
Must be obtained BEFORE data collection	✅ Phone numbers cannot be saved and PIN cannot be set until consent recorded

The app offers an optional AccessibilityService to intercept launches of selected protected apps and gate them behind authentication. Enabling it requires explicit user action in system settings and an in-app consent record (see Accessibility Service Consent section above). The service observes window state changes only to identify the foreground package; it does not transmit events off-device.

The AccessibilityService also enables distress PIN detection on the lock screen, allowing covert SOS triggers without visible indicators. This capability requires both Accessibility Consent and Phone Data Consent before activation.

• USB guarding prefers setUsbDataSignalingEnabled on Android 14/15+ and falls back to DISALLOW_USB_FILE_TRANSFER on Android 7+.
• forceStopPackage is invoked only on Android 7.0+ when available to a DO.
• Bluetooth monitoring honors BLUETOOTH_CONNECT (12+) or legacy permissions; if missing, the system defaults to “disconnected” without crashing.
• Foreground service types are set appropriately across OS versions; the service will not start without user notification consent on 13+.