Draft status: 2026-11-16 ยท Engineering summary

SeeMeTravel Privacy Engineering Disclosure

Technical draft awaiting review: This document records factual engineering behavior implemented in the SeeMeTravel codebase and awaits owner approval and formal legal counsel review before public App Store or Google Play submission.

Account identity and backend access controls

Traveler accounts authenticate through Sign in with Apple and Google via Firebase Authentication, and all API traffic routes through HTTPS to api.seemetravel.app. Direct client access to Firestore is denied by rule (allow read, write: if false), so every trip, expense, message, and entitlement request passes authenticated server validation.

On-device processing vs server AI extraction

Trip media uploads and public read-only links

Shared album photos (maximum 500 photos and 25 members per trip) are resized on the client to at most 2048 px on the longest edge and 10 MB in JPEG or PNG format, and the backend verifies leading JPEG or PNG magic bytes before accepting uploads. Read-only web trip links at seemetravel.app/t/ serve itinerary stops, dates, and photo spot counts only and omit private financial expense ledgers and live member pins.

Opt-in live group location window

Live trip location pins are opt-in per trip, use low-power location updates restricted strictly to tripStart - 24h through tripEnd + 24h (maximum 30 days), and provide an immediate pause toggle inside the Group tab.

Account deletion and token revocation

Deleting an account invokes DELETE /v1/account, deletes the traveler profile and owned trips, strips the traveler's group membership, pins, messages, and shared photos from other trips, clears local caches and Spotlight indexes on device, and records only an aggregate deletion count tombstone without keeping personal profile fields.