Loading page
Loading page
This describes what the service actually records. Where a claim is made here, it is because the implementation behaves that way — the two are kept in step deliberately.
Last updated
Using this site requires no registration, no email address and no sign-in. Because there is no account, there is no user record, no history attached to you, and nothing to delete when you stop using it.
When you submit a post link, it is validated and normalized — tracking parameters removed, host standardized — and one row is written containing: the normalized link, the post id, whether the lookup succeeded, an error category if it did not, how long it took, which media provider answered, and a short summary of what was found (how many files, and their qualities).
The normalized link is erased automatically 24 hours after it is written. What remains is an anonymous row used for reliability statistics and nothing else. The row also carries a keyed hash of the link, which lets us recognise a repeat lookup without holding the link itself; a hash cannot be turned back into a URL.
We do not record who submitted a link. There is no field for it.
We do not store IP addresses in readable form. Rate limiting needs to distinguish one visitor from another, so the address is passed through a keyed hash and only that result is kept, together with a request count and a time window. The hash is not reversible and is not usable to identify you.
These rate-limit records are removed once they are old enough to be irrelevant, within twenty-four hours.
Our web server also keeps ordinary access logs for a short period for security and diagnostics, as essentially every web server does. Application logs are written deliberately narrow: a request id, the outcome, a duration and an error category. Submitted URLs are not written to them.
The site itself sets no cookies. There is no session cookie, no login and no preference cookie, because there is nothing to remember about you between visits.
Google Analytics, described in the next section, does set cookies — typically _ga and _ga_<id>. They hold a randomly generated identifier that lets Google tell a returning browser from a new one so visit counts are not inflated. They are first-party cookies, they contain nothing you have typed, and they expire after two years unless you clear them sooner.
You can block them with any browser setting or extension that blocks cookies or trackers. Nothing on this site depends on them: the downloader works identically with analytics blocked, and we would rather lose the measurement than break the tool.
Your browser may also keep ordinary cached copies of pages and images. That is a browser function, not something we set or can read.
We count events — a lookup started, a lookup succeeded, a lookup failed and why — as plain totals with no request context attached. There is no visitor identifier, no session, and nothing that could be traced to a person or a device.
We also use Google Analytics 4 (measurement idG-DS759BF758) to understand how many people use the site and which pages they arrive on. This is a third-party service: when you load a page, your browser fetches a script from Google and sends measurement data to Google's servers.
What Google receives in that process includes your IP address, the page you are on, the page that referred you, and general information about your browser and device. Google Analytics 4 does not log or store the IP address, but it does use it to derive an approximate location — typically city level — before discarding it. Google acts as our data processor for this, and its own terms govern what it may do with the data.
What we never send to Google: the links you paste, the posts you look up, or anything you type into the contact form. Those stay within the boundaries described above. The events we record are limited to actions like a lookup starting, succeeding or failing, and which quality was chosen.
If you would rather not be measured, blocking cookies or using a tracker-blocking extension stops it, and Google publishes a browser opt-out add-on. The site works exactly the same either way.
When you tap a download button the file is streamed through our server rather than fetched by your browser from the platform. We do this because a browser ignores a filename on a cross-origin link, so a direct link opens the video in a tab instead of saving it — and because the MP3, M4A and GIF options do not exist upstream at all and have to be produced here.
Nothing is stored in the process. The bytes are passed from the platform to you as they arrive; no copy is written to disk, and nothing about the file is recorded beyond the ordinary request log described above.
One consequence worth stating plainly: because the request goes through us, the platform's content network sees our server rather than your device, so your IP address is not disclosed to it by the download. Our server does see the request, and the same hashing and retention rules in this policy apply to it.
If you use the contact form, we store the name, email address, subject and message you provide, so that we can reply. A keyed hash of your IP address is stored alongside it purely to limit spam.
Those messages are kept while the matter is open and for a reasonable period afterwards, then deleted. They are not added to any mailing list, and they are not used for anything other than answering you.
No advertising network is integrated at the time of writing. Space is reserved in the layout for future advertising; while none is running, nothing is loaded into it and no third-party script executes.
When advertising is introduced, this section will say which provider is used and what it collects, before it is switched on.
Nobody. We do not sell, rent or share what we store. The only outside party involved in normal operation is the platform itself: our server asks it which files a post contains, and then streams those files from it to you.
This is a general-purpose utility and is not directed at children. We do not knowingly collect information from anyone, which includes children, because we collect almost nothing from anyone.
Data protection law gives you rights of access, correction and erasure over personal data about you. In practice we hold almost none: without an account, and with links erased on a timer and addresses stored only as hashes, there is usually nothing to retrieve.
The exception is a message you have sent through the contact form. Ask at support@ssstwitter.site and we will send you a copy or delete it.
If this policy changes, the date at the top changes with it. Changes that affect what is collected will be made here before they take effect in the service.