Brand the app; the tunnel stays the same.

White-Label VPN and Export Invoices

Export Invoices can sit on a branded KloxVPN client. It does not replace WireGuard, OpenVPN, OpenConnect, Shadowsocks, the five-device limit, or the 7-day first-purchase refund.

KloxVPN Team
12 min readPublished 2022-12-23
White-Label VPN and Export Invoices
Brand the app; the tunnel stays the same.

White-label VPN partners often ask how Export Invoices 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.

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.

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.

Export Invoices may appear in your stack — website, comments, installers, or admin tools. None of that replaces the VPN protocol or adds a secret "Export Invoices mode" inside the tunnel.

Looking for a reliable VPN?

KloxVPN — from $2.83/month. Apps for every device.

View Plans

What Export Invoices is in your stack

It is not a request for a new protocol. Klox white-label ships the same four-protocol core consumers get.

Keep marketing, engineering, and support in one thread when `Export Invoices` changes. Silent renames cause refund spikes.

Partners grep builds, store listings, and support macros for strings like `Export Invoices`. That is a packaging question: does the name still ship, should it be renamed, or removed?

Reseller and white-label paths differ; pick one story on your homepage.

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

Download, sign in, connect WireGuard, fall back to OpenVPN
Install from klox.app/download. WireGuard first. OpenVPN if UDP is blocked.

    How to read this page

  1. 1Skim the diagram above.
  2. 2Do the numbered steps once on your real network.
  3. 3Use the FAQ if a sentence was too long.
  4. 4Follow one related article — not ten tabs.
What to export, who it is for, what to omit. Confirm tax fields with counsel. Not a Klox SLA for partner brands.
ArtifactWho it is forWhat it must not include
User PDFBuyer, expense reportExit IPs, connection timestamps, device fingerprints if you claim no-logs
Admin CSVAccountant, year-endSame: no tunnel telemetry, no peer keys
Date-range dumpAudit folder, tax filingLive entitlement secrets, support ticket bodies
Store IAPApple or Google receiptA PDF you invent that pretends you charged them
Credit noteRefundsSilent reuse of the original invoice number

The accountant wants last year as a CSV. The user wants a PDF. Neither should include an exit IP.

— KloxVPN operator notes

Cloudflare Learning: What is a VPN?

Wikipedia: Virtual private network

IETF RFC 8446 (TLS 1.3)

NordVPN: get a receipt or invoice (competitor specimen)

Store vs tunnel

App Store screenshots and Play listing text are marketing surfaces. The tunnel handshake is engineering. Keep tickets separated.

When unsure, link to /white-label instead of improvising specs in sales email.

When users mention Export Invoices

If a subscriber cites `Export Invoices` in a ticket, clarify whether they mean your website, your installer, or a VPN error message.

Document which version removed or renamed `Export Invoices` so SEO pages like this one stay truthful.

What the tunnel still does

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.

Store reviewers compare screenshots to real behavior. Mislabelled `Export Invoices` strings are an easy rejection reason.

Run quarterly content audits on blog posts that mention `Export Invoices` so partners do not contradict each other.

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

Do not promise features Klox does not ship — extra protocols, unlimited devices beyond plan limits, or compliance badges you cannot show.

Device cap

five devices per subscription is still enforced. Your pricing page should say so clearly.

Run quarterly content audits on blog posts that mention `Export Invoices` so partners do not contradict each other.

Protocol choice

WireGuard first, OpenVPN fallback — same as consumer. Document that in partner FAQs.

Keep marketing, engineering, and support in one thread when `Export Invoices` changes. Silent renames cause refund spikes.

Branding checklist around Export Invoices

If you rebrand, update every surface in one release when possible. Half-old names confuse users and app review.

Keep marketing, engineering, and support in one thread when `Export Invoices` changes. Silent renames cause refund spikes.

Keep /download logic in mind: consumer links on your domain should point to your build, not klox.app, unless that is intentional.

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

Store reviewers compare screenshots to real behavior. Mislabelled `Export Invoices` strings are an easy rejection reason.

Five devices on one KloxVPN plan
One account, five devices online at the same time.

Comments and CMS plugins

Some partners embed comment systems or CMS tools named `Export Invoices`. That is website plumbing, not VPN configuration.

Reseller and white-label paths differ; pick one story on your homepage.

2FA and admin panels

Protect reseller panels separately. See admin 2FA checklist if you have not locked down logins.

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

Support scripts that work

When unsure, link to /white-label instead of improvising specs in sales email.

Never tell a user to edit Linux sysctls because a partner string appeared in a log — that is a different team.

Escalate tunnel failures to infrastructure. Escalate storefront or installer naming to your release manager.

Keep marketing, engineering, and support in one thread when `Export Invoices` changes. Silent renames cause refund spikes.

Ask: OS, app version, protocol, and whether Connect ever worked on another network. Only then dig into build strings like `Export Invoices`.

Refund policy

Mirror 7-day money-back on your first purchase in your terms or explain differences in writing before checkout.

Document which version removed or renamed `Export Invoices` so SEO pages like this one stay truthful.

Launch week

Use launch checklist so `Export Invoices` questions do not land on day one.

When unsure, link to /white-label instead of improvising specs in sales email.

What not to promise

White-label is speed to market with a proven tunnel — not a license to invent physics.

Keep marketing, engineering, and support in one thread when `Export Invoices` changes. Silent renames cause refund spikes.

No invented "Export Invoices encryption." No secret city counts. No SOC 2 badge unless you actually hold one.

Reseller and white-label paths differ; pick one story on your homepage.

Run quarterly content audits on blog posts that mention `Export Invoices` so partners do not contradict each other.

Competitor comparisons

Compare features you ship. Avoid review-farm copy; it ages badly and triggers store rejection.

Store reviewers compare screenshots to real behavior. Mislabelled `Export Invoices` strings are an easy rejection reason.

Next step

Talk to sales via /white-label when you are ready to ship glass with your logo.

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

Release checklist when Export Invoices appears in builds

Update release notes if `Export Invoices` is user-visible.

Confirm billing pages still mention five devices and refund policy accurately.

Search your repo and CI artifacts for `Export Invoices` before every store submission.

Store reviewers compare screenshots to real behavior. Mislabelled `Export Invoices` strings are an easy rejection reason.

Keep marketing, engineering, and support in one thread when `Export Invoices` changes. Silent renames cause refund spikes.

App review

Apple and Google reject inconsistent VPN claims. Keep copy aligned with actual protocols.

When unsure, link to /white-label instead of improvising specs in sales email.

Versioning

Tag builds that change `Export Invoices` so support can map tickets to releases.

Document which version removed or renamed `Export Invoices` so SEO pages like this one stay truthful.

Partner FAQ snippets

Q: Does `Export Invoices` change encryption? A: No. WireGuard, OpenVPN, OpenConnect, and Shadowsocks still powers the tunnel.

Q: Refunds? A: Honor 7-day money-back on your first purchase or publish your own policy clearly.

Store reviewers compare screenshots to real behavior. Mislabelled `Export Invoices` strings are an easy rejection reason.

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

Q: Do we operate servers? A: You brand and support; infrastructure follows your Klox agreement.

Sales

Point enterprise buyers to /trust-center for published policies.

Run quarterly content audits on blog posts that mention `Export Invoices` so partners do not contradict each other.

Reseller

Reseller program if you want volume without full white-label.

Keep marketing, engineering, and support in one thread when `Export Invoices` changes. Silent renames cause refund spikes.

Long-term maintenance

Train new support staff on tunnel vs branding tickets in the first week.

When Klox updates core apps, regression-test your branded build before wide release.

Reseller and white-label paths differ; pick one story on your homepage.

Store reviewers compare screenshots to real behavior. Mislabelled `Export Invoices` strings are an easy rejection reason.

Keep marketing, engineering, and support in one thread when `Export Invoices` changes. Silent renames cause refund spikes.

Branding

Branding checklist

Reseller and white-label paths differ; pick one story on your homepage.

Contact

White-label for partnership questions.

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

Key Takeaways

Document naming decisions, split support tickets, and do not promise features the core app does not have.

Key takeaway: Export Invoices 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

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-label

Frequently Asked Questions

No. Partner apps still use WireGuard, OpenVPN, OpenConnect, and Shadowsocks.

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.