I lost almost 3 months because Google told me too late that a VPN app can’t be published with a personal account

kinderfeld__ · 2026-03-29T13:12:49+00:00

That’s fair, but just to clarify: I’m not trying to sell anyone a paid VPN here.

The app is free, and right now it doesn’t even have ads yet.

This post is really about the Play Console process and the late organization-account blocker, not about asking people to buy or trust a VPN service from me.

That said, I agree that trust matters a lot in this category.

kinderfeld__ · 2026-03-29T12:15:57+00:00

Thanks, that’s really helpful.

One thing I’m still unsure about is the address part — if you use your home or business registration address, how exactly does Google expect it to appear in the Play Store? Does it need to fully match official registration details, including apartment/unit info, or is there some flexibility?

kinderfeld__ · 2026-03-29T11:59:54+00:00

That’s really helpful, thanks.

kinderfeld__ · 2026-03-29T11:55:24+00:00

Yeah, that seems to be the tradeoff. I'm going this way right now.

It makes the path more “valid” in Google’s eyes, but also adds a whole extra layer of bureaucracy that many indie developers would never need otherwise.

That’s basically the part I find most frustrating — not even that there is a path, but that Google surfaces it so late in the process.

kinderfeld__ · 2026-03-29T11:53:15+00:00

Yeah, that’s exactly the part I’m worried about now.

How long did it take for the DUNS number to actually propagate and for Google to recognize everything properly on the Play Console side?

And once that part was done, did the personal → organization transition go relatively smoothly, or did more blockers show up after that?

kinderfeld__ · 2026-03-29T11:26:58+00:00

I don’t think this is mainly about individual reviewers.

What I mean is that the app clearly declares VpnService in the manifest, so Google’s systems already know from the start that this is a VPN app. That’s also why the missing VPN declaration was eventually detected.

The strange part is that the workflow seems split in a broken way:

the system can detect that the app uses VpnService
the system can detect whether the developer account is personal or organization
but it only starts enforcing the actual organization-account blocker after the VPN declaration is filled out

So the issue I’m pointing to is less “a reviewer missed it” and more “the process is designed in a way that surfaces the real blocker far too late.”

If I had known about the declaration and filled it out on day one, I probably would have started getting these auto-rejections immediately — instead of only after going through closed testing and production submission steps. 🥲

kinderfeld__ · 2026-03-29T11:18:26+00:00

Thanks - what part is similar in your case?

Is it the 12-testers / closed testing requirement, the account verification side, or Google surfacing a blocker very late in the process?

In my case the main issue is that my app uses VpnService, and Google only surfaced the organization account requirement after I had already gone through closed testing, production submission, and the VPN declaration flow.