The Android build of Qubetics Wallet, which includes the dVPN feature, has been submitted multiple times to the Google Play Store for approval. Even though the feature is fully developed, tested, and working as expected, the app has not been approved.
The main reason for this is Google Play’s strict enforcement of its Vpn Service policy. This policy controls how apps are allowed to use VPN functionality on Android, and it has become the key blocker in getting the build approved.
This piece explains what happened during the submission process, including the timeline of submissions and responses from Google, the exact feedback received from their review team, and the actual reason behind the rejection. It also helps clarify that the issue is not with the technical implementation itself, but with how the app is classified under Google Play’s policies
How the dVPN Feature Works on Android
The dVPN feature in the Qubetics Wallet is built using Android’s native VpnService API, which is the standard framework for creating VPN connections at the system level. It establishes a virtual network interface (TUN) on the device, allowing internet traffic to pass through a secure and controlled tunnel.
The implementation is based on:
- Android VpnService
- A device-level virtual network interface (TUN)
- Encrypted routing of network traffic through decentralized nodes
Because of this setup, the app creates a system-level VPN tunnel that routes device traffic through the VPN layer. It also requires the android.permission.BIND_VPN_SERVICE permission to function correctly.
From Android’s perspective, this behaves like a full device-level VPN implementation, even though it exists as a feature within a broader wallet application.
Submission Timeline and Process
The Android build with dVPN was submitted multiple times, but each attempt resulted in rejection from Google Play. Despite making several adjustments, the feedback remained unchanged, pointing to a deeper policy-level issue rather than a submission error.
Initial Submission
The first version of the Android build (version code 17) was submitted with the dVPN feature fully integrated using Android’s VpnService. The feature was complete, functional, and included as part of the app’s core capabilities at the time of submission through the Play Console.
First Review Outcome
The app was rejected during the first review. Google stated that the use of VpnService in the app did not qualify as a permitted use case under their policy. Their response specifically mentioned that they were unable to confirm the declared use and instructed that the VpnService component should be removed from the app manifest across all release tracks. This made it clear that the issue was not minor but related to compliance with platform rules.
Follow-Up Submission and Changes
After the rejection, multiple changes were made to try and align with Google Play requirements. The VpnService declaration form was updated, and different core functionality options were tested to see if classification was the issue. The app category was also adjusted toward network and connectivity-related use cases.
Additional clarifications were provided regarding how the VPN works, including whether it acts as a general-purpose service and whether traffic is routed outside the app. The Play Store listing was improved to better explain the feature, and it was clearly stated that no user data is collected and no traffic is manipulated or monetized.
Second Review Outcome
Even after all these updates, the app was rejected again with the exact same response. Google repeated that the use of VpnService is not a permitted use case and that they could not confirm its validity under their policy. This confirmed that the rejection was due to a strict policy constraint rather than issues with the submission itself.
Google Play Policy Restrictions on VPN Usage
One of the main reasons behind the rejection is Google Play’s strict policy around the use of VpnService. According to their guidelines, only apps where VPN is the core functionality are allowed to create a secure, device-level tunnel using this API.
Google also limits VPN usage to specific types of apps. These include parental control apps, enterprise or device management tools, device security applications, browsers, and carrier connectivity services. Apps that clearly fall within these categories are considered compliant.
However, any app that does not fit into these approved categories but still uses VpnService is treated as non-compliant. This means that even if the implementation is technically correct and secure, it will still be rejected if the app’s primary purpose does not match Google’s defined use cases for VPN functionality.
Root Cause Of The Rejection
The core reason behind the rejection comes down to a mismatch between how the app is built and how it is classified on Google Play. While the technical implementation clearly behaves like a VPN, the app itself is not positioned as one.
Api Usage Vs App Classification
On the technical side, the app uses Android’s VpnService, which means it is treated as a device-level VPN by the operating system. This allows it to create a secure tunnel and route traffic just like any standard VPN app.
However, from a product and listing perspective, the app is categorized as a crypto wallet, not a VPN application. Because of this, the dVPN feature is seen as an additional or secondary feature rather than the main purpose of the app.
This difference creates a conflict. Technically, the app behaves like a full VPN, but from Google Play’s point of view, it is not classified as one. That misalignment is what ultimately leads to the rejection.
The Core Conflict
When we look at Google’s requirements versus how the app is actually built, the issue becomes much clearer. For an app to use VpnService, VPN must be its core functionality, and it must fall under one of the permitted categories defined by Google. In this case, neither of those conditions is met.
The app does implement a full device-level VPN using VpnService, which technically satisfies the implementation requirement. However, since the app is not positioned as a VPN-first product and does not fall under approved categories like security tools or enterprise solutions, it fails to meet the policy criteria.
Because of this, two key outcomes arise. First, the VPN usage is classified as non-permitted by Google. Second, the rejection continues regardless of any changes made to metadata, declarations, or explanations during submission. This confirms that the issue is not about how the app is presented, but about how it fundamentally aligns with Google Play’s policy requirements.
Key Takeaways From The Review Process
The review process clearly showed a consistent pattern across all submissions. Despite multiple updates and attempts to align with Google Play requirements, the outcome did not change, indicating that the issue goes beyond surface-level fixes.
- Consistent rejections across all submissions
Every version of the app submitted with the dVPN feature was rejected. Even after making several adjustments, the outcome remained the same, which shows that the issue is not tied to a specific build or version. - No signs of metadata or technical issues
There was no feedback suggesting problems with the app’s functionality, code, or Play Store listing. This confirms that the implementation itself is stable and not the cause of rejection. - Identical feedback from Google each time
The response from Google remained unchanged across review cycles. This consistency strongly indicates that the rejection is based on a fixed policy rule rather than something that can be resolved through clarification or updates. - Direct instruction to remove VpnService
Google explicitly instructed that the VpnService component should be removed from the app manifest. This is a clear indication that the current use of VPN functionality is not acceptable under their guidelines. - Policy-level limitation
All of the above points confirm that the issue is driven by strict policy enforcement. The rejection is not due to how the app is built, but because of how it is classified and how that classification conflicts with Google Play’s VPN usage rules.
Potential Risks And Challenges
The current situation does not just block the release, it also introduces ongoing risks if the same approach is continued. Based on Google’s responses, it’s clear that this is not a one-time rejection but something that will persist unless changes are made.
Ongoing Rejection Risk
If the app is resubmitted with the same architecture and use of VpnService, it will continue to be rejected. Since the issue is rooted in policy and not implementation, no amount of minor adjustments or resubmission attempts will change the outcome. This means that continuing with the current setup will only lead to repeated rejections.
Risk Of Policy Enforcement
Google has also explicitly warned that the app must comply with their policies or it may face further enforcement actions. This raises additional concerns beyond just rejection.
- Risk of delisting existing versions
If Google determines ongoing non-compliance, even currently live versions of the app could be removed from the Play Store. - Increased scrutiny on future submissions
Future updates or new releases may undergo stricter review processes, making approvals more difficult and time-consuming.
Overall, this is not just a release blocker but a broader compliance risk that needs to be addressed carefully.
Operational Status
At this stage, the dVPN feature is fully developed, tested, and working as intended. From a technical perspective, there are no issues with the implementation, and the feature is ready for deployment.
However, the Android build has been rejected on the Google Play Store due to policy constraints. The primary blocker is Google’s enforcement of the VpnService policy, which does not allow the current implementation under the app’s classification.
In simple terms, the product is ready from a development standpoint, but it cannot be published on the Play Store in its current form because of policy restrictions.
Final Thoughts
The Android dVPN build is currently blocked due to strict enforcement of Google Play’s VpnService policy, particularly around how VPN functionality is classified within the application. While the feature itself is technically sound and fully functional, it does not meet the specific criteria required for permitted use of VpnService under Google’s guidelines.
This limitation is not related to the quality of the implementation, but rather to policy restrictions that define when and how VPN capabilities can be used within an app. As a result, the current approach is not eligible for approval in its existing form.
At this stage, the team is actively evaluating alternative approaches to address this constraint. Work is ongoing to identify a compliant solution that aligns with Google Play requirements and enables successful deployment.