No account required
clipdls does not require a username, password, or profile to process a link.
Privacy details
Privacy Policy
This policy explains what clipdls receives, why each piece is needed, how temporary processing works, and what controls you have when you use the app.
Temporary files
Output files expire automatically and can be deleted from the result screen.
Abuse protection
Rate limiting uses hashed network identifiers to protect service reliability.
Information you submit
When you paste a link, clipdls receives the submitted URL and the output settings you choose, such as download, audio extraction, conversion, quality, output format, or clip start and end times.
- The app does not require an account, profile name, password, or email address for the core workflow.
- Submitted URLs are used to inspect the public source and process the output you request.
Temporary files and job records
Input and output files are created only to complete the requested job. Job records store processing state and technical details needed to run, display, expire, and clean up the result.
- Ready files expire automatically after the visible timer ends.
- Job records can include status, platform, operation, output metadata, file size, timestamps, and hashed values for abuse prevention.
- If the source is rejected before heavy processing, a file may never be created.
Rate limiting and abuse prevention
clipdls uses Redis-backed rate limiting and hashed network identifiers to prevent overload, automated abuse, and repeated expensive processing from the same source.
- Rate-limit data is used to decide whether a request is allowed, delayed, or rejected.
- Hashing helps avoid storing raw network identifiers in rate-limit keys.
Analytics
clipdls uses Google Analytics to understand page usage, device classes, navigation patterns, and performance signals. Analytics helps improve reliability, mobile experience, and SEO.
- Analytics is not used by clipdls to store the raw media URL you paste into the tool.
- Your browser, extensions, or privacy settings may limit analytics collection.
- Google Analytics processing is governed by Google's own terms and controls.
Security controls
The app uses platform allowlists, SSRF protections, strict security headers, temporary file cleanup, size and duration checks, and Redis-backed request limits to reduce exposure.
- Private, login-only, deleted, live, region-blocked, or unsupported sources may be refused before processing.
- Operational endpoints are kept out of search indexing with robots controls where appropriate.
Your controls
You control whether to submit a URL, what output options to choose, and whether to delete a ready file before automatic expiry when the result screen offers that control.
- You can avoid submitting sensitive or private links.
- You can use browser privacy settings to limit analytics persistence where supported.
- You can return to the result screen during the expiry window to manage the file when the job link is available.