As an initial solution, given that we haven't encountered many cases yet and the situation is still relatively new.
Firstly, if you've bought an account from someone: the company may disable your application, so don't publish your app directly, publish it on test first.
Buying an account or the method of opening it may be one of the reasons.
Secondly, if you've opened an account and you published your app, don't buy a test from someone else. Try to share with some people you know, not your family, and they should be in separated places.
Regarding your application, make sure you've filled in all the information as it is, as this is the main problem in this situation. Google start using artificial intelligence for review.
Initially, any opened account information should not have been used before and should be accurate. It would be better if you updated all your information, including the developer's picture. Treat it as if you're dealing with something of value to you and you want it to be professional.
And I emphasize this: when you receive this notice and you're sure that your application and its permissions are correct, appeal and explain to them why your application is good, don't just complain and ask why, I personally get my google play console account reinstated with an appeal after getting terminated by high risk.
In short, there are many solutions, and the solution lies in understanding the problem. Each case is isolated, so don't compare why one account is old and not new.
Waiting for other cases with this problem.
I tried to focus on the important points: high risk = multi-account.
Firstly, if you've bought an account from someone: the company may disable your application, so don't publish your app directly, publish it on test first.
Buying an account or the method of opening it may be one of the reasons.
Secondly, if you've opened an account and you published your app, don't buy a test from someone else. Try to share with some people you know, not your family, and they should be in separated places.
Regarding your application, make sure you've filled in all the information as it is, as this is the main problem in this situation. Google start using artificial intelligence for review.
Initially, any opened account information should not have been used before and should be accurate. It would be better if you updated all your information, including the developer's picture. Treat it as if you're dealing with something of value to you and you want it to be professional.
And I emphasize this: when you receive this notice and you're sure that your application and its permissions are correct, appeal and explain to them why your application is good, don't just complain and ask why, I personally get my google play console account reinstated with an appeal after getting terminated by high risk.
In short, there are many solutions, and the solution lies in understanding the problem. Each case is isolated, so don't compare why one account is old and not new.
Waiting for other cases with this problem.
I tried to focus on the important points: high risk = multi-account.
