Privacy Policy
Planlog (store app name: Plan Log - 내가 만들고 주도하는 여행앱) processes personal information as described below to provide travel planning and journaling services. This policy applies to our website and Android and iOS apps.
Effective and last updated: September 28, 2026
1. Information we process and why
We process information you enter or generate while using features, to the extent needed for the purposes below. If you do not use an optional feature, we do not request photo or location access for that feature.
- Account and sign-in: email address, nickname, authentication provider and account identifiers for registration, sign-in and account identification. Supabase Auth handles email/password authentication; Google or Apple handles the social sign-in you select.
- Travel preferences: your departure city, travel frequency, companions, interests, languages, dietary preferences, transport, budget and other preferences you enter, for planning and recommendations.
- Plans and journals: travel groups and members, itineraries, flights and accommodation, saved places, addresses and coordinates, notes, visit dates and time zones, photos, watched brands, checklists and other information you register, for storage, retrieval, group collaboration and travel assistance.
- AI requests and searches: questions, search terms, attached images and relevant trip/place context for place recognition, travel assistance, recommendations, information extraction and product searches.
- Device and usage information: access times, IP address, browser/device information and request/error records for communication, security, troubleshooting and operation. Optional usage analytics are collected after separate consent.
2. Current and background location
Current location is used to search nearby places, calculate and sort distances to saved places, display maps and find branches of watched brands. Depending on device permissions, we use precise or approximate location. Approximate-only access may reduce distance and alert accuracy.
After your consent and permission, this feature uses background location, including while the app is closed or you are using another app, to detect entry within 500 metres of stores of brands you have registered and enabled alerts for. During your trip, the device's geofencing service monitors saved branches and displays arrival notifications on the device.
When nearby branches are searched, the search-origin location and branch information are processed and stored on our server. Alert targets and notification history are stored on the device. This feature does not continuously record your entire movement route on our server.
You can turn off alerts for each brand or revoke location/notification permissions in device settings. Travel planning and journaling features that do not require location remain available when you decline permission. Logging out or disabling the alert feature removes the related device alert registrations.
3. Photos, visit journals and sharing
We upload only photos you select. Visit-journal photos are compressed and processed to remove photo metadata such as location during upload. Faces, documents and addresses visible within an image are not automatically obscured.
Visit journals are private to the author by default. They are shared with travel members when you choose that visibility. Collaborative information registered in a travel group, such as places, itineraries and notes, is visible to group members.
When you save a share image or share through an external app such as Instagram, the photos and text you select are provided to that destination. Information you publish on an external service is governed by that service's policies and visibility settings.
Content safety and report information
We process reporter and target identifiers, report reasons and descriptions, limited text snapshots, block/hide lists, community consent and moderation history for safety and appeals. Authorized operators can review the reported content and available target photos. Submitted text and visit photos are sent to OpenAI for automated safety checks. Records are retained as necessary for report handling and appeals, then deleted when the purpose ends. Contact admin@planlog.io for access or deletion requests.
Trip expenses and receipts
We process payer and participant names (including guests), original amounts and currencies, exchange-rate references, settlement amounts, payment confirmations, refunds, change history and attached receipts to provide trip expense tracking. Expenses and attached receipts are shared with the trip’s members. When you select receipt OCR, the image is sent to OpenAI to extract merchant, date, currency and amounts. Cover sensitive information such as card numbers before attaching a receipt. You review OCR results before saving an expense. Planlog does not move money or connect to bank accounts. Records are retained as needed for the trip and expense service; contact us for deletion requests.
4. External services and overseas processing
We use the external services below to provide Planlog. Information necessary for each request is transmitted over the network and may be processed on overseas providers' systems. The policies of the providers also apply to external sign-in and sharing features you select.
| Service | Processing | Policy |
|---|---|---|
| Supabase | Account authentication and database storage of account, trip, place and visit records and uploaded photos | Supabase |
| Vercel | Web/API hosting, request/error processing and consented usage analytics | Vercel |
| Selected Google sign-in; search terms, location, origin and destination needed for maps, places and routes; consented Google Analytics statistics | ||
| Apple | Account authentication and identifiers for selected Apple sign-in | Apple |
| OpenAI | Requested AI analysis and automated safety checks of submitted text and visit photos | OpenAI |
| SerpApi | Product/price search using terms such as product names | SerpApi |
We disable response storage in AI requests, but this does not mean that a provider's security or abuse-prevention records are immediately deleted. See the linked provider policies for their processing and retention practices.
You may stop using features requiring external processing, withdraw optional permissions, or request deletion of your account and stored information. If you do not wish to use essential processing such as authentication and storage, your use of the service may be limited.
5. Retention and disposal
Account information is retained while the account remains active. Trip, place and visit records and photos are retained until the relevant information is deleted or account deletion is processed. Unsaved drafts may remain on the device or server for recovery and can be removed by discarding the draft or requesting deletion.
Information is deleted when its processing purpose ends. If applicable law requires retention, we retain that information separately for the applicable period and then dispose of it. We explain the specific scope and any legal retention exceptions when handling a deletion request. Electronic information is deleted in a manner intended to prevent recovery.
Service operation records and external providers' security and backup records are processed under their respective operational and retention policies. Not every copy is necessarily removed simultaneously at the moment of a request.
Delete your Planlog account and data
Request deletion of your Plan Log (Planlog) account and associated data, or delete your account yourself. You do not need to reinstall the app.
Delete your Planlog account and data · Sign in and delete account
Trips with other members remain. If you are the only owner, ownership passes to the earliest remaining member. Schedule entries linked to your deleted places and previous generated itinerary/change snapshots are cleared. Shared expense amounts, allocations and payment confirmations remain, but your account link, name, authored descriptions and receipts are removed. Jointly managed schedules and souvenirs, content written by others, and copies already saved by others may remain. Email us to request removal of personal information in specific shared content.
Direct deletion takes effect in the active service database when it succeeds; there is no account-deletion grace period. Failures are not shown as completed and can be retried. Email requests are processed after ownership verification, followed by a completion reply or an explanation of any further action needed. Shared records with the account link removed remain until the trip is deleted. Infrastructure backups and security logs follow each provider’s retention policies, so not all copies disappear immediately. If a legal retention obligation applies, we separately explain the affected data, basis and period.
7. Cookies, device storage and optional analytics
We use cookies, browser storage and device storage for sign-in sessions, language/display preferences, draft recovery and feature state. Blocking or clearing essential storage may sign you out or remove unsaved drafts.
Google Analytics and Vercel Analytics usage statistics are enabled after consent. You can change your choice in Analytics settings. Your consent choice is kept for up to 180 days. We remove sensitive path components such as travel-group identifiers and query parameters outside our allowlist from analytics transmissions.
8. Safeguards
We protect personal information through authentication and access checks, encrypted communication and authorization checks for private photos. Authentication is handled by our authentication service, and access to information is restricted to what is needed for service operation.
9. Operator and privacy contact
Business operator: 영앤리치 (Young & Rich)
Privacy contact: 박형주 (Park Hyeongju)
Email: admin@planlog.io
Contact the above address for privacy inquiries, exercise of your rights and account deletion. In Korea, you can also seek advice from the Personal Information Infringement Report Center (118 within Korea, privacy.kisa.or.kr).
10. Changes to this policy
When processing practices or applicable rules change, we update this page with the changes and effective date. We notify users of material changes affecting their rights through the service or other appropriate channels, and seek consent when separate consent is required.