Know what stays here and what leaves.

When you use local scheduling

Chrome’s extension storage keeps local task records and settings in that Chrome profile. A task record includes its prompt, the target conversation reference, schedule, retry settings, status, and task history. The optional Cloudflare token is also saved in that profile if you configure Cloud mode.

For Browser tasks, the extension opens or uses the saved Claude chat URL and the content script interacts with that Claude page. When sending proceeds, Claude receives the prompt through your signed-in browser session. The extension does not read or export browser cookies.

When you configure Cloudflare

The extension sends task fields—including prompt text, task name, selected target reference, schedule, and retry options—to the Worker URL you configure. The Worker stores task data in the D1 database attached to your Cloudflare account. Your Worker access token is sent in the Authorization header and kept in local extension storage.

Cloudflare mode is optional. You provide and operate the Worker, database, token, retention, and deployment. The Worker marks tasks due; a local Chrome extension still performs the Browser action, and Desktop tasks still need the Windows helper.

What Desktop support inspects

The Windows helper reads Claude Desktop’s accessible UI controls to identify the active chat, chat choices, composer, Send control, and visible message-count information. It sends the task prompt to the local helper through Chrome Native Messaging so it can interact with Claude Desktop. When sending proceeds, Claude receives the prompt through your signed-in Desktop session.

The helper writes local diagnostic files under %LOCALAPPDATA%\ClaudeAutoResume. The UI Automation snapshot redacts message body text, but can include chat titles, window titles, control names, identifiers, and layout metadata. Extension and helper execution logs record task IDs, prompt length and hash; the helper hashes conversation references. They do not record prompt text. Review diagnostic files before sharing them.

Safeguards and limits

The extension checks the target before acting, preserves unrelated composer drafts, and records a send as verified only when it can observe the expected result. If delivery is uncertain, it does not automatically resend. A user must check Claude before manually retrying.

The extension requires access to Claude pages to perform its core function. Chrome displays requested permissions during installation; review those permissions before approving.

Remove the data and software

Remove the extension from chrome://extensions. Clearing its local data removes extension settings and tasks. If you installed Desktop support, run the package’s uninstall script to remove the helper and registration; inspect and remove local diagnostics under %LOCALAPPDATA%\ClaudeAutoResume if desired.

For Cloud mode, remove tasks and data from the Worker/D1 resources you control and revoke or rotate the token in your Cloudflare configuration. Uninstalling the extension does not delete data already sent to your Worker.

What this website does

The interactive task preview changes only in the page; it does not connect to Claude or submit a prompt. The site source has no analytics SDK or contact form. A hosting provider may process standard request logs under its own privacy terms.