Privacy policy

1. Information processed

KPin does not require a separate registration form. If you choose to sign in, KPin receives only the account information listed below from the sign-in provider. It does not directly collect your phone number, postal address, date of birth, card number or bank-account number.

1.1 When you use KPin without signing in

• Your IP address is not stored. It is combined with the date, salted with a server-side secret and hashed one way (SHA-256). Only that result is stored, and the original address cannot be recovered from it.
• The public post URL you submit (YouTube, Instagram, TikTok) and the analysis result.
• Processing records: status, duration, number of external calls, tokens used, estimated cost, number of verified places, and any error message.
• If you leave place-accuracy feedback: the verdict you chose and the corrected place name you typed.
• Clicks made on a result card, such as opening a map.
• Credit-account records: a signed first-party device cookie, remaining starter, purchased and ad-reward credits, expiry and ad-free status. The random cookie identifier is stored on the server only as a one-way hash.
• If you buy a Travel Pack in the app: app store, product ID, transaction ID, purchase time and expiry. Apple or Google processes your card or bank details and does not send them to KPin.
• If you watch a rewarded ad: date, ad-reward transaction ID and a one-time verification value. The ads SDK may process consent status, IP address, device or advertising identifiers and ad interactions under Google's policies.
• If you report a place, the reason, the place and the source post it appeared in, when you reported it, and only where you typed them, a corrected place name, address, map link, note and link to your evidence. The reporter is recorded only as the one-way hashed account or device identifier above, together with whether the review returned credits.
• If you open a result from the saved-place search, the words you searched with and the time, stored against the one-way hashed device identifier above. It exists so other visitors can be offered what people search for, and a word is only ever shown once two different people have used it. Search words are deleted after 90 days, and anything that looks like a link, an email address or a telephone number is not stored at all. A search you did not open a result from is not recorded.
• If you open the mobile app, the one-time value from the signal the app signed (stored one-way hashed), the install identifier (also one-way hashed), the platform and the time. It exists so one signal cannot be credited twice, and it contains no device advertising identifier and no location.

1.2 Stored only on your device

• A summary of up to 50 recently analyzed videos (source URL, checked time, last opened time, place names, address, area) is kept in your browser or app storage. It is not sent to the server unless you sign in.

1.3 If you choose to sign in (Google, Kakao, NAVER or Apple)

• Google: KPin requests the openid, email and profile scopes. KPin actually reads and uses the Google account identifier, verified email address and display name. It does not use or store the profile photo or other profile fields.
• Kakao: KPin receives only the Kakao account identifier and nickname; it does not request an email address. NAVER: KPin receives only the NAVER account identifier and member name; it does not request an email address. Apple: KPin receives the Apple account identifier and, when Apple provides them, an email address and name. If you use Hide My Email, Apple may provide a private relay address. Your password never reaches KPin with any sign-in method.
• KPin uses an email address as the account basis only when Google or Apple states that it verified that address. The same verified email from those two providers opens the same trip list. Kakao and NAVER accounts stay separate and use their provider account identifiers.
• The server database stores only a one-way hash of the account-basis identifier made with a server secret. The raw email address and display name are not stored in the server database. They remain in a signed, HTTP-only sign-in cookie for up to 30 days, and signing out deletes that cookie.
• Google user data is used only to sign you in, show your name, and sync recent history and your trip list. It is not used for ad personalization or user tracking, is not sold, and is not disclosed to other users or independent third parties, except for processing by the service processor listed in section 5 or where the law requires it.
• Recent history synced to the account, up to 50 items.
• Saved places, up to 100, with their want-to-go or visited status.
• Deletion markers, up to 200. So that an offline device cannot restore something you deleted, KPin keeps an account-scoped one-way hash of the deleted video URL and the latest clear-all time, not the deleted URL or the place details.

1.4 Not collected

• Device location. KPin never requests location permission and does not process personal location data. The only locations it handles are the addresses of places that appear in a video.
• Phone number, postal address, date of birth, card number or bank-account number beyond the sign-in-provider items described in section 1.3.
• Video or image files. You are never asked to upload one, and source videos and post images are not stored or redistributed.
• Shared result links. The share button on a result creates a public address (/r/…) that is the post's own address written out short. The page it opens shows only the venues that were verified, their name, area, address and map link, and never anything about the person who asked for the analysis, nor the post's caption, subtitles, menu or opening hours. One post always has one such address, so anyone who knows the post can open the same page. No sign-in and no credits are needed to open it, and opening it starts no analysis.
• The map screen. When your saved places are shown on a map, NAVER draws that map on your own device. Your IP address and browser information reach NAVER in the process, and KPin stores none of the map data that comes back. No connection is made unless you open the map.

2. Purposes

• Identifying places in a post, verifying them with a map provider and returning place cards.
• Reusing a saved result when the same URL is opened again, to control response time and cost.
• Applying the daily per-user and total cost limits and preventing abuse.
• Checking place-matching accuracy and improving result quality.
• Providing synced recent history and the travel list to signed-in users.
• Issuing, debiting and restoring starter, purchased and ad-reward credits; verifying in-app purchases; and preventing abuse.
• Showing an ad with a free saved result and a rewarded ad only when you choose to watch one.
• Counting saved places across users, with no user distinguished, to show which venues are saved together. A pair is only published once at least three distinct people saved both, and all that is published is the venue and the number of people. No user’s saved list, account identifier or save time is shown on screen or given to another user, and the venue itself is described from this service’s own analyses rather than from anything a user stored.

3. Retention

• Analysis results and processing records: kept while they serve the operating purpose. There is currently no fixed automatic deletion interval; if one is introduced, this policy will be amended and published.
• Analysis caches assisted by a YouTube description: up to 30 days from the check. They are refreshed when the video is requested again, and expired caches are removed automatically even without a new request. Raw YouTube titles, descriptions and tags are not stored.
• Account-synced history: until you delete it. Beyond 50 items, the oldest are removed automatically.
• Saved places: until you delete them, up to 100 per account.
• Deletion markers: up to 200 per account; the oldest are removed beyond that.
• On-device recent history: until you delete it or clear app or browser data.
• Deterministic failure records for links that cannot be processed: 24 hours.
• Venue names and area names read from a video’s own frames or from public web research: up to 30 days. Only the name and the area are stored; the frames, images, caption text and publishing account they were read from are not. Expired records are deleted automatically.
• Records that a map search returned nothing: up to 7 days. Only the search term and the time it was asked are kept, so a venue listed later is looked for again once the record expires.
• Map and public-register lookups: Kakao search results up to 14 days, business-licence lookups up to 7 days, a video’s length up to 90 days. These hold venue information and video length only, never a user identifier.
• Signed first-party device cookie: up to one year from issue.
• Sign-in cookie: up to 30 days from issue; deleted immediately when you sign out.
• Credit-account and ad-reward records: until their service-delivery and abuse-prevention purpose ends.
• In-app purchase transaction records: for the period required by applicable law.
• Where a law requires retention, the information is kept for that period.

4. Disclosure to third parties

KPin does not provide your personal information to third parties, except where a law specifically requires it or an investigative authority requests it through the procedure and method set out in law.

5. Processing entrusted to others

KPin also calls OpenAI (Responses API), Google (the Gemini model, YouTube Data API and Places API), Kakao (Kakao Local) and NAVER (local search on NAVER API HUB, part of NAVER Cloud Platform) to verify places. What is sent to them is the public post URL you submitted, the public text of that post, temporary screenshots of public post content made only during analysis, and place-name or address strings. The screenshots are not stored. Nothing that identifies you is sent. Only the place-name string being checked is sent to NAVER local search, and usage information arising from that call may be stored and used by NAVER Cloud Corp. and NAVER Corp. When public text does not settle an exact branch, KPin researches that public post text through OpenAI with response storage disabled (store: false) and checks the candidate through Google Places only for the current request. The post text sent to OpenAI, researched web-page bodies, the full raw OpenAI response, and Google Places response fields are not stored or cached in the service database or browser history. To avoid paying to research the same public post again, KPin stores the extracted place candidates (name, area and address), source URLs and titles, research time, model and prompt version, actual web-search count, input/cache/output/reasoning tokens and calculated USD cost without a fixed expiry date. KPin deletes that research result when a confirmed error report invalidates it. This storage and reuse begins on September 2, 2026. If Kakao has no listing but Google Places verifies the exact name and address of an operational venue, KPin may show it with Google Maps attribution in that response only; it is not added to recent history, trips or the analysis cache. A reusable place card is stored only when Kakao independently confirms the same venue, using Kakao's name, address and place ID. Google Maps buttons are outbound links built from a stored Kakao place or a request-scoped NAVER or Google Places result.

For a YouTube link, KPin temporarily reads its public description and tags through the YouTube Data API only when the free public title cannot verify a place. The raw text is not stored. A resulting cache keeps only its last-check marker and is refreshed or deleted within 30 days. This use is subject to the YouTube Terms of Service and Google Privacy Policy. KPin does not request access to a YouTube account. You can review or revoke any connected Google-account access in Google security settings.

6. Transfer outside Korea

Timing and method: transmitted over the network at the moment you use the service. You may refuse the transfer, in which case the service cannot be used. To refuse, contact the privacy officer in section 12.

7. Your rights and how to exercise them

You may request access, correction, deletion or suspension of processing at any time.

• Directly in the app: delete one recent-history item or clear all of it, remove a saved place, delete your account, and sign out. Deletions made while signed in propagate to your other devices.
• Deleting your account: press ‘Delete account’ at the foot of the app's settings screen. Your saved places, folders, notes, saved posts and account-synced recent history are all removed and you are signed out. This cannot be undone. If you do not have the app installed, or cannot complete it there, email the address in section 12 and we will delete the same things for you.
• Anything else: email the privacy officer in section 12.
• A legal representative or an authorized agent may also make the request.

One technical limit, stated plainly. Usage records from visitors who are not signed in are stored only as irreversible one-way hashes, so KPin cannot locate a specific person's records to show or delete them. This is not a way of protecting you less, it is because the records are never kept in a form that identifies you. Information tied to a signed-in account can be deleted as described above.

8. Destruction

Information is destroyed without delay once its retention period ends or its purpose is achieved. Items you delete in the app are removed immediately, and records beyond each cap are removed automatically. Electronic files are deleted by a method that prevents recovery.

9. Security measures

• Minimal collection: anything not needed to run the service is never requested.
• Hashing: account identifiers and visitor identifiers are stored only as salted one-way hashes and cannot be reversed.
• Encryption in transit: all traffic uses HTTPS.
• Least privilege: operator screens require operator authentication.
• Secret handling: access keys and secrets live only in server environment variables and are never written into source code or the repository.

10. Automatic collection devices

• Browser and app storage keeps your recent history and screen settings on your device. You can clear it at any time through your browser settings or by clearing app data.
• KPin uses a first-party authentication cookie to keep you signed in after you choose Google, Kakao, NAVER or Apple. Signing out clears it.
• A signed first-party device cookie is used for up to one year so starter credits are issued once and an anonymous balance can continue without sign-in. Blocking or deleting it prevents KPin from reconnecting that anonymous credit account.
• The Google Mobile Ads SDK in the mobile app may process advertising identifiers and ad interactions within the consent you provide. The app presents the applicable consent flow and shows no ads while a Travel Pack is active.

11. Children under 14

KPin is not directed at children under 14 and does not knowingly collect their personal information.

12. Privacy officer

Send requests for access, correction, deletion or suspension of processing, and any privacy question, to the address above. Requests are handled without delay and the outcome is communicated to you.

13. Remedies

If you need to report a privacy violation or seek advice, you can contact the following Korean authorities.

A person whose rights or interests are harmed by a disposition or omission in response to a request under Articles 35, 36 and 37 of the Personal Information Protection Act may file an administrative appeal under the Administrative Appeals Act.

14. Terms of service

The scope of the service, its accuracy limits and prohibited uses are set out in the terms of service.

15. Changes to this policy

Changes are announced on this page at least 7 days before they take effect, or 30 days before when they materially affect your rights.

This privacy policy applies from August 26, 2026.