PRIVACY POLICY · นโยบายความเป็นส่วนตัว

How ContentOS handles data

ContentOS รู้เรื่อง is a creator workflow operated by the owner of the RuRuang / รู้เรื่อง channels. It is used for those channels, rather than as a service for the public to connect social accounts.

Last updated: 5 November 2026

1. Operator and contact

The operator is the owner of the RuRuang channels. For privacy questions, complaints, or deletion requests, contact mos.thaiof@gmail.com. Do not include passwords, access tokens, refresh tokens, or OAuth client secrets in a message.

2. Website visitors

This information website has no registration, social sign-in, upload form, advertising, embedded social feed, or third-party analytics script. Its own code does not set tracking cookies or collect form submissions. The hosting provider, Cloudflare, processes technical request information such as IP address, requested URL, browser information and security events to deliver and protect the website. See the Cloudflare Privacy Policy. Following an external link or emailing the operator is subject to the destination provider’s practices.

3. Connected platform data and purposes

Facebook: the รู้เรื่อง Page

The existing connection is restricted to the รู้เรื่อง Page, @ruruang. ContentOS uses Page identity (ID, name and link), connection permissions and token-validity information to verify the correct destination. The approved Page permissions are pages_show_list (identify the available authorized Page), pages_read_engagement (read the Page’s content and related information), and pages_manage_posts (create and manage the Page’s posts). Meta’s basic public_profile permission is also present in the grant. These permissions are used for the owner’s Page workflow, not to build profiles of viewers.

When the owner approves publishing, the video or image, caption and other required publishing fields are sent to Meta. Local publication records can contain the resulting post ID, URL, destination and publishing time. ContentOS does not provide a website feature for collecting viewers’ personal information.

YouTube: RuRuang

The verified YouTube connection is for the RuRuang channel, channel ID UC6_0_VsZJkqSKCUveyAxWrQ. ContentOS uses YouTube API Services. The granted scopes are youtube.readonly and youtube.upload.

The connection check reads the authorized channel’s ID, name, handle and channel statistics to verify the intended channel and report its status to the owner. OAuth access and refresh tokens allow the local workflow to continue accessing only the permissions granted by the owner. An OAuth client configuration is also stored locally. The upload scope is used by the local upload tool to send owner-approved videos, titles, descriptions and publishing settings to YouTube. Before sending, the tool checks the owner’s approval, final file, title and description, destination channel and AI disclosure, and guards against duplicate or uncertain attempts. This connection has not been used for a test upload. No upload or account connection takes place on this public website.

Google account data is not accessed for Gmail, Drive, contacts or unrelated Google services. The channel check requires the expected channel ID; it does not accept a different channel as a publishing destination. Google’s OAuth scopes are granted by the platform and may be broader than the checks applied by ContentOS.

TikTok: planned, not connected

TikTok integration is under preparation. ContentOS currently has no TikTok API connection and does not collect TikTok account data through that API. Any future connection, data categories and permissions must be disclosed and authorized before use, and depend on TikTok’s applicable app review and product requirements. This policy does not claim approval for TikTok publishing.

4. Storage, access and sharing

Connection credentials are stored outside the public website and source repository in local files readable and writable only by the operating-system user (file mode 0600, inside a private configuration directory). Local project files may include connection reports and publication records with channel or Page identifiers, permission names, verification times, publication IDs and links. These are separate from the static website and are not uploaded with it.

The operator accesses these records for the channel workflow, troubleshooting and security. Platform requests are sent over HTTPS to the relevant platform. Publishing necessarily sends the approved content and its metadata to the selected platform, where that platform’s policies and the selected audience settings apply. The static hosting provider does not receive local OAuth credentials as part of this website.

ContentOS does not sell platform data, share it with advertising networks or data brokers, or use it for personalized advertising. Data obtained from connected platform APIs is not used to train or improve generalized AI or machine-learning models. The owner may use authorized automation assistants to run local tools and inspect non-secret connection status, channel metadata and publication records for the disclosed workflow. Content creation may use AI with separately supplied materials; that does not authorize reuse of connected-account API data for unrelated purposes.

ContentOS complies with the Google API Services User Data Policy, including its Limited Use requirements. Data transfers are limited to the disclosed channel features with the owner’s permission, security, or applicable legal obligations. See also the Google Privacy Policy and Meta Privacy Policy.

5. Retention, revocation and deletion

Connection credentials are retained locally while the owner keeps the connection enabled; they can stop working when revoked, expired or restricted by the platform. Local connection and publication records support the owner’s publishing workflow. Apart from authorization tokens needed for an active, consented connection, stored Google/YouTube API data, including channel metadata and API-derived upload results, is refreshed or removed within 30 calendar days. Marking a record as historical does not extend that limit. Connection records do not retain channel statistics. Authorization tokens may be kept while necessary for the active, consented connection. The operator checks stored Google data and authorization manually at least every 30 days, and removes data associated with revoked or invalid authorization promptly, no later than 30 calendar days after revocation. There is no automated retention scheduler or public deletion endpoint.

The owner can revoke Google access through Google Account third-party connections, and Meta access through Facebook Business Integrations. Revoking platform access and deleting local files are separate steps. To request deletion of local credentials, downloaded API data or connection reports, email the operator at mos.thaiof@gmail.com with the platform and channel/Page concerned. The operator verifies control of the affected account and handles removal manually. Requests to remove stored Google/YouTube user data are completed promptly and within seven calendar days of receipt. This is a manual responsibility of the operator, rather than an automated website feature.

Deleting local ContentOS data does not delete a post or video already stored by Facebook or YouTube. Manage that content in the platform’s own tools. See the detailed revocation and deletion instructions.

6. Changes

The date above identifies this policy version. A new use of connected-account data or a new platform connection requires an updated disclosure and the owner’s consent before that use begins.