SaveMySave

Privacy Policy

This policy describes the free public beta. Server-side processing is necessary; the service is not an anonymity tool.

1. Scope and contact

This policy covers the SaveMySave web service and temporary file delivery. For privacy questions and requests, contact [email protected]. The source platforms and your browser/device have their own policies and controls. The service does not require a SaveMySave account.

2. Data processed

A request can involve the submitted URL, source responses, thumbnail/media data, title, available formats, job identifiers, status, timestamps and temporary file metadata. Internet connections also carry IP addresses and browser/network headers. Fields processed for a request are not necessarily retained as a permanent record. Do not submit account credentials or private access tokens.

3. Purposes

Data is used to validate the link, contact its source, prepare and deliver a permitted file, show progress and errors, enforce capacity and abuse controls, maintain the service and respond to requests. Link processing is not confined to your device: our server contacts source services, which receive its requests and apply their own rules.

4. Functional browser storage

Your explicit language choice is stored in localStorage (savemysave.language.manual and savemysave.language) and the functional savemysave_language cookie for up to one year. Appearance uses savemysave-theme in localStorage. Dismissed language suggestions use sessionStorage for the tab session. Opening a language-specific page does not replace your explicit preference.

Download recovery and cancellation controls may use sessionStorage in the same tab, including a job identifier, temporary file capability or cancellation-control secret. Treat your browser profile as private. These are not accounts or a permanent cross-device media history. You can clear site storage; this does not erase already downloaded files.

5. Temporary results and records

A prepared file normally has a fixed four-hour access window from readiness. GET, HEAD and Range requests do not renew it. Cancellation or storage pressure can shorten availability. Cleanup is scheduled; an active transfer may delay physical removal. The deadline does not promise secure erasure from every storage layer at the same instant.

Job-state metadata is used during processing, recovery and result availability and is cleaned with the job lifecycle. Aggregate operational counters retain up to 24 UTC monthly summaries and cumulative totals. Those counters do not contain submitted URLs, titles, file links or visitor identifiers. Correspondence is separate and is used to resolve the request and necessary follow-up. Provider-side records follow the relevant provider’s policy.

6. Operational measurements and protection

The service measures fixed aggregate categories such as attempts, preparation outcomes, elapsed time, byte volumes, queue state and failures. Counts are not unique people or proof that a file was saved. Browser-reported aggregates distinguish public traffic from private preview origins without treating this as automatic bot filtering.

A signed work key is valid for fifteen minutes and is kept in page memory. Short-lived request-budget entries are held in server memory; obtaining a new key does not reset shared limits. Job-control secrets and file capabilities protect operations but do not establish a person’s identity. Do not share them. Application redaction and capability-aware gateway diagnostics reduce exposure, but operational records must not be described as fully anonymous.

7. Recipients and infrastructure

The beta runs on the operator’s server infrastructure. The main public website uses Cloudflare’s HTTPS proxy and DNS. The dl file hostname uses Cloudflare DNS, while HTTPS file transfers go directly to the server, not through Cloudflare’s HTTP proxy. Cloudflare can process connection information for requests using its services. Source platforms and media hosts receive the server requests needed to fulfill a submitted link.

These services may process data in different countries under their applicable arrangements and policies. SaveMySave does not promise that every request is processed in one country. The privacy information of Cloudflare is available at https://www.cloudflare.com/privacypolicy/. Your email provider and our service mailbox also process support correspondence.

Security checks with Cloudflare Turnstile

When Turnstile protection is enabled, starting a new link check or file preparation may load Cloudflare’s security widget. Cloudflare receives connection and browser signals needed for its check. Our server validates the resulting token with Cloudflare; we do not include the submitted video URL in that validation request. The widget is not loaded just to read a page or retrieve a prepared file.

The server keeps successful admission in memory for up to ten minutes, never longer than the fifteen-minute work context. It is not a permanent identity or a guarantee that every bot is detected. Security limits remain in place. Provider-side processing is described at https://www.cloudflare.com/privacypolicy/ and https://www.cloudflare.com/turnstile-privacy-policy/.

8. Advertising, analytics and payments

Advertising, optional Google Analytics and payment integrations are disabled for this launch. There are no donation or subscription charges. Reading this policy does not opt you into future tracking. Any later activation requires updated disclosures and applicable choices before optional requests are sent.

9. Your choices and requests

You can cancel a request, clear site storage and manage your downloaded copies. Where applicable, you can request access, correction, deletion, restriction or objection and complain to the competent supervisory authority. Write to [email protected], explain the request and provide the minimum information needed to locate relevant data, such as an approximate time and job identifier. Do not send a password, cookie or active file capability. We may need to verify your connection with a record. We cannot delete source-platform records or files on your own or another person’s device.

10. Security and updates

Encryption in transit, URL validation, temporary results, access controls and bounded capacity reduce risks but do not guarantee absolute security. Never submit information you are not entitled to share. Material processing changes will be reflected in a dated policy. Essential processing is distinct from optional tracking; this document is not a blanket consent to every future use of data.

Service contact

[email protected]
Back to the downloader