Privacy, stated precisely.
This policy describes the data flow of the Fetchora application itself. A deployment operator can connect external services; their policies apply to those requests.
Last updated: October 23, 2026
What you send
When you analyze a URL, that URL is sent to the Fetchora Worker. It is validated and may be sent to the source platform, an oEmbed endpoint, or the optional yt-dlp extraction service. The target can therefore see the Worker's request and network address, and the extraction host can see the source URL. Fetchora does not require an account and does not set application cookies.
What is not collected
Fetchora has no user profile, media library, analytics database, or email list. It does not store uploaded files because there are no uploads. Media is streamed and discarded. The default deployment does not enable advertising; if an operator turns it on, Google AdSense may process data under Google's own terms.
Local toolkit
Files selected in the local toolkit are read with the browser File API and written to FFmpeg.wasm memory in your tab. They are not uploaded to Fetchora. The pinned FFmpeg core is fetched from jsDelivr only when you start a job; jsDelivr receives a request for that static file but not your media. Generated downloads are Blob URLs in your browser and are revoked after use.
Server logs and security
Cloudflare may process standard request metadata as the infrastructure provider. The application does not log full URLs with query strings for downloads. Rate limiting is held in Worker isolate memory and is not a persistent record. Signed download tokens contain encrypted destinations and expire after 20 minutes.
Third parties
Source platforms receive requests when you ask Fetchora to resolve their content. Optional oEmbed endpoints receive the requested URL. If the extraction service is connected, it receives the URL and makes its own requests. If advertising is enabled, the configured Google AdSense client and its vendors may use cookies or identifiers under Google's policies. Thumbnail images are loaded from the source platform, so your browser contacts that host directly when a preview is displayed.
Retention and contact
Media is not retained. Signed tokens expire. Transient metadata exists only for the request. For privacy questions, use the contact channel configured by this deployment; if none is displayed, the operator has not published one.