Privacy Policy

1. Scope and current status

This Privacy Policy applies to the VPN - Fast & Unlimited website, iOS app, VPN service, backend API, and related support communications operated by Jarski LLC.

The product is currently under development. The current iOS Release build does not contain production token acquisition and therefore does not provide a completed consumer connection flow. Development builds can use a manually supplied, short-lived access token to test provisioning. Planned features are identified below and should not be understood as currently active.

2. Information stored on the device

Device identifier

The app generates a random UUID to identify the VPN device. It stores that identifier in the iOS Keychain and uses it when requesting VPN provisioning. It is not an advertising identifier and is not derived from your name, email address, Apple Account, or hardware serial number.

WireGuard keys

The app generates a WireGuard private key and stores it in the iOS Keychain with access available after the device has first been unlocked. The corresponding public key is derived on the device and sent to the backend during provisioning. The private key is not sent to the VPNPassport backend.

In the current development implementation, the app also serializes the complete WireGuard configuration—including the private key—into the configuration saved for Apple's Network Extension framework so that the packet-tunnel extension can start the connection. Moving this secret-bearing configuration to a shared, device-only Keychain item is planned but has not yet been implemented.

VPN configuration

The app receives and processes an assigned internal VPN address, VPN server public key, server endpoint, allowed routes, DNS server address, persistent-keepalive value, and region. These values are used to construct and save the system VPN configuration. The app also observes the connection status reported by Apple's Network Extension framework.

3. Information sent to and stored by the backend

A provisioning request currently sends the random device identifier, WireGuard public key, requested region identifier, and a bearer access token over HTTPS. The backend may store:

• the device identifier;
• the WireGuard public key and a cryptographic fingerprint of that public key;
• the current public-key version and device status;
• the assigned internal VPN address and region;
• record creation and update timestamps; and
• the relationship between the device and its regional VPN connection.

The backend uses this information to prevent conflicting device/key registrations, allocate an internal VPN address, configure the WireGuard peer, return the connection settings, support additional regions, and revoke regional access.

4. Anonymous customer, entitlement, and installation records

The current development database schema includes records for anonymous customers, entitlements, app installations, VPN devices, versioned public keys, authentication challenges, token grants, and JWT signing-key metadata.

For devices migrated into or created through the current development flow, the backend creates random internal customer, entitlement, and installation identifiers. These records contain status and version fields, timestamps, the iOS platform and app bundle identifier, and links to the VPN device. Development entitlements are marked unverified and installations are marked pending. They do not represent a verified purchase or a completed consumer account.

The schema contains fields reserved for future App Attest keys and counters, one-time authentication challenges, token identifiers, scopes, regions, expiration, and signing-key metadata. The repository does not yet implement production App Attest, DeviceCheck, StoreKit subscription verification, consumer JWT issuance, or an email/password account system, so those future fields are not currently populated through a consumer authentication flow.

5. Authentication information

The backend currently supports short-lived JWT bearer tokens for development provisioning. A token contains a device subject and issue and expiration times, is signed by the backend, and expires after approximately 15 minutes by default. The iOS development build reads a manually supplied token from its launch environment and sends it in the Authorization header. The app does not currently save that token in its Keychain or database.

The backend also uses a separate server-side administrative API key for protected testing and device revocation. That API key and the JWT signing secret are stored in a restricted server environment file and are not embedded in the iOS app or this website.

6. VPN activity we do not log

VPN - Fast & Unlimited is not designed to log or persist:

• the contents of VPN traffic;
• DNS queries made through the VPN;
• browsing destinations or destination history;
• a history of websites or services visited through the VPN; or
• per-user bandwidth usage or bandwidth history.

The WireGuard tunnel provider's library messages are disabled in production builds and remain available only in debug builds.

7. Operational and security logs

The API's per-request Uvicorn access log is disabled. Warning and error diagnostics are retained for reliability, security, and incident response and are rate-limited to 1,000 messages per 30 seconds. The primary system journal is compressed and sealed, limited to 250 MB of persistent storage and 50 MB of runtime storage, rotates files daily, and is configured for a maximum retention of 14 days.

Low-level firewall logging remains enabled. Firewall and other system logs may include packet or request metadata such as source and destination IP addresses, ports, protocol, timestamps, requested paths, and error details. The server's normal operating-system logging path may also forward journal entries to its syslog service, where separate system retention controls can apply. These logs are not intended to create VPN browsing profiles and must not include bearer tokens, device identifiers, WireGuard keys, provisioning request bodies, traffic contents, DNS queries, browsing destinations, or per-user bandwidth records.

The current Caddy configuration does not enable a separate Caddy access log. Operational configuration can change where necessary for security or reliability, but any change must remain consistent with this policy.

8. Website and support information

The current website is static. It contains no Jarski LLC analytics, advertising, tracking pixels, account login, payment form, or contact form, and it does not intentionally set cookies. When the site is hosted, infrastructure providers may process ordinary delivery and security information such as IP address, timestamp, requested page, browser information, and security signals.

If you contact us by email, we receive your email address and whatever information you choose to provide. Do not send passwords, private keys, access tokens, or other sensitive credentials.

9. How information is used

We use the information described above to develop, provide, secure, test, and maintain the service; provision and revoke VPN peers; assign and return regional VPN settings; prevent duplicate or conflicting registrations; enforce rate limits and future device-access rules; diagnose failures; respond to support requests; and comply with applicable legal obligations.

We do not sell personal information. The current product does not include advertising SDKs, behavioral analytics, or cross-app tracking.

10. Service providers and disclosures

Current project infrastructure includes Cloudflare for domain, proxy, and email-routing services and DigitalOcean for API and VPN server hosting. These providers may process technical information on our behalf under their own terms and policies. Apple provides the iOS platform, Keychain, and Network Extension framework; future distribution, App Attest, DeviceCheck, or StoreKit functionality would involve Apple as described when those features are implemented.

We may disclose information when reasonably necessary to comply with law, protect users or the service, investigate abuse or security incidents, or complete a business transaction subject to appropriate safeguards. We do not provide VPN browsing activity to advertisers because the service is not designed to collect that activity.

11. Retention and deletion

The current backend does not yet implement a final consumer data-retention schedule or self-service deletion workflow. Device, public-key, anonymous customer, entitlement, installation, and connection records may remain in SQLite until they are administratively removed or a future retention policy is implemented. Revoking one regional connection currently removes that regional connection record but does not necessarily remove the global device or its related development identity records.

Daily SQLite backups are configured for 30-day retention by default. Diagnostic journal retention is described above; forwarded system logs can follow separate operating-system retention. Support-email retention has not yet been finalized.

You may contact us to ask about or request deletion of information associated with you or your device. We may need information sufficient to verify the request, and deletion can be limited where records are required for security, legal compliance, dispute resolution, or protection against abuse. Removing device records will end related VPN access.

12. Planned production model

The planned initial consumer model is accountless: it is not expected to require a customer email address or password solely to use an Apple-platform subscription. The planned backend would use anonymous customer and installation identifiers, Apple-verified subscription evidence, and App Attest—and potentially DeviceCheck as a secondary abuse signal—to determine whether an installation may receive a short-lived, device-bound provisioning token.

If implemented, this would involve processing Apple attestation key identifiers, public verification material, assertion counters, one-time challenges, normalized subscription product and status information, entitlement versions, and token metadata. It would not authorize collecting browsing history or traffic contents. This model is planned, not active, and this policy will be updated before production use to reflect the final Apple and subscription implementation.

13. Security

We use measures intended to protect information, including HTTPS, restricted server credentials, iOS Keychain storage, database foreign-key and uniqueness controls, rate limiting, firewall controls, limited operational logging, and backups. The current development architecture still has known work remaining, including moving the secret-bearing tunnel configuration out of Network Extension preferences and completing production authentication and Apple signing capabilities. No system can guarantee absolute security.

14. Changes and contact

We may update this policy as the product, production deployment, service providers, and legal requirements evolve. The date above identifies the latest revision. Material changes will be presented through an appropriate notice when required.

Privacy questions or requests may be sent to admin@getvpnpassport.com.

Jarski LLC
Email: admin@getvpnpassport.com