Effective: September 14, 2026 (section 2-2 Community Board added) · Previous effective date: August 27, 2026 · Privacy Officer: Jiyoung Park · Change history
Amendment notice (September 14, 2026). The Community Board section (2-2) is in effect from September 14, 2026. The effective date originally announced as September 21, 2026 was moved to September 14, 2026 (notice posted September 11, 2026). See section 2-2 · Change history
This English version is provided for reference only. The Korean-language version is the authoritative text and governs in the event of any conflict. · 한국어 원문 보기
① TripGo!go! can be used continuously without logging in; if you don't log in, we don't require personally identifying information such as your name or contact details.
② Travel conditions you enter (region, dates, number of travelers, etc.) are processed solely to generate your itinerary.
③ Itineraries created without logging in are stored only on your device (browser) — we do not keep them on our servers under an account.
④ For service improvement, we may keep server-side request-processing records (request ID, timestamp, error details) that do not identify a specific individual.
① We offer three login methods — Kakao, Google, and email verification code — and do not accept separate ID/password registration.
② Data collected (by login method):
· Kakao — unique Kakao ID, nickname (required) / profile photo (optional)
· Google — unique Google ID, name, email address, profile photo
· Email — email address
③ Purpose: member identification and account management, saving/restoring itineraries across devices, processing purchases and maintaining purchase history (for paid one-time items).
④ Retention: the above is destroyed immediately upon account deletion, except where law requires longer retention of specific items.
⑤ Users under 14 may not use this service's login features. If a user is found to be under 14, we restrict the account's registration or delete the collected information without delay.
① We use Google Analytics 4 (provided by Google LLC) to understand service usage and improve the service.
② Data collected: pages/screens visited, clicks and other usage behavior, device/browser type, approximate location (country/city level), and access time. We do not send personally identifying information such as name or email to Google Analytics.
③ Purpose: visitor counts, popular pages, usage paths, service improvement.
④ Retention: per our Google Analytics configuration, event data is retained for up to 14 months and then automatically deleted.
⑤ Third-party transfer: the data above is transferred to Google LLC (USA); Google's own Privacy Policy applies.
⑥ Opt-out: block cookies in your browser settings, or install the Google Analytics Opt-out Browser Add-on. Opting out does not affect your ability to use the service.
Information you provide when contacting us via our KakaoTalk channel or by phone (0507-1338-9149) — such as your Kakao profile nickname or a phone number given during a call — is processed only for the purpose of handling your inquiry. Support records are deleted within a reasonable period after the inquiry is resolved.
① We do not sell or otherwise provide your information to third parties.
② Identity verification: we use Kakao Corp. and Google LLC as identity-verification providers for login; in this process, profile information each company holds about you (see the per-method items in Section 2) is transmitted to us.
③ Processing entrusted to third parties: we entrust the following processors with parts of our service operations.
| Processor | Task | Data processed | Storage location | Retention |
|---|---|---|---|---|
| Supabase, Inc. (USA) |
Member authentication and account storage | All authentication/account data | South Korea (Seoul-region data center) | Until account deletion or end of contract |
| Resend (Plus Five Five, Inc., USA) |
Sending verification codes and other service emails | Email address | - | Deleted promptly after sending |
| Google LLC (USA) |
Analytics (Google Analytics 4) | Usage behavior, device/browser info, approximate location | Overseas (USA) | Up to 14 months per Google Analytics settings |
④ Cross-border transfer notice: all processors above are entities located overseas (USA). In Supabase's case, the actual data is stored in a data center in the Seoul region of South Korea, but the operating entity, Supabase, Inc., is a U.S. company, as is Resend (Plus Five Five, Inc.). The items transferred, recipients, purposes, and retention periods are as shown in the table above.
You may delete device-stored data at any time via your browser settings. To view, correct, or delete (withdraw) a logged-in account, please contact us. Other inquiries: contact@tripgogo.co.kr · 0507-1338-9149
If we introduce a new feature that expands the personal data we collect — such as new analytics tools — we will revise this policy and announce it within the service before it takes effect.
The following is part of this policy from September 14, 2026. The Korean text governs.
① Items: nickname, posts (title, text, city, travel dates), comments, times posted/edited/taken down, report contents (reason, details), moderation records (target number, action code, reason code, time), and the identifier linking your login account to your community profile.
② How collected: entered by you (report and moderation records are created during processing).
③ Purpose: posting and displaying community content, editing/deleting your own posts, handling reports and disputes, and grounds for moderation.
④ Retention: published posts are kept while published. The text and attachments of taken-down posts (taken down by you or hidden by us, including comments under them) are kept for 90 days from takedown; the title and text immediately before an edit for 90 days from the edit; report details for 90 days after the report is resolved; report records for 1 year after resolution; moderation records for 1 year after the action. For posts under an open report, the period restarts when the report is resolved.
⑤ On account withdrawal: your posts and comments are taken down and destroyed after the periods above, your nickname changes to "Withdrawn user", and the information linking your login account to community records is deleted after the login account is deleted.
⑥ Preservation exception: where preservation is required by law, an investigation, or litigation, we may postpone destruction, the nickname change, and deletion of the linking information until the reason ends. Posts remain hidden in that case.
⑦ Destruction method: post titles and text are overwritten with fixed wording so the original is erased, and attachments are deleted from storage. Pre-edit text, report records, and moderation records are deleted; report details are cleared. After the original is erased, a record that the post existed (times, city, community profile number) remains. Destruction is run by staff every Monday after review, so it may take up to 7 more days after the period ends.
⑧ Note: posts are visible to people who are not logged in. Do not include personal data such as phone numbers, passport numbers, or booking numbers.
You can edit or delete your own community posts yourself; appeals about posts hidden by us go to customer support.
