BeeSensible Spell-check for privacy
Get started
Documentation Changelog
Support

Troubleshooting

Common issues and how to fix them when BeeSensible does not detect or highlight as expected.

Most issues fix themselves with one or two checks. Work through the section that matches the symptom. If nothing here works, contact support at the bottom of this page.

No highlights are appearing

You are typing in a supported app and nothing highlights.

  1. Check the extension is active on the page. Click the BeeSensible icon. The popup should read Active on this page. If it shows Inactive or Paused, click the toggle and refresh the page.
  2. Check the page is in your covered apps list. BeeSensible only runs on apps your admin has enabled. If the app should be covered, ask your admin to add it.
  3. Refresh the page. If the extension loaded after the app, a refresh ensures the two attach correctly.
  4. Allow a few seconds. Some apps render their text fields after the page loads. Type a short sentence and wait two to three seconds.
  5. Disable other extensions. Ad blockers, privacy tools, and grammar checkers can interfere with the highlight overlay. Disable them temporarily to see if highlights return.

A detection looks wrong

False positives happen because detection is pattern-based.

  • Dismiss a one-off. Open the side panel, find the detection, and click × next to it. The highlight goes away for that instance.
  • Report a recurring false positive to your admin. If the same kind of value is consistently flagged, your admin can adjust the detection profile.
  • Sensitive data that is not flagged. Tell your admin, including the format of the value (with the actual sensitive content redacted).

Browser support

BeeSensible runs in the current versions of Google Chrome and Microsoft Edge. Other browsers are not supported.

Updating the extension

The browser updates extensions automatically when you restart it. After an update, refresh tabs that use BeeSensible-monitored apps so the new version attaches to the page.

If the version stays on an older release after restart, contact support.

Contacting support

hello@beesensible.eu

When you write in, please include:

  • Your browser name and version.
  • The URL of the page where the issue happened.
  • A screenshot if you have one.
  • Your organization, and the detection profile assigned to your account if you know it.
  • A short description of what you were doing and what you expected to see.

Your admin can also raise a ticket on your behalf from the BeeSensible admin dashboard.