Clear data practices. Restricted access.

This policy applies to the BTC Command Center website, member service, payment and support workflows, and the private owner-operated BCC Content Studio API client. BTC Command Center is the operator. Privacy or deletion requests may be submitted through the current official channel on the Contact page.

We may process a name, email address, contact number, country, support messages, member identifier, plan, start/expiry date, device-binding information, login/security events and technical logs needed to provide and protect the service.

When checkout becomes available, an approved payment provider processes payment instruments under its own privacy and security terms. We may retain order and payment references, amount, currency, payment status, refund/dispute status and invoice information. BTC Command Center does not store full card numbers, CVV, bank PINs or UPI PINs.

Data is used to create and secure accounts, verify payment and entitlement status, deliver access, provide support, prevent duplicate welcome offers and abuse, process valid cancellation/refund requests, keep transaction and consent records, meet legal obligations and improve service reliability.

Necessary data may be processed by approved hosting, security, communications, analytics or payment providers solely to operate the requested service. Data is not sold. We do not share personal data with exchanges for trading, and we do not request access to a member's exchange funds.

Hosting and security providers may process IP address, browser/device information, request logs and essential cookies or similar technologies for delivery, fraud prevention and security. Material analytics or advertising changes will be disclosed before use where required.

Account data is retained while access is active and for a reasonable period needed for support, fraud prevention and legal claims. Payment, invoice, refund, consent and audit records may be retained for the period required by tax, accounting, payment-network and other applicable obligations. Data no longer needed is deleted or de-identified where reasonably possible.

Administrative access is restricted, secrets are not placed in customer-facing code, and payment confirmation must be verified server-side before access is issued. No internet service can promise absolute security; suspected incidents should be reported through the Contact page.

A verified user may request access to, correction of or deletion of eligible personal data. Some transaction, security or legal records may need to be retained. Requests are completed after identity and authority are verified.

Transactional messages may cover payment status, activation, expiry, security, refunds and material service changes. Promotional messages, where used, must provide any opt-out required by applicable law.

BCC Content Studio uses YouTube API Services. Its only authorized operator is the owner of the connected channel. YouTube-connected functionality is also governed by the YouTube Terms of Service and Google Privacy Policy.

After OAuth consent, the API client accesses connected-channel identity to verify ownership, sends owner-created videos and owner-controlled metadata for upload, sets an eligible thumbnail and reads resulting upload visibility to confirm the owner's setting. It does not request YouTube passwords, watch history, comments, contacts, subscriptions, advertising data or other users' channel data.

The client requests youtube.upload and youtube.readonly for the owner-authorized workflow. The owner may edit queued metadata and visibility, hold or skip items, pause publishing or disconnect the account. New outputs wait through a review window and automation applies only after explicit activation.

OAuth material remains on private Google Cloud infrastructure with restricted operating-system access. YouTube API response fields retained in publisher state are removed within 30 days; non-YouTube content hashes may remain for duplicate prevention. The owner may revoke access in Google Security settings or use the disconnect control to delete the local OAuth token and YouTube API response state.

The service is not directed to children, and original educational market videos are marked as not made for kids. We do not knowingly collect children's personal data.

Material changes are posted here with a revised date. A new use of YouTube-authorized data or a material new payment/data practice will be disclosed before that use where required.