App package: com.msdnd.duashield.android • iOS bundle (placeholder): com.msdnd.duashield.ios
Last updated: February 22, 2026
Welcome to DuaShield (the “App”). This page explains how we handle data, the permissions the App requires, how third parties are used, and the rules that govern use of the App (our End User License Agreement — EULA). Please read both sections carefully. By using DuaShield you accept these terms. If you do not agree, please do not use the App.
Below are the Android permissions the app currently requests. iOS-specific permissions are listed as placeholders (you'll update that section when you prepare the iOS Info.plist).
android.permission.INTERNET — needed to reach our services and third-party SDKs (analytics, crash reporting, RevenueCat, AdMob).android.permission.POST_NOTIFICATIONS — to show notifications (subscription receipts, reminders, shield-related notifications).android.permission.SYSTEM_ALERT_WINDOW — for the overlay we display when shielding a blocked app (overlay shows the "shield" screen).android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS — optional; used to reduce interruptions to long-running shielding or background tasks when the user enables this setting.android.permission.QUERY_ALL_PACKAGES — used only to present a list of installed apps so a user can select which apps to shield. This is not used to upload the full installed apps list off-device.Dua Shield on iOS will use Apple’s Screen Time API to enable gate/shield behaviors — that API is controlled by Apple and behaves differently than Android Accessibility.
What we use Accessibility for: on Android the App requests Accessibility permission to detect which app is foregrounded so it can temporarily show the shield overlay when the user has enabled shielding for a selected app. Accessibility is required for the core app gating feature to work; without it the App will still open, but shielding (the primary feature) will not function.
What data Accessibility sees and where it goes: the App observes the foreground app package name (to know when to show the shield). We do not read or persist UI text content. Only the list of apps that you explicitly choose to shield is stored locally on your device. No Accessibility-derived data that could identify your content is uploaded off-device.
Overlay usage: the overlay (SYSTEM_ALERT_WINDOW) is used to show a shield screen. The overlay records only aggregated local metrics such as total duration of shield sessions for use in local statistics and to show progress inside the App. These metrics are stored on-device and not shared unless you explicitly enable a feature that sends such stats to a server (currently not used).
We collect and process the following categories of information. For each category we explain where it is stored and who it is shared with.
DuaShield uses a small number of third-party services. Below is what we use and the types of data they typically receive. Many SDKs collect identifiers, events, and IP for their functionality.
Note on data sent to these providers: they commonly receive pseudonymous identifiers (app instance ID, advertising ID), event data (analytics), crash traces, and IP addresses. They are used only for their stated purpose. We do not authorize third-party access to your raw shielded-app lists or Accessibility content.
We display ads through Google AdMob. In jurisdictions where consent is required (e.g., EEA), we show a consent prompt (UMP). Consent choices are stored locally in the App's preferences. If personalized ads are enabled, ad SDKs may use Advertising IDs and other identifiers to personalize ads. You can reset or revoke an advertising ID via the device OS settings.
All subscriptions are processed via RevenueCat and the platform billing providers (App Store / Play Billing). We do not collect or store payment card details. For refunds, users should follow the app store refund processes:
Hosting: account authentication uses Supabase (project region: Singapore). App analytics and crash reporting use Firebase (configured to an India region for project resources where applicable). Backups and provider storage are managed by those services.
Cross-border transfer: data may be transferred across borders as required to operate services (for example, analytics backends, RevenueCat, or other service endpoints). We rely on provider safeguards (encryption in transit, encryption at rest, and the providers' compliance measures). You can contact us for more details about safeguards in place for transfers.
We support user rights under applicable laws:
How to exercise your rights: contact us at dev@beigelynx.com or use the in-app settings where present for account deletion. When contacting us, please state the request (e.g., access, deletion) and provide the email address or identifier associated with your account. We may need to verify your identity before fulfilling requests.
We take reasonable measures to protect data: connections to our services and to third-party providers are encrypted in transit (TLS) and provider-side storage is encrypted at rest. Supabase and Firebase document encryption-in-transit and encryption-at-rest for their services. While we take steps to protect your information, no system is 100% secure, so we cannot guarantee absolute security.
In the event of a security incident involving user personal data, we will investigate, take remediation steps, and notify affected users and regulators as required by applicable law.
DuaShield is not intended for children under 13 (or applicable age in your country). We do not knowingly collect information from children under the age required by local law. If you believe we have collected data from a child in violation of law, contact us and we will promptly take steps to remove that data.
We may update this policy from time to time. We will publish the updated policy and the “Last updated” date at the top. Substantial changes will be highlighted for existing users where feasible.
If you have questions about this policy or want to exercise your rights, contact:
Developer / Data Controller:
Name: Mohammed Sané (personal developer)
Email: dev@beigelynx.com
Address (minimal contact): Jaipur, Rajasthan, India
DuaShield is licensed, not sold, to you. We grant you a non-transferable, non-sublicensable license to use the App on devices you own or control, subject to this EULA and any app-store rules.
You must not misuse the App. You may not reverse-engineer, decompile, or modify the App except where applicable law permits such actions despite this restriction.
You agree that we may collect and use technical data and related information about your device and App usage as described in the Privacy Policy to provide and improve the App. When required by law or platform rules we will obtain your consent (for example, for personalized advertising in EEA).
The App may enable access to third-party services (e.g., RevenueCat, AdMob, Supabase). Your use of those services may be subject to additional terms and the service providers’ privacy policies.
We may terminate or suspend access if you break this EULA. You may terminate by uninstalling the App and deleting your account.
The App is provided “as is” and “as available”. To the maximum extent permitted by applicable law, we disclaim all warranties, whether express or implied, including merchantability, fitness for a particular purpose, and non-infringement.
To the extent permitted by law, our liability to you is limited. We are not liable for indirect, incidental, special, exemplary, or consequential damages, or damages for loss of profits, data or goodwill. In jurisdictions that limit the ability to disclaim certain warranties or exclude certain damages, those laws apply to the extent required.
You will not export or re-export the App except in compliance with applicable export laws.
If you are located in India, consumer protection laws of India and applicable jurisdiction will apply. For users in other countries, local laws may apply. If a dispute arises we will first try to resolve it directly with you; if necessary, disputes will be handled in accordance with applicable law for your location.