Why this happens
- Public WiFi networks (airports, hotels, cafés) often use shared IPs, captive portals, or traffic filtering that can disrupt reCAPTCHA.
- If your first login attempt fails on such a network, your browser may cache an invalid token in cookies or local storage.
- Even after moving to a secure or private network, that cached data can continue to block login attempts until it’s cleared.
Quick fix
Clearing your browser data forces a fresh reCAPTCHA token to be generated and resolves most cases.1
Clear cookies and cache for app.demand-genius.com
In your browser settings, clear cookies and cached files scoped to
app.demand-genius.com. You can usually do this from the browser’s site settings or privacy panel.2
Switch to a secure network
Move to a trusted private network (e.g., your home or office WiFi) rather than a public hotspot.
3
Reload the login page and sign in
Refresh the Demand-Genius login page and attempt to sign in again. Your browser will generate a new reCAPTCHA token.
Other things to try
If clearing cookies and cache doesn’t resolve the error, work through the following steps:- Disable ad blockers or privacy extensions temporarily. Some extensions intercept or block the scripts reCAPTCHA depends on.
- Ensure JavaScript and cookies are enabled in your browser settings. reCAPTCHA requires both to function.
- If you’re using a VPN or proxy, disconnect it and try signing in again. Some VPN exit nodes are flagged by reCAPTCHA’s risk scoring.
Best practices on public WiFi
Public networks introduce the most common conditions that trigger this error. Following these steps before you log in can prevent the issue from occurring.
- Log in from a secure, private network whenever possible.
- If you must use public WiFi, complete any captive portal login first (for example, the “Accept Terms” screen that appears when you connect).
- If login fails on a public network, clear your cookies and cache before retrying on another network.