Scope and operator
This policy covers the shengli-gsc application, described as Shengli Pak Search and Video Management, operated by Shengli Pak (Suzhou) Co., Ltd. It covers the connected search and video administration workflow. It is not a general policy for all sales enquiries or all activity on the company’s website.
Privacy contact: [email protected].
Information we access and use
Google Search Console provides the website properties and permission levels available to the connected account; search queries, page URLs, countries, devices and dates; clicks, impressions, click-through rates and average positions; and available indexing, crawling and sitemap information. We use these records to produce search performance reports, investigate website visibility and plan content improvements. This connection uses read-only Search Console access.
The application uses YouTube API Services. For an authorized channel, it can access channel identifiers and names, video identifiers and metadata, publication and processing status, caption and playlist information, and available video statistics. We use this information to check the target channel, prevent duplicate uploads, verify publishing results and review content performance. Public channel and video information may also be used for relevant market research.
Staff supply source videos, thumbnails, captions and proposed titles, descriptions and tags. The application sends approved content and changes to YouTube. Published material is visible according to its YouTube visibility setting.
OAuth access and refresh tokens allow the software to make authorized requests without repeated sign-in. We also keep request timestamps, error categories, upload progress and operation records for troubleshooting. The application does not ask staff to provide their Google password and does not request Gmail access for these functions.
Access and service providers
Authorized administrators and staff can review the records needed for their assigned work. Google receives requests needed to provide Search Console and YouTube functionality. Administrative work may use software assistants, including OpenAI Codex, to inspect relevant reports and prepare content. Report excerpts and approved working material may therefore be processed by those tools under the operator’s account settings. OAuth secrets must not be included in prompts or public reports.
Google API data is used to provide these specific operational functions, not sold, used for personalized advertising or supplied by us as a general-purpose model training dataset. Shengli Pak’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 where applicable.
Storage and protection
Credentials and working records are stored in the administrator-controlled project environment. Credential files are separate from public website content. Access restrictions and redaction are used to reduce accidental disclosure. Authorized software assistants may process selected records outside the local device; this workflow should not be understood as exclusively local storage. We do not claim that every stored file is encrypted or that access risks can be eliminated.
Retention and removal
Search Console exports and reports are retained for up to 12 months, then deleted or de-identified unless a shorter period is requested. Tokens are retained only while the connection is needed. Retention reviews and deletion requests are handled by the administrator, assisted by local inventory and deletion tools.
YouTube API metadata is refreshed or removed within 30 days. We do not rely on indefinite archival copies. Requested deletion of stored YouTube user data is completed within 7 days. Revocation through Google settings results in removal of associated API data as soon as possible and within 30 days. The administrator checks copies in reports and backups under our control as part of removal. Records processed by external software assistants are also subject to the provider’s account controls; contact us for help identifying and removing project copies.
Company-supplied original media is managed separately from API-retrieved data. Removing our stored records does not delete a video from YouTube; use YouTube Studio to manage published videos.
Your choices
Disconnect the application through Google account permissions. To request deletion of local records or ask a privacy question, email the privacy contact and identify the relevant property or channel. Do not send passwords or tokens. We may verify your authority before processing a request.
Google’s processing is described in the Google Privacy Policy. Embedded YouTube players may collect device and playback information and use cookies under Google’s policies.
Updates
We will update the published policy when the workflow changes. A materially different use of connected account data requires notice and any additional consent required before that use starts.