Why the Age Check Followed Me After I Switched VPN Servers

The VPN said I had moved from London to Tokyo.

The age-verification screen followed me there.

I was trying to read a public sexual-health discussion before an appointment with my therapist. The thread contained adults talking about intimacy after antidepressants, but the forum had classified the entire section as mature content.

When I opened it, a verification window covered the page:

Confirm that you are over 18.

The choices were a facial scan or photo identification.

I was 34. I had used the same forum account for years and had already entered my birth date in its settings.

I blamed the UK connection first.

I turned on a major VPN provider, selected Japan, and refreshed.

The age check remained.

I switched to Canada.

Still there.

Then I chose a U.S. server and reopened the thread in another tab.

The same camera and ID buttons appeared.

An independent IP page confirmed that every server change had worked. My visible address had moved across three countries in five minutes.

The verification screen had not moved at all.

The age check was attached to more than my location

Age checks have become much harder to avoid in the UK.

Since July 25, 2025, services carrying pornographic or other restricted material have faced stronger age-assurance duties under the Online Safety Act. Ofcom’s 2026 reporting described age checks expanding across pornography, social media, dating, and gaming platforms. (Ofcom)

That made my assumption seem reasonable: if the prompt appeared because the site saw a UK address, changing the address should remove it.

But the IP address was only one part of what the forum knew.

A platform can attach an age status to the account itself. It may use the birth date entered during registration, the age of the account, previous verification attempts, app-store information, or activity associated with the profile.

Reddit’s age-assurance documentation offers a clear example. It may use account age, email information, birth date, posts, subscriptions, app-store signals, and previous verification status when determining an age group. (Reddit)

Once that information is attached to an account, changing the VPN server does not create a different user.

That explained why Tokyo had not helped.

I had moved the connection.

I had brought the same logged-in identity with me.

The tab carried the old decision too

The account was not the only thing following me.

I had kept refreshing the same browser session after every server change. The forum continued receiving its existing cookies and session information alongside the new IP address.

Those small pieces of stored data allow a site to recognise that a visit is continuing. The server location can change while the account and browser session remain the same. (MDN)

From the forum’s perspective, it could see:

• a different public IP;
• the same account;
• the same browser session;
• and an age-verification process that had already begun.

The geography changed. The visitor did not.

Other users have run into the same confusion: they select a distant VPN server, refresh repeatedly, and still see the age prompt. (Reddit) The useful detail is not the country they selected. It is that they kept moving the same session.

That was exactly what I had done.

I was testing servers when I should have been restarting the visit.

More countries repeated the same mistake

The established VPN provider was not failing at its basic job.

It had years of public history, extensive support resources, mature infrastructure, and servers across dozens of countries. Every IP check confirmed that the selected route was active.

The large network simply encouraged me to keep solving the wrong problem.

I moved from Japan to Canada, then to the United States and Switzerland. Each switch made the next country look like a possible reset.

It never was.

The provider also required a conventional account tied to my regular email address. That had not bothered me when I subscribed. It felt more noticeable while the destination was asking for my face or identification.

I was using one named account to protect access to another named account, while the forum carried the same age status from server to server.

The server map made the process look active.

Nothing important was changing.

By the fourth country, I no longer wanted more locations. I wanted one accepted route and a genuinely fresh visit, established in the right order.

I stopped moving the old session around

I closed every tab connected to the forum.

Then I signed out and removed the site’s stored browser data. I did not submit the facial scan or begin the ID process.

Instead of reconnecting through another city in the large provider, I opened OnlydogVPN.

The smaller app did not ask me to create a conventional email-and-password account before basic use. That removed one identity link from a session already crowded with them.

Its interface was organised around situations rather than geography. I selected the option for a service that was restricting or challenging the current connection.

This time, I connected before reopening the browser.

Then I launched a fresh private window and pasted the direct link to the public health discussion.

The verification screen did not return.

The page opened at the first comment.

I scrolled to the section on medication-related changes in desire and copied three questions into my notes. I opened a second thread, returned to the first one, and refreshed.

Both pages remained available.

That was the result I had been trying to produce with four server changes.

The smaller app gave me a route the destination accepted without first asking me to create another named account. The fresh browser window prevented the old verification session from being carried into the new connection.

Its obfuscated, HTTP/3-based transport handled the route in the background. What mattered on the screen was simpler: the forum opened, the prompt stayed away, and I reached the information before my appointment.

The whole attempt had changed—not merely the flag beside the VPN button.

Switching servers was not the same as starting over

After the appointment, I repeated the test to make sure I understood it.

First, I opened the forum on my normal connection and signed into the original account.

The age prompt appeared.

I left the tab open, connected through the smaller app, and refreshed.

The prompt remained.

Then I closed the tab, opened a fresh private window while the VPN was already connected, and loaded the public thread without the old account session.

The page opened.

That comparison settled the question.

The VPN changed the public IP in both attempts. The failed attempt still carried the account and browser session that had already been placed behind the age gate. The successful attempt arrived through the new route without bringing that state along.

This is why age verification can appear to follow someone after a server switch.

It may be following the account or session rather than the physical location.

Some age decisions are meant to follow the account

There is also a difference between an uncompleted prompt and a finished verification.

When a person completes an age check, a platform may deliberately store the resulting age status with the account. Reddit, for example, says it can retain the verified age and status rather than the submitted ID or selfie. (Reddit)

That prevents the platform from asking for proof on every visit.

In that situation, changing VPN servers should not erase the result. The service is remembering an account attribute, not estimating age from the latest country.

The privacy question is therefore not simply whether a record exists. It is what the record contains.

UK data-protection guidance encourages age-assurance systems to collect the minimum necessary information and retain a simple threshold result instead of an identity document when that is enough. (Org)

That is far better than repeatedly storing passports or face images.

It also means the age status can remain attached to the account after the IP address changes.

A VPN changes the route. It does not rewrite information already stored inside a platform account.

The next page revealed another kind of persistence

After reading the discussion, I opened an article linked from the thread.

The app’s blocked-request counter increased as the page loaded.

Some background connections matched advertising and tracking services and were filtered before they completed.

I could see the counter changing, but I could not inspect the service’s internal filtering rules or determine the purpose of every blocked request.

That was not what removed the age prompt. The accepted route and fresh session had already completed the immediate task.

It was useful for a different reason.

The age gate had shown how easily information can persist when someone assumes that changing an IP creates a new identity. The counter showed that other services were also trying to participate after the page opened.

The smaller app helped at both ends of the visit: less identity required before connecting, then fewer unnecessary background requests during the session.

The old session mattered more than the new country

The service has fewer locations, a shorter public history, and fewer independent ratings than the established provider I tried first.

Someone who regularly needs a precise exit city may still prefer the larger network.

My problem had not been a shortage of countries.

The established provider moved the same account and browser session through four of them. The age-verification screen remained because the signals that mattered travelled with me.

The smaller app made the successful sequence natural: connect through an accepted route first, then begin a clean visit without creating another conventional account.

Changing servers altered the address the website saw.

The age check disappeared only when I stopped carrying the old session across the border.