C.C.O.S.

Data deletion

Disconnect cleanly. Delete at the right boundary.

C.C.O.S. separates local customer data, third-party platform data, and any information the seller may hold through support.

Owner/legal review required before deployment · Effective date: [OWNER TO SUPPLY]

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 command for the platform. Where remote revocation is supported, provide required private configuration so revocation can complete safely.
  3. Revoke the C.C.O.S. application in the platform's own account/security settings.
  4. Remove the private encrypted connection store and customer-selected runtime state directory only after verifying the exact paths and backups. This removes local tokens, workflow state, logs, artifacts, and packages contained there.
  5. Remove separately stored environment keys, client files, and backups you control.

Local deletion is controlled by the customer. Consult the purchased connection and recovery documentation before removing state; deletion may be irreversible.

Third-party platform data

Disconnecting C.C.O.S. does not delete posts, account data, provider logs, or other information held by Google, Meta, TikTok, Pinterest, X, LinkedIn, Threads, AI model providers, or infrastructure providers. Use each provider's account controls and deletion process. C.C.O.S. cannot promise deletion of data controlled by another organization.

Seller-held data

The qualified static site has no customer database. If you contacted support or purchased through a separate seller/storefront system, request deletion from [PUBLIC PRIVACY/DELETION CONTACT TO BE SUPPLIED]. The seller will assess the request subject to identity verification, legal retention duties, fraud/security needs, and records the seller is permitted or required to retain. Response timing and jurisdiction-specific rights require [LEGAL REVIEW].

OAuth callback data

These public callback pages do not process or store authorization codes or tokens. They immediately remove callback query and fragment data from browser history. Complete or cancel authorization in the customer-local C.C.O.S. flow.