Privacy Policy

JingShen (Nguyễn Văn Linh) operates jingshen.cloud and the personal JingShen Studio workspace. This notice covers that website and its connected-channel features, including the owner-operated local installation. Other services you choose to use have their own privacy terms.

The app processes the information needed for the feature you choose. It does not obtain access to your entire Google or Meta account simply because you connect a channel.

• Creative content: briefs, prompts, scripts, reference images, uploaded or generated video, edits, captions and your publishing choices.
• Connection data: channel/Page/account identifiers and names, granted capabilities, encrypted authorization tokens, connection dates and token-health or expiry information.
• Publishing records: the selected asset, title/caption, destination, upload progress, returned video/post identifiers and links, processing status, timestamps and safe error messages.
• Website use: essential session or anti-abuse cookies, interface preferences and technical request information. A contact message includes the name, reply details, message and browser information you submit.
• Public AI assistant: your submitted question is sent to the configured AI service with the public information needed to answer it. Do not submit confidential or sensitive personal information to that assistant.

JingShen Studio uses YouTube API Services. The current integration requests youtube.upload to upload a video you choose, and youtube.readonly to identify your authorized channel and check uploaded video status. These permissions do not include Gmail, Google Drive or private messages.

The app sends the selected video file, title, description, privacy choice, audience setting and synthetic-content disclosure to YouTube after you confirm. It saves channel identity and upload/status records to show the connection, recover interrupted work and display the outcome. YouTube may apply its own restrictions.

Google API data is used for these user-facing connection and publishing features, not sold, used for targeted advertising or used to train AI models. JingShen’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

The Meta integration reads Pages you authorize and their linked professional Instagram identity, checks permissions and publishes content you approve. The configured permissions are pages_show_list, pages_read_engagement, pages_manage_posts, instagram_basic and instagram_content_publish. No inbox or advertising permissions are requested by this integration.

Page tokens are encrypted when saved. During long-lived-token setup, the App Secret and valid User Token are sent through the JingShen server to Meta for the exchange; this form does not retain those two inputs. A token without a fixed expiry can still lose permission or reach a separate data-access deadline.

Publishing sends the selected media and approved text to the platform you choose. Its visibility depends on your selection and the platform’s rules. A media-delivery link may be used to let that platform retrieve the selected file; do not share delivery links with others.

AI features send the brief and materials selected for that task through the filmmaking backend to the configured provider. The current social-caption workflow uses your draft context and instructions; it does not automatically send Google/Meta tokens or your channel’s API history to the AI model. Check the chosen provider and its terms before submitting personal information.

The hosting and AI services used for a feature may process information outside your country under their own terms. The operator may access stored information when needed to operate the service, provide support you request, investigate security issues or comply with applicable law. JingShen does not sell connected-account data or use it for advertising.

The active installation stores workspace content, media and publishing history on its server or local machine. Local and hosted installations are separate; connecting a channel locally does not automatically copy that connection to the hosted website.

Saved social tokens and saved Google client secrets are encrypted at rest. The app does not claim that all creative files or metadata are encrypted at rest. Server-side integrations keep provider credentials out of public API responses; authentication and same-origin checks protect private actions. No system can guarantee absolute security.

The app uses cookies and browser storage for sign-in, abuse prevention and interface state. These information pages contain no advertising or tracking SDK. Following an external link opens a third-party service that applies its own policies.

Your own drafts, media, captions and local action history are separate from YouTube API data. The app attempts to refresh channel identity and video status after seven days and removes API metadata that has not been refreshed within 30 days. A definitive Google grant failure blocks use immediately; related YouTube data is removed after seven days without a new grant. Temporary network failures do not count as revocation.

In Channels, the YouTube data control removes saved channel identity, video identifiers/status, upload-session data and connection credentials from this installation, and immediately attempts to revoke the Google grant. An encrypted token may remain solely for bounded revocation retries for up to six days. The UI distinguishes Google-confirmed revocation from a pending or unconfirmed result. Your own films, drafts and a non-API action/deduplication record remain; this never deletes videos on YouTube. The separate local-only disconnect removes the local YouTube connection and API metadata without revoking Google access. Meta disconnection removes the connection, not past publishing records or its provider grant.

Automatic checks run while this installation’s server is running. When it restarts, expired data is hidden from responses and maintenance removes it; a powered-off local machine cannot perform scheduled deletion. Local and hosted installations must be handled separately. You can also revoke access directly in your Google Account or Facebook business-integration settings.

For removal of your own media, drafts, remaining action history or Meta records, email the operator. Identify the channel and installation without sending credentials. The operator verifies your authority and handles authorized YouTube-data deletion requests within seven days. Backups, if maintained, must also be included when completing a removal request; the automatic control covers the active installation, not independent backup copies.

Contact the operator with access, correction, deletion or privacy questions. The private workspace is not offered as a service for children. If you believe a child’s personal information has been submitted, contact the operator for review and removal.

This notice will be updated when data practices change. A new purpose for connected-account data requires an updated disclosure and any additional consent required by the provider or applicable law. The dated version identifies the notice being reviewed.