Passport Privacy Notice
Last updated: October 19, 2026. Applies to the limited iPhone beta and Passport's published policy and support website.
Passport is operated by Kevin Garand. Privacy questions and requests: kevingarand@berkeley.edu. This beta is for adults aged 18 or older. No separate invite code is required: an Apple-authenticated account can join after accepting the beta terms while signups are open and the 50-account limit has not been reached. Admission does not verify membership in a particular TestFlight group or guarantee that other testers are people you know.
What we collect and why
- Account information: Sign in with Apple supplies an account identifier and may supply an email address (including an Apple relay address) and name. Supabase manages authentication and sessions. Passport does not receive your Apple password. Signing in can create an authentication record before beta onboarding is completed; you can request deletion even if you never join the beta. You choose your public display name and username. We record beta membership and the version and time of your acceptance of the beta terms and acknowledgment of the privacy notice. Onboarding asks you to confirm that you are at least 18; it is not independent age verification.
- Your travel log: destinations and coordinates, travel dates, trip groupings, ratings, notes, links, photos, profile information, and optional home city/coordinates are stored to provide your Passport. Home city is optional and used for distance calculations; please do not enter a street address. Photos are optional and processed for upload, including resizing and re-encoding. Do not include sensitive documents or private location details in photos or captions. The cloud beta does not request continuous device-location tracking or your contacts. You can decline optional photo access and still use the travel log without uploading photos.
- Interactions: follows, blocks, likes, comments, private saves, reports, and hidden recommendations support social and safety features. If you enable personalized recommendations, searches and viewed/opened destinations and links are also stored. This setting is off for new cloud accounts. Turning it off deletes stored passive history and stops recording new history, but does not delete explicit likes, saves, comments, follows, or your travel log. Recommendations are calculated on your device from permitted app data, not sent to an AI service.
- Operational and support information: our hosting and authentication providers process technical request information such as IP addresses, timestamps, and authentication/security logs. Account-linked usage counters help enforce limits and prevent abuse. If you email us or submit TestFlight feedback, we receive the information you choose to provide, which may include screenshots or diagnostic details. We use this to operate the service, investigate failures or abuse, moderate content, and respond to requests. Avoid sending other people's information or account secrets in feedback.
Who can see information
Your Passport starts private. Home settings, passive history, hidden recommendations, and saves are not shared with other travelers. If you make your Passport public, approved profile and travel content can be viewed by other admitted testers. New or edited public content requires operator review. Comments you post on another visible item may remain visible even if your own Passport is private. Blocking restricts reciprocal access; it cannot recall a copy someone already downloaded or photographed.
Photos are held in a private storage bucket. Permitted viewers receive temporary links, which can continue working for up to five minutes after visibility changes. Authorized operators can access backend records for administration, moderation, and support. This service is not end-to-end encrypted.
Services used by Passport
- Apple: Sign in with Apple, iOS services, and TestFlight distribution/feedback. Apple's own privacy settings and policies apply to information Apple handles.
- Supabase: account authentication, database, photo storage, and server functions. App data and relevant requests are processed by Supabase and its infrastructure providers.
- Expo / EAS: building and distributing app software. Build configuration is provided to Expo; Passport does not intentionally send your travel log or uploaded photos to EAS for builds.
- OpenStreetMap Foundation / Nominatim: place searches are sent when you explicitly submit them, not on every keystroke. A search passes through our server to this service, with an app/operator contact, when a cached result is unavailable. Nominatim receives the query and our server's request information; we do not attach your account identifier or email. Search text itself can reveal information, so do not submit private addresses, names, or confidential details. Use @username for traveler-only searches. Shared cached search results are not a private notebook; do not assume a query is anonymous merely because we omit your account identifier.
- Wikimedia services: Wikipedia, Wikidata, Wikivoyage, and Wikimedia Commons provide destination facts, travel text, and photographs. Your device sends requested article identifiers, destination coordinates where needed, and image requests directly to these services. They can receive your IP address and technical request information.
- jsDelivr: the globe's Earth image textures are downloaded from this CDN. It can receive your IP address and image-request information. The globe's executable rendering code is bundled in the app; Passport does not send your travel pins or home location to the texture CDN.
- Cloudflare Pages: hosts the published policy and support website. Visiting those pages exposes technical request information, including your IP address and the requested page, to Cloudflare for delivery and security. These static pages contain no sign-in, data-entry forms, advertising, analytics scripts, or externally hosted fonts. We do not intentionally set visitor-tracking cookies on them; hosting/security services may process technical information as described in Cloudflare's Privacy Policy.
- External websites and email: opening a travel link, source, policy, or support email invokes that website or your email provider, whose practices apply there. Our support inbox uses the berkeley.edu email service.
We do not sell personal information or share it for cross-context behavioral advertising. This beta has no advertising, third-party behavioral analytics, or session-replay SDKs. Our app and policy website do not currently change their behavior in response to browser Do Not Track or Global Privacy Control signals; the no-sale/no-advertising-sharing practices above apply regardless of those signals. This does not limit privacy rights available under applicable law.
We may disclose limited information when legally required or necessary to address abuse, protect users, or enforce the beta rules. Service providers may process information outside your state or country. Providers handling personal data on Passport's behalf must provide the same or equal protection described in this notice and required by applicable law and Apple's privacy requirements, and use it only for the agreed services and permitted security or legal purposes. Providers also maintain their own privacy notices; those do not replace this notice for Passport's processing. Independently operated websites you choose to visit have their own practices.
Retention and deletion
Account and travel content is retained while needed to provide your account, unless you remove it or request deletion. Passive history is limited to the latest 500 events and a 90-day retention window. Place-search cache entries expire after 30 days. Routine maintenance removes expired operational records and resolved reports created more than 90 days ago; open reports may remain while an investigation is ongoing. Report text can remain after account deletion with account references removed; unnecessary identifying details are removed during review. Support correspondence is kept as needed to resolve a request and handle related security or legal issues, then deleted when no longer needed.
Removed, replaced, or abandoned photo uploads become eligible for cleanup once they are at least 24 hours old and no saved profile or Passport references them. Cleanup is performed by scheduled server maintenance; deletion is not instantaneous and failures can delay it. Account deletion separately attempts to remove all of that account's uploads before deleting the account. Security markers identifying retired photo paths remain until account deletion to prevent stale devices reattaching deleted media.
Use Edit profile → Account & safety → Delete my account to delete your account, associated app records, and uploads, and revoke the Apple authorization. You will confirm with Apple. Signing out or uninstalling is not account deletion. If deletion fails, the app tells you it is incomplete: retry or contact us. Limited abuse reports, provider logs, and restricted backups may outlast deletion from the active system. Backup and provider-log retention depends on the configured service and plan; contact us for the current periods. Backups are not used to restore deleted accounts to normal service without reapplying deletion.
Your choices and requests
Edit or remove your content, keep your Passport private, disable personalization, clear history, block/report travelers, or delete your account in the app. Contact Kevin Garand at kevingarand@berkeley.edu to request access, a copy, correction, deletion, or other rights available where you live. We may verify account ownership before responding; never send passwords, Apple codes, or access tokens. Some requests require retaining limited information for legal or safety reasons. This beta is not intended for children, and we do not knowingly collect their personal information; contact us if you believe a child has provided information.
Depending on where you live, you may also have rights to object to or restrict certain processing, withdraw consent where consent is the basis for processing, appeal a privacy-request decision, or complain to a privacy regulator. Contact us to exercise applicable rights; we will explain any refusal or exception. Accepting the beta terms does not waive those rights or automatically authorize a new, unrelated use of your information.
Changes to this notice
We update the date above when this notice changes. For material changes, we will provide an additional notice through the app or a contact method associated with your account before the new practices take effect, where required, and obtain any legally required consent. If the current handling of your data is unclear, contact us before sharing sensitive information.
Beta Terms and Community Rules · Support and Privacy Requests