Privacy policy.

Effective date: October 27, 2026 · Offport 1.1 (12) development preview. Offport is provided by Trevor Sherba. This policy describes the build 12 local planner and optional community features. Community access requires an authenticated account and profile. The build 12 preview does not include in-app purchases, subscription verification or system wake-up alarms.

Private information on your device

Your calendar connection credentials remain in device-only Keychain storage. Your parsed local itinerary, private trip and reusable hotel notes, pickup instructions, membership numbers, saved food and prices, preferences, local arrival confirmations and travel caches retain their device-local design. Community sign-out or account deletion does not erase those independent private records. Community sessions use separate device-only Keychain accounts. Personal preferences, saved places, personal prices and personal hotel/layover notes are eligible for ordinary device backups, depending on your device settings. This does not provide app-managed sync, a backup receipt or guaranteed reinstall recovery. Credentials, loyalty information, community content, account-scoped community drafts, shared context files and downloaded caches remain excluded from this personal-data backup set.

A limited local projection of itinerary dates, flights, stays, hotel/transport names, hotel coordinates, pickup/planning times and explicit arrival confirmations supports widgets, Live Activities, local notifications and app intents. Raw private notes, pickup instructions, credentials and membership numbers are excluded. Enabled Home and Lock Screen surfaces can display travel information; your iPhone settings control visibility and permissions.

Optional community accounts and hosting

The community beta uses Sign in with Apple and a developer-operated service hosted by Supabase in its U.S. East region. The service receives your Apple sign-in identifier, account ID, email when supplied, real-name profile and optional self-entered base, equipment, seat and employee number. An employee number you choose to enter is visible to eligible community members with your profile details and can be used for exact person lookup. It is not taken from your calendar and does not verify employment. Authentication/session tokens support access and account security. Community data is account-linked; it is not anonymous or end-to-end encrypted.

The server also stores invitations and accepted/pending friend relationships, sharing choices, blocks, profile photos, hotel Wi-Fi contributions, comments, votes, reports and private moderation/security records. Profiles and community contributions can be visible to eligible beta members under the app's access rules. Accepted friends may view a shared schedule only while sharing and access remain enabled. Family/friends may participate without sharing a calendar back. Reports and operator records are restricted to authorized moderation/support operations.

Calendar and schedule sharing

Offport downloads your optional compatible HTTPS calendar subscription directly from the server you specify and parses it on your phone. Calendar credentials and the raw subscription URL or complete source file are not sent to Offport's community service.

Sharing is a separate explicit choice. When enabled, the service stores the selected flight routes/numbers/scheduled times, pairing/start-day labels, layover airports/times and matched hotel identities needed for shared Calendar/Trips and scheduled overlaps. Hotel name/address/destination information can also be sent for catalog matching or intake when using signed-in hotel/community features, including when friend schedule sharing is off. Hotel matching is separate from publishing your schedule to friends. Normal shared schedule payloads exclude duty/report/release times, private notes, pickup instructions, calendar credentials, calendar-derived employee numbers and room/reservation/loyalty numbers. The optional employee number entered separately in your profile is a visible profile detail, as described above. Scheduled overlaps do not establish your current physical location or arrival. Unknown and ambiguous hotel identities stay unresolved until the supported confirmation path is used.

Pausing sharing or removing/blocking a friend restricts further authorized access. It cannot recall screenshots, copies or information another person already viewed. Protected friend schedules and images are held in session memory rather than restored as an offline friend database.

Photos and community content

Only photos you select through the system picker are submitted. Offport downsizes the selected photo on your device and uploads only a cropped 512-by-512 JPEG no larger than 512 KiB; the original full-resolution photo is not uploaded. Uploads first enter private owner-only quarantine. Trusted processing decodes, resizes and re-encodes a fresh image and strips source metadata before publication. This processing is not a guarantee that content has received human review. Development profile/photo preapproval is currently disabled; valid processed photos can publish automatically. New and edited comments currently publish without preapproval. The service retains a private review setting, reporting and moderator removal; previously pending comments are not automatically approved.

Hotel Wi-Fi and comments are shared contributions, not private notes. Do not submit employer-restricted information, private credentials, room/reservation details or another person's personal information. Contributions and self-entered names may be inaccurate. Failed/dismissed edits and selected crops can remain as account/property-scoped local drafts for retry.

Crew food recommendations are shared hotel Food comments. Your displayed name, recommendation, optional tip and contribution date may be visible to eligible community members. Recommendations are opinions, not verified ratings, prices, hours or dietary information. Private saved places and personal notes remain private unless you explicitly share content.

Maps, food, weather and airport information

Apple receives map, place-search, native place-detail, Look Around street-preview, walking-route and WeatherKit requests used by those features. Requests can include search terms, hotel names/addresses and coordinates for the viewed or searched area. Community builds use Apple food services; optional user-supplied Google Places integration described in older builds is not used by this community build. Earlier Google-enabled builds send the supplied key, bundle identifier, food terms, search coordinates and radius directly to Google, which may charge the user's project.

The native map can show your device's location while visible/active with While Using permission. An explicit Around me search or directions request can send relevant coordinates to Apple. Device GPS coordinates are not uploaded to the Offport community server or shared with friends. Optional arrival suggestions give iOS limited regions for local reminders; no Always permission or continuous background GPS is requested. At gate/At hotel confirmations are explicit local actions, not automatic proof of arrival.

Radar requests go to NOAA and may include the map area/time. The crew-access directory can update from TSA. Airport Status downloads the public FAA NAS feed directly and filters it locally; it does not send your itinerary or favorites to FAA. European coverage opens the official EUROCONTROL portal separately. Saved reports may be stale; missing coverage is not an all-clear or individual-flight prediction. Saved static maps are not offline navigation.

Online providers receive connection/security information such as IP addresses and process requests under their own policies: Apple · Supabase · Google for earlier builds · NWS/NOAA · TSA · FAA.

Optional local reminders

With your notification permission and the relevant reminder settings enabled, build 12 can schedule local notifications for planned sleep/wake times, van pickup and scheduled arrival. iOS receives the scheduled notification time, travel-related message and local stay identifier needed to display and open that reminder. Optional arrival suggestions use iOS region triggers as described above. These are notifications, not AlarmKit system alarms or guaranteed wake-up alerts. Your iPhone settings affect delivery and visibility. Reminder scheduling does not upload your private itinerary to Offport’s community service.

Retention, choices and deletion

The server's scheduled cleanup removes shared flight legs more than seven days after arrival and shared layovers more than seven days after ending. That rule does not delete your phone's itinerary, future shared trips, hotel contributions or profile photos. Raw/failed photo cleanup is retried through service activity or operator actions; immediate global purging is not promised.

Use community account settings to sign out, pause sharing, manage friends/blocks or request account deletion. Apple-linked deletion requires fresh authentication with the same Apple account. A confirmed deletion handoff hides account access and revokes sessions, then retries Apple-token revocation, Storage cleanup and Auth/content deletion if required. If the handoff cannot be confirmed, the app asks you to retry rather than claiming deletion succeeded. Keep the support receipt when cleanup is pending.

To support Apple sign-in revocation during deletion, the deletion service receives a fresh Apple authorization code and may exchange it for a revocation token. The service stores the token encrypted while cleanup needs retries and clears that secret after completed cleanup. Your Apple password is not requested by this service.

After completed account cleanup, profile-linked schedules, relationships, tips, votes and reports are removed through their account relationships. Shared hotel catalog/Wi-Fi facts can remain with account attribution cleared. Private moderation and Wi-Fi revision history and deletion-job records can retain action details/account IDs; no automatic expiry for those records is promised. Provider security logs and legally required records may have separate retention. Contact the developer for access, correction or deletion requests, including a pending cleanup receipt. Previously downloaded copies cannot be recalled.

Calendar Disconnect removes its saved connection/schedule/travel-cache data but does not remove every independent note, favorite, personal price, membership or community account. Edit/remove supported local items separately. Before uninstalling, clear saved calendar credentials, membership numbers and any legacy Places key through their settings; iOS can retain Keychain entries after uninstall. Device/Keychain errors can prevent cleanup and are reported.

Developer access and feedback

Authorized operators can access community information needed to run the beta, handle reports and perform security/support actions. The developer does not automatically receive your raw private calendar, local notes or calendar password. No advertising network, data sale, cross-app advertising tracking or embedded analytics service is added. Ordinary service operations and security logs are distinct from analytics.

Apple TestFlight provides beta diagnostics, usage and feedback under its terms. Email or feedback shares what you choose to include and may reveal your email, screenshots or logs. Support information is used to respond and investigate while needed or required; Apple, hosting and email providers can retain their own records. Never send secrets or unredacted rosters.

Website and support email

The offport.app website and support mailbox use IONOS hosting/email. Visiting the website sends technical request information needed to serve its pages; IONOS may process operational/security logs under its privacy policy. Support emails include the sender address and any message content or attachments you choose to send. We use these to answer requests and investigate issues while needed or required. Offport’s site has no embedded advertising or analytics scripts, external fonts or tracking cookies; hosting-provider processing is separate. We do not automatically receive your private local itinerary or notes from a website visit.

Changes and contact

Policy updates are identified above. Privacy/support contact: Trevor Sherba, support@offport.app. Optional Google services in earlier builds remain subject to Google Maps/Google Earth Additional Terms.

Community rules

Use your real name, share only information you are authorized to share, respect others' privacy, and keep comments relevant. Harassment, threats, sexual/abusive content, impersonation, spam and private/employer-restricted data are not permitted. Use in-app Report and Block controls or email support. Trevor monitors the beta report queue; content or account access may be removed under the community rules. No response-time guarantee is offered.

Beta support

Email support@offport.app or use TestFlight feedback. Include version/build, device/iOS version, steps and expected behavior, using synthetic data where possible. Do not send passwords, tokens, API keys or private rosters.

The local planner's Take a look around first sample itinerary requires no calendar credentials. Community features separately require Sign in with Apple and profile setup. An invitation code is no longer required; account access, reporting, blocking and moderation controls still apply. The beta uses development hosting; availability and capacity are limited. Rest plans are estimates, not medical advice or duty/rest legality checks. Airport reports and scheduled overlaps are not live flight or physical-location verification.