Privacy Policy

Last updated: 23 October 2026

This policy explains how All video saver handles information when you visit the website, submit a video link, prepare a download or contact support. The service is operated by Shiva Shukla.

1. Information used to provide the service

When you submit a request, the service processes the video URL, your permission confirmation and information needed to manage the request. This can include a job identifier, request timestamps, processing status, error details and output file information.

A URL can contain personal information or access tokens. Submit only links you are authorised to share with the service. Do not submit passwords, private access links or confidential information.

2. Anonymous browser sessions

You do not need to create an account. The service uses an anonymous session cookie to associate requests with your browser and restrict access to their status and prepared files.

The interface may also store a request identifier in browser session storage so that it can look up a recent request after a page refresh. These identifiers are not a social media login.

Blocking or clearing browser storage can stop you from accessing an existing request. Clearing browser storage does not itself delete records already held by the server or its providers.

3. Temporary media processing

The server retrieves and temporarily stores media while preparing a requested file. Processing may create separate video, audio and merged output files. A prepared file remains available only during its download availability period.

The service uses expiry and cleanup mechanisms for temporary files. Expiry of a download link and physical deletion of a file are separate events. Cleanup can be delayed by a stopped worker, server failure or maintenance.

All video saver is not a permanent storage or backup service. Keep your own copy of any file you are entitled to retain.

4. Why information is processed

• Validate and process a submitted link.
• Queue requests and provide status updates.
• Deliver a prepared file to the requesting session.
• Apply usage limits and prevent abuse.
• Investigate errors and security incidents.
• Respond to support and rights-related requests.
• Meet applicable legal obligations.

5. Infrastructure and external services

All video saver currently runs from a computer operated by Shiva Shukla. Public access is provided through ngrok, which forwards requests to the application. Availability depends on that computer, its internet connection and the running application and worker.

The service uses Redis Cloud for its download queue. Queue records include submitted video URLs, hashed browser-session identifiers, request timestamps, processing status and result information.

Prepared media and temporary processing files are stored on the application computer. The current download process does not upload these media files into the Redis queue.

ngrok, Redis Cloud and the relevant video source platform process information needed to provide their services. This may include request metadata, network addresses and operational records. Their processing locations and retention practices depend on the providers and configured services.

Sending a message to the support address also involves the email providers used to deliver and store that correspondence.

6. Retention and deletion

Different types of information have different retention periods. Download availability, physical file deletion, queue-record removal and browser-cookie expiry are separate processes.

• Browser session: The clipnest-session cookie is configured to expire 24 hours after it is issued. You can also remove it through your browser settings.
• Prepared media: A completed file is normally available for 30 minutes after preparation finishes. New download requests for that file are rejected after its expiry.
• Physical file cleanup: While running, the worker checks temporary storage approximately every 60 seconds and attempts to remove expired files. Cleanup also runs when the worker starts and before processing a job. Server downtime, storage errors or a stopped worker can delay physical deletion.
• Unsuccessful processing: The worker attempts to remove temporary files when processing fails or is cancelled. Remaining abandoned directories are also subject to periodic cleanup.
• Queue records: Submitted URLs, hashed session identifiers, timestamps, status and processing results are stored in the Redis-backed queue. Completed and failed jobs have automatic removal settings based on an age of one hour and a count limit of 100 records in each category. These settings are not a guaranteed deletion deadline: removal is triggered by queue activity, and records can remain longer when processing stops.
• Waiting requests: Requests older than 15 minutes are rejected when checked by the relevant status or worker logic. This age check does not independently guarantee deletion of the waiting queue record at 15 minutes.
• Operational keys: Rate-limit counters expire after 60 seconds. Active-request reservation keys have a 30-minute expiry, and cancellation flags have a one-hour expiry. Shared queue bookkeeping is maintained separately.

Cancelling a request asks the service to stop queued or active processing. It is not a general deletion request. Cancelling an already completed request does not immediately erase its prepared file. The normal expiry and cleanup process still applies.

These application settings do not determine the retention of infrastructure logs, provider backups or email correspondence. Relevant records may also need to be retained for a lawful security, complaint-handling or legal purpose.

To ask about information associated with a request, contact factsshivaa@gmail.com. Include the request identifier if available, but never send your session cookie or other credentials.

7. Advertising and analytics

This policy does not grant blanket permission for future advertising or analytics tracking. If such services are introduced, their purposes, providers and relevant choices must be explained before the new processing begins. Consent controls will be provided where required.

8. Security

The service uses controls intended to limit unauthorised access and misuse. No website, network or storage system can guarantee absolute security. Avoid submitting sensitive material and report suspected security problems by email.

9. Your choices and privacy requests

You can stop using the service, cancel an active request where the interface allows it, clear browser storage, or contact the operator about access, correction, deletion or other applicable privacy rights.

Applicable rights depend on the law in force and the circumstances. To locate a record, the operator may ask for a request identifier, approximate submission time or other proportionate information. Do not send your session cookie.

10. Children’s privacy

The service is not specifically directed at children and does not ask users to submit their age. Do not submit children’s personal or private material. If you believe a child’s information has been submitted inappropriately, contact the operator so the matter can be reviewed.

11. Processing locations

Information may be processed where the operator and infrastructure providers run their services. Do not assume that all processing occurs in India. Applicable restrictions on data transfers must be considered when choosing hosting and providers.

12. Policy updates

This page will be updated when material changes are made to the service or its data practices. The date above identifies the latest revision. Additional notice or consent will be used where required.

13. Contact

Privacy contact: Shiva Shukla
Email: factsshivaa@gmail.com
Suggested subject: All video saver — Privacy request