getssdl.com processes only the information needed to complete download requests, protect the service, diagnose errors, and handle sponsor orders. Submitted links reach the self-hosted processor and source platform, but media files are not kept as a permanent library.
We follow a data-minimisation approach: no source-platform password is requested, unrelated information is not intentionally collected, and operational or business records are retained only when reasonably needed for operations, security, or law.
This page is reviewed when product data flows, processing components, or contact details change. People may contact [email protected] about access, correction, or deletion of information they submitted.
What data can a download request create?
A request can contain the public media URL, selected quality or audio mode, a server-issued time value, a request signature, and network data needed to communicate, such as IP address, browser information, and time. Limited status and diagnostic details may be logged when an error occurs. The service does not ask for source-platform usernames, passwords, or private cookies, and users should avoid unnecessary personal parameters in shared URLs.
Why is that information processed?
The link and format identify the platform, processor, and requested file. Time and signature values reduce direct scripted abuse of the endpoint. IP and frequency data support rate limiting and security, while error details help diagnose extraction failures and outages. Sponsor website, description, email, amount, and duration are used for review, payment reconciliation, and contact. Information is not repurposed for unrelated profiling or sold to data brokers.
Who can receive data?
A media URL must reach the self-hosted Cobalt or yt-dlp service, which then contacts the source platform to read public media. Google Analytics may receive ordinary visit and interaction data for aggregate traffic reporting. A configured mail service sends sponsor notifications. Submitted information is not intentionally disclosed elsewhere except to provide the service, protect it, meet a legal obligation, or act with the user’s permission.
How long are files and logs kept?
Direct downloads are normally streamed. Jobs that merge or convert media may create a temporary file that is removed after the response or failure. Operational logs remain only as long as reasonably necessary for security, operations, and troubleshooting; sponsor orders and payment records may remain longer for business or legal reasons. Retention can vary with deployment and law, but downloaded content is not organised into a searchable permanent archive.
What can a user request?
A person may email [email protected] to ask whether the site holds information they submitted and request reasonable access, correction, or deletion. Identity related to an order or email may need verification to prevent abuse. Information required for law, security investigations, payment records, or dispute handling may not be removed immediately. Stopping submissions prevents new processing, but a network request already sent to a source platform cannot be recalled.
“We only collect personal data we actually need for our specified purposes.”