00Google Play Data Safety Matrix
In compliance with Google Play's mandatory Data Safety disclosure requirements, the following table summarizes every category of data our application may access, collect, or process, and how it is handled. This mirrors the information submitted in the Google Play Console Data Safety form.
| Data Category | Data Type | Collected? | Shared? | Purpose | Encrypted? | Deletable? |
|---|---|---|---|---|---|---|
| Location | Approximate & Precise location | On-device only | Not shared | Situational geo-fencing triggers only (if enabled) | Yes (Android keystore) | Yes |
| Photos & Videos | Photos, Videos captured by app | On-device only | Not shared | User-initiated gesture shortcuts only | Yes | Yes |
| Audio | Voice commands, recorded audio memos | On-device only | Not shared | On-device TTS/STT, voice gesture triggers, audio memos | Yes | Yes |
| Contacts | Contact names, phone numbers | On-device only | Not shared | Quick-dial gesture shortcuts (user-initiated only) | Yes | Yes |
| App Activity | App interactions, crash logs | Anonymized | Google Firebase | Crash diagnostics, anonymous analytics | Yes (TLS 1.3) | Yes (email request) |
| Device & Other IDs | Advertising ID (GAID), App Set ID, IP address, and App-Scoped Android ID (SSAID / Settings.Secure.ANDROID_ID, collected only upon optional external promo code redemption) |
Pseudonymized | Google AdMob, Meta, Unity Ads & Private Promo Backend | Personalized advertising, promotional code licensing, fraud prevention & single-device entitlement binding | Yes (TLS 1.3 / HTTPS) | Yes (contact developer or promo expiration) |
| Financial Info | Purchase history | Google Play only | Not collected by us | In-app purchase verification via Google Play Billing | Yes (Google infrastructure) | N/A (managed by Google) |
| Accessibility Data | Touch events, gesture vectors | Not stored | Not shared | Transient gesture processing in RAM only | N/A (never persisted) | N/A |
| Personal Info | Name, email, user ID | Not collected | Not shared | Not required β no account system | N/A | N/A |
Settings.Secure.ANDROID_ID / SSAID) is transmitted via encrypted HTTPS to our backend spreadsheet. This identifier is used exclusively for licensing, subscription entitlement verification, and preventing code duplication abuse. It is strictly tied to this application's signing key, is never used for advertising, behavioral profiling, or cross-app tracking, and is never shared with third-party data brokers or marketing networks.
01Introduction & Privacy Philosophy
Welcome to Dynamic Edge Gesture Control ("EDGE", "Application", "we", "our", or "us"), developed and maintained by independent developer Madhusudan Payra. We are unwaveringly committed to user privacy, complete technical transparency, and protecting your digital autonomy.
This Privacy Policy comprehensively details: (a) the categories of data processed by EDGE; (b) our strict on-device data retention principles; (c) all explicit system permissions requested on Android; (d) our technical integrations with Google Firebase and Google AdMob; (e) how we handle third-party automation platforms (e.g., Tasker); and (f) your statutory rights under all applicable global data protection laws.
This policy applies to all users of the Dynamic Edge Gesture Control Android application available on the Google Play Store (package: com.m.payra.gesture.control.app), as well as this privacy policy webpage hosted at bullat859.github.io.
By installing or using Dynamic Edge Gesture Control, you acknowledge and agree to the data practices described in this Privacy Policy and our Terms of Use. If you disagree with any part of this policy, please uninstall the application and contact us to request deletion of any residual diagnostic data.
Who We Are
Dynamic Edge Gesture Control is published by Madhusudan Payra, an independent Android developer based in India. For all privacy inquiries, data subject requests, or regulatory correspondence, contact us at m.payra859appsupport@gmail.com. For GDPR-specific requests, see Section 28 (DPO Contact & GDPR Representative).
02AccessibilityService API β Detailed Disclosure
Dynamic Edge Gesture Control utilizes Android's AccessibilityService API as a core foundational engine. In full compliance with Google Play's User Data Policy and Accessibility Policies for non-assistive utility apps, we provide the following comprehensive technical explanation:
Why AccessibilityService is Required
- Drawing Overlay Gesture Zones: To render interactive edge bars, dynamic island handles, notch overlays, floating bubbles, and pie menus over other active apps on the perimeter of your screen.
- Touch & Swipe Motion Tracking: To calculate touch vectors, drag velocity, swipe angles, hold durations, and fling gestures within user-configured edge zones.
- Performing Global System Actions: To execute system-level actions on behalf of the user when a gesture is triggered β including: Back (
GLOBAL_ACTION_BACK), Home (GLOBAL_ACTION_HOME), Recents (GLOBAL_ACTION_RECENTS), Notifications (GLOBAL_ACTION_NOTIFICATIONS), Quick Settings (GLOBAL_ACTION_QUICK_SETTINGS), Lock Screen (GLOBAL_ACTION_LOCK_SCREEN), Power Dialog (GLOBAL_ACTION_POWER_DIALOG), Screenshot (GLOBAL_ACTION_TAKE_SCREENSHOT), and Split-Screen (GLOBAL_ACTION_TOGGLE_SPLIT_SCREEN). - Active Window Detection: To read the package name of the currently active foreground application solely for app-specific gesture profile switching (e.g., different profiles for gaming apps vs. browser). No window text, view hierarchy content, or UI element data is read or logged.
isAccessibilityTool="true" because this application is a personalization and system control utility β not an assistive technology.
How to Revoke AccessibilityService Access
You may revoke Accessibility permission at any time without uninstalling the app:
- Go to Android Settings β Accessibility
- Find Installed Services or Downloaded Apps
- Tap Dynamic Edge Gesture Control
- Toggle the service OFF
Revoking this permission will disable gesture recognition and system navigation features. Core app settings and configuration will remain intact.
03Comprehensive Android Permissions Breakdown
Every permission declared in our AndroidManifest.xml serves an explicit, user-initiated functional purpose. We strictly adhere to the Android principle of minimal permission scope. No permission is declared speculatively or for future use. Below is a full disclosure of all declared permissions:
SYSTEM_ALERT_WINDOW β Display Over Other Apps
Renders interactive edge sliders, notch handles, volume overlays, and pie navigation menus over other running apps. User must explicitly grant via Settings.
WRITE_SETTINGS β Modify System Settings
Allows gestures to adjust device brightness, screen rotation lock, screen timeout duration, audio volume streams, and haptic feedback intensity profiles.
CAMERA β Camera Hardware
Accesses device camera exclusively for user-initiated gesture shortcut actions: one-touch camera shortcuts, QR/barcode scanning, and quick video recording memos. The camera utilizes standard Android camera APIs and is never activated passively or in the background without an explicit gesture trigger.
RECORD_AUDIO β Microphone
Accesses the microphone for user-initiated gesture triggers: voice command detection (on-device TTS/STT), audio memo recording, and ambient sound level detection for adaptive gesture sensitivity. Audio is never transmitted to remote servers.
ACCESS_FINE_LOCATION + ACCESS_BACKGROUND_LOCATION
Reads precise GPS coordinates to enable situational geo-fencing: automatically activating or deactivating specific gesture profiles based on user-defined geographic zones (e.g., "at home" profile vs. "at work" profile). Location is never uploaded or shared.
READ_CONTACTS β Single Contact Shortcut Reference Only
Strict High-Risk Permission Transparency: Dynamic Edge Gesture Control does not read, harvest, replicate, or store your address book in a local database, nor does it sync or upload contact records to any remote server or third party. Contacts access is utilized strictly via an on-demand picker solely when you explicitly map a "Quick-Dial" or "Direct-Message" gesture shortcut. The application holds only a local Android URI reference / phone number string for the single contact record you specifically selected for that gesture action.
CALL_PHONE β Direct Phone Call Shortcut
Direct User-Initiated Telephony: Governed as a sensitive permission, CALL_PHONE allows a configured gesture to initiate a phone call strictly to the pre-assigned contact number chosen by the user. Calls are never initiated automatically, covertly, or in the background. The action is triggered exclusively upon your deliberate edge gesture. The application does not read, monitor, log, or transmit your device call history or call duration records.
QUERY_ALL_PACKAGES β Package Visibility
Reads the list of installed applications on your device. Used exclusively to: (a) populate the app-picker list in gesture action configuration; and (b) enable app-specific gesture profile switching based on the active foreground application. App lists are processed entirely on-device and never transmitted.
VIBRATE β Haptic Feedback
Triggers device vibration motor for haptic confirmation feedback when gesture actions are executed. No vibration patterns are transmitted; all haptic output is local.
BLUETOOTH_CONNECT + BLUETOOTH_SCAN β Bluetooth
Detects Bluetooth connection state (connected headphones, car kit, speaker) to enable situational Bluetooth-aware gesture profiles (e.g., "car mode" when connected to a car Bluetooth device). No audio data, Bluetooth device addresses, or pairing keys are transmitted.
READ_MEDIA_AUDIO β Media Library Access
Accesses audio files on device storage so users can assign custom audio playback (music tracks, notification sounds) as gesture actions. Files are selected by the user; no media is uploaded.
FOREGROUND_SERVICE_CAMERA + FOREGROUND_SERVICE_MICROPHONE β Transient Execution
Strict Android 14+ Policy Compliance: Declares foreground service sub-types strictly required under Android 14+ when invoking camera and microphone hardware. These services are transientβactivated exclusively during the exact momentary execution of a user-initiated camera shortcut, QR scan, or voice recognition session, and are immediately released upon completion. The application does not continuously hold camera or microphone hardware in the background, and always displays a visible, mandatory foreground service notification during execution.
SCHEDULE_EXACT_ALARM + USE_EXACT_ALARM
Allows the app to schedule time-based gesture triggers and automation routines at exact times. Used for scheduled profile switching (e.g., "night mode" at 10 PM) and repeating gesture automations. Required by Android 12+ for exact alarm scheduling.
REQUEST_IGNORE_BATTERY_OPTIMIZATIONS
Requests exclusion from Android's battery optimization system so the foreground gesture detection service is not killed by the OS during extended usage. Prevents missed gesture triggers when the device is in Doze mode.
WAKE_LOCK
Prevents the CPU from sleeping during active gesture recognition sessions initiated by the user. Released immediately when the gesture session ends to conserve battery.
INTERNET
Enables outbound network connectivity for: (a) Google Firebase crash reporting and anonymous analytics; (b) Google AdMob ad network communication; (c) Google Play Billing transaction verification; and (d) downloading app update metadata from Google Play. No personal user data is transmitted over this connection beyond what is disclosed in Sections 10 and 11.
POST_NOTIFICATIONS
Required by Android 13+ (API 33+) to display the persistent foreground service notification (mandatory for active Accessibility and camera/microphone foreground services) and to send optional user-configured gesture event alerts.
04Camera, Microphone & Media Privacy
Camera Usage & One-Touch Shortcuts
The camera hardware is accessed only when the user configures and triggers a camera-based gesture shortcut action. The app relies on standard Android Camera/Camera2 platform APIs. Specific user-directed use cases include:
- One-Touch Camera Capture: The user maps an edge swipe or hold gesture as a direct shortcut to snap a quick photo. The captured photo is immediately saved to the standard Android MediaStore / DCIM directory on the device with full user visibility. It is never uploaded to any remote server or third party.
- Quick Video Memo: User assigns a gesture to begin a short video recording memo. The video file is stored directly in the device's public or app-specific media directory. It is never transmitted remotely.
- QR / Barcode Scanner: Opens the camera in scan mode to read QR codes or barcodes. Scan results are displayed on-screen for the user to use. No scan history is persisted by the application.
- Flashlight Torch Toggle: Activates/deactivates the rear camera flash LED as a torch. No camera preview or image capture occurs during torch-only operations.
All captured photos and videos remain in standard Android gallery directories and are subject to the user's own device backup settings (e.g., Google Photos automatic backup, Samsung Cloud). EDGE does not control or have insight into such device-level backup behaviors.
Microphone Usage
The microphone is accessed only under these strictly user-controlled conditions:
- Voice Command Gesture Trigger: The user configures a gesture to activate a voice recognition session. Speech is processed entirely on-device using the Android Speech Recognition API (operating locally or via the user's selected default recognition engine, which may be Google, Samsung, or a third-party engine subject to that engine's own privacy policy).
- Audio Memo Recording: User assigns a gesture to begin an audio memo recording. The resulting file is saved to app-private storage on-device and never transmitted by EDGE.
- Ambient Sound Sensitivity: If the user enables adaptive gesture sensitivity based on ambient noise level, the microphone briefly samples background dBSPL without recording or storing any audio data.
Transient Foreground Service Policy
In strict compliance with Android 14+ (API 34+) Google Play foreground service policies: FOREGROUND_SERVICE_CAMERA and FOREGROUND_SERVICE_MICROPHONE are strictly transient. They are activated only at the exact instant a user triggers a camera capture or voice gesture, and terminate immediately once the action finishes. They are never held active indefinitely in the background, and an active foreground service notification is visibly maintained during their momentary runtime.
05Voice Assistant & Speech Processing Privacy
Dynamic Edge Gesture Control includes an optional Voice Assistant integration that allows users to trigger gesture actions via spoken voice commands. This feature operates under the following privacy architecture:
- On-Device Speech Recognition: All voice command processing is performed locally using Android's built-in
SpeechRecognizerframework or the user's selected speech recognition engine. EDGE does not operate its own speech recognition server. - No Voice Audio Stored by EDGE: Audio captured during a voice command session is not persisted by Dynamic Edge Gesture Control. Once the recognized command is processed and the corresponding action executed, the audio session buffer is cleared from memory.
- Third-Party Speech Engines: If your device uses a third-party speech recognition engine (Google Assistant, Samsung Bixby, or others), that engine's audio processing and privacy policy apply to the speech recognition component independently. EDGE does not control what data those engines may retain.
- Wake-Word Detection: EDGE does not implement any passive wake-word or always-listening hot-word detection. Voice command sessions are exclusively initiated by explicit, user-triggered gesture actions.
- Text-to-Speech (TTS) Output: Voice feedback and status announcements use the Android TTS engine. No text content is transmitted; synthesis occurs entirely on-device.
06Location Data & Geo-Fencing Privacy
Dynamic Edge Gesture Control may request access to your device's location (both foreground and background) to power the Situational Geo-Fencing feature. This is an entirely optional feature that users must explicitly enable and configure.
How Location is Used
- Gesture Profile Auto-Switching: Location coordinates are compared against user-defined geographic zones (polygons or radius circles drawn in app settings) to automatically activate the appropriate gesture profile. For example: activating a "Driving Mode" gesture layout when the device enters a car's Bluetooth range and a defined location zone simultaneously.
- Background Location (
ACCESS_BACKGROUND_LOCATION): Required because gesture profile switching must function even when the app is not in the foreground. We request this permission only when the user enables the Geo-Fencing feature and explains the purpose clearly at permission request time.
How to Disable Location Access
Navigate to Settings β Apps β Dynamic Edge Gesture Control β Permissions β Location and select "Deny" or "Allow only while using the app" to restrict background access. The geo-fencing feature will be automatically disabled but all other features remain operational.
07System Overlays, Edge Trigger Zones & Floating UI
The SYSTEM_ALERT_WINDOW ("Draw over other apps") permission is central to EDGE's core functionality. This permission allows the app to render interactive UI elements on top of other applications and the system interface.
Overlay Use Cases
- Edge Trigger Bars: Thin, semi-transparent, customizable edge strips along the left, right, top, or bottom screen edges that detect user swipe and hold gestures.
- Dynamic Island / Notch Handles: Interactive handles rendered in the camera notch or dynamic island area for quick action access.
- Floating Bubbles / Launchers: Draggable circular floating widgets that expand into quick-action menus.
- Pie Navigation Menus: Radial context menus triggered by long-press or swipe-and-hold gestures.
- Notification / Volume HUD: Compact heads-up overlays for volume adjustment and notification preview.
You can disable the overlay permission at any time: Settings β Apps β Dynamic Edge Gesture Control β Display over other apps β OFF. This will disable edge trigger rendering but other settings remain intact.
08App Package Querying (QUERY_ALL_PACKAGES)
Dynamic Edge Gesture Control declares the QUERY_ALL_PACKAGES permission in its manifest. Google Play requires explicit justification for this permission, and we provide it here in full:
Privacy Safeguards for Package Querying
- The list of installed applications is queried and displayed entirely on-device. It is never uploaded, transmitted, or shared with any external service.
- The application does not build analytics profiles based on installed app data.
- No sensitive app categories (e.g., banking apps, health apps, adult content apps) are specifically targeted or logged.
- The package visibility list is refreshed locally each time the App Picker is opened and is not cached persistently.
09Physical Hardware Sensors, Haptics & Device Hardware
Dynamic Edge Gesture Control may access the following device hardware sensors to enhance gesture precision and enable contextual trigger conditions:
Accelerometer & Gyroscope
Detects device orientation, tilt angle, and shake motion to enable gesture triggers based on physical device movement (e.g., "shake twice" gesture). Sensor readings are processed on-device and not recorded.
Proximity Sensor
Used to detect when the device is held near the user's face (e.g., during a phone call) to temporarily suspend edge gesture detection and prevent accidental triggers.
Fingerprint / Biometric Sensor
If the user configures biometric authentication as a lock for EDGE's settings panel, the device's biometric hardware is invoked through Android's BiometricPrompt API. See Section 18 (Biometric Authentication) for full disclosure.
Vibration Motor (Haptics)
The VIBRATE permission allows EDGE to produce haptic feedback pulses confirming successful gesture recognition. No vibration data is transmitted. Pattern intensity and style are configurable in app settings.
Screen Brightness Sensor (Ambient Light)
Reads ambient light level to enable adaptive screen brightness adjustment as a gesture action. Sensor readings are processed transiently and not stored.
Battery Status
Reads current battery level to enable battery-level-conditional gesture profiles (e.g., activating a power-saving overlay when battery drops below 20%). Not transmitted remotely.
10Billing, In-App Purchases & Promotional Codes
Dynamic Edge Gesture Control offers optional in-app purchases and/or a premium subscription tier to unlock advanced gesture customization features, additional gesture action types, backup/restore capabilities, and ad-free usage. All commercial billing and payment processing is handled exclusively by Google Play Billing.
Promotional Codes & Device-Bound Entitlement
To reward community contributors, beta testers, and promotional campaign participants, the application supports two methods of promotional code redemption:
- Lifetime Play Store Promo Codes: Official Google Play Store promotional codes redeemable directly through Google Play (
play.google.com/redeem). All entitlements are governed and validated by Google's infrastructure. - External Promotional Codes (Direct Creator Promotions): Time-limited promotional codes (e.g., 1-week, 1-month, 2-month, 3-month, or 1-year plans) provided directly by the developer. When you redeem an external promo code, the application verifies the code against our private, encrypted Google Sheets backend.
- When redeeming an external promo code, the application reads the device's app-specific Android ID (
Settings.Secure.ANDROID_ID/ SSAID) and sends it over encrypted HTTPS to our backend. - Purpose & Scope: This identifier is utilized strictly for App Functionality (tracking active subscription start and expiry dates) and Fraud Prevention (binding each code to a single hardware device to prevent unauthorized code sharing, scraping, or multi-device abuse).
- Scoped Privacy Guarantee: Under Android 8.0+ (API 26+), the SSAID is unique to this app and our developer signing key; it cannot be correlated with other applications on your device. It is never used for advertising, behavioral profiling, or shared with third parties.
- Optional Participation: External promo code redemption is 100% voluntary. Users who do not redeem external promotional codes never have their SSAID collected or transmitted.
What We Receive from Google Play Billing
- A boolean acknowledgment confirming whether a specific purchase or subscription is active ("entitled").
- A non-personal purchase token (a pseudonymous string) generated by Google Play for purchase verification and subscription management.
Refund Policy
All refund requests for in-app purchases or subscriptions are processed via Google Play's refund mechanism. You can request a refund through Google Play β Order History β Request a Refund. We do not process refunds independently.
Subscription Auto-Renewal
If you subscribe to a premium plan, your subscription will auto-renew through Google Play at the end of each billing period unless cancelled at least 24 hours before the renewal date. Manage and cancel subscriptions via Google Play β Subscriptions.
11Mobile Advertising Networks (Google AdMob, Meta Audience Network, Unity Ads)
To support the ongoing development, optimization, and serverless maintenance of Dynamic Edge Gesture Control while keeping core navigation and gesture customization tools 100% free for all users, our free tier displays advertisements brokered and mediated through leading, certified mobile ad networks: Google AdMob, Meta Audience Network (Facebook Ads), and Unity Ads.
Integrated Ad Partner SDKs
Depending on your geographic territory, device characteristics, consent selections, and ad inventory availability, advertisements (including non-intrusive banner strips, transition interstitials, and opt-in rewarded video formats for unlocking specific customization themes) may be served through the following certified partners:
Google AdMob (Google LLC)
Serves contextual and personalized advertisements. AdMob evaluates your Google Advertising ID (GAID), IP address, general coarse location (country/city level), and standard device diagnostic metrics (OS version, device model, screen size) to serve and measure ads.
Meta Audience Network (Meta Platforms, Inc.)
Enables delivery of high-relevance targeted and non-targeted ads powered by Meta's advertising ecosystem. Meta Audience Network may collect device identifiers (GAID, IDFA), IP address, app package name, and interaction timestamps to serve ads and prevent fraudulent impressions.
Unity Ads (Unity Technologies ApS)
Specializes in high-performance video and interactive rewarded ads. Unity Ads processes hardware device identifiers, operating system characteristics, game/utility context, and advertising attribution tokens to deliver and credit rewarded video ads.
Ad Mediation & Real-Time Bidding
We may employ real-time bidding and ad mediation (e.g., via Google Mobile Ads Mediation). In this configuration, ad requests are dispatched in real time to eligible demand partners (AdMob, Meta, Unity). Each network evaluates contextual signals to return the highest-value or most relevant advertisement. No personal user data generated inside the app is shared during this bidding exchange.
How to Opt-Out of Personalized Ads Across All Networks
- System-Level Opt-Out (Android OS):
Navigate to Android Settings → Google → All Services → Ads and tap "Reset Advertising ID" or tap "Delete Advertising ID" (available on Android 12+). When deleted, your device returns a zeroed-out string of zeros (
00000000-0000-0000-0000-000000000000), effectively preventing cross-app behavioral tracking across AdMob, Meta, and Unity Ads simultaneously. - Meta Ad Preferences: If you maintain a Facebook/Meta account, you can customize or limit how Meta uses your off-platform activity to target ads at facebook.com/adpreferences.
- In-App European & UK Consent Management: Users located in the European Economic Area (EEA), United Kingdom, and Switzerland can revoke or adjust consent for individual advertising vendors (Google, Meta, Unity) at any time via Settings → Privacy → Manage Ad Consent.
- Ad-Free Premium Option: Users who upgrade to the Pro/Premium version via Google Play Billing enjoy a completely ad-free experience, during which all ad requests and third-party advertising SDK initializations are completely halted.
12Google Firebase Services & Technical Telemetry
Dynamic Edge Gesture Control integrates Google Firebase (a cloud-backed mobile development platform operated by Google LLC) strictly for stability monitoring, crash diagnostics, performance metrics, and remote configuration flags. Firebase operates entirely separate from advertising tracking.
Firebase Modules Deployed
Firebase Crashlytics
Automatically captures anonymized crash reports including stack traces, device model, Android OS version, app version, and memory state at crash time. Crash reports do NOT include screen content, user input, personal data, or location.
Firebase Analytics (Google Analytics for Firebase)
Collects anonymized, aggregated app usage events (e.g., feature screen opens, gesture action trigger counts) to understand which features are most used. No personally identifiable information is included in analytics events. Analytics collection can be disabled via in-app Privacy Settings.
Firebase Remote Config
Fetches remote configuration flags (e.g., feature toggles, A/B test parameters, default values) from Firebase servers. No user-identifying data is transmitted during config fetches.
Firebase Performance Monitoring
Measures app startup time, screen rendering performance, and network request latency to identify and fix performance regressions. Data is aggregated and anonymized.
How to Opt-Out of Firebase Analytics
You can opt out of anonymous usage analytics at any time directly inside the app: navigate to Settings → Privacy → Anonymous Analytics Opt-Out. Toggling this off stops all analytical event dispatches to Google Firebase.
13EU & UK Consent Management (GDPR / UMP SDK)
For users in the European Economic Area (EEA), United Kingdom, and Switzerland, Dynamic Edge Gesture Control implements a fully GDPR-compliant consent management process using the Google User Messaging Platform (UMP) SDK.
Consent Collection
- On first launch, users in applicable regions are presented with a standardized IAB TCF v2.2-compliant consent form.
- Users may choose between Consent All (personalized ads and analytics), Reject All (non-personalized ads, no analytics data sharing), or manage granular vendor-level consent preferences.
- Consent status is stored locally on the device and transmitted to AdMob and Firebase to configure ad serving behavior accordingly.
Legal Bases Under GDPR (Regulation (EU) 2016/679)
- Legitimate Interest (Art. 6(1)(f)): Processing of minimal crash diagnostic data necessary for app stability and security.
- Consent (Art. 6(1)(a)): Processing of advertising identifiers for personalized ads; aggregated analytics events. You may withdraw consent at any time via In-App Settings β Privacy β Manage Ad Consent.
- Contract Performance (Art. 6(1)(b)): Processing of Google Play purchase tokens to verify and deliver premium subscription entitlements.
Withdrawing Consent
You can revisit and change your consent choices at any time by navigating to In-App Settings β Privacy β Manage Consent. Withdrawal of consent for analytics does not affect prior data already transmitted. To request deletion of prior Firebase data, see Section 22 (Data Deletion & Right to Erasure).
14Tasker, Shortcuts & Third-Party Automation Integrations
Dynamic Edge Gesture Control supports integration with Android automation platforms including Tasker, MacroDroid, KWGT, and standard Android Shortcuts. These integrations allow users to trigger EDGE gesture actions from external automation workflows and vice versa.
Privacy Scope of Automation Integrations
- EDGE exposes a limited set of public Intent actions and Broadcast receivers that automation apps can use to trigger pre-configured EDGE gesture profiles.
- EDGE does not provide APIs to third-party automation apps that would allow them to read user gesture configuration data, personal files, contacts, or any other sensitive information.
- Automation tasks defined by the user using EDGE's built-in task engine are stored exclusively in local app-private storage and are never synchronized to cloud services by EDGE itself. (Note: Tasker's own cloud sync features are governed by Tasker's privacy policy.)
- EDGE does not access or parse automation task definitions from Tasker or other third-party automation apps. Data flow is one-directional: the user instructs an automation platform to send a specific Intent to EDGE.
15Local Storage, Backups & Data Security
Dynamic Edge Gesture Control stores user configuration and operational data exclusively within Android's sandboxed application-private storage (/data/data/com.m.payra.gesture.control.app/). This directory is inaccessible to other applications without root access.
What is Stored Locally
- Gesture profile configurations (swipe directions, zones, assigned actions)
- App-specific gesture profile assignments (package-to-profile mappings)
- Geo-fence zone definitions (stored as encrypted local JSON)
- In-app Notes text content (stored in encrypted SQLite database)
- Audio memo files (stored in app-private external storage)
- Camera shortcut capture thumbnails (stored in MediaStore with full user visibility)
- AdMob consent preferences and Firebase installation ID
Android Auto-Backup
Android may automatically back up application data to the user's Google Account via Android Auto Backup or Google One Backup. EDGE's backup configuration explicitly excludes sensitive files (e.g., audio memo recordings, photo captures) from automatic backup. Core configuration preferences may be backed up to enable seamless restore after device migration.
You can disable app-level backup for EDGE specifically: Android Settings β System β Backup β App data β Dynamic Edge Gesture Control β Disable.
Data Encryption
All locally stored configuration data, geo-fence definitions, notes content, and audio memos are encrypted at rest using the Android Keystore system (AES-256-GCM where applicable). The device's locked-screen state protects against unauthorized physical access.
16Network Security & Data Transmission
Dynamic Edge Gesture Control's network communication is strictly limited to the third-party integrations disclosed in this policy (Firebase, AdMob, Google Play Billing). We implement the following network security measures:
- TLS 1.3 Enforcement: All outbound network connections use TLS 1.3 (minimum TLS 1.2). Plaintext HTTP connections are prohibited by the application's Network Security Configuration (
network_security_config.xml), which declarescleartextTrafficPermitted="false". - Certificate Pinning: Critical API endpoints (Firebase Remote Config) implement certificate pinning to prevent man-in-the-middle (MITM) attacks on certificate spoofing vectors.
- No Custom Backend Servers: Dynamic Edge Gesture Control does not operate its own backend infrastructure. There are no EDGE company servers that receive or store user data. All third-party network communication is to Google-operated infrastructure (Firebase, AdMob, Google Play).
- No Telemetry to Developer Servers: No telemetry, log data, or analytics data is sent to servers controlled by Madhusudan Payra. All diagnostic data flows exclusively to Google Firebase, which is governed by Google's data processing agreements.
- DoNotTrack Compliance: Although Android does not implement a formal DNT signal, EDGE respects the semantics of the concept: users who opt out of analytics via Privacy Settings will have all third-party analytical data transmission suppressed.
17Third-Party Trademark Disclaimer & Nominative Fair Use
Dynamic Edge Gesture Control references certain third-party trademarks, product names, service marks, logos, and brands solely for informational purposes, technical interoperability explanations, and statutory data disclosures under the legal doctrine of Nominative Fair Use.
The factual use of these names, trademarks, and brands within our application and documentation:
- Does NOT constitute, imply, or suggest any affiliation with, sponsorship of, endorsement by, or official commercial partnership with the respective trademark holders.
- Is made solely to identify compatible software, operating platforms, hardware sensors, Android system services, or integrated advertising and telemetry SDK partners as legally mandated by Google Play User Data policies, EU GDPR, and CCPA/CPRA disclosures.
- Dynamic Edge Gesture Control™ and EDGE are independent proprietary creations developed and owned exclusively by Madhusudan Payra.
Software licensing restrictions, acceptable use terms, and prohibitions against reverse engineering, decompilation, and code tampering are governed exclusively under our Terms of Use (Section 11).
If you are a trademark owner and believe any content or reference infringes upon your intellectual property rights, please contact us immediately at m.payra859appsupport@gmail.com for prompt review and resolution.
18Biometric Authentication & Zero Credential Storage Warranty
Dynamic Edge Gesture Control optionally allows users to protect access to the app's settings panel with biometric authentication (fingerprint or face recognition). This feature leverages exclusively Android's BiometricPrompt API provided by the Android operating system.
BiometricPrompt API.
Illinois BIPA Compliance Statement
The Illinois Biometric Information Privacy Act (740 ILCS 14/) applies to the collection and commercial use of biometric identifiers and information. Because Dynamic Edge Gesture Control does not collect, capture, purchase, receive through trade, or otherwise obtain biometric identifiers or biometric information (as defined under 740 ILCS 14/10), EDGE is not required to maintain a written retention policy under BIPA. All biometric processing is handled exclusively by the Android OS; EDGE serves only as a caller of the platform's BiometricPrompt API and receives no biometric data. This section is maintained for transparency for Illinois residents. See also Section 26 (BIPA Compliance).
No passwords, PINs, biometric templates, cryptographic keys, or authentication credentials of any kind are stored by Dynamic Edge Gesture Control in plaintext or any recoverable format.
19Power Management, Alarms & Battery Optimization
Dynamic Edge Gesture Control requests several system-level permissions related to power management and alarm scheduling to ensure reliable gesture detection and automation execution:
REQUEST_IGNORE_BATTERY_OPTIMIZATIONS: Requests that the Android battery optimization system exempt the EDGE foreground service from automatic process killing during Doze mode. This permission is disclosed to the user in a plain-language explanation at the time of request. It can be revoked via Settings β Battery β Battery Optimization β Dynamic Edge Gesture Control β Optimize.SCHEDULE_EXACT_ALARM/USE_EXACT_ALARM: Required for scheduling time-precise gesture automation triggers (e.g., "activate Night Mode profile at exactly 10:00 PM"). Uses Android'sAlarmManager.setExactAndAllowWhileIdle()API. Alarm schedules are stored locally and never transmitted.WAKE_LOCK: Prevents CPU sleep during active gesture recognition sessions. Released immediately upon gesture completion to minimize battery impact.- Foreground Service with Notification: A persistent notification is shown whenever EDGE's gesture detection service is running, in compliance with Android's foreground service requirements (API 28+). The notification shows service status and provides a quick toggle to pause detection.
We are committed to minimizing battery impact. EDGE's gesture detection service is designed to operate at low CPU priority and uses event-driven wake triggers rather than continuous polling where possible.
20Bluetooth Connectivity & Situational Awareness
Dynamic Edge Gesture Control requests BLUETOOTH_CONNECT and BLUETOOTH_SCAN permissions (required on Android 12+ / API 31+) to enable Bluetooth-Aware Gesture Profiles.
How Bluetooth Permissions Are Used
- Connection State Detection: Checks whether the device is connected to a specific Bluetooth device (identified by device name, not address) to trigger profile switching. Example: switching to "Car Mode" gestures when connected to a named Bluetooth car kit.
- Bluetooth Device Name Scanning: Briefly scans for nearby Bluetooth devices to compare against user-defined device name rules. Scanning occurs only when the Bluetooth situational feature is enabled and stops once the rule evaluation is complete.
Bluetooth permission usage is in full compliance with Google Play's Bluetooth policy requirements. Revoking Bluetooth permissions disables situational Bluetooth profile switching but does not affect any other EDGE functionality.
21Notifications & Alert Policies
Dynamic Edge Gesture Control uses Android's notification system for the following purposes:
- Foreground Service Notification (Mandatory): A persistent notification displayed while the gesture detection service is active, required by Android policy for apps running foreground services that access camera, microphone, or location. This notification cannot be disabled while the service is running but can be minimized to silent/low-priority channel on most devices.
- Gesture Action Confirmation Alerts: Optional brief toast notifications or notification alerts confirming specific gesture action executions (e.g., "Screenshot taken"). Can be disabled in Settings β Notifications.
- Update & Promotional Notifications: Occasionally, we may send in-app update announcements. These are delivered via Firebase Remote Config (not push notifications) and displayed as in-app banners rather than system notification channel notifications.
POST_NOTIFICATIONS runtime permission at first launch before displaying any notifications. You may deny this permission; only the mandatory foreground service notification (which is displayed as a system foreground service notification regardless) is affected by this choice.
You can manage EDGE's notification channels at any time via Android Settings β Apps β Dynamic Edge Gesture Control β Notifications.
22Data Deletion, Right to Erasure & User Data Requests
In compliance with Google Play's mandatory User Data Deletion requirements (effective December 2023), the GDPR Right to Erasure (Article 17), and the CCPA Right to Delete (Cal. Civ. Code Β§ 1798.105), we provide the following data deletion mechanisms:
Immediate On-Device Deletion
You can delete all locally stored EDGE data instantly:
- In-App Reset: Navigate to Settings β Advanced β Reset All Settings to clear all gesture profiles, automation rules, geo-fence zones, notes, and configuration preferences.
- Uninstall: Uninstalling Dynamic Edge Gesture Control permanently removes all app-private storage data from your device, including configuration, notes, and audio memos, in accordance with Android's application sandbox rules.
- Android Clear Data: Via Settings β Apps β Dynamic Edge Gesture Control β Storage β Clear Data.
Third-Party Analytics Data Deletion
To request deletion of diagnostic/analytics data stored by Firebase (anonymized crash logs, analytics events):
- Email us at m.payra859appsupport@gmail.com with the subject line "Data Deletion Request β EDGE Analytics" and include your Firebase Installation ID (found in Settings β About β App Info β Installation ID).
- We will submit a deletion request to Google Firebase on your behalf within 30 days of receiving your request. Google Firebase retains the right to maintain aggregated, anonymized data that cannot be linked back to individuals.
Because EDGE does not maintain its own user database or account system, there is no user account to delete β only optional Firebase diagnostic data and AdMob advertising identifier interactions.
23Children's Privacy β COPPA, GDPR Article 8 & CCPA
Dynamic Edge Gesture Control is designed exclusively for users who are at least 13 years of age (or the applicable age of digital consent in your jurisdiction β 16 in certain EU member states under GDPR Article 8, 13 in the United States under COPPA). The application is NOT directed at children under these age thresholds.
COPPA Compliance (USA β Children's Online Privacy Protection Act, 15 U.S.C. Β§ 6501 et seq.)
We do not knowingly collect personal information from children under 13 years of age in the United States. Dynamic Edge Gesture Control does not implement any age-verification mechanism because it does not collect any personal information from users (accounts, emails, profile data). The camera, microphone, and location features are general-purpose gesture trigger mechanisms, not features designed to appeal specifically to or be directed at children as defined under COPPA Section 312.2.
If we discover that we have inadvertently received personal data from a child under 13 via Firebase crash reports (e.g., a device model identifier linked to a minor), we will promptly delete such data. Parents or guardians who believe their child has inadvertently used this application may contact us at m.payra859appsupport@gmail.com for data review and deletion.
GDPR Article 8 β Children in the European Union
In EU member states that set the age of consent for information society services at 16 years (including Germany, the Netherlands, and others), we recommend that parents/guardians supervise the installation and configuration of EDGE on devices used by minors aged 13β15. Our Google UMP consent dialog is calibrated to treat users below the applicable age threshold as non-consenting for purposes of personalized advertising and to serve only non-personalized ads.
CCPA β California Minors (Cal. Bus. & Prof. Code Β§ 22580β22582)
Under the California Online Privacy Protection Act (CalOPPA) and related statutes, operators of websites or online services directed to minors must post specific privacy disclosures. Because EDGE is directed at users 13 and older and does not knowingly collect personal information from minors, EDGE complies with these requirements by default. California minors may request removal of content they have publicly posted; however, since EDGE does not have any user-generated public content platform, this provision does not apply to EDGE's feature set.
24GDPR & CCPA/CPRA β Your International Privacy Rights
Rights Under EU/UK GDPR (Regulation (EU) 2016/679)
If you are a resident of the European Economic Area (EEA) or United Kingdom, you have the following rights regarding your personal data:
- Right of Access (Art. 15): Request a copy of the personal data we hold about you (e.g., Firebase Installation ID, anonymized crash log identifiers).
- Right to Rectification (Art. 16): Request correction of inaccurate personal data.
- Right to Erasure / "Right to be Forgotten" (Art. 17): Request deletion of your personal data. See Section 22 for the deletion process.
- Right to Restriction of Processing (Art. 18): Request that we restrict processing of your data in certain circumstances.
- Right to Data Portability (Art. 20): Request your personal data in a machine-readable format. (Note: because EDGE stores configuration data locally on your device, most data is inherently portable and accessible directly to you.)
- Right to Object (Art. 21): Object to processing based on legitimate interests (e.g., crash diagnostics).
- Rights Related to Automated Decision-Making (Art. 22): EDGE does not engage in automated profiling or decision-making that produces legal or similarly significant effects for users.
- Right to Lodge a Complaint: You have the right to lodge a complaint with your local supervisory authority. In the EU, find your authority at edpb.europa.eu. In the UK: Information Commissioner's Office (ICO).
Rights Under CCPA/CPRA (California Consumer Privacy Act & California Privacy Rights Act)
If you are a California resident, the CCPA (as amended by CPRA, effective January 1, 2023) grants you the following rights:
- Right to Know (Β§ 1798.100): Know what personal information we collect, use, disclose, and sell.
- Right to Delete (Β§ 1798.105): Request deletion of your personal information.
- Right to Opt-Out of Sale/Sharing (Β§ 1798.120): We do not sell personal information as defined under CCPA. We do share the Google Advertising ID with AdMob for advertising purposes (with consent), which may constitute "sharing" under CPRA. You may opt out by resetting or deleting your Google Advertising ID and opting out of Firebase Analytics via in-app settings.
- Right to Non-Discrimination (Β§ 1798.125): We will not discriminate against you for exercising your CCPA rights. Premium features are not conditioned on consenting to data collection.
- Right to Correct Inaccurate Information (Β§ 1798.106, added by CPRA): Request correction of inaccurate personal information.
- Right to Limit Use of Sensitive Personal Information (Β§ 1798.121, added by CPRA): EDGE does not sell or use sensitive personal information for advertising. Location data, biometric data, and health data are used solely for app functionality as disclosed herein.
To exercise any of these rights, contact us at: m.payra859appsupport@gmail.com with the subject line "Privacy Rights Request β [Your Right Name]". We will respond within 45 days (extendable by a further 45 days with notice).
25U.S. State Privacy Laws β Virginia, Colorado, Connecticut & Others
In addition to the California CCPA/CPRA, Dynamic Edge Gesture Control acknowledges the following state privacy laws now in effect in the United States:
Virginia Consumer Data Protection Act (VCDPA) β Effective Jan 1, 2023
Virginia residents have rights to access, correct, delete, and obtain a copy of personal data, and to opt out of targeted advertising, sale of personal data, and profiling. Our disclosures in Section 24 cover these rights equivalently. Contact us to exercise VCDPA rights.
Colorado Privacy Act (CPA) β Effective July 1, 2023
Colorado residents have rights to opt out of targeted advertising and the sale of personal data. Our AdMob opt-out mechanism (reset Google Advertising ID) serves as the technical implementation for this opt-out right.
Connecticut Data Privacy Act (CTDPA) β Effective July 1, 2023
Connecticut residents have substantially equivalent rights to Virginia and Colorado residents under the CTDPA. Our data deletion and opt-out mechanisms apply equally.
Texas Data Privacy and Security Act (TDPSA) β Effective July 1, 2024
Texas residents are entitled to know, correct, delete, and obtain their personal data, and to opt out of targeted advertising. The same mechanisms described above apply.
Oregon Consumer Privacy Act (OCPA) β Effective July 1, 2024
Oregon residents have comparable rights. Contact us at the support email with "OCPA Privacy Request" in the subject line.
Indiana Consumer Data Protection Act β Effective Jan 1, 2026
We are preparing for Indiana's forthcoming law. Rights under the Indiana CDPA will be serviced via our existing data request mechanism.
Users in any U.S. state may exercise their applicable privacy rights by contacting m.payra859appsupport@gmail.com. We will assess the applicable law based on your state of residency as disclosed in your request.
26Illinois Biometric Information Privacy Act (BIPA)
Illinois residents are protected by the Biometric Information Privacy Act (740 ILCS 14/), which governs the collection, storage, use, and destruction of biometric identifiers and biometric information.
BiometricPrompt API, which processes all biometric matching within the device's Trusted Execution Environment (TEE). EDGE receives only a pass/fail boolean result and never receives, stores, or transmits any biometric template, fingerprint scan data, facial geometry, iris scan, voiceprint, retina scan, hand scan, or any other biometric identifier.
Therefore, EDGE is not subject to BIPA's requirements to: (1) develop a written policy for biometric data retention; (2) obtain written consent before collecting biometric data; (3) provide a retention schedule; or (4) avoid selling or profiting from biometric data. We maintain this disclosure for complete transparency with Illinois residents.
If you have questions about BIPA applicability, contact: m.payra859appsupport@gmail.com
27California Shine the Light Act (Cal. Civ. Code Β§ 1798.83)
California's "Shine the Light" law (California Civil Code Section 1798.83) gives California residents the right to receive information about whether businesses disclose personal information to third parties for direct marketing purposes, and to request a list of the categories of personal information shared and the names of those third parties.
California residents with questions about this disclosure may contact us at m.payra859appsupport@gmail.com with the subject line "Shine the Light Request".
28Data Protection Officer (DPO) & GDPR EU Representative
As an independent developer operating as a sole proprietor without employees, Madhusudan Payra is not legally required to appoint a formal Data Protection Officer (DPO) under GDPR Article 37 (which applies to organizations that carry out systematic, large-scale processing of sensitive personal data). EDGE does not carry out such large-scale systematic processing.
Privacy Point of Contact
All data protection inquiries, data subject access requests (DSARs), and GDPR/CCPA/BIPA compliance questions should be directed to:
Privacy Contact β Madhusudan Payra
Email: m.payra859appsupport@gmail.com
Subject line prefix: "PRIVACY REQUEST:"
Response time: Within 72 hours (acknowledgment); 30 days (full response)
GDPR EU Representative (Art. 27)
Dynamic Edge Gesture Control's data controller (Madhusudan Payra) is based outside the EU/EEA. As a sole-developer application with minimal data processing and no systematic monitoring of EU data subjects, we invoke the exemption under GDPR Article 27 for controllers that only occasionally process data not on a large scale, do not process special category data, and whose processing is unlikely to result in a risk to the rights and freedoms of natural persons.
If you are an EU/EEA resident and wish to exercise your GDPR rights, please contact us directly at the email above. Unresolved concerns may be escalated to your country's national data protection authority (DPA), listed at edpb.europa.eu.
29Accessibility & Privacy of This Policy Webpage
This privacy policy is hosted as a static HTML webpage at bullat859.github.io/privacy-policy/ via GitHub Pages, operated by GitHub, Inc. (a subsidiary of Microsoft Corporation). By visiting this webpage, you are subject to GitHub's privacy policy at docs.github.com, which governs GitHub's own data collection (including server logs, IP addresses, and browser metadata for static page delivery).
No Tracking on This Webpage
- This webpage does NOT set any cookies (first-party or third-party).
- This webpage does NOT use Google Analytics, Facebook Pixel, or any other analytics tracking scripts.
- This webpage does NOT serve advertisements.
- This webpage does NOT use tracking pixels, web beacons, session recording tools, or fingerprinting scripts.
- All fonts are loaded from Google Fonts (fonts.googleapis.com), which may log your IP address and browser UA in accordance with Google's Privacy Policy. If you prefer, you may block fonts.googleapis.com via your browser or a content blocker; the page remains fully functional with system fallback fonts.
Accessibility of This Webpage
This privacy policy webpage is designed to meet WCAG 2.1 Level AA accessibility guidelines: it uses semantic HTML5, ARIA labels where appropriate, sufficient color contrast ratios, scalable text, and keyboard navigability. If you encounter accessibility barriers, please contact m.payra859appsupport@gmail.com.
30Policy Changes, Version History & Notifications
We may update this Privacy Policy periodically to reflect changes in our app's functionality, applicable law, or third-party service updates. We are committed to transparent policy governance:
- Material Changes: For material changes (e.g., introduction of new data collection categories, new third-party integrations, or changes to how we use sensitive permissions), we will notify users via an in-app notification and/or a highlighted update notice on this webpage for at least 30 days before the changes take effect.
- Non-Material Changes: Minor clarifications, typographical fixes, or structural reorganization of this policy that do not affect data practices will be updated without specific advance notice, but the "Last Updated" date will be revised.
- Version Archive: Prior versions of this Privacy Policy are available upon request by emailing m.payra859appsupport@gmail.com with the subject "Privacy Policy Version History Request".
- Continued Use: Continued use of Dynamic Edge Gesture Control following a policy update constitutes acceptance of the updated policy. If you do not agree with the updated policy, please uninstall the application.
31Data Security Architecture, Retention & Incident Response
Security Architecture
- Android Keystore Integration: Sensitive locally stored data (geo-fence definitions, notes, configuration secrets) is encrypted using keys managed by the Android Keystore System, which stores cryptographic keys in hardware-backed secure storage (TEE/StrongBox) where available.
- Application Sandbox Isolation: App data is stored in an isolated sandbox (
/data/data/com.m.payra.gesture.control.app/) inaccessible to other apps without root compromise. - ProGuard / R8 Code Obfuscation: The application is compiled with R8 code shrinking and obfuscation to reduce attack surface from decompilation attempts.
- No Hardcoded Credentials: No API keys, database credentials, or server certificates are hardcoded in the application binary. All secrets are managed via secure build-time injection or runtime secure storage mechanisms.
- Secure Network Transport: All internet communications use TLS 1.3 as described in Section 16.
Data Retention Periods
- Local Configuration Data: Retained indefinitely until the user manually deletes it, resets the app, or uninstalls the application.
- Firebase Crash Reports: Retained by Google Firebase for up to 90 days per Firebase's default retention settings. Anonymized aggregated metrics may be retained longer in non-identifiable form.
- Firebase Analytics Events: Retained for up to 14 months per Google's default analytics retention policy (configurable by the developer down to 2 months in the Firebase Console).
- AdMob Advertising Identifier: The Google Advertising ID is not permanently stored by EDGE. It is passed to AdMob at ad request time and governed by AdMob's retention policies.
Security Incident Response
In the event of a confirmed security breach affecting EDGE user data (including any breach of Firebase data storage accessed by unauthorized parties), we commit to:
- Notifying affected users via an in-app notification and update announcement within 72 hours of confirmed breach (in compliance with GDPR Article 33/34 notification requirements).
- Reporting the breach to relevant supervisory authorities where required by applicable law.
- Publishing a detailed post-incident report on this webpage within 30 days of breach confirmation.
To report a suspected security vulnerability, please contact: m.payra859appsupport@gmail.com with the subject "Security Vulnerability Report". We appreciate and respond to responsible disclosure reports.
32Contact & Legal Inquiries
If you have questions, privacy requests, DSAR inquiries, permission clarifications, or statutory requests regarding this Privacy Policy, please reach out directly:
Madhusudan Payra
Solo Developer & Owner — Dynamic Edge Gesture Control™
📍 India