Privacy

Trip planning data

When you plan a trip, PodPaiGo uses inputs such as origin, destination, airport when applicable, dates, transportation preferences, parking preferences, and timing choices to generate recommendations. Trip details may be sent to connected services for routes, weather, parking, rideshare, transit, destination search, or airport-related information when those features are enabled.

Location access

PodPaiGo uses your device location only if you grant browser location access. You can also type an origin manually. Location may be used to estimate routes, nearby parking, and point-to-point trip options.

Account, email, and profile data

If you create an account, PodPaiGo stores account information through Supabase Auth. That may include your email address, display name, and profile photo metadata returned by your sign-in provider. Account data is used to identify you, protect your saved content, and keep you signed in across sessions.

Saved trip data

When you save a trip while signed in, PodPaiGo stores the trip payload you chose to save so you can reopen it later from your account page. Saved trips are associated with your user account and protected by database access rules.

OAuth via Supabase and Google

Google sign-in is handled by Supabase Auth, not directly by PodPaiGo. When you choose Google sign-in, Google and Supabase process the OAuth exchange. PodPaiGo receives the authenticated session and basic profile fields needed for your account experience. See docs/supabase-oauth-setup.md for setup details.

API usage, caching, and safe mode

PodPaiGo may cache route, parking, places, and usage data to reduce repeated external API calls and control cost. Local development defaults include safe-mode quota protection and disabled Google Places / live parking discovery unless you explicitly enable them. API usage counters and cached snapshots help the app avoid unnecessary paid requests. Cached or saved parking options may be shown when live refresh is paused or rate-limited.

Google Maps and Google Places

Some features can use Google Maps or Google Places when configured and enabled. In local development, Google Places and related live discovery are disabled by default. When enabled, trip and airport search inputs may be sent to Google services according to your environment configuration.

AI trip assistant

The AI trip assistant can run in mock mode by default. If a live AI provider is configured in the future, trip text you submit for parsing would be sent only to the configured provider for that feature.

Product analytics

PodPaiGo records privacy-conscious product analytics to understand which features are used and where the experience breaks down. Events are sent to our server API and stored in Supabase when configured. We use a random anonymous identifier and a short-lived session identifier in your browser storage — not advertising IDs and not Google Analytics.

Event properties are limited to coarse fields such as airport code, destination category, transport preference, provider name, and whether live or cached data was used. Raw home or work addresses, email, phone numbers, and API keys are stripped before storage. Signed-in users may be linked by account id for product improvement; analytics rows are not readable from the client and are intended for admin review only.

Outbound clicks and partner links

When you click provider booking or directions links, PodPaiGo may record a lightweight outbound click event (provider, airport or destination category, lot, destination URL, and optional trip id). Some links may become partner links in the future. We do not sell your personal data.

AI trip assistant usage

If you use the AI trip assistant, the text you submit may be parsed by a mock parser or an optional live OpenAI provider depending on environment settings. Parsed fields are shown for review before recommendations run. AI usage may be logged server-side with input size and token counts for budget control.

What we do not do

PodPaiGo does not sell your personal data. We do not use your account or saved-trip information for advertising resale. Do not store secrets, payment card numbers, or passport numbers in saved trips.

Confirm important details

Prices, availability, traffic, weather, TSA estimates, shuttle timing, street or meter rules, and transit details may change. Street parking rules vary by block and posted signs always win. Confirm important details directly with your airline, parking provider, posted signs, or transportation service before travel.