Terms, privacy, support, acceptable use, and retention for Videvra Restore.

Videvra Restore is an experimental video-processing service. By uploading a file or submitting a job, you confirm that you have the right to use the material and that your use is lawful.

The service is provided on an “as is” and “as available” basis. Outputs may contain artefacts, temporal instability, colour shifts, incorrect restoration, or other defects. We do not promise historical accuracy, broadcast suitability, or fitness for any particular purpose.

You are responsible for the source material you upload, the rights you have to process it, and what you do with the output. Do not rely on the beta as your only copy of important footage. Download and back up results you want to keep.

We may suspend, rate-limit, reject, or delete jobs that threaten stability, violate these terms, or create legal, copyright, or abuse risk. We may also change, pause, or withdraw the beta at any time.

To run the beta, the service processes uploaded video files, generated outputs, job metadata, queue state, runtime metrics, and basic request logs. Depending on the deployment, those logs may include IP address, browser/user-agent information, timestamps, and error details.

We use this information to run the service, diagnose failures, enforce limits, investigate abuse, and improve reliability. The beta is not designed as a private archive. Only upload material you are comfortable processing through an experimental hosted workflow.

Operational run analytics may be kept briefly to understand which presets are used, whether jobs complete successfully, and what runtime characteristics they show. For this beta, IP-linked run analytics are intended to be redacted after a short period and then deleted on a fixed cleanup schedule.

We do not intentionally sell uploaded content or personal data. Access to uploads and outputs is limited to the operator and the infrastructure needed to run the beta, but no hosted beta can promise perfect security.

If your footage includes personal data, sensitive material, or third-party content, you are responsible for making sure you have a lawful basis to upload it and that using the service is appropriate for that material.

You must not use the beta to upload, process, or distribute material that is illegal, abusive, deceptive, or that you do not have the right to use.

• Do not upload copyrighted or confidential material unless you are authorised to process it.
• Do not use the service to harass, defame, impersonate, exploit, or deceive other people.
• Do not upload malware, malformed files intended to break the service, or workloads designed to exhaust compute, storage, or bandwidth.
• Do not attempt to infer, expose, or access other users' uploads, outputs, or metadata.
• Do not attempt to bypass rate limits, queue controls, preset caps, or administrative restrictions.
• Do not use the beta where a failed, delayed, or inaccurate output could create a high-risk safety, legal, medical, or compliance outcome.

Violations may result in immediate job cancellation, deletion of uploaded material or outputs, rate limits, suspension, or a permanent block from the beta.

For help, deletion requests, copyright complaints, or takedown questions, email [email protected].

Please include the job reference, the page URL or file name if available, and a short description of the issue or request. That helps us find the right run quickly and respond without guesswork.

We will make reasonable efforts to review support and takedown requests promptly, but immediate deletion from every system is not guaranteed. Some operational copies, logs, or backups may persist for a period if needed for service reliability or incident analysis.

If you need a formal copyright notice, include enough information for us to identify the material, the basis for the request, and how you want the matter handled.

Uploads, processed outputs, manifests, queue records, and run-level operational analytics are kept only as long as the beta needs them for operation, debugging, abuse review, or manual cleanup. There is no guarantee that files will remain available for any fixed period.

In practice, uploads and outputs may be removed during routine cleanup, storage pressure, incident response, or redeployments. Those files may disappear before the short-lived run analytics are removed. You should assume that completed jobs can disappear without much notice. If you want an output, download it promptly and keep your own copy.

For the free beta, the intended operational policy is:

• uploads, outputs, manifests, and queue records may be deleted at any time during routine cleanup or storage pressure
• run-level technical analytics may be retained briefly for service analysis and debugging
• IP-linked run analytics are intended to be redacted after about 7 days
• those run analytics are intended to be deleted after about 14 days, unless a shorter window is needed operationally
• aggregate non-identifying summaries may be kept longer for reliability and product analysis

This beta does not yet provide a guaranteed self-service deletion workflow. Deletion requests should go to [email protected]. Even when active storage is cleaned up, limited operational logs or backups may persist for a period if needed for service reliability or incident analysis.

If your material should not be stored outside your own controlled environment, do not upload it to the beta.