Hello everyone,
We are currently facing a frustrating situation: we are trying to publish an app that enables VPN connection with our platform, which is offered exclusively to our clients. However, our app is being repeatedly rejected under Guideline 4.3(a) - Design - Spam.
To clarify, this VPN app is strictly for enterprise use and only operates in specifically provisioned environments. It is not a generic VPN client and cannot function outside of its intended context.
- Authorship: The entire codebase is original and exclusive. The only third-party dependencies are:
- WireGuardKit: used for establishing the VPN tunnel (WireGuard protocol).
- ZIPFoundation: used for compression and decompression of packages.
- Uniqueness: No other VPN app on the market works with our solution. The only thing in common with some is the use of the WireGuard protocol. Our app includes an agent that reports device information to our platform for security policy evaluation and access control. It uses entirely proprietary authentication and authorization processes.
We cannot “do something different”: removing or changing these core functions would eliminate necessary telemetry, authentication, or restrictions, and the app would no longer fulfill its corporate purpose. It provides exactly what is needed for our enterprise clients, nothing more and nothing less.
We kindly ask for advice or insights from anyone who has faced similar issues, or from moderators/admins if there is a way to get more specific feedback or reconsideration. We are open to providing any additional information if needed.
Thank you in advance for your help and suggestions.
Best regards,
