This page is for founders, agencies, and IT shops packaging Klox under their own name. It is not a consumer setup guide — end users still download your app build and press Connect.
Export Compliance may appear in your stack — website, comments, installers, or admin tools. None of that replaces the VPN protocol or adds a secret "Export Compliance mode" inside the tunnel.
We keep commercial facts upfront: consumer pricing reference is $2.83/month on the yearly plan with 7-day money-back on your first purchase; partner economics live on /white-label and /reseller.
White-label VPN partners often ask how Export Compliance fits next to a branded Klox client. Short answer: branding, billing, and support are yours; the tunnel is still WireGuard, OpenVPN, OpenConnect, and Shadowsocks on five devices.
Looking for a reliable VPN?
KloxVPN — from $2.83/month. Apps for every device.
What Export Compliance is in your stack
Keep marketing, engineering, and support in one thread when `Export Compliance` changes. Silent renames cause refund spikes.
It is not a request for a new protocol. Klox white-label ships the same four-protocol core consumers get.
Partners grep builds, store listings, and support macros for strings like `Export Compliance`. That is a packaging question: does the name still ship, should it be renamed, or removed?
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
Run quarterly content audits on blog posts that mention `Export Compliance` so partners do not contradict each other.
- 1Skim the diagram above.
- 2Do the numbered steps once on your real network.
- 3Use the FAQ if a sentence was too long.
- 4Follow one related article — not ten tabs.
How to read this page
| Surface | Must match | Lie | Who quotes it |
|---|---|---|---|
| App Store Connect encryption questions | The IPA encrypts user traffic | No encryption / flashlight | Reviewer, reject notes |
| ITSAppUsesNonExemptEncryption | Counsel plus the binary you ship | false because HTTPS exists | Upload, review notes |
| Listing / What's New | Encrypted tunnel, named protocols you ship | Military-grade with no paperwork | Screenshot pack |
| Privacy nutrition labels | Data types you actually collect | Encryption as a nutrition label tick | Reviewer |
| Support macro | We use encryption; counsel owns filings | Here is our CCATS from a blog | Ticket, App Review reply |
A VPN encrypts packets. Ticking no encryption is how Review opens the IPA and laughs.
— KloxVPN operator notes
Cloudflare Learning: What is a VPN?
Wikipedia: Virtual private network
NordVPN on the App Store (competitor specimen of a VPN that already exists as an encrypted product)
Store vs tunnel
App Store screenshots and Play listing text are marketing surfaces. The tunnel handshake is engineering. Keep tickets separated.
Document which version removed or renamed `Export Compliance` so SEO pages like this one stay truthful.
When users mention Export Compliance
If a subscriber cites `Export Compliance` in a ticket, clarify whether they mean your website, your installer, or a VPN error message.
When unsure, link to /white-label instead of improvising specs in sales email.
What the tunnel still does
Store reviewers compare screenshots to real behavior. Mislabelled `Export Compliance` strings are an easy rejection reason.
Keep marketing, engineering, and support in one thread when `Export Compliance` changes. Silent renames cause refund spikes.
You inherit server capacity, protocol maintenance, and core app updates from Klox infrastructure. You own front-line support and brand promise.
Regardless of brand paint, the client wraps traffic the same way: encrypted tunnel to your chosen server, DNS through the tunnel when configured, kill switch optional per platform.
When unsure, link to /white-label instead of improvising specs in sales email.
Device cap
five devices per subscription is still enforced. Your pricing page should say so clearly.
Reseller and white-label paths differ; pick one story on your homepage.
Protocol choice
WireGuard first, OpenVPN fallback — same as consumer. Document that in partner FAQs.
Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.
Branding checklist around Export Compliance
Confirm `Export Compliance` still appears where you expect: installer metadata, about screen, support templates, and marketing site.
Keep /download logic in mind: consumer links on your domain should point to your build, not klox.app, unless that is intentional.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
Reseller and white-label paths differ; pick one story on your homepage.
Store reviewers compare screenshots to real behavior. Mislabelled `Export Compliance` strings are an easy rejection reason.
Comments and CMS plugins
Some partners embed comment systems or CMS tools named `Export Compliance`. That is website plumbing, not VPN configuration.
Run quarterly content audits on blog posts that mention `Export Compliance` so partners do not contradict each other.
2FA and admin panels
Protect reseller panels separately. See admin 2FA checklist if you have not locked down logins.
Keep marketing, engineering, and support in one thread when `Export Compliance` changes. Silent renames cause refund spikes.
Support scripts that work
Escalate tunnel failures to infrastructure. Escalate storefront or installer naming to your release manager.
When unsure, link to /white-label instead of improvising specs in sales email.
Reseller and white-label paths differ; pick one story on your homepage.
Never tell a user to edit Linux sysctls because a partner string appeared in a log — that is a different team.
Ask: OS, app version, protocol, and whether Connect ever worked on another network. Only then dig into build strings like `Export Compliance`.
Refund policy
Mirror 7-day money-back on your first purchase in your terms or explain differences in writing before checkout.
When unsure, link to /white-label instead of improvising specs in sales email.
Launch week
Use launch checklist so `Export Compliance` questions do not land on day one.
Document which version removed or renamed `Export Compliance` so SEO pages like this one stay truthful.
What not to promise
Run quarterly content audits on blog posts that mention `Export Compliance` so partners do not contradict each other.
Point enterprise buyers to /trust-center for what Klox publishes today, then add your own policies honestly.
Store reviewers compare screenshots to real behavior. Mislabelled `Export Compliance` strings are an easy rejection reason.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
White-label is speed to market with a proven tunnel — not a license to invent physics.
Competitor comparisons
Compare features you ship. Avoid review-farm copy; it ages badly and triggers store rejection.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
Next step
Talk to sales via /white-label when you are ready to ship glass with your logo.
Store reviewers compare screenshots to real behavior. Mislabelled `Export Compliance` strings are an easy rejection reason.
Release checklist when Export Compliance appears in builds
Run quarterly content audits on blog posts that mention `Export Compliance` so partners do not contradict each other.
Update release notes if `Export Compliance` is user-visible.
Search your repo and CI artifacts for `Export Compliance` before every store submission.
Confirm billing pages still mention five devices and refund policy accurately.
Archive old screenshots so marketing does not resurrect retired strings.
App review
Apple and Google reject inconsistent VPN claims. Keep copy aligned with actual protocols.
Document which version removed or renamed `Export Compliance` so SEO pages like this one stay truthful.
Versioning
Tag builds that change `Export Compliance` so support can map tickets to releases.
When unsure, link to /white-label instead of improvising specs in sales email.
Partner FAQ snippets
Keep marketing, engineering, and support in one thread when `Export Compliance` changes. Silent renames cause refund spikes.
Q: Where is pricing? A: You set retail; reference $2.83/month on the yearly plan only if you mirror consumer tiers.
Q: Can we sell unlimited devices? A: Only if your commercial plan allows it; default is five devices.
Q: Does `Export Compliance` change encryption? A: No. WireGuard, OpenVPN, OpenConnect, and Shadowsocks still powers the tunnel.
When unsure, link to /white-label instead of improvising specs in sales email.
Sales
Point enterprise buyers to /trust-center for published policies.
Reseller and white-label paths differ; pick one story on your homepage.
Reseller
Reseller program if you want volume without full white-label.
Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.
Long-term maintenance
Schedule quarterly reviews of strings like `Export Compliance` across website, app, and support macros.
Keep a single internal doc listing approved product claims.
When Klox updates core apps, regression-test your branded build before wide release.
Collect user feedback on confusing labels — rename in the next release rather than debating in chat.
Reseller and white-label paths differ; pick one story on your homepage.
Branding
Run quarterly content audits on blog posts that mention `Export Compliance` so partners do not contradict each other.
Contact
White-label for partnership questions.
Keep marketing, engineering, and support in one thread when `Export Compliance` changes. Silent renames cause refund spikes.
Key Takeaways
Key takeaway: Export Compliance is part of your brand or stack — not a new tunnel protocol. Klox white-label still ships WireGuard, OpenVPN, OpenConnect, and Shadowsocks on five devices.
White-label · Launch checklist · Download reference app
Document naming decisions, split support tickets, and do not promise features the core app does not have.
Related Resources
Launch your branded VPN
KloxVPN — WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, $2.83/month on the yearly plan. 7-day money-back on your first purchase.
Explore white-labelFrequently Asked Questions
KloxVPN Team
Experts in VPN infrastructure, network security, and online privacy. The KloxVPN team has been building and operating VPN services since 2019, providing consumer and white-label VPN solutions to thousands of users worldwide.