Privacy Policy
This policy explains how the Android app Easy Video Downloader (io.gomeng.easydownloader) and this information website handle information.
The app does not transmit ordinary browsing or download lists. If you consent to an individual or automatic failure report, the selected failure URL and limited diagnostics are sent to the developer. The operator also receives information you submit through the external form to investigate issues and handle inquiries.
1. Information processed on your device
- Browser information: browsing records, visits resulting from searches, bookmarks, open tabs, cookies and website data, used for browsing, restoring tabs and applying your settings.
- Downloads and media: media and source URLs, filenames, storage locations, download records, thumbnails, duration, size and other metadata, used for detection, downloads, playback, file management and duplicate download checks.
- Settings and access: storage settings, remaining downloads, premium purchase status and advertising consent status needed to provide app features.
- Custom storage: connection details you enter, including the network storage address, username, storage path and password, used to connect to your chosen storage.
- Locks and clipboard: verification values for your PIN or password are stored on the device. Biometric authentication uses the Android authentication result; the app does not receive raw biometric information. If clipboard URL checking is enabled, the app checks for a URL while you use the app and asks whether to open it.
The app does not upload browsing or media URLs to the operator except for failure reports you consent to send. Filenames and network storage credentials are not included in reports, and browsing/download lists are not added to advertising requests. The app has no developer-operated sign-up account. With separate permission, app usage and download start, completion and failure counts are measured as described below, without browsing or media URLs or file lists.
2. Websites, search and external storage
Browsing, searches, thumbnails, media requests and downloads may send your IP address, user agent, request contents and necessary cookies or credentials to the website, search engine or media provider. Updating ad-blocking lists connects to the list provider. Those services also handle information under their own policies.
Your FTP/FTPS storage receives the authentication information needed for connection and the files and paths you choose. Opening, sharing or exporting through another app or storage location sends the information needed for that action to the destination you select.
3. Advertising and consent choices
The app uses Google AdMob rewarded ads to provide free download credits and Google's User Messaging Platform (UMP) for consent management. The advertising SDK collects and shares the following for advertising, measurement and fraud prevention:
- IP address and approximate location inferred from it
- App and advertising interactions, such as app launches, ad impressions, taps and video views
- App and SDK performance and diagnostic information
- Android advertising ID, app set ID and applicable device/account identifiers
Google's advertising services and advertising partners listed in the consent interface process information according to applicable settings and consent status. The app does not add your browsing or download lists to ad requests. Consent management is presented where required, and an advertising privacy choice in app settings lets you update your choice when applicable. You can manage your advertising ID in Android settings.
Further information about processing and retention: Google Privacy Policy, Google advertising technologies, AdMob SDK data disclosure.
3-1. Optional app usage analytics
Versions with this feature show a separate consent notice. Firebase Analytics collection is off until you agree. With your permission, the operator uses Google Firebase Analytics and Google Analytics to measure daily active users and download starts, completions and failures, understand app usage and improve download reliability. Declining or closing the notice with Back does not restrict any app features.
Google may process a random app instance identifier, app, device, operating system and language information, app launch, session and engagement events, approximate location derived from IP, and applicable advertising or purchase events (such as product, amount and currency). Google's Privacy Policy governs the SDK's data and processing. Information may be used for usage and advertising revenue analysis across Firebase, Google Analytics and the linked AdMob service. Processing occurs over HTTPS on Google infrastructure, including in the United States and other countries.
The app adds only fixed event names for download starts, completions and failures, and for rewarded-ad offer views, button choices, consent handling, preparation, display, dismissal, rewards and server verification. Failures use predefined categories such as network, no ad inventory or authentication failure. We do not attach page or media URLs, searches, titles, filenames, file contents, raw error messages, cookies, login details, storage credentials or ad/entitlement-server identifiers. Downloads started in incognito tabs and ad interactions in incognito screens are excluded. Analytics advertising ID and SSAID collection, automatic screen reporting and ad personalization are disabled, and we do not set a custom user ID. AdMob's own processing follows the advertising section and its separate consent settings above. Random identifiers make this data pseudonymous, not fully anonymous.
You can turn off Usage analytics in Settings at any time. This stops future analytics collection and resets the device's Analytics identifier and pending analytics data; it does not immediately delete data already received by Google. Google Analytics retains event-level data for 2 months and user data for 14 months; new user activity resets the user-data retention period. Aggregated standard reports may remain longer. For privacy or deletion inquiries, use the email below. Because the developer keeps no mapping between names or emails and analytics identifiers, locating a particular record may be limited.
4. Payments
Premium purchases use Google Play Billing. The app processes product details, purchase status and purchase tokens needed for confirmation and restoration. Purchase tokens are stored encrypted on your device and sent over HTTPS to the verification server for Google Play purchase lookup and acknowledgement. The server does not retain raw purchase tokens; it stores their hashes and premium verification status valid for up to 24 hours. The operator does not directly receive card numbers or payment account information from the app. Google Play's policies and applicable law govern payment and transaction information.
5. Permissions and security
The app uses the Play Integrity API and a Cloudflare Workers verification server for app security and abuse prevention. During entitlement registration, ad preparation, purchase verification and new download or resume attempts, Google Play Store processes app metadata (package, version and signing certificate), Play app license status, device attestation information and a request hash. The hash binds the app package, random request and installation identifiers and operation data. It does not include browsing or media URLs, filenames, cookies, storage credentials or advertising ID.
The app sends integrity tokens, a random installation identifier, an installation credential and entitlement operation data to the server over HTTPS. The server asks Google to decode the token and checks app/device integrity and the Play installation license. Purchase tokens are used separately for Google Play purchase verification. Ad rewards are granted only after verifying signed server callbacks from Google AdMob, with five video download credits per reward. A random installation identifier and ad operation identifier link the callback to your installation; the SDK reward notification alone does not grant credits.
The server stores a hash of the installation credential, remaining credits, purchase token hash and premium expiry, ad reward transaction/operation identifiers, and reservation, completion and refund states keyed by download operation identifiers. If test access is authenticated, authentication success and test access state are also stored. These records provide entitlements, purchase restoration and protection against duplicate rewards and abuse. Browsing and download lists are not sent to the entitlement verification server. Raw integrity tokens, decoded verdicts, request bodies and passwords are not retained in server logs or a database. Cloudflare processes IP addresses and service information, and the server limits short-period IP request counts. Google and Cloudflare process information under their respective policies. See the Cloudflare Privacy Policy and Google Privacy Policy.
If authorization fails or the server is unavailable, a new download does not start and you can retry. Credits charged for failed or cancelled tasks are refunded; offline refund requests are retained on your device and retried when a connection is available. Playing and managing already saved media does not require this verification.
Media and folder permissions display and save the files you allow. Notifications report download status. Network status supports options such as Wi-Fi downloads, and vibration is used for media detection and completion notices according to your settings.
Network storage passwords are encrypted on the device using an Android Keystore key. PIN/password verification values are kept separately from the original secret. App and item locks control access through the app; they do not encrypt media files themselves. Android automatic backup and device transfer are disabled for the app.
HTTP websites and FTP storage may transmit information without encryption. Use HTTPS and FTPS where supported. Device, external storage and destination access controls and security settings also affect data protection.
6. Retention, deletion and choices
Information on your device is kept while needed for app features or until you delete it. You can change browsing/download history preferences and delete records, cookies and website data in settings. Turning off download history may leave task and media information needed for file management or active downloads. Incognito tabs are excluded from ordinary browsing history and tab restoration, but files you explicitly save from an incognito tab remain at their destination.
You can delete saved files through the app. Uninstalling removes internal app data according to Android's uninstall behavior. Files in the media library, selected folders or network storage may remain and need to be deleted at that location. Use each external service's own methods to delete information retained by websites, Google or other services.
Server entitlement records are automatically deleted after 365 days without server activity. Uninstalling or clearing app data does not immediately delete server records. If the installation identifier and credential are lost, free credits for that installation cannot be restored. Premium purchases can be verified again by restoring purchases with the same Google Play account. For inquiries about entitlement information, use the privacy contact email below.
7. Information website and contact
This website is hosted on GitHub Pages. It uses no additional ads, analytics scripts, input forms or tracking cookies. GitHub may process connection information, including visitor IP addresses, to provide and secure its service. See GitHub Pages data collection and the GitHub Privacy Statement.
Privacy contact: public GitHub contact page. Submitting a request through your GitHub account makes your account name and message public. The operator reviews and uses them as needed to handle requests and maintain a response history; request records are kept on GitHub. You can use GitHub features and the contact page to edit or delete your own content or request deletion of a request record. GitHub's policies apply to the account and connection information it processes.
Do not post personal information, browsing/download records, video URLs or network storage passwords in a public request. General app or privacy questions can be submitted without this information.
The download problem button opens the Google report form in an external browser. The external form has no prefilled URLs, errors, country, files, identifiers or diagnostics from the app. The page URL and issue type you submit, and any optional error or reproduction details, country, device/app version, suggestions and contact email you enter, are stored in Google Forms. The operator processes them only while needed to investigate issues, reply and improve app features, and deletes them when no longer needed. The Google Form does not enable response summaries or automatic email collection, and does not require sign-in. The Google Privacy Policy also applies.
For deletion requests or email inquiries, contact gomeng-dev@protonmail.com. Email addresses and messages you send are also processed only while needed to resolve the inquiry and deleted when no longer needed. Your email provider's policies also apply. Do not include passwords, cookies, authentication tokens or unnecessary personal information in a form or email.
Optional in-app failure URL reports
Versions offering this feature show the report URL and collected information after a download failure. Report sends that report only. Checking automatic reports and pressing Report, or accepting the disclosure in settings, enables reports of future failures. This is off by default; Cancel and Back are not consent. You can switch it off at any time. Incognito downloads are excluded.
A report contains the page URL (or media URL if no page is available), a structured error code, media format, app version and a random per-report identifier. The server records the receipt time. No name, email, files, cookies, authentication headers, installation ID or payment history are attached, and reports are not linked with advertising or entitlement records. Embedded URL credentials, fragments and unapproved query parameters are removed. Paths and remaining parameters can still reveal content or identify a person, so complete anonymity cannot be guaranteed.
Reports are sent over HTTPS to a separate private Cloudflare inbox that requires operator authentication for access. The server does not automatically visit reported URLs. Cloudflare processes connection IPs for service delivery and abuse prevention; the application server does not store IPs with reports. Processing may take place in Cloudflare infrastructure outside your country. Reports are removed from the active inbox within 30 days; recovery backups may retain them for up to 30 additional days. For earlier deletion, email the privacy contact above with the report URL. Unsent prompts on the device expire after 24 hours and are cleared when the app is next used. Rate limits or connectivity failures may prevent delivery. Reporting choices do not restrict download features.
8. Changes
If app features or information handling change, this page and its effective date will be updated. Changes requiring additional notice or consent will be handled under applicable law and platform requirements.