Revoke access and delete data

In the private studio, open Accounts, select a YouTube connection and use its access-revocation and data-deletion control. Revocation concerns the authorization that the particular Google user granted to the application. Google may also invalidate that user's other access that relies on the same or combined authorization.

As a precaution, the current SMM prepares this operation for all local YouTube connections, including connections for other brands. The preview explicitly lists them before confirmation. SMM determines this scope; it does not mean that every listed connection necessarily shares one Google authorization. Confirm only if you intend to revoke the stored authorizations and erase the data of every listed connection. The application must identify incomplete revocation, required Keychain access or unresolved backup copies and must not treat deletion as complete while any of these steps remain pending.

You may also send a deletion request to the operator's contact below. Identify the studio account or relevant channel, Page or profile and the data covered by the request; do not send passwords, tokens, access keys or OAuth JSON. Requests must be handled within seven calendar days. The operator verifies the requester's authorization before processing.

Deleting data stored by this application does not delete the YouTube channel or its videos. Use YouTube Studio for remote content. You may independently revoke authorization in Google account permissions.

To erase data obtained through Facebook or Instagram, send the operator a request identifying the relevant platform and account. The operator confirms the scope with you, stops further use of the affected access and arranges removal of the relevant local credentials, connection and publication-operation records, temporary delivery copies and controlled backups. This process is handled under the operator's supervision; SMM's current built-in revocation and deletion control applies to YouTube and does not itself erase Meta data.

Disconnecting Facebook or Instagram from SMM removes locally stored access. It does not itself revoke authorization at Meta, erase retained provider records or remove the Page, profile or published posts. Manage the app's authorization separately in the relevant Meta account settings. Manage already retrieved copies and published content directly on Facebook or Instagram.

Temporary Cloudflare R2 storage contains only explicitly approved final exports for Instagram, not originals. SMM records transfers and deletion results. Once Meta confirms completed processing or the attempt has definitively ended, SMM requests object removal and verifies it. A request to erase temporary exports must cover stored objects and any incomplete uploads. Missing access, an unresponsive provider or an uncertain result means removal is not confirmed. Neither expiry of the one-hour link nor the one-day fallback rule is evidence of deletion.

Removing storage access from SMM removes the local key from the server Mac's Keychain. It does not delete the storage or its contents and does not revoke the key at Cloudflare. Resolve pending deletions before removing or revoking access; missing access may require action directly at Cloudflare. The operator must not represent a request as fully completed if only local deletion has been confirmed while requested remote steps or controlled copies remain unresolved.

Original photos, source videos, local creative drafts and editorial approvals are separate from provider-derived data. Their deletion requires a separate, explicit owner instruction. Controlled backup copies of provider data must be included in provider-data erasure; external owner-made copies need the owner's action.