YKL Global Social Media Operations Platform

Authorization Revocation Instructions

YKL Authorization Revocation Instructions

Effective Date: August 12, 2026

1. Overview

The YKL Global Social Media Operations Platform connects to an eligible third-party platform only after a user authorizes access through the platform's official OAuth or authorization process.

A user may revoke or disconnect that authorization at any time, subject to the user's account authority and the platform's available controls.

Revoking authorization is different from:

  • deleting the YKL account;
  • deleting information stored by YKL;
  • deleting content already published on a third-party platform; or
  • closing an account with the third-party platform.

For deletion of information held by YKL, see https://www.ykltop.com/data-deletion.

2. Revoke Authorization in YKL

Where the applicable controls are available:

  1. Sign in to YKL.
  2. Go to Social Accounts or Account & Security.
  3. Open Authorization & Data Controls.
  4. Select the Connected Platform Account.
  5. Choose Disconnect, Revoke Authorization, or the equivalent control.
  6. Review the effect on pending jobs and synchronized information.
  7. Confirm the action.

The names and location of controls may change as the Service develops.

If the self-service control is unavailable, contact:

privacy@ykltop.com

Include the YKL account email, organization name, Connected Platform, and the account or business asset to be disconnected. Do not include a password, token, client secret, OAuth code, or webhook secret.

3. Revoke Authorization Through the Platform

Users may also remove YKL through the applicable platform's account, security, business-integration, or authorized-app settings.

The platform controls the location and operation of those settings. The user should follow the platform's current instructions for removing a third-party application.

Revoking through the platform may not immediately update YKL's interface if the platform does not provide an immediate status event. YKL will update the connection when it receives the event, detects an invalid authorization, or processes the user's request.

4. What Happens After Revocation

After YKL processes a revocation:

  • YKL will stop initiating new API requests on behalf of the disconnected account, except where needed to complete revocation, deletion, security, or legal obligations;
  • pending publishing, synchronization, or other jobs for that connection should be cancelled or disabled where technically possible;
  • the connection status will be changed to disconnected, revoked, expired, or a similar status;
  • access and refresh credentials will be revoked, invalidated, or deleted as supported by the platform and YKL's implementation;
  • any pending actions dependent on the connection will no longer run;
  • platform data will no longer be refreshed; and
  • YKL-held data will be retained, deleted, or de-identified according to the Privacy Policy, a valid deletion request, platform rules, and applicable law.

Revocation does not guarantee that the platform will remove content already published, comments already sent, or other completed actions. Users must manage completed platform content directly through the platform where necessary.

5. Pending and In-Progress Actions

YKL will use reasonable efforts to cancel actions that have not yet been sent to the platform.

An action may still complete if:

  • it was already accepted by the platform;
  • it was being processed when revocation occurred;
  • the platform did not support cancellation; or
  • the status event was delayed.

Users should review the Connected Platform directly after revocation.

6. Data Deletion After Revocation

Revocation stops future authorized access; it is not automatically a request to delete every record held by YKL.

A user may separately request deletion of YKL-held information through:

YKL generally aims to delete verified requested information from active systems within 30 days, subject to platform-specific shorter periods and lawful retention exceptions.

7. Reconnecting an Account

If a user later reconnects an account:

  • the user must complete the platform's current OAuth process again;
  • YKL will request only the scopes needed for enabled features;
  • prior authorization does not automatically restore a revoked token;
  • the platform may require new consent, account selection, or administrator approval; and
  • previously deleted information may not be recoverable.

8. Organization and Role Changes

An organization administrator may disconnect an integration managed by the organization. An individual member may not have authority to revoke an organization-owned connection.

If a user's role on a platform or in YKL changes, YKL may restrict or disconnect the integration where the user no longer has appropriate authority.

9. Platform Availability

Revocation behavior depends in part on the platform. A platform may:

  • expire or invalidate a token;
  • require revocation through its own settings;
  • notify YKL through an API or webhook;
  • impose a deletion deadline;
  • continue displaying previously published content; or
  • suspend the account or application independently.

YKL follows the applicable platform's current supported process and does not claim control over the platform's systems.

10. Support

Authorization, privacy, and deletion questions: privacy@ykltop.com

General support: support@ykltop.com

Platform review communications: review@ykltop.com

Display name: YKL Team

Company: Hangzhou YunKaiLiang Intelligent Technology Co., Ltd.

Privacy Policy: https://www.ykltop.com/privacy

Data Deletion Instructions: https://www.ykltop.com/data-deletion

Contact YKL Back to homepage