Privacy

Overview

SwiftVid handles account and generation data so users can create, review, and iterate efficiently.

This page gives a practical explanation of data flow and user controls in everyday platform usage.

The goal is transparency: what is collected, why it is needed, and how users can manage it.

Account Data

• Account email and authentication state.
• Basic sign-in provider metadata required for session management.
• Session status signals used to keep secure access active.

Generation Data

Generation workflows rely on prompt text, selected model configuration, and output metadata.

These records are used to process requests, show status, and support retries or variations in recent history.

• Prompt and control parameters attached to each generation request.
• Task progress, completion state, and error feedback.
• Output URLs and result metadata shown in history views.

How Data Is Used

• To execute image/video generation tasks and return results.
• To power recent history, task tracking, and regeneration flows.
• To monitor stability, detect failures, and improve product reliability.
• To reduce misuse and protect platform quality for normal users.

Uploads and Reference Assets

When workflows include reference images or uploaded media, those files are processed to complete requested tasks.

File handling is tightly connected to generation workflows and output delivery.

• Uploads are associated with your generation request context.
• If an upload expires or fails, you may need to upload again.
• Use only assets you are comfortable submitting in your own workflow.

Storage and Retention

Data retention is aligned with product functionality such as recent history and download access.

Retention windows and storage behavior can evolve as infrastructure and features are improved.

• Recent-generation records are kept to support normal usage.
• Some intermediate processing artifacts may be temporary.
• Storage strategy can be adjusted for reliability and performance optimization.

Security and Abuse Prevention

SwiftVid applies practical controls to protect accounts, reduce abuse, and keep service quality stable.

Operational monitoring helps identify unusual request patterns and service risks.

• Authentication checks are enforced on protected API routes.
• Task pipelines include status validation and integrity checks.
• Operational logs may be used for troubleshooting and reliability analysis.

Third-Party Model Providers

SwiftVid integrates with multiple model vendors to provide broad generation capabilities.

Selected prompt and parameter context can be passed to provider endpoints to execute tasks.

• Provider usage depends on the model selected in your workflow.
• Availability and latency can vary by provider and workload.
• Model mappings may be updated as provider capabilities change.

User Controls and Support

Users can manage ongoing creation workflows directly from interface pages such as Recent.

If you need account-level assistance, support is available by email.

• You can manage your generation history directly in the product.
• If you need account-level support, contact help@swiftvid.art.
• SwiftVid is built and maintained by an independent developer in Shenzhen, China.