NexaFetchWeb Studio
Home Privacy Responsible use

Last updated: August 7, 2026 · Applies to NexaFetch Web, Android, and desktop editions where noted

Privacy Policy

NexaFetch is a personal media utility created by John Edward Dela Cruz (CodeDev by Edward). It does not require an account and is not designed as a social network, marketplace, or cloud locker.

1. Summary

  • No account registration and no advertising or analytics SDKs from CodeDev by Edward.
  • Web edition: links you submit are processed on the same-origin server you are using for temporary jobs only.
  • Android / desktop editions: queue, history, and files stay on your device unless you share them yourself.
  • Network requests go to the media website (and extractor endpoints required by yt-dlp), not to a NexaFetch “user database.”

2. Data the Web edition processes

Submitted links and options

When you analyze or download a URL, that link and your selected format options are sent to the NexaFetch web server so it can request public metadata and streams from the source site through yt-dlp. Do not submit private, login-only, or confidential URLs.

Temporary jobs and files

Each web task uses an isolated temporary folder. Job status, progress, options, and the completed file remain on the server only until the configured expiration period, then they are deleted automatically. Hosting providers may still keep infrastructure logs, backups, or monitoring records outside the application’s control.

Browser storage

The site may store local preferences (for example theme) in your browser via localStorage. Clearing site data removes those preferences. The optional service worker caches static app files for offline shell support; it does not upload your download history to CodeDev by Edward.

3. Data the Android and desktop editions process

  • On device: download URLs, queue entries, history, settings, temporary work files, and completed media you choose to save.
  • Not uploaded: CodeDev by Edward does not operate a cloud account system that receives your queue or history.
  • Network: requests go to the source media website / yt-dlp extractor endpoints from the device.
  • Android backups: application data is configured so sensitive queue content is not intended for automatic cloud backup.

4. Permissions (Android)

NexaFetch may request notification access for download progress, and storage / media access only as needed to save files you start. Camera, contacts, microphone, and precise location are not required for core downloading.

5. Cookies and third parties

The official web edition does not use third-party advertising cookies. Source websites you contact (for example video platforms) may set their own cookies or logs when yt-dlp requests public pages. NexaFetch does not accept or store user login cookies for those platforms in the public web edition.

6. Donations

Optional support links (for example Ko-fi or GCash) are handled by those payment providers. NexaFetch does not receive your full payment card details through the app. Follow the privacy policy of the payment service you use.

7. Children

NexaFetch is a general-purpose utility and is not directed at children under 13. Do not use it to collect personal information from children.

8. Your choices

  • Stop submitting links at any time.
  • Clear browser site data or uninstall the app to remove local preferences and queues.
  • Delete files saved under Downloads / NexaFetch Studio from your device file manager.

9. Contact

Project: NexaFetch · Creator: John Edward Dela Cruz · Brand: CodeDev by Edward
Portfolio hub: myportfoliohub.online
Web app: nexafetch.myportfoliohub.online

10. Changes

This policy may be updated when features or hosting arrangements change. The “Last updated” date at the top will be revised when material changes are published.

See also Responsible use for copyright and acceptable-use rules.