Skip to main content
Requestly’s cloud services run in the United States. Requestly has no regional deployment, and there is no setting that changes where your cloud data is stored. Because of that, BrowserStack can mark Requestly as restricted for an organization that is subject to data residency, also called Geo-Region Restriction (GRR). When it does, Requestly shows a compliance screen instead of the app.

​
What you see

Signing in to the Requestly desktop app or web app with a restricted account replaces the app with a compliance notice:
This product is not compliant with Data Residency (GRR) regulations Your Organization has enabled Data Residency, which mandates you to use compliant products. Contact your Customer Success Manager to discuss continued usage of this product.
The only action on that screen is Sign out. The app itself does not load behind it, so no requests, collections, environments or projects are reachable while you are signed in with that account. You are not doing anything wrong, and there is no setting inside Requestly that clears this. The restriction comes from your BrowserStack organization, not from your Requestly account.

​
Who is affected

The restriction is set per BrowserStack group, and it is resolved per product. Requestly is restricted for a group when both of these are true:
  • BrowserStack has set a data-residency region on the group, and
  • Requestly is not exempted from that group’s data-residency setting.
Having data residency enabled does not by itself block Requestly. BrowserStack can exempt individual products from a group’s data-residency setting, and an exempted product is not blocked. Whether Requestly is exempted for your organization is a question for your Customer Success Manager.
Where it does apply, it applies to everyone in that group. Data residency is treated restrictively: if you belong to more than one group and any one of them is restricted for Requestly, you see the compliance screen. Accounts that belong to no restricted group are unaffected and never see any of this.

​
What to do

1

Contact your Customer Success Manager

The compliance screen names this for a reason: data residency is a BrowserStack organization setting, and your Customer Success Manager is the person who can tell you whether Requestly can be used under your organization’s terms.
2

Or sign in with an unrestricted account

Click Sign out on the compliance screen and sign in with an account that does not belong to a restricted group.

​
If the restriction is lifted

Requestly reads your organization’s data-residency setting from BrowserStack each time your organization’s details are synced, which includes every sign-in. Once BrowserStack clears the restriction or exempts Requestly, the compliance screen stops appearing. If it still appears after you have been told the restriction was lifted, sign out and sign back in.