TripWink Privacy Policy

Effective September 26, 2026 · Externum LLC

TripWink helps you plan trips, travelers, reservations, budgets, activities, packing and reminders. Contact admin@externum.dev with privacy questions.

Local planning remains available without an account. Optional cloud account registration is enabled for compatible updated builds. Older installed versions may require an app update to show sign-in controls.

Plans and files on your device

Trip details, traveler information you enter, budgets, checklists, imported documents and selected photos are processed and stored on your device for local planning. Importing PDF, CSV or spreadsheet lists does not upload the source document to TripWink's lookup service. Exported files and copies you share are controlled by you and their recipients. Avoid entering information you do not need for the trip.

Location, maps and vehicle lookups

Device location is optional and requested when you choose Use my location. There is no background location tracking. You can adjust the pin or enter mileage manually. Address searches and selected routing coordinates are sent through TripWink's Vercel-hosted service to HeiGIT/openrouteservice. Vehicle selections are sent to FuelEconomy.gov. These requests provide suggestions, distance and fuel estimates; they do not verify a street address.

Viewing a map loads OpenStreetMap tiles and reveals the viewed map area and network metadata to its provider. Hosting and lookup providers may process IP addresses and request metadata for service operation and security. The lookup service does not store trip plans or traveler records. See HeiGIT privacy, Vercel privacy, OpenStreetMap privacy and FuelEconomy.gov privacy.

Android document recognition

Android uses Google ML Kit to recognize text in selected images and scanned PDFs on your device. ML Kit does not send the input images or recognized text to Google for recognition. Its SDK collects installation identifiers, device and app information, feature usage, error codes and performance metrics for diagnostics and usage analytics. See Google ML Kit data disclosure. This diagnostic collection is separate from optionally uploading a trip or photo to your account.

Optional account trips

Account access uses an email address and a sign-in code, or an existing account password. Authentication emails are processed by Resend using a dedicated TripWink sending credential. Local trips upload only after you select and confirm them. Account trips may contain destinations, dates, traveler names and ages, notes, reservations, budgets, checklists and selected photos. Saved account edits synchronize while the app is open and connected; offline changes wait on the device.

Account information, private trip snapshots and photos are hosted in TripWink's dedicated Supabase project in Oregon, United States. They are scoped to the account owner; no public photo links are created. Browser sign-in tokens are memory-only. Android account sessions and cached snapshots use Android Keystore protection. On iOS, account credentials are stored using the iOS Keychain. App-private photos are not a promise of end-to-end encryption. Read Supabase privacy.

Reminders and Wink transfers

Trip reminders use device notifications when you grant permission. BudgetWink transfers contain only the selected savings goal and planning amounts. Transfers to ShiftWink contain the selected trip name and dates. You review transfers before applying them. They do not move money, access bank accounts, share every trip or obtain employer approval.

Purchases, advertising and use of data

Apple processes iOS subscriptions through the App Store, and Google Play processes Android subscriptions under their respective policies. TripWink receives purchase identifiers, product and entitlement status needed to activate, restore and support your subscription, but does not receive your payment-card details. TripWink does not sell personal information or show advertising. Data is used to provide requested planning, lookup and account functions, respond to support requests and protect the service. Information may also be retained or disclosed when required by law.

Your choices, retention and deletion

You can decline optional location and notifications, use local planning, remove trips, and export your information. Local data remains until you remove it or clear app storage; copies in exports, backups or recipients' possession are separate. Account data is retained while the account exists unless you remove it. Account deletion removes the cloud account, trips and photos. Provider backups and required security or legal records may persist for their applicable retention periods; deletion is not an assertion that every backup is erased instantly.

Request account and associated data deletion through our deletion page, including without reinstalling the app. We verify ownership before acting. Guest trips and previously exported copies are not removed by deleting a cloud account. Do not send passwords, sign-in codes or payment-card information in a request.

Children and policy changes

TripWink is a planning tool for the person organizing the trip. A planner may enter details about accompanying children; enter only necessary information and ensure you have authority to provide it. Changes to this policy will appear here with an updated effective date.