Your data, explained.
Operator and launch status
Dash Social. This is a functional policy draft dated 30 October 2026. The operator must add their business/legal identity, address, jurisdiction, contact, subprocessors, international-transfer details and local retention decisions before public use.
What is stored
Accounts store your email, a salted password hash, role and creation date in the hosted MySQL database. HTTP-only session cookies hold random credentials for up to seven days. The database stores hashed session credentials. Requests store the source URL, platform, selected quality, timestamps, progress, result metadata and the storage-consent version. Guest requests use an unpredictable identifier in their private session; other guests cannot view them.
Private server files and download access
Before every request you must agree that the completed file will be stored in private server history for 30 days. It is downloadable only through the guest session or account that created the request. The operator also retains a protected operational copy. Do not submit confidential or private content. Temporary processing files are removed after a request when normal cleanup completes.
Why data is used
The service uses this data to maintain accounts, isolate request history, process the queue, prevent abuse and record the specific consent to local storage. The worker contacts the public source platform and its permitted media CDNs, exposing the worker’s public network address to those services. Hosting, database and platform operators may process network logs under their own policies. Legal bases and applicable rights must be reviewed by the operator for their jurisdiction.
Retention and deletion
The cleanup command deletes expired sessions, rate-limit records, terminal request records and their matching private server files after 30 days when run daily. Accounts remain until operator deletion. Protected operational copies and backups require operator-managed deletion; contact the operator with the request ID for a deletion request.
Cookies and advertising
Only an essential session cookie is used by default. Analytics and AdSense are off by default. The optional ad component stays inactive unless the operator configures a publisher/slot and an actual certified CMP supplies consent. No ad cookies are placed by this project in its default configuration. If ads are enabled, update this policy with the vendors, cookie purposes and withdrawal mechanism before launch.
Your choices
You can use guest mode, decline server-history consent, cancel queued or running requests, download a completed file, and sign out. Declining consent means no job is created. Guest history is tied to its browser session and is lost when you sign out, register, sign in or clear that session. No silent migration of guest history into an account occurs. Contact the operator for access, correction or deletion; ownership verification is necessary.