SentryScreen
Menu

Support

How can we help?

Report a problem on GitHub, send us a diagnostic report from the app, or write to us.

Report a problem

Open an issue on GitHub: what you expected, what happened, your macOS version and the SentryScreen version (Settings shows it). Never attach a screenshot of explicit content.

Open an issue

Send a diagnostic report

A report shows us what the app was doing, without anything from your screen. In SentryScreen’s settings, open the diagnostics section, read the report, and approve sending it. Nothing is sent before you approve it, and it is sent only once. Before you press Send, copy the report’s machine_id from the review screen and mention it in your issue so we can find the report. What a report contains.

Write to us

For anything you would rather not post in public, email us.

Report a security problem

Found a way around SentryScreen’s protection, or a security problem in the app, this site or our server? Report it privately through GitHub security advisories, or write to the address above with “Security” in the subject. Please do not open a public issue for it.

How to check a Mac

If you think SentryScreen is not covering on a Mac, these steps take a few minutes.

  1. Open SentryScreen on that Mac

    Click the SentryScreen icon in the menu bar. It should say Protected. If it says anything else, or the icon is missing, sign in to an administrator account, open SentryScreen from the Applications folder and follow what it says. If a second screen is connected, it also names the one screen it protects; anything on the other screen is not covered.

  2. Make sure your child's account is Standard

    Open System Settings, then Users & Groups. Your child's account should say Standard, not Admin. Anyone with an administrator account can stop or remove any app, SentryScreen included.

  3. Change the parent PIN if you are unsure

    If your child might know it, choose a new one: click the SentryScreen icon, then Settings…, then Change PIN.

  4. Still not right? Tell us

    Send a diagnostic report and open an issue on GitHub with what you saw.