Routing and readiness
Security Notes
This product supports signed-in paid checkout. Public pages keep billing, retention, provider routing, and lawful-use boundaries explicit for customers and merchant review.
1. Default provider path
Google Cloud Translation is now the preferred live default because it is more accessible in the current operator environment while still providing a well-documented public API path for merchant review.
The provider path is part of the public promise. We do not want a gap between what the product says, how billing is explained, and which route is actually processing subtitle jobs.
Subtitle Translator is an independent subtitle workflow product. It uses Google Cloud Translation as a processor, but it is not the Google product itself and does not claim any deeper affiliation.
2. File handling
The current public workflow processes subtitle files transiently and discards them after export. Persistent storage is intentionally narrow and limited to account metadata, quota ownership, and recent job history.
- Transient processing for the current translation run
- No long-term subtitle file archive for public uploads
- Retention rules stay public before they can expand
3. Acceptable use and moderation
Subtitle Translator is a subtitle workflow product, not an uncensored content-processing surface. The public Acceptable Use Policy prohibits NSFW material, rights-violating uploads, deepfake-linked abuse, third-party ripping workflows, scraping, credential misuse, and quota bypass attempts.
Those boundaries exist for customers, providers, and payment compliance at the same time. Unsafe or deceptive use is grounds for blocking jobs, suspending access, or refusing service.
4. Budget fallback
Cheaper routing and Azure compatibility remain behind feature or credential gates. They are not part of the public promise until subtitle QA, fallback behavior, and policy wording are complete.
That keeps cost optimization from drifting ahead of the actual trust and quality guarantees exposed on the site.
5. Operational readiness
Paid checkout now routes through Creem for signed-in users. The remaining operational work is to keep webhook state, quota grants, support inboxes, and payout onboarding aligned with what the public site promises.
Public product branding stays as nosme, but paid billing operations are attached to AI Master. That relationship needs to stay explicit on the site and in the payment configuration.
- Production provider credentials verified
- Public pricing, legal, and routing copy aligned with live behavior
- Visible acceptable-use rules aligned with merchant review expectations
- Webhook state and quota grants verified against a real paid order