MiaoTuGo data practices

Clerk handles sign-in. The travel API stores your private trips, preferences, expenses, reviewed files and itinerary history. Authorized group members receive only the shared itinerary and checklist; private notes, photos, expenses and AI prompts are excluded.

AI and providers

Explicit planning, research, translation and extraction requests send relevant travel content to the configured AI service: local vLLM, Ollama or OpenAI. Local mode has no automatic OpenAI fallback. Web research sends destination and search terms to the configured search service and its search engines. File extraction processes only the file you select. Place and route queries go to Google Maps; weather queries go to OpenWeather; reference conversion goes to Frankfurter. Partner searches, when enabled, go to Duffel or Viator. Accommodation purchases occur on external sites.

Files and location

Photos have embedded location metadata removed. Files require current owner authorization. Group location sharing sends one point after you grant permission; it expires after five minutes. Nearby uses a foreground location fix to search Google Places through the travel API. Nearby search coordinates are not saved to your trip or the application database. MiaoTuGo does not continuously track your location.

Retention and control

Private itinerary history retains the latest 100 snapshots. AI jobs are retained for seven days; unused queued requests expire after one day. Request replay records expire after one day. Audit and completed deletion records expire after 30 days. Account deletion immediately disables access and queues private-file and Clerk identity reconciliation. Protected backups can retain earlier data until the operator’s backup retention period expires; offline exports cannot be remotely erased.

Travel DNA learning requires consent and review before a suggested preference is applied. Export and deletion require a recent sign-in. Open a support case from Help to contact the deployment operator about stored data.

Google Maps use is subject to Google’s privacy policy. The deployment details below identify whether operator information is still a sample.