Privacy policy

Effective 12 September 2026 · Last updated 18 October 2026

1 Who this policy is from

In this policy, "we" means Vurctube’s operator, ZXW Investment Pty Ltd. Contact: zw@vurctne.com.

This policy covers vurctube.com, the private service at mcp.vurctube.com, and enquiries sent to us. The separate self-hosted CLI is distinguished in section 8. It does not describe a publicly available cloud-localization product.

2 Data accessed and why

• Google identity: OpenID Connect subject identifier and verified email address, used to authenticate the invited owner. Your email is checked against the invite list; it is not an MCP access token.
• Authorization: Google OAuth authorization codes and tokens, used to verify the channel and make authorized requests. Google passwords are entered only at Google, never at Vurctube. Google refresh tokens are encrypted at rest on our service, not returned to your agent.
• YouTube data: channel identity and metadata, video metadata and statistics, and other supported Data API results requested by the approved client. This can include private resources available under your grant. Metadata proposals additionally retain before/after values, proposed changes, approval and execution records, and readback results. The remote pilot does not request Analytics or Reporting scopes and does not download video/audio files.
• Connection records: registered client ID, exact return address, permission, expiry, channel binding and minimal operation/quota records. These enforce access control and request limits; they are not advertising profiles.

If you contact us by email, we receive your email address, name if provided, and message content through our email provider. We use this correspondence to respond to your enquiry and discuss the project. Please do not send passwords, API keys or confidential media in an initial enquiry. For access, correction or deletion enquiries relating to correspondence, contact the address above; applicable recordkeeping obligations may affect deletion.

3 How your Google data is handled

The remote pilot uses Vurctube's Google Web OAuth client and the official YouTube Data API. The requested scopes are openid, email and https://www.googleapis.com/auth/youtube.readonly. Enabled metadata editing also requests https://www.googleapis.com/auth/youtube.force-ssl, a Google permission broader than the bounded edit tools this pilot exposes. You do not need your own Google Cloud project. The data path is:

• You use Google's consent screen to authorize Vurctube. We verify the returned identity and channel before enabling access.
• You separately approve a preregistered MCP client. Your agent gets a Vurctube token, not your Google credential.
• For a permitted read, our Oracle-hosted service sends a request to Google and returns its result through Cloudflare to the approved MCP client. We are in this data path. The client can then send the result to its chosen model provider or store it in its conversation history.
• Google's own handling of your account and of API traffic is described in the Google Privacy Policy.
• A proposal-enabled agent can submit an exact title, description or tag change. The owner must independently approve it in the browser before Vurctube sends the update to Google. We retain the proposal and relevant metadata to check concurrent changes, record the decision and verify the result. Uncertain results are not silently retried; automatic rollback is not available. Different capabilities in the local CLI are not remote product features.

4 Limited Use

We use Google data only to provide the explicitly requested connector features. We do not sell it, use it for advertising, or train general-purpose AI models with it. It is not routinely read by our staff. Human access is limited to your affirmative agreement for specific support data, necessary security investigation, or legal requirements permitted by Google's policy.

Only connect a client whose processing, retention and training settings are compatible with Google's Limited Use requirements. Do not use this connection to send Google data for general-purpose model training, advertising or resale. We cannot remove copies already held by your chosen client or model provider; use their controls and contact them for deletion. These downstream responsibilities do not remove Vurctube's own obligations.

5 Hosted storage and retention

• Google refresh credential: encrypted using AES-GCM, with the key stored separately from the database. The pilot connection has an absolute seven-day lifetime from Google authorization; reuse does not extend it. Pending credentials expire after ten minutes.
• Google identity and channel binding: used only for the connected pilot. Channel ID/title and permission metadata are stored with the profile. Channel identity is checked from Google on authorization. Ordinary read results are passed to the client, not saved as a historical content library. Metadata editing additionally stores before-images, proposal payloads, execution intent and readback/audit content for safe execution and reconciliation.
• MCP authorization: short-lived access tokens expire after five minutes. Rotating refresh grants expire within seven days. Browser identity sessions expire after eight hours. One-use login and consent transactions expire after ten minutes. Opaque bearer values are hashed rather than stored in plaintext.
• Cleanup: a maintenance sweep runs every minute while the service is healthy. Expired credentials and inactive profile data are removed. Stored API-content payloads and channel titles are scheduled for removal after 29 days or an earlier recorded expiry; reconnecting does not reset their age. Minimal operation outcomes and accounting can remain without those payloads. If the service is offline, cleanup runs before it accepts requests at restart. Failure leaves access denied and requires recovery; a prolonged outage can delay cleanup. Reauthorization refreshes the channel binding; it is not an extension of old agent grant expiry. This is cleanup of the current hosted store, not a guarantee of erasure from external backups or your agent's storage.
• Operational accounting: minimal quota totals, request-method/outcome records and lifecycle locks are used to control access and costs. Shared project quota accounting is retained after disconnect; it does not contain returned video titles, descriptions, comments, tokens or media. The pilot does not make automatic historical backups of creator grants.

Application request/query logging is disabled in the hosted pilot. Access to the host and stored data is restricted. These controls do not make the system risk-free, and downstream agent storage follows that provider's controls. Public unattended use is not yet offered.

6 Revoking access

Use Manage connection and choose Disconnect and delete Vurctube channel data. This invalidates Vurctube agent grants, removes our Google credential copy and purges the dedicated channel profile. It does not delete YouTube content or affect another application's local files. Cleanup failure denies access and is retried by maintenance.

You can also revoke Google's grant at myaccount.google.com/permissions. Our disconnect does not automatically call Google's project-wide revocation, which can also affect other clients in the same Google project. For a deletion request without signing in, contact zw@vurctne.com; we will verify identity and handle deletion as soon as possible and within seven calendar days. Do not send passwords or tokens. Separately remove any data retained by your agent or model provider.

7 Service providers, cookies and this website

vurctube.com is a set of static pages served by Cloudflare. Our page source sets no cookies and includes no custom analytics code. When you use the language switch, we save only your language choice in this browser’s local storage. On the home entry page, that choice takes priority over your browser language; explicit language URLs remain available. This preference is not sent to our servers, and we do not use geolocation to choose a language. The hosting platform can inject a Cloudflare Web Analytics script into delivered pages to measure visits and page performance. See Cloudflare Web Analytics information and Cloudflare's privacy policy for its handling of these requests. The pages also load fonts from Google Fonts, so your browser makes a request to Google's font servers when you visit.

The remote MCP service is different from the static website: it uses secure, HttpOnly, SameSite cookies for login, anti-forgery protection and consent. It runs on Oracle infrastructure (Oracle privacy information) and uses Cloudflare for HTTPS delivery. These providers process network requests as part of delivering the service. Google provides identity and YouTube APIs. Your selected agent/model provider is an additional recipient when you approve that client. Processing can occur outside your country; this pilot does not promise Australian-only data residency.

8 Separate self-hosted build

The separate local CLI/stdio build can run on the operator's computer with the operator's own OAuth files and records. Those files are not automatically uploaded to Vurctube. It may store proposed requests, metadata before-images and execution records; automatic rollback is not available. Its local retention maintenance is not complete, so the operator must manage cleanup separately. This is not the remote product's onboarding path or evidence that remote data remains on your computer.

9 Children

Vurctube is intended for creators and professional media teams, not children. If you believe a child has provided personal information through an enquiry, contact us.

10 Changes to this policy

If this policy changes, the new version will be published on this page with a new "last updated" date. If a future version collects a new kind of data, uses Google data for a new purpose, or shares it in a new way, the software will tell you and ask for your consent before doing so.

11 Contact

Questions about this policy: zw@vurctne.com.