Privacy Policy
Last updated: November 3, 2026
1. Data We Collect
When you sign in to Travel AI Plan with your Google account, we collect the following information:
- Google Account ID
- Email address
- Display name
- Profile picture URL
2. Purpose of Data Use
- Create and manage your account
- Provide personalized travel itinerary planning services
- Identify members for itinerary sharing and collaboration
- Improve service quality and user experience
3. Third-party Services
We use the following third-party services to provide full functionality:
- Google Maps API: For map display, attraction info and photos
- AI Services (Claude / GPT / Gemini): For smart itinerary planning and suggestion generation
- Google OAuth: For secure authentication
- Notion API (optional): For exporting itineraries to Notion
- NewebPay: used to process payment transactions
4. Data Retention
Your account data is retained during your use of the service. Deleted itineraries are soft-deleted (marked as deleted), and database records are permanently purged after 90 days. You can request deletion of your account and all related data at any time.
5. Data Security
We employ industry-standard security measures to protect your data, including HTTPS encrypted transmission, JWT authentication, and AES-256 encryption for sensitive data storage.
6. Cookie Usage
We use necessary session cookies to maintain your login status. We do not use tracking cookies or third-party advertising cookies.
7. Contact
If you have any questions about this privacy policy, please contact us via email:yentechstudio@gmail.com
8. Payment Processing and Transaction Records
This Service uses NewebPay as our third-party payment processor to handle transactions. We do not directly store your credit card number or other payment credentials. Transaction records are retained for at least 5 years in accordance with statutory accounting and tax requirements.
9. Sharing, LINE Group Bot and Data Visibility
(1) LINE share links: the "Share to LINE" button on an itinerary page only opens LINE's share screen. You choose the recipients and send the message yourself inside LINE; we do not obtain any LINE account or chat data from this. (2) LINE group bot: once the bot is added to a group, the LINE platform delivers the group's messages to our service, but we only process messages that start with a command (such as "今天" (today), "下一站" (next stop), "記帳" (add expense), "結算" (settle up) or "行李" (packing)). Non-command messages are not stored, not replied to, and their content is not logged. We only store: the LINE group ID (linking the group to an itinerary), the LINE user ID you choose to link with the "我是 code" command, and expense records you create with the "記帳" command. Binding codes are kept temporarily for 15 minutes only. The bot only sends messages as replies and never sends push messages. To unlink: remove the bot from the group (this deletes the link between that group and the itinerary and stops it receiving group messages), delete the itinerary (the link stops working and is purged together with the itinerary data as described in Section 4), or contact us via the email in Section 7 to delete the group link and your LINE binding. (3) Packing list and personal expenses: an itinerary's packing list (items, who is bringing them, and whether they are packed) can be viewed and edited by the itinerary owner and accepted travel companions. Expenses marked as "personal" on the expenses page are visible only to the person who created them; they are not shown to other companions and are excluded from cost splitting, settlement and the trip's total spending. (4) Trip recap page: by default, the recap page is visible only to the itinerary owner and companions. Once the owner turns on "Public", anyone with the link (no sign-in required) can see the destination, dates, daily route of places and the trip's total spending (summed by currency, excluding personal expenses), but companions' names, profile pictures and email addresses are never shown. The owner can turn public access off at any time, after which the link can no longer be viewed. (5) Calendar auto-sync and trip map: when you choose "Add to Google Calendar" or iPhone / Mac Calendar on the itinerary page, the Service creates a subscription URL containing a random secret key for that itinerary. Your calendar service (e.g. Google, Apple) periodically reads the itinerary's place names, times and locations through this URL. Anyone with the URL can see the trip schedule, so please do not post it publicly; the itinerary owner can reset the URL at any time to make the old one stop working. The "Trip map" on the itinerary page uses OpenStreetMap map data. When you open the map, your browser downloads map images directly from OpenStreetMap servers, so OpenStreetMap receives your IP address and browser information (handled under its privacy policy). The Service does not send your account or itinerary content to OpenStreetMap, and no connection is made unless you press "Show trip map".