Privacy
Privacy and temporary processing
Extractor is designed around short-lived processing rather than permanent media storage or user accounts.
Information used to provide the service
A request includes the submitted media URL, selected download mode and selected quality profile. Standard web-server records may also contain technical request information such as time, network address, user agent, requested path and response status.
Temporary media files
Extractor creates temporary working files while resolving and preparing a download. Completed job files are removed after delivery. Stale temporary folders are also subject to scheduled cleanup.
Browser-side history
The visible session history is maintained in the browser interface for convenience. Clearing browser storage or using a private session may remove that local history.
Third-party sources
To resolve a submitted URL, the service communicates with the source website. That source may apply its own logging, privacy policy, access rules and terms.
No user accounts
The current public interface does not require an Extractor account. Do not submit secrets, private tokens or URLs that expose confidential information.
Last updated: 27 July 2026.
Anonymous service measurement
Extractor records a small set of operational events to measure visits, accepted download jobs, cancellations, processing failures, and completed file delivery. Campaign parameters such as UTM source, medium, campaign, and term may be included when they are present in the page address.
This measurement uses no cookies and does not record the submitted media URL, media title, output filename, name, email address, or IP address in the internal measurement log. A temporary random session identifier is created in memory for the current page only. Metrics are stored in a size-limited rotating server log for operational and campaign analysis.