PRIVACY POLICY

We do not need to keep your original video.

SubChinese is designed around a simple privacy boundary: process the media to make subtitles, then keep the useful text artifacts instead of storing the original video or audio as a long-term asset.

Uploaded video and audio

Uploaded videos and extracted audio are used to process the subtitle job. They should not be kept as long-term user assets. The product direction is to delete source media after processing, because storing original media creates unnecessary privacy, copyright, storage, and bandwidth risk.

Generated text we may keep

For account history and paid membership value, we may keep the generated Chinese transcript, pinyin, translation, timing segments, SRT, ASS, filename, duration, job status, creation time, and user ID. This lets users reopen previous subtitle work without asking us to store the original video.

What users should not upload

Users should avoid uploading videos they do not have the right to process, sensitive personal recordings, confidential business content, or material that violates applicable law or platform rules.

Deletion and retention

Free accounts can have shorter history retention. Paid accounts may keep more subtitle jobs. The intended model is to delete source media quickly while keeping text-based subtitle artifacts according to account settings and plan limits.

Third-party processing

The service may use ASR and translation providers to generate transcript and translation text. Uploaded media or extracted audio may be temporarily sent to those processors for the requested job.

Account email and marketing

We keep the email address connected to your account so we can provide sign-in, account, billing, security, and service messages. We only use it for product updates or marketing when you explicitly opt in during registration or through a later account setting. Marketing messages will include an unsubscribe option.

Security direction

Production deployment should use private uploads, signed URLs, access-controlled job records, and provider credentials stored only on the server side. API keys must not be exposed in browser code.