Trippia Privacy Policy

Trippia respects your privacy and does not sell personal information. Depending on the features you use, we may process account details (email, display name, authentication and legal-acceptance metadata), subscription entitlements, trip inputs (destinations, dates, traveler counts and ages, interests, preferences, travel style and free-text requests), saved content, purchase-verification information, and technical or usage data. We share information only as needed with service providers, to meet legal obligations, or to protect the service and its users.

Signed-in accounts use Google Sign-In or Apple Sign-In where supported, with Firebase Authentication infrastructure. Trippia may process authentication metadata, profile information, legal-acceptance status, and subscription or entitlement status. Trippia does not currently offer an email-and-password sign-in flow.

Relevant trip, chat, and feature inputs may be sent to OpenAI and Google Translation / Google Cloud Translation to generate itineraries, answer through Trippia Buddy, enrich requested City Vibes content, or translate content. xAI may process relevant requests in the separately available Christmas Markets feature; it is not a City Vibes V3 provider. Only information relevant to the requested feature is sent.

Trippia does not continuously track location merely because the app is open. Manual City Vibes city search does not require GPS. Precise or current location is used only when you intentionally select a location-based feature, such as Current Location, Nearby tools, or SOS. Relevant coordinates or location context may be sent to mapping, location, weather, emergency, or backend providers to supply that feature. Permissions can be managed in device settings.

To operate features, understand reliability, diagnose failures, improve performance, and protect service integrity, Trippia may record account-linked technical and usage telemetry. Categories can include feature usage, sessions and activity, success or failure outcomes, errors, latency, provider or model metadata, AI token counts when available, and app version, platform, and language. This does not expand the current analytics fields or mean full trip prompts are recorded as analytics.

Website measurement: Google Analytics loads only after you choose Analytics only or Analytics + ad measurement. It measures page visits and clicks to the app stores, website language, device information, referral source, and allowlisted campaign parameters. The ad measurement choice also permits Google click identifiers. Analytics cookies and session attribution storage are used only with this permission; advertising storage and advertising user data are enabled only by the separate ad measurement choice. Google signals and advertising personalization stay disabled. Use Cookie preferences in the footer to decline, withdraw or reduce permission. Reducing permission to analytics only removes saved advertising click identifiers and advertising cookies. Withdrawal stops further collection and removes the website’s Analytics cookies and saved attribution; it does not delete data already sent. Your choice is saved locally for up to 180 days. Existing first-party Stay22 newsletter counters are separate and record campaign visits and store clicks using temporary session state and event identifiers. Store clicks do not prove an installation or connect website visitors to app accounts.

Some content and settings may be stored locally, including Saved Trips, saved City Vibes snapshots, app preferences, and applicable local chat or translation state. Depending on platform settings, some local application data may be included in operating-system backup or device transfer. Sensitive saved-trip document files configured as excluded are not included in Android backup. Account deletion clears safely attributable account-linked local data from the active device, but cannot guarantee removal of copies already held in an external platform backup.

Trippia relies on third-party services, including Firebase and other Google services, Apple and Google authentication or payment services, OpenAI, Google Translation, xAI for the separately available Christmas Markets feature, and mapping, weather, events, media, and travel providers. Trippia may include affiliate links and may earn a commission at no additional cost to you. External transactions, availability, content, and terms are controlled by the provider.

Stay22 is an accommodation technology and affiliate partner. Accommodation offers are optional promotional notifications. We activate the Stay22 service only after you explicitly opt in. Your choice applies to your Trippia account and can be changed in Settings. Declining or switching off does not affect hotel searches, normal Trippia features, or your other Trippia notification preferences. Device notification permission is a separate control. Turning this setting ON yourself is also an explicit opt-in. You may withdraw it at any time. Trippia may receive an affiliate commission at no additional cost to you.

For this feature, Trippia supplies Stay22 only the destination text, check-in date and check-out date of the selected eligible saved trip. We select one trip at a time from the eligible trips available on your device. We do not supply your Trippia account ID, name, email, phone number, precise coordinates, hotel name, trip ID, trip notes, other free-form content or passenger details in this context.

The Stay22 SDK separately processes our partner ID (aid), an identifier stored on the device and reused across launches (sid22), the originating IP address and approximate location derived from it, operating-system and SDK versions, whether selected booking apps are installed, notification shown or failure events, and attribution or conversion information. These data support offer delivery, frequency control, analytics and attribution of bookings to offers. Processing may occur while Trippia is in the background. Stay22 does not request GPS location permission or access an Advertising ID for this integration.

Stay22’s default retention for its frequency-cap record, which includes the session’s destination and dates, is seven days and can be configured per partner. This is not a seven-day retention promise for all Stay22 data. Switching off stops new trip-context submissions and clears the current context through the integration; it does not automatically erase previously collected partner records. Turning off accommodation offers stops new Stay22 offers. In rare cases, if a notification was already in progress before you turned the feature off, one final notification may still appear.

Logout, account switching and account deletion stop future use for the previous account and clear or suspend this feature’s local state and active context on the current device. They do not guarantee erasure of historical Stay22 records. Stay22 and external booking providers process relevant information under their own privacy policies, and processing may take place in countries other than your own. For privacy requests, contact contact@trippiaapp.com or Stay22 at privacy@stay22.com. Stay22’s processing and retention practices are described at https://www.stay22.com/privacy.

Information is retained only as reasonably necessary to provide and operate the service, verify transactions and maintain accounting records, protect security and prevent fraud or abuse, meet legal or regulatory obligations, handle disputes, and support legitimate operations. When information is no longer reasonably needed, it may be deleted or anonymized as appropriate, subject to applicable law. Trippia does not promise a fixed retention period that the product does not enforce.

Cloud, AI, mapping, translation, and other providers supporting Trippia may process information in countries or regions other than your own. Trippia does not promise a particular storage region. Processing is handled subject to applicable privacy and data-protection requirements as appropriate.

Trippia applies reasonable technical and organizational measures intended to protect information and service integrity. No online, mobile, or cloud service can guarantee absolute security.

Trippia accounts are intended for people aged 18 or older. A child may be included as a traveler in an itinerary, and a user may provide a child's age solely to personalize trip planning. This does not make the child an account holder, and relevant traveler-age information may be processed when generating the requested plan.

You may permanently delete your Trippia account. This deletes your Trippia account and profile identity and removes account-linked local content from the active device. Deleting the account does not automatically cancel subscriptions managed by Apple App Store or Google Play. Some records outside the active account and profile, such as purchase, security, or service-operation records, may not be removed automatically.

Trippia may update this Privacy Policy and Terms of Use to reflect changes in services or features, law or regulation, security practices, or operational requirements. The current version will be available inside Trippia and identified by its Last Updated date. Users should review it periodically. Continued use after an update becomes effective may constitute acceptance, except where applicable law requires additional notice or consent.