Chrome extension support
Help with Done Here?
Email ChromeExtensionSupport@purelymail.com. Do not send cookie values, passwords, authentication tokens, private page content, or form entries.
Confirm the extension is enabled and that Chrome website access was granted during onboarding. Ignored sites intentionally do not show the prompt. Chrome internal pages and the Chrome Web Store cannot be injected into.
This is intentional when Done Here? cannot identify a reliable visible sign-out control. The extension should refuse to guess rather than claim a server-side logout it cannot prove.
Last-tab safety can prevent cleanup from invalidating other open work on the same site. Close the other matching tabs or deliberately override the protection.
Some cookies belong to a broader registrable domain. Clearing them can sign you out of sibling services that share that cookie scope.
Maximum targets local browser data Chrome exposes. It does not remove server-held records, saved passwords, remote logs, or sessions on other devices.
Include in a support request
Enough evidence to reproduce the problem—without sending secrets.
- Chrome version and Done Here? version.
- The website origin, without credentials or private query strings.
- The selected action.
- Whether another matching tab was open.
- Expected and actual behavior.
- A sanitized screenshot when useful.
For product behavior and release status, see the Done Here? product page and evidence record.