Karvan

Privacy Policy

Effective 14 September 2026. Karvan is operated by Forgewake LLC.

This policy explains what Karvan (“the App”) collects, why, and what you can do about it. Forgewake LLC, a Wyoming limited liability company, is the data controller.

---

1. What we do not do

Karvan does not record, inspect, or store the content of your network traffic, the sites or services you reach, your DNS queries, or your browsing history. We do not keep records that would let us reconstruct what any person did while connected, and we cannot produce such records on request because they are never created.

We do not sell personal data, and we do not share it for cross-context behavioural advertising beyond the advertising described in section 5.

2. What we collect

Category	Data	Why
Account	An anonymous account identifier generated on first launch. No name, e-mail address, or phone number is required to use the App.	To keep your subscription, earned time, and settings attached to you across launches.
Sign-in (optional)	If you choose to sign in with Apple or Google: the identifier that provider gives us, and the e-mail address it releases. With Apple you may choose to hide your address, in which case we only ever see Apple's relay address. There is no password to set, because we do not offer one.	To let you carry premium to another device, and to recover it after a reinstall.
Connection key	Your device's public key. The matching private key is generated on your device and never leaves it — we could not obtain it if we wanted to.	To admit your device to the chosen location.
Connection metadata	The location you selected, the internal address assigned to your device, connect and disconnect times, session length, and total bytes carried. Not the traffic itself.	To run the service, balance load, apply fair-use and plan limits, and investigate faults.
Purchases	Subscription status and store transaction identifiers, received from the app stores through our subscription processor. We never see your card details.	To unlock premium and to restore it on a new device.
Advertising	Your device's advertising identifier and ad interaction events, where permitted. On iOS this only happens if you allow tracking when asked.	To show ads to people on the free tier and to grant rewarded premium time.
Diagnostics	Crash reports, app version, device model, operating system version, and language.	To find and fix faults.
Notifications	A push token, if you allow notifications.	To send service messages you have opted into.

3. Legal bases (EEA / UK)

• Performance of a contract — account, connection key, connection metadata, and purchases: without these the App cannot work.
• Consent — advertising identifiers, tracking-based advertising, push notifications, and signing in with a provider. You may withdraw consent at any time in your device settings, and you can sign out or delete the account whenever you like.
• Legitimate interests — diagnostics, and preventing fraud and abuse of the service.

4. Processors we use

We use a small number of providers, each acting on our instructions under a data processing agreement:

• Supabase — account records and the connection control plane.
• Google Firebase — crash reporting, aggregate analytics, and push delivery.
• Google AdMob — advertising on the free tier.
• RevenueCat, with Apple and Google — subscription processing.
• TikTok — install attribution, only where you have allowed tracking.
• Apple and Google — identity providers, if you choose to sign in with one.
• Independent data-centre operators who host the locations you connect through.

5. Advertising

People on the free tier see ads, and may watch a short video to earn premium time. On iOS we ask for permission through App Tracking Transparency before any tracking-based advertising; if you decline, ads still appear but are not personalised. You can reset or limit your advertising identifier in your device settings at any time. Subscribers see no ads.

6. International transfers

We are based in the United States and our providers operate globally, so your data may be processed outside your country. Where data leaves the EEA or the UK, transfers rely on the European Commission's Standard Contractual Clauses or an equivalent safeguard.

7. How long we keep it

• Connection metadata — kept briefly for operations and troubleshooting, then deleted or aggregated beyond recognition.
• Account, key, and balance records — kept while your account exists, and removed when you delete it.
• Transaction records — retained as long as tax and accounting law requires.

8. Your rights

Depending on where you live, you may request access to your data, correction, deletion, a copy in portable form, restriction of or objection to processing, and — where processing rests on consent — withdrawal of that consent. Exercising a right never costs you service or money.

You can delete your account and its data yourself: Settings → Profile → Delete account. See the account deletion page for what that removes. For anything else, write to karvan@forgewake.com; we answer within 30 days. If you are in the EEA or the UK you may also complain to your local supervisory authority.

9. Security

Your traffic is encrypted between your device and the location you choose, using modern cryptography with keys generated on your device. Traffic to our own backend uses TLS. Access to production systems is limited to those who need it. No system is perfectly secure, but we hold ourselves to current practice and design so that the data we could lose is as thin as possible.

10. Children

Karvan is not directed at children under 13, or under the minimum age of consent where you live, and we do not knowingly collect their data. If you believe a child has provided us data, write to us and we will remove it.

11. Changes

We may update this policy. The effective date above always reflects the current version, and material changes are announced in the App before they take effect.