Legal

Privacy Policy

The short version: SSAVEX has no accounts, asks for nothing personal, and works from a URL alone. This page explains exactly what is collected, what is never collected, and the choices you have.

Overview

This policy describes how SSAVEX (“the service”) handles information when you use the website. The service is intentionally minimal: there are no accounts, no sign-up flows and no profiles, so the amount of data that exists about you is small by design rather than by promise. The sections below describe each category plainly, without burying anything in legalese.

If anything here is unclear, the contact address at the bottom answers privacy questions the same way it answers everything else — directly, from a person.

What SSAVEX does not collect

There is no registration, so no email addresses, names or passwords are ever collected. There is no upload feature, so no personal files. The service does not build user profiles, does not sell data, does not share data with data brokers, and does not fingerprint browsers for tracking across other sites. Downloads happen straight from the page you are on — they are not attributed to an identity because no identity exists.

Server logs

Like every website, SSAVEX receives standard technical information with each request: your IP address, the time of the request, the URL requested, the user agent of your browser and the referring page. This is used to operate the service — delivering pages, applying rate limits against abuse, and diagnosing errors — and is kept only as long as operationally necessary. Logs are not used to build a profile of you, and IP addresses in logs are not correlated with anything else because there is nothing else to correlate them with.

Post metadata cache

To make the service fast, SSAVEX caches public metadata about posts (video qualities, image addresses, display names) for a short period after it is fetched from the platform's public embed interface. This cache contains information about posts — which are already public — and nothing about the people requesting them. Cached entries expire automatically and are not shared with anyone.

Analytics

The service may use Google Analytics 4 to understand aggregate usage: which pages are visited, which downloads are started, and coarse technical context such as device type and country. When enabled, IP addresses are anonymized at collection time, and no cross-site tracking identifiers are used. You can refuse analytics tracking entirely with any standard cookie-blocking setting or browser extension — the service functions identically without it.

Events sent to analytics are coarse by design: “a download started”, “the result page rendered”. They contain no post URLs, no account handles and nothing that identifies an individual person.

Advertising

If advertising is enabled on the service in the future, ads are served by third-party advertising networks (such as Google AdSense) which may use cookies or similar technologies to show you more relevant advertising. You can control or opt out of personalized advertising through the network provider's own settings (for Google, via Google Ads Settings) and through your browser settings. Ad units on SSAVEX are always labelled and are never placed over download buttons or disguised as site functionality.

Your choices

You can browse the service with JavaScript-based analytics blocked and lose nothing. You can use the URL trick without ever touching the paste box, which means nothing you paste is stored anywhere. There is no account to delete because there is no account. If you believe any information about you is held by the service and want it addressed, the contact address below is the way to ask.

Changes to this policy

If this policy changes materially, the updated version will be posted on this page with the changes described plainly. The policy will not be changed in ways that retroactively invent rights over data the service never collected.

Contact

Privacy questions and requests: support@ssavex.com. For copyright matters, use the process on the DMCA page.