Support
What each message means, what to do about it, and how to tell us about a problem.
Please never include the message you were sending, or any personal data, in a report. We don’t need it. The site you were on, the kind of data involved (“a phone number”) and the message the extension showed are enough to find the problem.
“Could not check this message”
This dialog means Guard could not finish checking before you sent. It never blocks you: you can still choose to send. There are three versions, and they have different causes.
CloakLLM Guard was updated or restarted, so it could not check this message. Reload this page to start checking again.
What to do: reload the page. This happens after the extension updates or is restarted: tabs that were already open keep running the old copy until they reload.
CloakLLM Guard could not read this message box, so it does not know whether the message contains personal data. This usually means the site changed and the extension needs an update.
What to do: please report it, with the site you were on. Chat sites change their layout without notice, and this is how we find out. Until it is fixed, Guard cannot check messages on that site.
CloakLLM Guard could not check this message, so it does not know whether it contains personal data.
What to do: try sending again. If it keeps happening, turn the extension off and on again at chrome://extensions, then reload the page. If it still happens, report it.
The toolbar popup says it could not reach its background service
Guard could not reach its background service.
The popup could not get an answer from the part of the extension that does the checking, so it cannot show what has been caught, and the extension may not be checking your messages right now.
What to do: reload the page you were on. If that doesn’t help, turn the extension off and on again at chrome://extensions. If it persists, report it.
It warned me about something that isn’t personal data
Some things look like personal data. A long order number can look like a phone number, for example.
What to do: if one kind of warning keeps getting in your way, switch that category off: open the toolbar popup, choose Settings, and untick it. We’d also like to hear about it: report the category and a description of what triggered it (“a 10-digit invoice number”), not the text itself.
It didn’t warn me when I expected it to
Check these first:
- The site is one Guard works on:
chatgpt.com,chat.openai.com,claude.ai,gemini.google.com,copilot.microsoft.comorm365.cloud.microsoft. It cannot see desktop apps, assistants inside a code editor, or anything sent from code. - That kind of data hasn’t been switched off in Settings.
- It’s a kind Guard recognises. It does not detect names, postal addresses or dates of birth.
What to do: if all three are true and it still didn’t warn you, report it. Tell us the site and the kind of data, but not the data itself.
How to report a problem
Please include:
- Your browser and its version.
- The Guard version, shown at
chrome://extensions. - The site you were on.
- Which of the messages above you saw, if any.
- Any line starting with
[CloakLLM Guard]from that page’s developer console. These lines name the site and the check that failed. They never contain what you typed.
Open an issue on GitHub
Public, so others with the same problem can find the answer.
Email team@cloakllm.dev
For anything you’d rather not post publicly.
Security issues
If you’ve found a way for the extension to leak data or be abused, please don’t open a public issue. Report it privately, so it can be fixed before it is widely known: report a vulnerability on GitHub (visible only to the maintainers), or email team@cloakllm.dev.