Why am I seeing this?

If a page asked you to complete a quick check, or told you it could not let you through, this page explains what happened and how to get moving again. You are in the right place, and this is not an accusation.

What happened

The site you were visiting sits behind an automated-abuse protection check. That check looks at technical signals from the connection to tell ordinary visitors apart from automated traffic. Sometimes it needs a quick extra step before it can let you continue, and once in a while it gets a real person’s visit wrong. Either way, this is about the connection, not about you, and there is a way forward below.

If you saw a quick check (challenge)

You were asked to complete a short verification step before continuing. In most cases you just wait a moment for it to finish, or follow the simple on-screen prompt, and the page then loads as normal.

The humanymous Pass verification check: slide three rows so each highlighted key lines up in the teal slot, then submit. It works by keyboard, by screen reader, and by tapping the on-screen arrows, and has no time limit.

This step is meant to work for everyone, including people using a screen reader or other assistive technology. If the check will not complete, or you cannot use it:

  • Try refreshing the page and completing the step again.
  • If it still will not let you through, contact support at [email protected]. Tell them you were stopped by a verification step and could not complete it, and mention any assistive technology you use so they can help directly.

Note: If you were blocked on someone else’s website, contact that site’s operator first — they control the deployment and the unblock path. [email protected] reaches the maintainers of the humanymous software, not every site that runs it.

We would rather hear from you than leave you stuck.

If you were blocked (denied)

If the page told you it could not let you through, you can ask us to take another look. Please contact support at [email protected] and include:

  • Your incident handle, if the page shows one — some deployments display a short reference code on the block/verification page. If you see one, include it; it is the fastest way for us to find your specific visit. If not, the details below still let us locate it.
  • Roughly when you were browsing — the date and approximate time, and your timezone if you know it.
  • What you were trying to do — for example, signing in, checking out, or opening a particular page.

With those details, support can review the decision and, where appropriate, let you back in. If you were in the middle of a purchase or another time-sensitive task, please say so and we will treat it as a priority.

Note: A block is a decision about a single visit, not a permanent judgment about you. Reviewing it is a normal part of how this protection is meant to work.

Accessibility

We aim for the quick check to meet the WCAG 2.2 AA accessibility standard, so that it works with screen readers, keyboard navigation, and other assistive technology. If it did not work for you, that is a bug we want to fix. Please report it to [email protected] and describe what happened and what you were using, and we will follow up.

Your privacy

We identify visits by pseudonymous technical signals from the connection — for example characteristics of the browser and network session — not by your name, your account, or your personal identity. These signals are stored in a pseudonymous form rather than as raw details. When you contact support, the incident handle is what links your message to the specific visit, so you do not need to share more personal information than you are comfortable with.

Note: If you have a data or privacy request about your visit, you can raise it with support at [email protected] and it will be routed to the right team.