X is adding a new disclosure to its Under the Hood account-data tool: eligible users will be able to see when the platform has limited the visibility of their posts in order to comply with local laws.
The new information is meant to make one particularly opaque kind of distribution decision more legible. When available, the tool will identify the country that sought the access restriction and the individual posts that prompted scrutiny. That does not make a difficult moderation or legal dispute disappear, but it gives an account holder something concrete to inspect rather than leaving them to infer a cause from falling reach or missing engagement.
What X is adding
Under the Hood previously surfaced information related to the systems behind X’s For You feed and labels applied to posts. The new local-law entry adds another category: a record of visibility reductions connected to a legal requirement in a particular country.
The key distinction is important. The available description concerns limited visibility, not necessarily deletion of a post or suspension of an account. A restriction on access can affect who is able to encounter content in a location while leaving the underlying post in place elsewhere. The planned display is also specific enough to point users toward the country involved and the posts affected, rather than merely issuing a broad warning that an account has been restricted.
That specificity is the meaningful part of the change. A creator, community manager, journalist, developer, or ordinary user whose audience shifts suddenly may now have a way to determine whether a local legal restriction is one known factor. It is not a complete explanation of distribution, but it can rule in a category of explanation that previously would have been invisible.
Why “shadowbanning” claims are so hard to settle
Shadowbanning is commonly used as a catch-all term for the belief that a platform has secretly reduced an account’s reach. It is a useful shorthand for frustration, but a poor diagnostic label on its own. It can refer to many different experiences: content reaching fewer people, an account not appearing where a user expects, an eligibility label, a recommendation change, a country-specific restriction, or simply normal variation in audience response.
The local-law notice does not prove or disprove every complaint about visibility. It addresses a narrower question: whether X has reduced access to particular posts because of local legal compliance. If the data identifies a country and an affected post, users have a documented explanation for that event. If it does not, that absence should not be treated as proof that no other ranking, policy, or audience factor exists.
That boundary matters because feeds are not one simple switch between “shown” and “hidden.” The For You feed is an algorithmic recommendation surface: it selects and orders posts for people who may not follow the account. A legal restriction is a different kind of intervention from a recommendation decision, even though both may be experienced by a poster as diminished visibility.
Related coverage includes X Adds Local-Law Visibility Notices to Under the Hood.
More precise terminology helps everyone involved. A country-specific access limit is not automatically evidence of a secret platform-wide penalty. Conversely, a user’s inability to explain a dip in reach has never been satisfying evidence that nothing happened. The new disclosure is useful because it identifies one defined circumstance and ties it to identifiable content.
Who can access Under the Hood
Access is not universal. X’s stated baseline requirements are that a profile must be more than one year old and must have published at least 10 posts during the previous month. Accounts that meet both conditions can use the feature and its added local-law visibility information.
Those requirements have practical consequences. A new account will not be able to use the menu as an immediate diagnostic tool, even if it is posting actively. Likewise, an older account that has been mostly inactive during the prior month will need to meet the posting threshold before it can access the data. Users assessing a visibility concern should therefore avoid assuming that failure to find the tool means no record exists; the account may simply be ineligible.
Under the Hood first appeared in limited testing in August. Its purpose is to offer some insight into data that has historically been difficult for regular users to see: the mechanisms and labels connected to distribution on a large social platform.
The data is useful, but it is not easy reading
There is a significant usability caveat. The information is delivered as a dense JSON file. JSON, short for JavaScript Object Notation, is a structured text format commonly used to represent data. It is well suited to software systems because it organizes information into named fields and values, but it is not automatically friendly to someone opening it simply to answer, “Why can’t people see this post?”
For a technically confident user, structured data can be valuable because it can preserve exact identifiers and relationships between entries. For many people, however, a raw data file can feel less like transparency and more like an extra decoding step. The disclosure’s practical value will depend on whether the relevant fields are clear enough to find and interpret without specialized knowledge.
Still, a machine-readable record is preferable to an entirely unexplained outcome. It gives users a place to begin: look for the affected post, note the country named in the entry, and distinguish that evidence from assumptions about the broader account. People handling a potentially sensitive issue may also want to preserve their own copy of what the account tool displays, along with the date they viewed it, since platform interfaces and data presentations can change.
A sensible way to read a restriction notice
- Confirm eligibility first. Check whether the profile is more than a year old and has made at least 10 posts in the last month.
- Identify the exact post. The point of the new disclosure is post-level clarity, so avoid treating one entry as a statement about every post from an account.
- Note the country named in the data. The restriction is described as a response to local law, making the location central to interpreting the result.
- Separate legal visibility limits from feed ranking. A local-law entry can explain one access restriction; it does not offer a universal account-health score or a complete map of recommendation behavior.
- Do not overstate what the data says. The presence of a notice documents a particular kind of limitation. Its absence does not diagnose all other distribution outcomes.
Why this matters beyond a single platform setting
Online visibility increasingly sits at the intersection of platform rules, recommendation systems, user behavior, and location-specific legal obligations. Users often see only the result: a post travels, stalls, receives a label, or is unavailable to part of an audience. They rarely see which layer produced that result.
X’s added entry does not open every layer. It does, however, separate a local-law compliance action from the platform’s broader black box of ranking and moderation questions. That is a modest but useful form of accountability: the company is attaching some context to a decision that can materially affect a person’s ability to communicate with an audience.
Transparency is particularly important where users make decisions based on distribution. Publishers may need to understand why an audience in one country cannot access a post. Businesses may need to assess whether a campaign’s reach has changed for reasons unrelated to its creative work. Community organizers and public-facing individuals may need to distinguish between a content-level restriction and an assumption that their whole account has been quietly suppressed.
The broader lesson is not that a single data export resolves platform trust. Rather, meaningful transparency tends to be granular. It tells people what happened, where it happened, and which piece of content was involved. The same demand for clearer rules and records appears in other digital-platform disputes, including questions around terms and user rights such as those raised in virtual ownership and annual resets in games.
What remains unanswered
The feature description leaves limits that users should keep in mind. Under the Hood’s local-law notices are not presented as a complete explanation for every change in reach. The tool’s eligibility thresholds also mean not every account can inspect the data. And the JSON-based format may make the information harder to use than a plain-language notice built directly into a post or account dashboard.
There is also an unavoidable difference between disclosure and remedy. Knowing that visibility was limited, seeing the country involved, and identifying the post at issue are valuable pieces of information. They do not by themselves explain the legal basis in detail, settle whether a restriction is appropriate, or change the restriction.
Even so, the update moves a consequential type of decision from speculation toward documentation. For users who qualify for Under the Hood, the next time a post’s audience appears unexpectedly constrained, there is now at least one additional place to look before reaching for the broadest possible explanation.
