Disconnect access. Then remove the copies.

Authorization, credentials and stored reports are different things. Use the steps that match where your access and data are held. The operator cannot delete files on your computer or records held by a third-party service remotely.

Revoke media access

In the relevant media account, review the connected application or integration and revoke the access you want to end. For Google, follow the official connected-app guidance. For Meta and TikTok, use that platform's current authorization controls for the connection concerned. Revoking access does not delete previously exported data.

Clear Pallas-managed credentials

Before removing the workspace metadata, ask your agent to inspect its Pallas connections and disconnect the selected connection. Pallas disables the local connection, attempts provider revocation where supported and removes credentials it owns. Read any returned warnings: remote revocation or credential cleanup may be incomplete. External environment credentials remain under your control.

Advanced: disconnect using the CLI

Advanced CLI, for an existing Pallas-managed connection only: create disconnect.json with the following structure, replacing the example identifier with the actual connection ID reported by Pallas.

{"action":"disconnect","connection_id":"connection_actual_id"}

pallas source manage --workspace /absolute/path/to/workspace --input disconnect.json

Paths and connection_actual_id are placeholders, not a ready-to-run deletion command. Use the pallas executable in your installed environment. This disconnect operation does not delete reports or databases.

Clear agent-host authorization

For a host-managed connection such as Meta's official MCP, use the corresponding Codex or Claude Code connection controls to disconnect or log out. Separately revoke access at the media platform. Pallas cannot remove credentials owned by the host. Do not delete undocumented host configuration files as a substitute.

Delete local workspaces and reports

Stop processes using the workspace and confirm its actual configured path. Remove the workspace you intend to erase using your file manager. Separately remove exported HTML reports, evidence attachments, copied files and backups wherever you stored them. Deleting one workspace does not find all other copies or revoke platform access.

Delete conversations and model-service data

Use your agent host's and model provider's history and data controls. Tool outputs may have been included in conversations sent to a model service. Local cleanup does not remove those records; the respective provider's policy and controls apply.

Ask about support correspondence

Email support@pallas-ads.com to request deletion of information actually held by Jieyi D, such as your correspondence and voluntarily sent attachments. Identify the relevant email conversation without sending credentials or more account data. The request covers operator-held material, not your device or third-party records.