Privacy Policy

LTX Publishing Hub (“LTX,” “we,” “the application”) is a private video production and publishing tool for authorized operators. This policy explains how LTX accesses, uses, stores and shares information when a user connects Google or YouTube accounts and uses publishing features. This informational website is hosted at ltx.sonet-usa.com; the production/editorial workspace is not publicly hosted here.

1. Services and permissions

LTX uses YouTube API Services. When a user expressly authorizes a YouTube account via Google OAuth, the application requests permissions corresponding to:

• youtube.upload: uploading operator-selected videos and their associated publishing metadata to the authorized YouTube channel.
• youtube.readonly: reading connected channel identity and relevant video details (such as video ID, title, upload/publication status and visibility) to verify the destination and display publication results.

Where an authorized operator enables Google Drive transport, LTX may separately request drive.file access to create and manage files created by the application. This is used to upload an operator-supplied video to Google Drive as temporary delivery media for an Instagram publishing workflow. It does not grant LTX unrestricted access to all Drive files.

2. Information processed

• Connected platform account identifiers and display names, such as YouTube channel ID and channel title.
• Google OAuth access and refresh tokens, scope grants and expiration information, used to maintain authorized connections.
• Operator-selected videos, titles, descriptions, tags, schedules, version/approval information and publication records, including returned video IDs, status and URLs.
• Information directly submitted by an operator as part of editorial production and troubleshooting.

LTX does not ask for or store Google account passwords.

3. Why the information is used

Information is used to connect the intended channel, upload videos when initiated and approved by an operator, check publishing results, display the state of publication jobs, troubleshoot failures, and maintain editorial/publishing history. Google user data is not used for advertising, behavioral profiling, or sale to data brokers.

4. Storage and security

The existing LTX application keeps connected-account details and encrypted OAuth credentials in its access-restricted local production database. Locally processed video assets and publication records are retained for workflow, operational and audit purposes. Connections with Google APIs use encrypted HTTPS transport. No internet-facing public upload or administrative interface is provided by this informational website.

Like any software system, these measures reduce risk but cannot guarantee absolute security.

5. Sharing with service providers

Google and YouTube receive the content and metadata that an authorized operator explicitly uploads or requests through their APIs. When the Instagram delivery workflow is used, an operator-supplied video may be temporarily uploaded to Google Drive and made reachable by a link so Meta can retrieve it; the application attempts to delete the temporary Drive file after ingestion. Where the operator separately selects other platforms, operator-supplied media and captions may be transmitted to those publishing services, including Meta or Buffer. LTX does not sell or transfer Google account profile data or OAuth tokens to those platforms for advertising.

Cloudflare Pages hosts this informational website and may process standard connection information necessary to serve the pages. This website contains no third-party advertising scripts or behavioral analytics scripts.

6. Retention and deletion

Publication records and local media may be retained for editorial and troubleshooting purposes. Temporary delivery copies are intended to be removed after the receiving platform has processed them, but deletion may be delayed if an external service or cleanup request fails. Permanent archival of final masters is a separate workflow and must not be confused with temporary delivery copies.

Authorized operators can disconnect Google/YouTube access through application controls where available, or contact us to request disconnection and deletion of locally stored account data. Some publication/audit records may need to be retained where operationally or legally necessary; we will explain any such limitation in a response to a request.

Users can also revoke LTX’s Google account access at any time through Google Account connections. Revocation stops future authorized API access, but does not automatically delete files already published on YouTube or all existing local records. Contact us for a separate deletion request.

7. Third-party policies

Use of YouTube and Google services is additionally governed by the YouTube Terms of Service, Google Privacy Policy, and applicable Google API Services policies. LTX is not endorsed by or affiliated with Google or YouTube.

8. Changes and contact

This policy may be updated to reflect changes to the application and applicable rules. The current version and effective date will be posted here. Material changes to how Google user data is used may require renewed user notice or consent. For questions, access revocation, or deletion requests, contact mr.cahi@gmail.com.