privacy policy

This is the privacy policy for depart., an iOS app published by Javed Hoosein (Apple Developer Team 827337QUAV). depart is built to collect as little as possible. This document describes exactly what that means in concrete, verifiable terms.

The short version

What depart collects, where it goes, and why

Location

• What: your iPhone's coordinates while a trip is active, plus a one-shot lookup the first time you search for a destination.
• Where it goes: Apple MapKit, on-device, to compute live drive time. Apple's privacy terms govern what Apple itself does with that request.
• Why: to give you an accurate "leave by" countdown that reflects current traffic.
• What depart does NOT do: we do not retain your location, log it, send it to depart-owned servers (we have none), share it with third parties, build a profile of where you go, infer a home or work address for advertising, or use it for any purpose other than the in-session drive-time calculation.

Calendar

• What: read-only access to your iOS Calendar, only the events that have a location attached.
• Where it goes: nowhere outside the app process. depart reads upcoming location-tagged events so it can offer them as one-tap trip starts, and so it can detect conflicting events if you have Pro.
• Why: so you don't have to retype destinations and times that depart can already see.
• What depart does NOT do: depart never writes to your calendar, never deletes events, never reads events without a location, never reads private notes or invitees, and never shares any calendar data anywhere. Calendar reads happen entirely on-device.

In-app purchase

• What: when you upgrade to depart Pro ($9.99 lifetime or $0.99/month), Apple's StoreKit handles the transaction. RevenueCat (the only third-party SDK we ship) records that your Apple ID owns the entitlement.
• What depart sees: an opaque user identifier generated by RevenueCat plus a boolean "is pro." We never receive your payment details, your real Apple ID email, your name, your billing country, or any other identifying data.
• What RevenueCat sees: the opaque user identifier, the purchase transaction, and an anonymized device identifier. We have configured RevenueCat with the minimum identifiers required for receipt validation. RevenueCat's own use of that data is governed by their privacy policy.
• If you never purchase Pro: RevenueCat is initialized so the app can render the price label and respond to a future purchase intent, but no purchase event is ever sent. The only data RevenueCat receives in the free-tier case is the opaque identifier it generated for the app instance.

Apple WeatherKit (Pro only)

If you have purchased depart Pro, depart queries Apple WeatherKit with your destination coordinate to fetch the forecast at your arrival time. The forecast is used in-session to adjust your buffer and prep alerts. Apple's WeatherKit privacy terms govern this. Non-Pro users never trigger a WeatherKit query.

What depart does NOT collect

This list is exhaustive at the time of publication:

• We do not collect your name, email address, phone number, postal address, contacts, photos, microphone audio, health or fitness data, advertising identifier (IDFA), device fingerprint, IP address (depart makes no network call that logs one), browsing history, biometric data, social graph, payment details, or device usage statistics.
• We do not run any analytics SDK. The Analytics.swift file in the source tree is a deliberate no-op shim.
• We do not run any crash reporter or telemetry SDK.
• We do not run any advertising SDK or tracking SDK.
• We do not show ads, anywhere, ever.
• We do not use the App Tracking Transparency permission because there is nothing to track.
• We do not log or transmit your trip history. Every trip you record lives on your device and is deleted with one tap from Settings.
• We do not link your purchase to any personal identifier we control. The link is between your Apple ID (which we never see) and the RevenueCat opaque user ID.

What about crash data?

We do not run a crash reporter. If your iPhone is configured to share iOS analytics with Apple (under Settings, then Privacy & Security, then Analytics & Improvements, then Share with App Developers), Apple may share anonymized crash data with us through App Store Connect. That sharing is governed entirely by Apple, you can opt out at any time in iOS Settings, and depart has no way to identify you from those reports.

Network calls depart makes

For full transparency, here is the complete list of network calls the app can make:

There are no other network calls. The app never contacts any server operated by depart. We do not operate any server.

Children

depart is rated 4+ and contains nothing inappropriate for any age. We do not knowingly collect data from anyone, including children. Because the app collects no personally identifying information from anyone, there is no children-specific data path to disclose.

Your rights

Because depart stores everything on-device, exercising your rights does not require contacting us:

• Access: tap Settings inside the app to see everything depart remembers.
• Delete: under Settings, then "delete all data," depart wipes destinations, trip history, the trip queue, recurring templates, and the pro entitlement cache from the device. The pro purchase itself is owned by your Apple ID (not by us). Use "restore purchase" to bring it back on this or any other device signed into the same Apple ID.
• Portability: under Settings, then Insights, then "export csv," depart dumps your full trip history to a CSV you can save anywhere. Pro users also get JSON and PDF export.
• Revoke calendar access: iOS Settings, then depart, then Calendars, then turn it off. depart will continue to work without calendar auto-start.
• Revoke location access: iOS Settings, then depart, then Location, then "Never." depart will continue to work, but live drive-time updates will not happen.

Government and law enforcement requests

Because depart operates no servers and stores no user data on infrastructure we control, we have nothing to hand over in response to any legal process. If we ever receive a subpoena, warrant, national security letter, or any other legal demand for user data, the truthful response is: depart possesses no user data to produce.

If a future version of depart ever begins collecting data we could be compelled to disclose, this section of the policy will be updated before the data starts flowing.

Changes to this policy

If we materially change this policy, we'll surface a notice in the app on next open. Material changes include: adding any new SDK that sends data off-device, adding any new server we operate, beginning to collect any data type not listed above, or changing the purpose of any existing data flow.