Disconnect cleanly. Delete at the right boundary.

Local customer data

1. Finish or stop active work and preserve any deliverables you want to keep.
2. Use the packaged C.C.O.S. disconnect operation for the exact workspace and platform. Where provider-side revocation is implemented, supply required configuration only through the private runtime boundary so revocation can complete safely.
3. Confirm the connection reports not connected. If provider revocation is unavailable or cannot be confirmed, use the provider's account security controls to remove C.C.O.S. access before deleting local credentials.
4. After verifying exact paths and backups, remove the customer-selected runtime state and encrypted connection store. This may remove tokens, workflow state, logs, artifacts, and packages stored under those paths and may be irreversible.
5. Remove separately stored encryption keys, provider client files, environment configuration, and backups that you control.

Connected-platform data

Disconnecting C.C.O.S. does not delete already published posts, account data, provider logs, or other information controlled by Google, Meta, TikTok, Pinterest, X, LinkedIn, Threads, AI model providers, or hosting providers. Use each provider's controls for data it holds. C.C.O.S. cannot guarantee deletion by another organization.

Google and Meta access

For Google/YouTube, revoke C.C.O.S. access through the Google Account third-party connection controls in addition to removing the encrypted local workspace record. For Instagram, the implemented disconnect requests deletion of the application's permissions and retains the local record if provider revocation cannot be confirmed. Reconnect only after the intended account or channel identity has been verified.

Seller-held correspondence

The qualified static website has no customer database. To request deletion of eligible information previously sent through support, privacy, security, or legal correspondence, email privacy@axiward.com from an address that permits reasonable request verification, or write to the public business mailing address below. Do not include credentials or unnecessary private data. Axiward Technologies retains correspondence only as long as reasonably necessary for the purpose collected, security, dispute resolution, legal obligations, and recordkeeping. Verified requests are handled within the time required by applicable law. Additional deletion rights, verification requirements, and exceptions may apply based on the requester's jurisdiction and will be honored where legally required.

OAuth callback data

The public callback pages do not exchange, relay, or store authorization codes or tokens. Their browser script removes callback query and fragment data from browser history. Authorization and credential storage occur only in the customer-local C.C.O.S. flow.