Privacy Policy

Summary

Peaceful Journey is designed as a local-first travel planning app. The app uses personal travel data only to provide planning, active-trip assistance, memories, receipts, safety context, and user-requested sharing features.

We do not sell personal data. We do not use data to track users across other companies' apps or websites.

Travel Plans And Local App Data

The app may store travel plans, itinerary items, destinations, notes, diary or travelogue content, receipts, expenses, and attached files created by the user. The product is designed to keep core travel data local-first.

Peaceful Journey does not use personal reservation numbers, raw calendar text, payment information, or exact lodging addresses as server-side owned assets. If a user chooses an export or sharing workflow, only the selected content is handled for that workflow.

Location

Location may be used when the user allows it for active-trip context, destination relevance, arrival or reminder support, nearby search, weather relevance, and hazard relevance. The app should avoid collecting exact location when a coarse or trip-context location is enough.

Photos, Camera, And Media

Photos, videos, camera captures, and photo metadata may be used when the user attaches media or asks the app to match trip memories. Large original media should stay outside CloudKit by default unless the user chooses a sharing or export flow.

Calendar

Calendar access may be used when the user imports booking events or adds trip plans to Apple Calendar. The app should avoid treating raw calendar text as a server asset. Users can control calendar permission in iOS Settings.

Microphone And Local Network

Local Guide / walkie features use microphone and Local Network access only when the user starts that feature, has the required entitlement when applicable, and grants the relevant iOS permission. The feature is intended for nearby communication and does not store raw audio files as part of the Local Guide privacy model.

Free or locked preview screens may explain why microphone or Local Network permission would be needed, but they should not start an active walkie session by themselves.

CloudKit, App Groups, And Secure Storage

Core travel data is intended to work locally on the user's device. Some protected files may be stored in an encrypted secure vault inside the app container. App Groups may be used for app-owned shared storage needed by approved app components.

If CloudKit or iCloud sharing is enabled, selected user content may be synced or shared through Apple's iCloud infrastructure according to the user's iCloud settings and sharing choices.

Public Data And Airport Operation Context

Airport operation context may use official or public data sources, including public airport or government data where available. The app can display context and source links, but it does not rewrite a user's itinerary.

Public-data API keys, when required, are intended to be kept on a server or Worker rather than embedded in the app binary.

Weather, Hazard, And Disaster Context

The app may show weather or hazard context when supported by current source data and official source links. It is not a substitute for government warnings, emergency services, or local authority instructions. Users should follow official local guidance during emergencies.

Natural disaster and weather information should provide links to official sources where possible. The app should avoid language that promises live coverage or personal safety outcomes.

AI Update Workflows

AI update workflows are intended to help users review travel context, benefits, events, and planning suggestions. The app does not store an OpenAI API key inside the app binary. When server or Worker mediation is used, API keys should be protected server-side.

AI-generated results are reference material and should be reviewed by the user before being applied to a trip, wishlist, bulletin, or travel library item.

Purchases And IAP

Paid plans and in-app purchases are processed by Apple. We do not receive full payment card details from Apple. StoreKit entitlements may be used by the app to decide which paid features are available.

Local Guide / walkie actual-use may require a verified in-app purchase entitlement. Safety controls such as stop, all-off, leave, and mute should remain available during an active session and should not be separately monetized.

Affiliate And Partner Links

The website or app may show clearly labeled affiliate, sponsored, or advertising links for travel services such as lodging, transport, events, or local experiences. Booking, payment, refund, cancellation, availability, taxes, and fees are handled by the partner website and its policies.

Some labeled links may pass through go.momokarose.com for campaign validation and redirect handling. The early redirect design avoids user IDs, exact GPS, sensitive profiles, receipts, photos, contacts, calendar data, passport data, payment card data, and full itinerary text.

Read the Affiliate And Advertising Disclosure for details.

Retention And Deletion

User-created app data remains until the user deletes it, removes the app, or uses an available export/delete workflow. Data synced through iCloud may also be controlled through the user's Apple ID and iCloud settings.

Contact

For privacy questions or deletion requests, contact [email protected].