Privacy Policy

1. Service overview

LingoSend translates titles and descriptions for channels that users connect and applies the result to videos selected by the user.

This app helps creators translate and publish localized titles and descriptions for videos they own or manage.

2. Information we collect

• Account information: email address, display name, legal name, phone number, approval status, and sign-in or registration records
• Registration details: the YouTube channel name entered by the user, approval or suspension records, and notice-display status
• Settings: title and description processing mode (Normal or Slow), quality option (Default or Advanced translation), source language, target languages and run options. Advanced translation requires active paid annual or lifetime access. Lyrics SRT and desktop AI provider and model settings remain separate.
• API keys: no user API key is needed for title and description translation. Lyrics SRT and desktop user API keys and provider settings remain separate.
• Google/YouTube information: OAuth tokens, connected channel ID, channel name, and thumbnail
• Job information: video links or IDs, translation status, success or failure logs, error reasons and account-level daily video-task usage records
• Historical web Lyrics SRT information: audio and TXT submitted before the desktop transition, alignment model, job status, error reason, and SRT output. Current desktop inputs and results remain on the PC; see the desktop supplement below.
• Payment, refund, and membership data: internal order number, Latpeed payment identifier, payer email, product and SKU, amount, paid cycle and access period, payment/cancellation/refund status and time, webhook verification, and entitlement grant or revocation records
• Refund-support data: account email, product, Latpeed order number, payment time, request reason, and handling record
• Payment method information: the app does not directly collect or store card numbers, bank account numbers, or payment passwords.
• Security and operations logs: access time, IP address, and audit records used by the administrator
• Cookies and similar technologies: a secure session cookie and CSRF protection cookie for login and security, plus browser storage for interface preferences. These are not used for advertising or cross-site tracking.
• Playlist Studio outcome reports: to understand service usage and failures, we store the job identifier linked to the signed-in account, completion or failure/cancellation result, authorization source, and receipt time. Supported app versions also report app version, render stage, elapsed time, a predefined error category, and render engine. These reports do not contain filenames, paths, audio, lyrics, finished videos, or raw error messages.
• Optional Google sign-in: we use your Google account identifier, verified email and display name to authenticate and link your account. The identifier is stored with your membership. Google sign-in access and refresh tokens are not stored. Encrypted temporary login proofs are valid for ten minutes and deleted on use, cancellation or cleanup during a subsequent login request. YouTube channel authorization is separate; signing in does not grant channel access.

3. Google user data

The YouTube Data API is used only after the user approves a YouTube channel connection with Google OAuth. The app reads connected-channel video information and updates selected title and description translations only after the user starts a job.

Optional Google sign-in: we use your Google account identifier, verified email and display name to authenticate and link your account. The identifier is stored with your membership. Google sign-in access and refresh tokens are not stored. Encrypted temporary login proofs are valid for ten minutes and deleted on use, cancellation or cleanup during a subsequent login request. YouTube channel authorization is separate; signing in does not grant channel access.

The app does not delete YouTube videos, manage comments, edit captions, or use Google data for advertising.

4. Information sent to AI providers

When you start title and description translation, the selected video's title, description, selected languages and translation guidance are sent to OpenAI using LingoSend's service credential. Google sign-in passwords and Google OAuth tokens are not sent to OpenAI. Lyrics SRT and desktop translation keep their existing selected providers and user API keys. When you select Batch, the same titles, descriptions and translation requests are uploaded as OpenAI Batch files. Encrypted local source and responses are cleared when the job ends; if acceptance remains uncertain, source content is scrubbed after 25 hours while reconciliation identifiers remain. We record usage from confirmed remote results before requesting file deletion and retry temporary cleanup failures. OpenAI Batch input/output files have a default 30-day expiration policy. Cleanup and usage receipts contain no source text, OAuth tokens or API keys.

5. Retention and protection

• OAuth tokens and API keys are encrypted at rest.
• The service uses HTTPS.
• YouTube API data is refreshed when the user starts a translation job.
• Stored YouTube API data and channel authorization are revalidated within 30 days; connections and related data that cannot be refreshed are deleted.
• Operational logs, job summaries, and translation cache entries are used for troubleshooting, security review, and user support.
• Stored connection data and OAuth tokens are deleted when the user requests account or stored-data deletion.
• Historical web Lyrics inputs are deleted after processing, and results keep their original retention period (24 hours by default). This period does not apply to current desktop output, which users manage on their PC.
• Payment, refund, and contract records may be retained for the period required by applicable e-commerce law and are securely deleted after the retention duty ends.

6. Sharing

The app does not sell Google user data or share it with advertising networks, data brokers or unnecessary third parties. Title and description translation uses Google APIs and OpenAI; hosting and security infrastructure support service operation. Lyrics SRT and desktop translation retain the user's selected AI provider. Latpeed and its payment providers process checkout; the app uses the minimum data needed for activation, expiry and refunds. Kakao's privacy policy applies to Open Chat; send account, payment and refund details by email instead.

7. Google API Services User Data Policy

This API Client uses YouTube API Services. Use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including Limited Use requirements. The Google Privacy Policy also applies.

Optional Google sign-in: we use your Google account identifier, verified email and display name to authenticate and link your account. The identifier is stored with your membership. Google sign-in access and refresh tokens are not stored. Encrypted temporary login proofs are valid for ten minutes and deleted on use, cancellation or cleanup during a subsequent login request. YouTube channel authorization is separate; signing in does not grant channel access.

8. User rights and deletion requests

When a user disconnects Google in the app, LingoSend immediately requests token revocation and deletes connected-channel data, YouTube API job records, and translation caches. This does not change videos or metadata stored by YouTube. Access can also be revoked through the Google Account connections page. Request account or additional data deletion at admin@plpl.co.kr.

9. Contact

For privacy, data deletion, Google OAuth, or service questions: admin@plpl.co.kr or open chat

10. Lyrics SRT desktop supplement (2026-09-29)

The desktop app aligns audio and saves SRT files on your PC. Source audio, lyrics, file paths and generated SRT files are not sent to LingoSend. If you select translation, the lyrics and selected languages are sent to the chosen AI provider. API keys entered in the app authenticate those requests and are stored on the PC with Windows user-account protection.

For connection and access checks, we store an account-linked random installation identifier, a hash of the connection request's IP address, hashed login tokens and their expiry times, and job identifiers, input-verification hashes, execution approvals and completion, failure or cancellation results. Verification hashes, rather than input content, identify repeated attempts.

Results and history stored on your PC are not subject to the web service's 24-hour download period and are not automatically removed when you uninstall the app. You can delete them yourself. Resetting credentials removes local sign-in information and the current account's API keys, while preserving source files and subtitles.

11. Optional Kakao sign-in (2026-10-03)

When you register with Kakao, we associate its app-specific account identifier, verified email and nickname with your member account. The identifier is deleted when the account is deleted or a verified Kakao unlink notification is received. Matching emails do not automatically merge existing accounts or access passes. Kakao sign-in access and refresh tokens are not stored.

Encrypted temporary sign-in proofs are valid for up to ten minutes and are removed on use, cancellation or subsequent sign-in cleanup. Hashed IP addresses and request counts limit excessive sign-in requests for ten minutes and are cleaned up on subsequent requests. Kakao sign-in is separate from YouTube authorization and payment. We do not access KakaoTalk messages or friends.

Account information needed for Kakao registration and sign-in is stored on the Render Services, Inc. production server in Oregon, United States, for service operation. The account retention and deletion rules in this policy apply. Data-center privacy contact: privacy@render.com, https://render.com/privacy. For LingoSend account or access-pass questions, use the service contact below.