You tap a link in Instagram or WhatsApp, press "Sign in with Google," and suddenly hit a wall: "Access blocked: This request does not comply with Google's policies" or "Error 403: disallowed_useragent." It looks alarming, but nothing is broken and there's nothing wrong with your account. The short version: this is a Google security policy — Google Sign-In doesn't work inside the "in-app browser" built into many apps. Switching to email login, or reopening the page in a regular browser like Safari or Chrome, solves it. This guide explains what the error means, why it happens, how to fix it right now, and how to avoid running into it again — step by step.
- The error comes from a Google policy — nothing is broken
- Google Sign-In is blocked inside in-app browsers
- Email login solves it on the spot
- Reopening the page in Safari or Chrome also works
- No changes to your device or account settings are needed
What Error 403 "disallowed_useragent" means
Error 403 "disallowed_useragent" is the message Google shows when it refuses a sign-in attempt from a browser environment it can't verify as safe. It's not caused by anything you did, and it's not an outage on the site you were signing in to — Google is blocking the request on purpose.
The key detail: this error only appears when you're browsing inside an in-app browser — the lightweight browser embedded in another app. When you tap a link in Instagram, Facebook, X, TikTok, WhatsApp, or similar apps, the page usually opens in that app's built-in browser rather than in Safari or Chrome. If you then try to continue with Google Sign-In, Google decides the environment doesn't meet its "use secure browsers" policy and returns a 403 error. It's not limited to social apps, either — the same thing can happen in any embedded view, such as the mini browser that opens from a mail app or after scanning a QR code.
How to tell if you're in an in-app browser
You can usually spot an in-app browser by its look. If there's an "×" (close) button at the top or bottom of the screen, the address bar is minimal and can't be edited, and there are no tabs or bookmarks to be found, you're most likely inside an in-app browser. In Safari or Chrome, you'll see the familiar address bar and tab icons.
This error does not mean your account has been hacked or is at risk. The same Google account will sign in without any problem from a regular browser.
Why Google Sign-In doesn't work in in-app browsers
Google Sign-In never hands over your password
The "Sign in with Google" button works by having you verify your identity on Google's own page — the site you're signing in to never sees your password, only the result. That whole model depends on one thing: the page where you type your password must genuinely be Google's. So Google strictly checks the environment its sign-in screen is displayed in.
Why in-app browsers don't qualify
An in-app browser is, by design, partly controlled by the app that's displaying the page. From Google's point of view, there's no way to fully confirm that the sign-in screen you're seeing is authentic, or that what you type is properly protected. To guard against phishing — fake login screens built to steal passwords — Google simply refuses sign-ins from these environments across the board.
In other words, this is a protection for users, and it happens on every site and service that offers Google Sign-In, not just Bloomy. It can't be switched off by the site or the app, so the fix is on your side: either change how you log in, or change which browser you're using. Either of the two methods below will work.
Fix 1: Sign in with email (the easiest)
Bloomy offers a passwordless "login link" option — you sign in using only your email address. Tap the link in the email you receive, and you're logged in. It works even inside an in-app browser, because no password is ever typed, so Google's restriction simply doesn't apply. If you want to fix this without leaving the screen you're on, this is the easiest route.
- Enter your email address on the login screen of your account page
- Tap "Send login link"
- Tap the link in the email you receive — you're signed in
If the email hasn't arrived after a few minutes, check your spam folder and make sure the address you entered has no typos.
Fix 2: Reopen the page in Safari or Chrome
If you'd rather keep using Google Sign-In, reopen the page in a regular browser. The menu location differs slightly from app to app, but the idea is always the same: "open the current page in an external browser."
In WhatsApp
If a link opens in WhatsApp's built-in browser, tap the menu icon (usually in a corner of the screen) and choose the option to open the page in your default browser. Once Safari or Chrome launches, tap Google Sign-In again.
In Instagram
Tap "…" at the top right of the screen and choose "Open in external browser."
In X (Twitter) or Facebook
From the share icon or the "…" menu at the top or bottom of the screen, pick the option that corresponds to "Open in browser." On Android devices, you can sometimes reopen the page by choosing a browser icon such as Chrome from the share sheet.
If you can't find the menu
Choose "Copy link" from the share menu, open Safari or Chrome yourself, and paste the link into the address bar. This works in every app, so it's a good fallback to remember whenever the menu is hard to find.
Note: menu names and locations vary by app version and may change over time.
Which fix should you choose?
| Fix | Effort | Best for |
|---|---|---|
| Sign in with email | Minimal (works right where you are) | Anyone who wants to log in right now with the fewest steps |
| Reopen in a browser | 2–3 taps | Anyone who prefers Google Sign-In or plans to keep using the browser |
| Copy the URL and open it manually | Moderate | Anyone who can't find the in-app menu |
If you're unsure, sign in with email first to get done what you came for, then bookmark the page in Safari or Chrome when you have a moment. From then on you can open it without going through an in-app browser, and you'll never see this error. And if you're not attached to signing in with your Google account, there's no need to memorize the reopen steps at all — email login is all you need.
How to avoid this error next time
Once you're signed in, a little preparation will keep the same error from bothering you again.
- Bookmark the pages you use often: Bookmark your account page in Safari or Chrome so you can open it directly, without going through a social media link.
- Add the page to your home screen: Adding it to your phone's home screen lets you open it with one tap, just like an app. On iPhone, use Safari's share menu; on Android, use Chrome's menu.
- Check the app's settings: Some apps have a setting to always open links in an external browser. Whether it exists and where it lives varies by app and version, so take a look through your app's settings menu.
Still can't sign in? Check these points
- The login email doesn't arrive: Check your spam folder and double-check the email address for typos. Some mail providers' filtering settings can also block the message.
- The error appears even in a regular browser: If cookies are blocked by private browsing or certain data-saver features, your login state may not persist. Try again in normal mode. If that doesn't help, clearing the browser cache and retrying often resolves it.
- Wait a moment and retry: On an unstable connection, the sign-in screens can take longer to load and hand off.
If none of this solves it, check the FAQ or reach out via our contact page — we'll work through it with you.
How Bloomy handles this: no dead ends by design
To keep this 403 error from becoming a dead end, Bloomy automatically detects when you're visiting from an in-app browser and shows guidance before you reach Google's screen. On top of that, email login — which works fine inside in-app browsers — is available as standard, so even from a link shared in WhatsApp or Instagram you can go all the way through buying an eSIM and checking your account without switching apps.
eSIM setup is just as streamlined: after purchase, you receive a setup link that completes installation in a single tap. The full walkthrough is in our setup guide. We keep refining these small details so first-time users don't get lost, and we publish our improvements in the changelog.
Bottom line: use email login, or reopen in a browser
Error 403 "disallowed_useragent" comes from Google's policy of not allowing Google Sign-In inside in-app browsers — there's nothing wrong with your device or your account. Switch to email login, or reopen the page in Safari or Chrome, and you'll be able to sign in as usual.
Once you're in, your account page shows the remaining data and validity of any eSIMs you've purchased. If you're still shopping for an eSIM for your next trip, the eSIM comparison page lets you filter plans by destination, data amount, and trip length — check current plans and pricing at the time of purchase. If your connection acts up while traveling, the connection troubleshooting page walks you through what to check, and if you want to start from the basics, see our eSIM guide.
Note: Bloomy eSIMs are data-only — they do not include a phone number, SMS, or voice calling. Plans are subject to a fair use policy, and actual speeds vary depending on the local network, your device, and your location.
The information in this article is current as of July 2026. App menu labels and Google's policies may change over time.
