Privacy Policy
Posted: October 3, 2026 · Effective: October 10, 2026 · Version 2026-10-10 · Previous version (2026-09-29)
1. Controller and privacy officer
TripDrop (the service operator) is the controller of personal data processed by this service. Privacy contact: TripDrop Operations / Phone +82 502-6805-2819 / Email tripdrop2026@gmail.com. Access, correction, deletion and restriction requests are handled promptly at this address.
2. Data and purposes
We process your Google account identifier, email, name and profile image for sign-in. We receive and parse the sender, recipient, subject, body and attachments of flight, hotel and rental confirmation emails you intentionally forward, plus booking numbers, itinerary, places and times, to build your travel timeline and provide original evidence. Access and error logs are used for security and troubleshooting.
3. Consent and necessity
Before registration, we separately disclose and obtain affirmative consent to the Terms, account/booking-email processing, and overseas processing. Declining required processing means the account and email-to-itinerary service cannot be provided.
4. Retention
Account, itinerary and consent records are kept until account deletion. Successfully parsed original emails and attachments are retained for 90 days; unsupported messages requiring review for up to 180 days; and unrelated messages for 30 days, then deleted. Minimum records may be retained where legally required.
5. Google user data
Sign-in requests only openid, email and profile. Read-only Calendar permission is requested separately when you enable Calendar import. We import only events whose titles begin with TD and that overlap your trip dates — just the title, time, location and description. Booking vouchers are not written to Google Calendar. Turning import off stops further API calls; you may also revoke access in your Google Account. When you disconnect, we revoke Google access immediately and delete the stored credentials. Imported events can be kept or deleted at your choice. Use of Google data complies with the Google API Services User Data Policy, including Limited Use. It is not used for ads, sale, credit decisions, or training general-purpose AI models.
6. Processors and international transfers
We use Google LLC for authentication and optional Calendar access, and Mailgun Technologies, Inc./Sinch for receiving and forwarding booking emails. When you sign in, forward mail, or sync Calendar, relevant data may be securely processed in the United States or other service regions for the period required by the service provider's policy and contract. Refusal prevents the relevant core feature. Firebase Cloud Messaging and Apple Push Notification service (push delivery) are also used; their servers may be outside Korea.
7. Sharing and human access
We do not sell personal data or share it with advertisers. Human review of a specific failed booking email is allowed only after a clear user request or affirmative consent for that item, except where needed for security or law.
8. Your rights
You may request access, correction, deletion, restriction, withdrawal and account deletion through Settings or our contact address. Calendar import can be disabled at any time.
9. Security
We use encrypted OAuth tokens and HTTPS, access controls, administrator authentication, separated secrets, processing logs and least privilege. Forwarding addresses and original vouchers are account-restricted.
10. Cookies and changes
Essential cookies support sessions, OAuth integrity and language. Material changes are announced in-product, and renewed consent is obtained before new purposes or materially different Google-data uses.
12. Destruction procedure
Personal data is destroyed without delay once the retention period ends or the processing purpose is fulfilled. Data contained in disaster-recovery backups is destroyed within 14 days at the latest, and backup files are kept with restricted permissions. Electronic files are permanently deleted in an unrecoverable manner; any paper documents are shredded or incinerated. On account deletion, account, itinerary, consent records and attachments are destroyed immediately, while the minimal records required by law are kept separately and destroyed in the same way at the end of their retention period. Destruction is recorded internally.
11. Booking email auto-import
Currently, only forwarding to your dedicated address is supported. TripDrop does not request Gmail read access or automatically import Gmail messages; only flight, hotel and rental confirmation emails forwarded to the dedicated TripDrop address shown in your account are processed and registered into your itinerary. Promotions and forum emails are excluded. If Gmail-connected import becomes available in the future, this policy will be updated and your consent will be obtained again.
13. Inquiries
We store the inquiry type, message, selected booking email ID and sending domain. Kept 1 year after the reply, deleted immediately on account deletion.
14. Push notifications
We store your browser push subscription (endpoint and keys); deleted when you turn notifications off or delete your account.
15. Access logs
We record when a login session was created or revoked and the reason; records are deleted 30 days after revocation.
16. Account deletion record
For dispute handling we keep a hashed email and the deletion count for 1 year.
17. External app handoff
Grab, Yandex Go, Kakao T, GO, Uber and Google Maps receive only the destination address; no other personal data is shared.
18. Service usage records (analytics)
To improve the service and understand usage, we collect device type (mobile/tablet/PC), whether the app is installed to the home screen, screen and feature usage (tab views, detail/support/deletion screens, ride-hailing and expense-export clicks), language and operating system, access time and an anonymous session identifier. Records are kept only for signed-in users, are never used for advertising, profiling or third-party sharing, and are deleted by a scheduled purge 13 months after collection. Collection under this section starts on the effective date of this revision (October 8, 2026); the feature stays off until then.