Security and trust
Security and privacy for subtitle files need to stay visible.
This product supports signed-in paid checkout. Public pages explain file handling, provider routing, support contacts, and policy boundaries before anyone uploads a real subtitle file.
The public trust layer is part of the product, not an afterthought.
Customers, reviewers, and searchers should be able to understand how subtitle files move through the workflow before they upload anything.
Visible file handling
The site explains temporary processing, recent-job visibility, and where subtitle files do and do not live.
Provider routing
The live path uses Google Cloud Translation by default and keeps provider changes behind explicit operational gates.
Commercial accountability
Billing, refund, privacy, and support routes stay public so the paid path is clear before checkout.
Named support routes
Support and billing issues route through support@nosme.pro and billing@nosme.pro instead of anonymous forms.
File flow
What happens between upload and export
The workflow is designed for subtitle review, not for hiding the mechanics behind a generic AI surface.
Upload and inspect
The workbench starts from a real subtitle file so cue structure, format labels, and billing context stay visible.
Translate with guardrails
Translation follows the active provider route and product limits while preserving subtitle timing and structure.
Review before release
Users preview the result before export, then move to billing or support only when they need more volume.
Billing and file handling
Trust also means keeping the commercial path legible.
Paid checkout, refund rules, file limits, and policy boundaries stay on public pages because subtitle tools still need a user-readable commercial path.
- Public pricing and policy routes stay reachable from every marketing page.
- The product does not promise a hidden permanent archive for uploaded subtitle files.
- Billing questions can escalate to billing@nosme.pro with order context.
Arabic · ASS
Course promo subtitles with style tags preserved
{\i1}يجب أن تنتقل الترجمات مع التوقيت نفسه.{\i0}
هذا ما يجعل الإطلاق متعدد اللغات ممكنًا.
Security and file-handling FAQ
These are the operational questions that matter before a creator or reviewer uploads a real subtitle file.
Do you keep uploaded subtitle files after translation?
The public workflow is positioned for transient processing and review. Files are handled for the active translation job rather than marketed as a permanent hidden archive.
Which providers touch the translated text?
The live production path uses Google Cloud Translation by default, with explicit gating around any fallback provider path. Provider routing stays visible in the product and support docs.
How do billing and support stay accountable?
Paid checkout is tied to Google sign-in, Creem billing, and public support contacts so the commercial path stays clear before checkout.
Where should teams send a security question?
Use support@nosme.pro for product support and billing@nosme.pro for billing issues that need account context.
Next step
Open the translator when the file flow fits.
Start in the translator first, then move to pricing only when the file workflow and support boundaries match your volume.