Privacy policy
Effective and last updated: November 5, 2026
GamerXP Studio HQ (“HQ”) is GamerXP Studio’s private workspace for studio operations, reporting and content planning. This policy explains how HQ handles information about its authorized users and connected accounts.
Email hello@gamerxpstudio.com. Identify the HQ account or connected channel concerned; do not send passwords, access tokens or private keys.
1. Information HQ processes
- Workspace accounts and activity: account details such as name and email, access permissions, sign-in/session information, security checks and operational logs.
- Information entered into HQ: projects, business contacts, opportunities, goals, financial records, drafts, files and reports supplied by authorized users.
- Connected-service information: account or channel identifiers, authorization credentials and the reports or content needed for the features a user connects. The categories used by Google integrations are explained below.
This policy covers HQ. Separate games, the public GamerXP Studio website and third-party services may have their own privacy policies.
2. Google and YouTube access
Connecting Google or YouTube uses Google’s authorization screen. Google handles your Google password; HQ receives authorization credentials, not that password. Access and refresh tokens let HQ perform authorized background updates without asking you to sign in for each report.
- Account identification: basic profile/account information made available during authorization, such as a Google account identifier, name and email, to identify or verify a connection. The YouTube connection is saved against its channel identifier and channel name.
- YouTube reporting: channel details and subscriber statistics; uploaded-video identifiers, titles, descriptions, links and publication dates; video statistics such as views, likes and comment counts; and authorized channel analytics such as daily views, subscriber gains/losses and per-video performance where returned by the selected report.
- Optional YouTube publishing: the current YouTube connection also requests upload permission. If an authorized user enables or schedules publishing in HQ, HQ can send that user’s video, title, description and publication settings to YouTube. Connecting a channel alone does not publish a video.
- Google Play reporting, when connected: Google account identifiers and read-only access to the configured app’s report files in its reporting bucket. Google’s Cloud Storage permission can cover other readable resources, but HQ’s reporting feature targets the configured bucket and app.
- Website analytics, when configured: authorized Google Analytics property reports, such as aggregate visitors, views and recorded website events. This connection uses the separately configured reporting credential and property.
HQ’s YouTube connection does not request Gmail or Google Contacts access and does not collect viewers’ personal watch histories. Reporting counts, such as the number of comments, do not mean HQ reads private messages.
3. Why HQ uses this information
HQ uses information to run the workspace, verify connections, display dashboards and comparisons, track studio goals, prepare reports, support user-directed publishing, and diagnose failed integrations or security problems. Reports and integration alerts may be sent to the workspace’s configured recipients. Authorized workspace users can view information according to their access permissions.
Google data is used for the connected features described here. We do not sell it, use it for advertising targeting, or use it to train general-purpose artificial intelligence models. Our use and transfer of Google user data follows the Google API Services User Data Policy, including its Limited Use requirements.
4. Storage, access and sharing
HQ stores connection credentials, imported measurements and workspace records on its server. Reports, exports, uploaded assets and operational backups may also contain workspace information. Access is controlled through HQ accounts and permissions; production connections use HTTPS. Credentials are not intended to appear in public pages or report emails.
Information may be processed by infrastructure and service providers needed to host HQ, store files, deliver configured emails or operate a connected feature. For publishing, the selected video and metadata are sent to YouTube. Information may also be disclosed where required by law or necessary to investigate abuse or protect security. We do not provide connected Google data to data brokers or advertising platforms.
5. Retention and deletion
Workspace information is retained while needed for its recorded business purpose. Connected Google data is retained only for the disclosed features and subject to the applicable Google and YouTube requirements. Historical authorized reporting statistics may remain useful for comparisons while the relevant authorization remains valid.
You can request access, correction, export or deletion by emailing hello@gamerxpstudio.com. We may need to verify that you control the account or channel. YouTube-data deletion requests are handled as soon as possible and within seven calendar days. Deleting data from HQ does not delete a channel, video or other information held by YouTube itself.
When we learn that YouTube authorization has been revoked or can no longer be verified, we stop using that authorization and arrange deletion of the associated YouTube API data as soon as possible and within 30 calendar days. Retention or refresh of other stored YouTube API data follows YouTube’s applicable rules. These requests are handled by the HQ operator; this policy does not describe deletion as an automatic background feature.
Removing a connection stops future synchronization for that saved connection. To ensure previously generated reports, exports or related stored data are included in a deletion request, identify them in your message. Any retention required by applicable law is limited to the information and period required and does not authorize continued use of revoked Google API data.
6. Disconnecting and revoking Google access
You can remove a saved YouTube connection through Social Accounts in HQ or ask the operator to disconnect it. You can independently revoke HQ’s authorization through your Google Account security settings. Revoking a Google application grant may affect other HQ connections that use that same grant. Disconnecting HQ does not remove content already published on YouTube.
7. Cookies, device storage and external services
HQ uses cookies and browser storage for functions such as sessions, security, authorization state and interface preferences. Your browser can restrict or clear these, but doing so can interrupt sign-in or connected workflows. This public policy page does not load advertising trackers or embedded YouTube players.
HQ uses YouTube API Services. YouTube’s own processing is described in the Google Privacy Policy; use of YouTube is also subject to the YouTube Terms of Service. Other linked services have their own terms and privacy practices.
8. Your choices and policy updates
Subject to applicable law, you may have rights to access, correct, export or delete your information and withdraw consent. Contact hello@gamerxpstudio.com to exercise these rights or raise a privacy concern. HQ is an authorized studio workspace and is not intended for children.
We will update this page when practices change. Material changes to how connected Google data is used will be disclosed before that new use, with renewed consent where required. The date at the top identifies the current version.