Privacy Policy

Effective Date: April 11, 2026  |  Last Updated: July 26, 2026

1. Who We Are

Jetseen is a residency and visa day-tracking application developed and operated by Utilities Studio ("we," "us," or "our"), based in Wyoming, United States of America. The Jetseen mobile app is currently offered on iOS. jetseen.com provides related web-based informational tools.

For privacy-related questions, contact us at: privacy@jetseen.com

2. Data We Do NOT Upload or Sell

Jetseen does not use a cloud backend for your travel records. We want to be explicit about what we do not do:

• We do not upload or store your trips, trackers, visas, citizenship records, or document attachments on our servers
• We do not upload raw GPS coordinates to our servers or analytics providers; optional GPS Auto-Entry processes location on-device and keeps only country-level detector state
• We do not use advertising SDKs, cross-app tracking, or behavioral advertising profiles
• We do not serve advertisements
• We do not sell your travel data, trip history, or document attachments to any third party
• We do not create advertising profiles or behavioural models from your travel data
• We do not use cookies for tracking (the web app may use essential cookies for functionality only)

3. Data Stored on Your Device

All data you enter into Jetseen is stored locally on your device using an on-device SQLite database. This includes:

• Trip records: Countries visited, dates, duration, purpose, accommodation names, travel notes, transit type, and entry document type
• Residency tracking rules: Rule type, countries, day thresholds, and calculation windows
• Citizenship information: Countries of citizenship, passport numbers (if you choose to enter them), and passport expiry dates
• Document attachments: Photos of travel documents, visited places, and bills/receipts that you attach to trips — stored as files on your device
• App settings: Your preferences for day counting, display, and backup configuration

Your working travel database and document attachments stay on your device. Jetseen does not send plaintext travel records to Supabase, Superwall, analytics providers, or Jetseen-operated servers. If you sign in, supported builds enable the encrypted personal-cloud backup described in Section 6; that feature stores an app-encrypted backup payload in your own iCloud or Google Drive account.

4. Device Permissions

Jetseen may request the following device permissions. Each is optional and used only for the stated purpose:

• Camera: To photograph travel documents (boarding passes, visa stamps, receipts) for attachment to trip records. Photos are stored locally on your device. We do not access your camera in the background.
• Photo Library: To select existing photos from your device for attachment to trip records. We do not scan, index, or upload your photo library.

You may deny these permissions and still use all core features of Jetseen. Document attachment is the only feature that requires these permissions.

5. Data Export and Backup

Jetseen provides the following data portability features:

• JSON Backup/Restore: You can export all your data as a JSON file and save it wherever you choose. You can restore from this file at any time.
• CSV Export: You can generate filtered CSV reports of your travel data for sharing with tax advisors or for personal records.

When you export data, the resulting file is handled by your device's native sharing mechanism. Jetseen does not retain a copy and has no visibility into where you send the file.

6. Cloud Backup (Optional)

For signed-in accounts, supported builds enable encrypted personal-cloud backup by default. Apple sign-in stores the latest encrypted backup in your personal iCloud account inside Jetseen's visible iCloud Documents container. Google sign-in stores the latest encrypted backup in your personal Google Drive appDataFolder space, including on iOS when you sign in with Google.

Cloud backups are AES-GCM encrypted by the app before upload. The backup encryption key is generated per user and escrowed in Supabase so a fresh device can restore after sign-in; this makes the backup encrypted from Apple/Google but account-recoverable, not zero-knowledge from Jetseen's backend. Cloud backups are personal-cloud copies, not Jetseen-hosted travel-history sync.

7. Accounts, Trial Sync, and Paid-Access Processing

Jetseen offers optional sign-in with Apple or Google. If you sign in, we use Supabase Authentication to store your authentication record, session, provider information, and limited account metadata used to keep your trial_start_date and paid-access state consistent across reinstalls and signed-in devices.

Your trip history, trackers, visas, citizenships, and document attachments are not stored in Supabase.

Jetseen offers a one-time Lifetime Access purchase after a 14-day free trial. Lifetime Access does not auto-renew. Your app store displays the price applicable to your region before confirmation. Payments are processed entirely by the platform through which you purchase access:

• iOS: Payments are processed by Apple through the App Store. Apple's privacy policy governs this data.

We use Superwall, a paywall management service, to present paid offers and verify paid-access status. Superwall receives a pseudonymous Jetseen account identifier plus product, entitlement, and paid-access status metadata from Apple or Google. This identifier is linked to the signed-in Jetseen account for purchase verification and restore, but not to trip data. Superwall does not receive your trips, visas, citizenships, or document attachments. Superwall's privacy policy is available at superwall.com/privacy.

We do not process, store, or have access to your payment card details, billing address, or your locally stored travel data.

8. Product Analytics

Jetseen uses limited first-party product analytics through PostHog only after you enable the in-app analytics setting. These events help us understand trial/paywall flow health and high-level feature usage.

PostHog may receive event names such as screen views, sign-in/sign-out events, backup export/restore events, trial/paywall events, sanitized runtime error events, and aggregate counts such as trip count or rule count. Runtime error events include only an error class, sanitized error name, source, recovery state, fatal flag, and stable stack-frame fingerprint. When analytics are enabled and you are signed in, PostHog uses your Jetseen account user identifier and authentication provider label. You can turn analytics off in Profile at any time. We do not send your email address, trip dates, travel notes, passport numbers, document contents, attached files, raw GPS coordinates, route parameters, raw stack traces, raw error messages, or per-trip country/travel-type details to PostHog.

Analytics are not used for advertising, sale of data, or cross-app tracking.

9. Third-Party Services

Jetseen integrates with the following third-party services, limited to the purposes described:

Service	Purpose	Data Shared
Supabase Authentication	Optional Apple/Google sign-in, session persistence, synced trial start metadata, and limited paid-access metadata	Authentication token, provider account identifier, email if provided by the sign-in provider, plus limited metadata such as trial_start_date and paid-access classification; no trip data
Apple App Store	Payment processing (iOS)	Payment handled by Apple; we receive account-linked product, transaction, and paid-access status metadata needed to verify and restore access, but no payment card details
Google Drive appDataFolder / iCloud Documents container	Default encrypted personal-cloud backup and restore for signed-in accounts	Your encrypted backup payload is stored in your own Google Drive or iCloud account according to your sign-in provider; we do not keep a server-side backup copy
Superwall	Paywall & paid-access management	Pseudonymous Jetseen account ID + product, entitlement, and paid-access status metadata
PostHog	First-party product analytics	Account/app identifier, screen and interaction events, trial/paywall events, sign-in provider label, and aggregate counts; no email, travel history, documents, passport numbers, raw coordinates, route parameters, or per-trip country details

Authentication, payment, paywall, and analytics providers do not receive your plaintext travel records, citizenship information, or document attachments. When signed-in personal-cloud backup is enabled, Apple or Google stores only the app-encrypted backup payload in your own cloud account. A third party can receive plaintext data only if you explicitly export a file and share it yourself.

10. Children's Privacy

Jetseen is not directed at individuals under the age of 18. We do not knowingly solicit children's personal data or travel records. Optional sign-in providers may process limited account data if the app is used anyway, but the product is not designed for children and should not be used by them.

11. Data Retention and Deletion

Your working travel data is stored locally on your device. If personal-cloud backup is enabled, a separate encrypted backup payload is also retained in your own iCloud or Google Drive account:

• Retention: Your data exists on your device for as long as you keep the app installed and do not delete it
• Deletion: You can delete individual trips, rules, or citizenships at any time within the app. You can delete all data at once using the "Reset App" function in Settings. Uninstalling the app removes all locally stored data permanently.

If you use optional sign-in, Supabase and the sign-in provider may retain the account record and limited authentication metadata until it is deleted under their retention policies or through our support workflow. Deleting local data or uninstalling Jetseen does not necessarily delete an encrypted personal-cloud backup or files you previously exported; those copies remain under your control in the applicable cloud or file provider.

PostHog analytics may retain product-interaction events according to the configured project retention policy. Contact us at privacy@jetseen.com if you want account-linked analytics identifiers deleted from our vendor project.

12. Data Security

Your data is protected by the security mechanisms of your device's operating system:

• On iOS: Data is protected by iOS Data Protection, which encrypts data at rest when your device is locked
• On Web: Data is stored in your browser's local storage, subject to your browser's security model

Current native builds use SQLCipher for local SQLite data and app-managed encryption for managed trip document payloads and local auto-backup JSON. User-created JSON and CSV exports remain plaintext for portability and are controlled by you after export.

We recommend that you protect your device with a passcode, biometric lock, or strong password, and keep your operating system updated.

13. International Users

Jetseen is available internationally. The core travel-tracking functionality remains local to your device, but optional sign-in, paid-access infrastructure, and personal-cloud backup may process limited account, purchase, or backup data on servers outside your country.

In particular, Supabase Authentication, Superwall, and PostHog may process account identifiers, product-interaction events, trial metadata, paid-access status, or consent-gated sanitized runtime error events on infrastructure located in the United States or other jurisdictions used by those providers. If you use signed-in cloud backup, your encrypted backup file is stored on Google or Apple's infrastructure in your own cloud account. Please review the relevant provider privacy documentation for current details.

14. Governing Law

Jetseen is operated from the State of Wyoming, United States of America. To the extent any aspect of this policy is governed by applicable law, we are committed to compliance with applicable United States federal and state privacy laws, including but not limited to the California Consumer Privacy Act (CCPA), the Children's Online Privacy Protection Act (COPPA), and any applicable Wyoming state regulations. Jetseen limits its server-side processing to the account, key-escrow, paid-access, and consented diagnostics data described above; local travel records are not stored on Jetseen-operated servers.

15. Changes to This Policy

If we make material changes to this privacy policy — particularly if we change the local-first data architecture or personal-cloud backup behavior — we will notify you through the app before the changes take effect. The "Last Updated" date at the top of this page indicates when the policy was most recently revised.

We will never retroactively change how we handle data that was created under a prior version of this policy without your explicit consent.

16. Your Rights

You control the working travel data stored on your device and any exports or personal-cloud backups held in your own accounts. You can:

• Access all your data within the app at any time
• Export all your data via JSON backup or CSV reports
• Correct any data by editing trips, rules, or citizenship records
• Delete any or all data at any time through the app
• Withdraw consent for device permissions (camera, photo library) through your device settings

You do not need to contact us to exercise any of these rights for locally stored travel data. If you used optional sign-in and want the related account record deleted, contact us at privacy@jetseen.com.

17. Contact

For questions, concerns, or requests related to this privacy policy:

Email: privacy@jetseen.com
Address: Wyoming, United States of America