Use by people aged 18 and over

KPin’s AI features are provided to people who confirm they are 18 or older, as required by our providers.
The welcome screen asks for your year of birth and, when the year alone cannot settle it, whether you have had this year’s birthday.
Your year of birth and that answer are used only for this check and are not stored in a cookie, on your device or on our server, and we do not ask for an identity document.
This is your own answer, not verification of identity or actual birth date.
You can read these policies, contact us about your data and delete an account without this confirmation.

Explicit terms acceptance effective 2026-11-12.
The welcome screen asks for the age declaration and Terms of Service acceptance separately.
The accepted terms version and acceptance time are also kept in the same device proof for up to one year.
An earlier age-only declaration is not treated as terms acceptance.

Age confirmation: the declaration and its time are kept in an essential cookie;
a one-way device value, confirmation time and expiry are also kept on our server for up to one year.
This lets the iPhone share sheet use a declaration already made in the app.
This record contains no original device identifier, IP, account details or birth date and is not used for advertising or age inference.
Clearing cookies requires another confirmation.
Expired server records are removed hourly.

If the check shows you are under 18, the device’s confirmation record is removed and, until the end of that day in Korea, an essential cookie keeps only the date and the fact that the check was not passed, so it cannot be answered again the same day.
It holds no age or year of birth.

Posted 2026-10-20 · age eligibility and confirmation notice effective 2026-10-20

KPIN · PRIVACY

Privacy policy

KPin (the “service”) finds and verifies Korean places from public travel and food videos and posts.
This policy explains what information the service processes and why, how long it is kept, where it is sent, and what you can ask for.

The Korean version is the original.
Every other language version, including this English text, is a translation;
if they differ in interpretation, the Korean version governs.

Amendment to this privacy policy (legal review)

Posted and effective: November 12, 2026

Together with the amendment to the terms of service, and following a legal expert's review, we have revised this policy.
Information received from YouTube and the cover verdict are now kept for a shorter time, files used for an analysis are deleted at once, and what the rights holder request form and the age check by year of birth process is set out.

  • Section 1: added what the rights holder request form collects and the age check by year of birth, and corrected that credit deductions have applied since November 9, 2026.
  • Section 3: source details of YouTube posts, YouTube video lengths and the titles of saved YouTube videos are kept for up to 30 days;
    source details are deleted at once if fetching them again shows the original is gone;
    the cover verdict is kept only as long as the cover address;
    and keeping periods were added for rights holder request records and the age-check refusal cookie.
  • Sections 5 and 6: files uploaded to Google's file storage are deleted as soon as the analysis ends, and where rights holder request alerts are received is stated.
  • Sections 10 and 11: added the age-check refusal cookie and the age check by year of birth.

The terms of service amended at the same time are accepted again on the welcome screen.
If you do not accept them, you can stop using KPin and delete your account and saved data.

Compare the wording before and after

Section 1.1, rights holder request form (new)

Before
(New wording)

After
If you use the rights holder request form: the post URL, the type of request (stopping display under copyright, or correcting place information), the requester's email address, the reason given and the time it was received.
The form needs no sign-in, and these are used only to handle requests from rights holders and place operators and to tell them the outcome.
To count how many requests can be sent in a day, a one-way hashed value of the internet connection is used for 48 hours, as for the other daily counts.

Section 1.1, age check (new)

Before
(New wording)

After
Age check: the year of birth entered on the welcome screen, and the answer to “Has your birthday passed this year?”
when it is asked, are used only to confirm that you are 18 or over and are not stored in a cookie, on the device or on the server;
no identity document is asked for.
When you pass, only the fact that you passed, the version of the terms you accepted and the time are kept in the confirmation record.
If you are found to be under 18, that device's confirmation record is deleted, and until the end of that day (Korea time) only the date and the fact that the check was not passed are kept in an essential cookie (kpin_age_refused), so that the check cannot be answered again the same day.

Section 1.1, credits and ads

Before
Credit deductions and ads apply from a date set by KPin after the mobile app launches.

After
Credit deductions and ads have applied since November 9, 2026.

Section 3, a post's source details

Before
The first line of a post's title, the publisher's name and the cover image URL: up to 90 days.
They are kept to be shown in lists and are deleted automatically when the period ends.
Cover image files are not stored.

After
The first line of a post's title, the publisher's name and the cover image URL: up to 30 days for YouTube posts and up to 90 days for other posts.
They are kept to credit the source, and when the period ends they are fetched again or deleted automatically.
If fetching them again shows that the original YouTube post has been deleted or made private, they are deleted at once.
Cover image files are not stored.

Section 3, the cover verdict

Before
The result of judging whether a person is the main subject of a cover image: up to 180 days.
Only the verdict is kept, and it is deleted automatically when the period ends.

After
The verdict that decides whether to show a cover (whether a person is its main subject, whether it carries large text): for the same period as the cover image URL (up to 30 days for YouTube posts and up to 90 days for other posts).
It is deleted automatically when the period ends.

Section 3, saved videos

Before
Saved videos and their titles: until you delete them.
Beyond 300, the oldest are removed automatically.

After
Saved videos and their titles: until you delete them.
Beyond 300, the oldest are removed automatically.
The title of a YouTube video, however, is kept for no more than 30 days after it is saved.

Section 3, map and public-data lookups

Before
Map and public-data lookups: business-licence lookups up to 7 days, tourism information up to 30 days, a video’s length up to 90 days.

After
Map and public-data lookups: business-licence lookups up to 7 days, tourism information up to 30 days, a video’s length up to 30 days for a YouTube video and up to 90 days for other videos.

Section 3, rights holder request records (new)

Before
(New wording)

After
Rights holder request records: deleted one year after the request was handled;
a request not yet handled is kept until it is handled.
The value that points to a post whose display was stopped (the block list) is kept for as long as the block lasts and holds no information about the requester.

Section 3, age-check refusal cookie (new)

Before
(New wording)

After
Cookie on a device that did not pass the age check (kpin_age_refused): until the end of that day (Korea time).
It holds only the date and the fact that the check was not passed;
the year of birth is not kept anywhere.

Section 5, Google's file storage

Before
Large files are uploaded to Google's file storage to be read, and Google deletes them automatically after 48 hours.

After
Large files are uploaded to Google's file storage to be read, and are deleted as soon as the analysis ends, whether it succeeded, failed or timed out.
If the deletion request fails, Google deletes them automatically after 48 hours.

Section 5, email

Before
Inquiry emails are received through Google's Gmail.

After
Inquiry emails and rights holder request alerts are received through Google's Gmail.

Section 6, how long Google LLC keeps it

Before
files 48 hours

After
files deleted as soon as the analysis ends (48 hours at the latest)

Section 10, age-check refusal cookie (new)

Before
(New wording)

After
Age-check refusal cookie (kpin_age_refused): if you are found to be under 18, that device's confirmation record is deleted, and until the end of that day (Korea time) only the date and the fact that the check was not passed are kept in this essential cookie, so that the check cannot be answered again the same day.

Section 11 (Children and adolescents)

Before
The service may be used only by people aged 18 or over, and you confirm yourself on the welcome screen that you are 18 or over.
KPin does not knowingly collect personal information of children under 14, and if it learns that such information has been collected, it deletes it without delay.

After
The service may be used only by people aged 18 or over, which is confirmed by entering your year of birth on the welcome screen.
The year of birth and the answer given are used only for that check and are not stored, and no identity document is asked for.
KPin does not knowingly collect personal information of children under 14, and if it learns that it has collected information about anyone below the minimum age, it deletes it without delay.

Amendment to this privacy policy (usage counts)

Posted and effective: November 9, 2026

The items below have been added to this policy.
They are there to learn how often and how quickly KPin gives an answer people can use.
They are counted as numbers only, and nothing that identifies a device or a person is stored.

  • Section 1.1: a new “usage counts” item
  • Section 1.2: a new “usage-count state” item
  • Section 3: a keeping period for usage counts
Read the added wording

Section 1.1 (added)

Usage counts: how a request for a link ended on the screen (a usable result, only a street or neighborhood, nothing found, declined as out of scope, failed, replaced by another search, or the screen left before a result), which time band the wait from your press until the screen responded and the result was drawn fell into, the day a usable place first appeared on the screen, the day you first saved a place yourself and whether the saved screen or the map or directions of a place saved earlier were opened again within the next 7 days, and whether the how-to guide shown at first launch appeared and was closed on its last page or before it, are counted as numbers only.
This is to learn how often and how quickly KPin gives an answer people can use, and whether the how-to guide reaches newcomers.
The server's counts hold only the signal, day, platform (web, iOS or Android), kind of result, whether the answer came from a stored answer or a new search, and the number in each time band, and nothing that identifies a device or a person.
The link you asked about, the places found, the request number and the exact time taken are neither sent nor stored.
So that one signal is not counted twice, a random send number made fresh for each signal, a one-way hash of the signal's contents, its day and the time it arrived are kept for 48 hours, then removed at the next hourly cleanup.
The send number is made new for every signal rather than fixed to a device, but the time it arrived is kept with it for those 48 hours.
No IP address or location is stored for these counts.

Section 1.2 (added)

Usage-count state: the status of each signal and the days they were accepted (including the day of your first save), any signal not yet sent (with its send number and the time it happened), the number of signals given up on, and until when these counts are allowed are kept in app or browser storage, and are removed when you clear that data.
While the counts are switched off none of this is kept, only a mark that they were stopped (a single number).
That mark is not a record of use and is never sent.

Section 3 (added)

Usage counts: send numbers, hashes and arrival times are removed at the next hourly cleanup once 48 hours have passed;
per-day counts are removed at the next regular cleanup once 90 days have passed.

Amendment to this privacy policy (usage counts: a map opened from an answer)

Posted: November 17, 2026 · Takes effect: November 24, 2026

One item is added to the usage counts.
They are still counted as numbers only, and nothing that identifies a device or a person is stored.

  • Section 1.1, usage counts: the day a map or directions was first opened from an answer
Read the wording to be added

Section 1.1 (added)

The day a map or directions button on an answer was first pressed is counted the same way, as a number only.
It is there to learn whether an answer was actually used;
which place or which map was opened is neither sent nor stored.

Amendment to this privacy policy (second legal opinion)

Posted: November 17, 2026 · Takes effect: November 24, 2026

We are revising this policy to reflect a legal expert’s review.
The way the service processes information does not change;
what it already does, and the rights you have, are stated more clearly and in line with the law.
The new wording enters the body on the effective day.

  • Section 2-2 (new): the basis on which the personal information of other people, such as a post’s author, is processed while finding places in a post, and what those people can ask for
  • Section 4: that information Google also processes for advertising has the character of provision to a third party
  • Section 6: that transfers outside Korea are a condition of using the service, and what you can do if you do not want them
  • Section 7: how someone who never signed in can delete their own records
  • Section 8: information another law requires to be kept, and the duty to destroy whether or not a record is deleted automatically
  • Section 10: that the trip vote cookie is stored on the device of the person who received the trip link
  • Section 12: the privacy officer’s telephone number
Read the wording that changes

2-2. Other people’s personal information in a post (new)

When KPin finds places in a public post you enter, it may read personal information of other people, such as the post’s author and people who appear in it (a name, an account name, a face or a voice).
It reads this only as far as needed to find the places.
It processes it only within a basis under Article 15 of the Personal Information Protection Act: information the person has already made public is used only within the purpose and scope for which it was made public, and anything else is processed only where it is needed for KPin’s legitimate interests and those interests clearly outweigh the person’s rights.
This information is used only to find places.
It is not used to look for people, and it is not sold or given to others.
Original videos and images are not kept;
the author’s name and the cover image address are kept, to show in lists, only for the period in section 3.
A person who appears in a post can ask, through the contact in section 12, to see, correct or delete their information or to stop its processing, and KPin takes the steps the law requires.

Section 4 (added)

However, where Google also processes the advertising identifier, IP address and ad interactions it receives from the app for Google’s own advertising purposes, that part is not work KPin entrusts to Google, so it has the character of provision to a third party.
Google’s privacy policy applies to that processing.

Section 6 (last paragraph replaced)

Transfers outside Korea that happen because KPin entrusts processing to others in order to provide the service are a condition of using the service.
If you do not agree, you cannot use the service;
you can stop using it and delete your account and saved information as described in section 7.
If a transfer ever needs a separate consent, it is explained separately in the relevant item.
Questions about transfers can be sent to the privacy officer in section 12.

Section 7 (added)

If you use KPin without signing in, you can delete your records yourself.
In the app, delete your recent history and saved places inside the app;
deleting the app also removes the data on the device.
In a browser, clear this site’s cookies and site data.
If you clear the device cookie, you can no longer see a credit balance used without signing in or your earlier place reports, so please check before you clear it.
Records kept on the server only as an irreversible one-way hash are not linked to the device you cleared, so KPin cannot find and delete them separately.

Section 8 (added)

Information that another law requires to be kept is kept for the period that law sets and then destroyed.
KPin meets this duty to destroy whether or not a record has an automatic deletion function.

Section 10 (added)

This cookie is stored on the device of the person who received the trip link, even if that person is not a KPin user or is not signed in.
You can delete it at any time in your browser settings;
after that, the earlier choices on that device can no longer be shown.

Section 12 (added)

Telephone: 070-8064-5528

Amendment to this privacy policy (nicknames)

Posted and effective: November 10, 2026

You now choose a nickname when you first use KPin.
Nicknames are kept on the server so that no two are alike, and are shown to people who receive a shared link.
If an account is linked with no nickname set, the name passed on by the sign-in provider is used.
The descriptions of shared result links, of what is kept and of how long it is kept have changed.

Amendment to this privacy policy (nearby branches)

Posted and effective: November 16, 2026

With the addition of finding the nearest branches of a chain store whose branch the video did not name (“See branches near me”), we revised sections 1, 3, 4, 5 and 6.
If you choose “Send” in the confirmation prompt, the location read at that moment is sent through our server to Kakao Map’s search to find nearby branches, and the server does not store the location.
The date and time each location was sent, the recipient and the purpose are kept for 6 months under the Location Information Act.
The details are in the location service terms.

Amendment to this privacy policy (bus and subway routes)

Posted and effective: November 12, 2026

With the addition of using where you are now as the starting point in the bus and subway route search, we revised sections 1, 3, 4, 5, 6 and 12.
Each time you choose “Send” in the confirmation prompt, the location read at that moment is sent through our server to Kakao to get the route, and the server does not store the location.
The date and time each location was sent, the recipient and the purpose are kept for 6 months under the Location Information Act.
The details are in the location service terms.

November 13, 2026: once you choose “Send” in the confirmation prompt, that yes is kept on your device and you are not asked again.
Telling you on screen each time a location is sent, and the 6-month record, stay as they are, and turning off “Use my location” in Settings withdraws the yes so that you are asked again.
In force from that date.

Amendment to this privacy policy (my location)

Posted and effective: November 6, 2026

With the optional my-location features starting, we revised the device location entry under “Not collected”.
If you agree, your location is used for calculations inside your phone only, and KPin does not receive or store it.
The details are in the location service terms.

November 10, 2026: now that the map can move to your location, we added that moving it lets NAVER Map and the sources of nearby information tell which area it is.
In force from that date.

Amendment to this privacy policy

Posted and effective: November 5, 2026

Ahead of launch, we revised this policy to match how information is actually processed.
The main changes are as follows.

  • Section 1: listed in full the items actually processed (the device cookie, trip link sharing and voting, Find & notify, the advertising component, and credits and ads).
  • Section 3: corrected the retention period of each item to match practice.
  • Sections 5 and 6: listed all the companies that KPin entrusts with processing or sends information to (Anthropic, OpenAI, Google, Apple, Kakao, NAVER), what is sent and their contact details, and stated that it is not used for AI training.
  • Sections 7 and 8: set out what is deleted when you delete an account, and how long deleted information can remain in backups (up to 90 days).
  • Sections 11 and 12: set the minimum age for use at 18 and named the privacy officer.

Product scans and shopping records

The shopping screen is not open yet.
This section applies once it is.

Only device storage is currently available.
Account storage will start after its effective date has been announced here at least 30 days in advance.

Product photos and camera frames are used to read codes on your device only.
They are not uploaded to or stored by KPin.
The camera starts only after you press Scan barcode and stops when you leave the page or open a product.
Searches are also processed locally.

Without sign-in, product codes, purchase flags and private notes are stored only on this device.
When account storage launches, the same fields, a change revision and last-save time are stored on the server under your existing one-way KPin account identifier, so they can be used on other devices.
Lists hold up to 300 products and notes up to 500 characters per product.
Device records move to the account only when you choose Import.
Recent searches and recently viewed products (including how often a product was looked up by its number) stay on this device only, never move to the account, and can be removed one by one or all at once on the shopping screen.
A note you have not saved stays on the device until you close that tab.

Shopping records are kept until you remove those records or delete your account.
Account deletion also removes shopping records.
Shopping notes are not sent to public reviews or usage analytics.
Device-only records can be removed by clearing the site's browser or app storage.

Staff reply translation · privacy policy addition

Published: 2026-10-11 · Effective: 2026-11-11

This addition applies to articles 1, 2, 3, 5 and 6 of this policy.

Only if you choose this feature, we process Korean staff audio (up to 30 seconds), typed or corrected replies, and the target language for interpretation.
Obtain the speaker’s permission first.
The microphone starts only after consent and Start listening;
canceling or leaving the screen stops capture and clears the content.
Typed replies require the same consent.
Declining does not affect place finding or prepared questions.

Posted: November 17, 2026 · Takes effect: November 24, 2026
From the effective day, the consent sentences above are replaced by the following.
This reflects a legal expert’s review.
When listening starts, a screen first tells the staff member who is speaking, in Korean, that their voice will be recorded and why.
The microphone is used only after that person presses “동의하고 말하기” on the screen.
If they press “동의하지 않음”, nothing is recorded and the screen closes.
If you cancel or leave the screen, recording stops and is cleared.
A typed reply is sent when the person typing presses the translate button.
Declining does not stop you from finding places or using the prepared questions.

Unlike public-post analysis, interpretation includes non-public conversation.
The above information is sent over encrypted connections through Cloudflare to Google LLC’s Gemini API.
It may be processed on overseas servers, including the US.
Google provides transcription and translation and may retain input and output for up to 55 days to prevent abuse.
Do not include names, contact details, payment information or other personal information.
Article 5’s description of sending only public information for post analysis does not apply to this separate transmission.

KPin does not save recordings, Korean transcripts or translations in a database, conversation history or device storage.
They appear temporarily and are cleared when canceled or when you leave the screen.
For usage limits, we separately keep a daily one-way value derived from the IP, date and a server secret, a daily count and the last request time.
Raw IPs are not stored;
records older than 48 hours are deleted hourly.
Service-wide call, token and cost totals contain no conversation or personal identifiers and follow the existing operational aggregate policy.

Google’s abuse-monitoring retention policy

Festival & exhibition news (promotional alerts) · privacy policy addition

Published: 2026-11-17 · Effective: 2026-11-17

This addition applies to articles 1, 2, 3, 5 and 6 of this policy.

Only if you agree to “Festival & exhibition news” in the iPhone app, we process your notification token (the address Apple gives this app on your phone), the alert language, the dates of consent and withdrawal and the version of the consent wording, to send app alerts about newly listed festivals and exhibitions (promotional messages).
Alerts come at most once a week, only between 8 a.m. and 9 p.m.
Korea time.
Saying no changes nothing else, and you can turn it off in Settings at any time.

The token and the alert text are delivered to your phone through Apple Inc.’s push notification service and may be processed on servers abroad, including in the US.
No name, contact detail or location is sent.

The token is kept while your consent stands and deleted as soon as you turn the alerts off or Apple reports the token can no longer be used.
The dates of consent and withdrawal and the wording version are kept for three years from the withdrawal as proof of consent, then deleted.
Every two years from your consent, an app alert reminds you that you agreed.

Ask · privacy policy addition

Published: 2026-11-12 · Effective: 2026-11-12

When you type a sentence into Ask, KPin uses it to find matching places among those it knows and shows them as place cards.
The sentence is used for this purpose only.

Your question is sent over encrypted connections through Cloudflare to Anthropic PBC’s Claude API and may be processed overseas, including in the US.
Anthropic normally deletes inputs and outputs within 30 days, with exceptions for legal obligations or policy enforcement.
Do not include names, contact details, payment information or other personal information.

When you ask a follow-up, the one question before it is sent along too.
It stays on the screen only while the screen is open and is not saved.
When KPin knows no matching place, the area and kind of place read from your sentence, or the place name, are sent to Kakao’s map search and its results are shown.
When you ask about places near a subway station, the station’s name and the kind of place are sent to Kakao’s map search to check what stands near it, even when KPin knows a matching place.
Neither the whole sentence nor anything that identifies you is sent to Kakao.

KPin does not save the sentence or the answer in a database or on your device.
To keep to the daily limit (100 questions per person per day), we separately keep a daily one-way value derived from the IP, date and a server secret, a daily count and the last request time.
Raw IPs are not stored;
records older than 48 hours are deleted hourly.

Anthropic’s data retention 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.
The items processed are as follows.

1.1 When you use KPin without signing in (created and collected automatically)

  • Connecting IP address.
    The original IP address is not stored.
    It is combined with the date of use, salted with a secret held only on the server and hashed one way (SHA-256), and only that result is stored.
    The original IP address cannot be recovered from it.
    The value used to count daily use is deleted after 48 hours.
  • 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.
  • Device cookie: KPin issues a signed first-party device cookie for your confirmation that you are 18 or over and for looking up the place reports you have made.
    The random cookie identifier is stored on the server only as a one-way hash.
  • Age check: the year of birth entered on the welcome screen, and the answer to “Has your birthday passed this year?”
    when it is asked, are used only to confirm that you are 18 or over and are not stored in a cookie, on the device or on the server;
    no identity document is asked for.
    When you pass, only the fact that you passed, the version of the terms you accepted and the time are kept in the confirmation record.
    If you are found to be under 18, that device's confirmation record is deleted, and until the end of that day (Korea time) only the date and the fact that the check was not passed are kept in an essential cookie (kpin_age_refused), so that the check cannot be answered again the same day.
  • If you report place information: the reason, the place concerned and the source post URL, the time of the report and, only where you typed them, the correct place name, address, map link, description and evidence link.
    The reporter is recorded only as the one-way hashed account or device identifier above, and on the same device that identifier lets you see the status of the reports you made.
  • If you choose a result in the saved-place search: the search words and the time, kept with a one-way hashed value made from the internet connection you used.
    This value contains no date, so the same connection always gives the same value.
    It exists so that other visitors can be offered frequently searched words, and a search word is shown only once it has been used from two or more different connections.
    Search words are deleted automatically after 90 days, and anything that looks like a link, an email address or a telephone number is not stored.
    A search for which you did not choose a result is not recorded.
  • If you receive a trip link and press Like or Not for me: a random value that tells devices apart is kept in a cookie (kpin_voter) for up to 1 year, and the server stores only a one-way hash of that value, your choice for each place and the time.
    No name or text is collected.
  • If you use Find & notify: the post URL sent from the app's share screen, its processing status and the number of places found are kept on the server for 7 days.
    If you allow completion notifications on an iPhone, the notification token is kept for up to 15 minutes and sent to the Apple push notification service together with notification text that contains place names.
  • If you open the mobile app: the app's Google Mobile Ads SDK starts, and even while no ad is being shown it may process consent status, IP address, and device and advertising identifiers under Google's policies.
  • Items used for credits and ads: credit-account records (a one-way hash of the device cookie if you are not signed in, or of the account if you are, with the remaining free analyses and credits);
    if you watch a rewarded ad, the date, the ad-reward transaction ID and a one-time verification value;
    the one-time verification value of the app-launch signal and the install identifier (one-way hashed);
    the platform and the time;
    and ad interaction information.
    Credit deductions and ads have applied since November 9, 2026.
  • If you use the rights holder request form: the post URL, the type of request (stopping display under copyright, or correcting place information), the requester's email address, the reason given and the time it was received.
    The form needs no sign-in, and these are used only to handle requests from rights holders and place operators and to tell them the outcome.
    To count how many requests can be sent in a day, a one-way hashed value of the internet connection is used for 48 hours, as for the other daily counts.
  • If you use KPin for the first time or open it again (return-visit counts): the day you first asked for a result, and whether the app screen was opened again within the next 7 days, are counted as numbers only, to learn whether KPin is useful enough to come back to.
    The server's counts hold only the signal, day, platform (web, iOS or Android) and trip status, and nothing that identifies a device or a person.
    So that one signal is not counted twice, a random send number made fresh for each signal, a one-way hash of the signal's contents, its day and the time it arrived are kept for 48 hours, then removed at the next hourly cleanup.
    The send number is made new for every signal rather than fixed to a device, but the time it arrived is kept with it for those 48 hours.
    No IP address or location is stored for these counts.
  • Usage counts: how a request for a link ended on the screen (a usable result, only a street or neighborhood, nothing found, declined as out of scope, failed, replaced by another search, or the screen left before a result), which time band the wait from your press until the screen responded and the result was drawn fell into, the day a usable place first appeared on the screen, the day you first saved a place yourself and whether the saved screen or the map or directions of a place saved earlier were opened again within the next 7 days, and whether the how-to guide shown at first launch appeared and was closed on its last page or before it, are counted as numbers only.
    This is to learn how often and how quickly KPin gives an answer people can use, and whether the how-to guide reaches newcomers.
    The server's counts hold only the signal, day, platform (web, iOS or Android), kind of result, whether the answer came from a stored answer or a new search, and the number in each time band, and nothing that identifies a device or a person.
    The link you asked about, the places found, the request number and the exact time taken are neither sent nor stored.
    So that one signal is not counted twice, a random send number made fresh for each signal, a one-way hash of the signal's contents, its day and the time it arrived are kept for 48 hours, then removed at the next hourly cleanup.
    The send number is made new for every signal rather than fixed to a device, but the time it arrived is kept with it for those 48 hours.
    No IP address or location is stored for these counts.

App screen error records are not collected yet.
KPin will announce it on this page before it starts collecting them.

1.2 Stored 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.
  • Places saved without signing in (up to 100), folder names, place notes, and trip dates and itineraries.
    They are not kept on the server unless you sign in.
    However, if you use sentence search in the Saved tab, the items described in section 5 are sent to Google through the server.
  • The Android app does not turn off Android's default backup.
    If you use Google backup, the data above in the app may be included in your Google account's backup.
  • Return-visit state: the day and time you first asked for a result, the status of signals already sent, and any signal not yet sent (with its send number) are kept in app or browser storage, and are removed when you clear that data.
  • Usage-count state: the status of each signal and the days they were accepted (including the day of your first save), any signal not yet sent (with its send number and the time it happened), the number of signals given up on, and until when these counts are allowed are kept in app or browser storage, and are removed when you clear that data.
    While the counts are switched off none of this is kept, only a mark that they were stopped (a single number).
    That mark is not a record of use and is never sent.
  • Visit photo cards: when you make a photo card at a saved place, KPin takes a photo with the camera or lets you choose a photo on your device, only when you choose to.
    The photo, the card, the date of the visit and the line you write are kept only in your browser or app storage, are not sent to the server, and are lost when you delete the app or clear that data.
    The finished card is saved to your device as an image or shared to an app you choose, only when you choose to.
    If your device asks for camera access or permission to add to Photos, allowing it is optional: everything else works without it, and you can change it at any time in your device settings.

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 processors 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/Visited” status, folder names, place notes (up to 200 characters), and trip dates and itineraries.
  • Saved videos, up to 300: the post URL, title and number of places found.
  • Your nickname: the name you chose or picked from the suggestions or, if you linked an account without choosing one, the name passed on by the sign-in provider.
    Without an account it is tied to the device cookie.
  • If you share a trip list by link: the share address, visibility setting, list name, description and area.
    Anyone who receives the link can see the list name, description, places and their order without signing in.
    Your name, private notes and trip dates are not shown.
    You can turn sharing off at any time on the sharing settings screen;
    once it is off, the old address no longer opens and the votes on that list are also deleted.
  • 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.
  • Deletion markers, up to 200.
    So that an out-of-date device cannot bring back something you already deleted, KPin keeps only an account-scoped one-way hash of the deleted video URL and the latest clear-all time.
    The deleted URL and the place details are not kept.

1.4 Not collected

  • Device location.
    My location is optional.
    Only if you agree, your location is read once when you press a button and used inside your phone to work out the straight-line distance to a place, to sort places nearest first, and to show your dot on a map.
    KPin does not store this location and, except for the bus and subway route search and the nearby branch search, does not receive it on its servers or provide it to anyone.
    If you press “Start from my location” in the bus and subway routes and choose “Send” in the confirmation prompt (once chosen, that yes is kept on your device and you are not asked again), the location read at that moment is sent through the server to Kakao to get the route, and is then discarded at once (section 4).
    If you press “See branches near me” on a chain store whose branch the video did not name and choose “Send” in the confirmation prompt, the location read at that moment and the chain’s name are sent through the server to Kakao Map’s search to get nearby branches, and the location is then discarded at once (section 4).
    The date and time it was sent, the recipient and the purpose are kept for 6 months under the Location Information Act (section 3).
    However, when the map moves to your location, it loads that area’s map and any nearby information you have turned on, so NAVER Map and those sources can tell which area it is.
    Your device keeps only the fact that you agreed and the date, and you can turn it off at any time with “Use my location” in Settings, which also withdraws the route yes so that you are asked again.
    The details are in the location service terms.
  • 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 kept in KPin's own storage or redistributed.
    How public videos and images are sent to Google while places are being found is described in section 5.
  • 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.
    The one exception is a nickname: when the person sharing has one, a marker pointing to it is added to the end of the address, and the nickname is shown on this page and in chat previews.
    Nicknames are kept on the server so that no two are alike, tied to the device cookie or to the linked account.
    If an account is linked with no nickname set, the name passed on by the sign-in provider is used;
    if someone else already has that name, a number or a random nickname is used instead.
    It can be changed at any time in Settings.
    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.

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 usage limit and the total cost limit, and preventing duplicate use and abuse.
  • Checking place-identification accuracy and improving the quality of the service.
  • Confirming that you are 18 or over and recording your acceptance of the terms, and handling place reports, inquiries and requests to exercise your rights.
  • Providing synced recent history and the trip list to users who choose to sign in.
  • Sharing by link the trip lists you choose and voting by your travel companions, and Find & notify completion notifications.
  • Showing posts looked up by two or more different people, and their places, on the Explore screen.
    Who looked them up is not shown.
  • Issuing, deducting and restoring credits and preventing abuse;
    providing ads, and rewarded ads that you choose to watch.
  • 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, processing records, place reports, accuracy feedback and click 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 made using a YouTube description and the publisher's comments: 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 descriptions, tags and comments are not stored.
  • The first line of a post's title, the publisher's name and the cover image URL: up to 30 days for YouTube posts and up to 90 days for other posts.
    They are kept to credit the source, and when the period ends they are fetched again or deleted automatically.
    If fetching them again shows that the original YouTube post has been deleted or made private, they are deleted at once.
    Cover image files are not stored.
  • The verdict that decides whether to show a cover (whether a person is its main subject, whether it carries large text): for the same period as the cover image URL (up to 30 days for YouTube posts and up to 90 days for other posts).
    It is deleted automatically when the period ends.
  • Account-synced history: until you delete it.
    Beyond 50 items, the oldest are removed automatically.
  • Saved places, folders, notes and trip itineraries: until you delete them, with up to 100 places per account.
  • Saved videos and their titles: until you delete them.
    Beyond 300, the oldest are removed automatically.
    The title of a YouTube video, however, is kept for no more than 30 days after it is saved.
  • Trip link sharing and travel-companion vote records: until you turn sharing off or delete your account.
  • Find & notify records: 7 days.
    Notification tokens: up to 15 minutes.
  • Nickname: until you change it or delete the account.
    A nickname set without an account is deleted if KPin is not opened for a year.
  • Deletion markers: up to 200 per account;
    the oldest are removed beyond that.
  • Items stored on your device: until you delete them 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 for YouTube posts and up to 1 year for other posts.
    Only the name and the area are stored;
    the frames, images and caption text 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-data lookups: business-licence lookups up to 7 days, tourism information up to 30 days, a video’s length up to 30 days for a YouTube video and up to 90 days for other videos. These hold venue information and video length only, never a user identifier.
    For a place found on Kakao, only its name, place ID and place URL are kept;
    Kakao's address and coordinates are not stored.
  • Value used to count daily use: 48 hours.
  • Records of sending your location to Kakao from the bus and subway route search or the nearby branch search (the date and time sent, the recipient, the purpose and, if you are signed in, a value made from your account): 6 months.
    The location itself is not stored (Article 16(2) of the Location Information Act).
  • Rights holder request records: deleted one year after the request was handled;
    a request not yet handled is kept until it is handled.
    The value that points to a post whose display was stopped (the block list) is kept for as long as the block lasts and holds no information about the requester.
  • Cookie on a device that did not pass the age check (kpin_age_refused): until the end of that day (Korea time).
    It holds only the date and the fact that the check was not passed;
    the year of birth is not kept anywhere.
  • Account deletion marker: 31 days after the account is deleted.
    It is used only to stop another device still signed in to that account from uploading the deleted recent history again.
    It holds only a value standing in for the account and the time of deletion, with no name or search content, and is removed automatically after that period.
  • Usage counts: send numbers, hashes and arrival times are removed at the next hourly cleanup once 48 hours have passed;
    per-day counts are removed at the next regular cleanup once 90 days have passed.
  • Return-visit counts: send numbers, hashes and arrival times are removed at the next hourly cleanup once 48 hours have passed;
    per-day counts are removed at the next regular cleanup once 90 days have passed.
  • 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.
  • Trip vote cookie: up to one year.
  • Credit-account and ad-reward records: until their service-delivery and abuse-prevention purpose ends.
    Deleting an account deletes that account's records with it.
  • 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.
What can be seen through a trip link you share yourself is as described in section 1.
The information processed by the Google Mobile Ads SDK in the mobile app is described in sections 5 and 6.

However, if you choose “Send” in the confirmation prompt of the bus and subway route search, KPin keeps that yes on your device and provides the following each time your location is sent.
You can also see routes without sending your location by searching for a starting point yourself, and each time it is sent, that screen tells you the recipient, the time it was sent and the purpose.
In the nearby branch search, a confirmation prompt appears each time you press “See branches near me”, and the following is provided only when you choose “Send”.

RecipientPurposeItemsRetention
Kakao Corp.Working out bus and subway routes and travel timesThe location read at that moment (latitude and longitude) and the destinationAs set out in Kakao’s privacy policy
Kakao Corp.Finding nearby branches of a chainThe location read at that moment (latitude and longitude) and the name of the chain to look forAs set out in Kakao’s privacy policy

5. Processing entrusted to others

ProcessorEntrusted workValues sent
Cloudflare, Inc.Hosting, execution and data storage for the serviceThe items that section 1 says are kept on the server, and the location that passes through the server in the bus and subway route search and the nearby branch search (not kept)
Anthropic PBC (Claude API)Place research on public posts (first choice)Place clues such as a public post's description and body text
OpenAI OpCo, LLC (Responses API)The same place research when Claude has an insufficient balance, an error or a slow responsePublic post text
Google LLC (Gemini API)Reading posts, judging cover images, translation, and sentence search in the Saved tabVideos, photos, cover images and text of public posts;
text to be translated, such as public reviews;
the sentence entered in sentence search and saved-place items
Google LLC (Places API, YouTube Data API)Verifying places and opening hours;
checking public YouTube information
Place-name and address strings;
YouTube video URLs
Google LLC (Mobile Ads SDK)Ad consent management;
verifying ads and rewards
Consent status, IP address, device and advertising identifiers, ad interactions
Apple Inc. (push notifications)Delivering Find & notify completion notificationsNotification token;
notification text containing place names
Kakao (Kakao Local, blog and web search)Verifying places and public web researchPlace-name, address and area strings
NAVER (NAVER API HUB local, blog and Cafe search)Verifying places and public web researchPlace-name and area strings

What is sent to the companies above does not include your account, email address or original IP address.
Post content is what was read from the public post you submitted.
Instagram Reel videos may include sound, and TikTok photos and post covers are also sent to Google as images.
Large files are uploaded to Google's file storage to be read, and are deleted as soon as the analysis ends, whether it succeeded, failed or timed out.
If the deletion request fails, Google deletes them automatically after 48 hours. KPin does not keep these files in its own storage.

Sentence search in the Saved tab: when no place matches the words you typed, your sentence and the name, neighborhood, type and saved date of your saved places (up to 100) are sent through the server to the Google Gemini API.
The same applies when you are not signed in.
KPin asks your permission on screen the first time you use this feature, and if you do not give it, word search still works as before.
Private notes and folder names are not sent.

AI training: KPin uses the AI above through paid APIs.
The paid API terms of Anthropic, OpenAI and Google state that the content sent and the responses are not used to train models, and KPin does not use your content for AI training either.
Each company may keep it for a set period for abuse monitoring and legal obligations (Anthropic: 30 days for its standard API;
OpenAI: up to 30 days;
Google: the period stated in its own notices).
If an AI answer is inappropriate or wrong, let us know through a place report or the contact in section 12.

When public text alone does not settle the exact branch, KPin first sends the public post text to Claude for research and, if that does not work, sends it to OpenAI with response storage disabled (store: false).
Google Places checks the resulting candidate only for the current request.
The post text sent, the researched web-page bodies and the full raw responses are not stored or cached in the service database or browser history.
From a Google Places response only the place ID is stored, not the name, address or coordinates.
To avoid researching the same public post again, the place candidates extracted from the research (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 are kept and reused without a fixed expiry date.
KPin deletes that research result when a confirmed error report invalidates it.
If Kakao has no listing but Google Places verifies the exact name and address of a venue currently in operation, KPin shows it with Google Maps attribution in that response only, and does not keep it in recent history, trip lists or the analysis cache.
A reusable place card is stored only when Kakao independently confirms the same venue, using Kakao's place name, place ID and place URL.
The Google Maps buttons on screen are outbound map links built from a stored Kakao place, or from a NAVER or Google Places place string verified in the current request.
Usage information arising in connection with NAVER search may be stored and used by NAVER Cloud Corp. and NAVER Corp.

For a YouTube link, KPin temporarily reads its public description, tags and the publisher's own comments through the YouTube Data API only when the free public title cannot verify a place.
The raw text is not stored.
An analysis cache built with it keeps only the time of the last check 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 ask you to sign in to a YouTube account or request any account permission.
You can review or revoke any connected Google-account access in Google security settings.

Where your device connects directly: in the cases below, your device's IP address and browser information go directly to the company concerned, and KPin does not receive that content.

  • NAVER Map.
    NAVER draws the map directly on your device.
    Because the app downloads map files in advance when it opens, so that the Explore screen opens quickly, a connection may be made even if you do not open the map.
    Map errors may be sent to NAVER's error-collection server.
  • Post cover images.
    They are loaded from the image servers of Instagram, TikTok, YouTube and other platforms.
  • YouTube and TikTok players.
    When you open a player, that platform's terms and policies apply.

Inquiry emails and rights holder request alerts are received through Google's Gmail. When KPin receives data from public bodies such as the Seoul Metropolitan Government and the Korea Tourism Organization, it sends only place names or area codes and no information about you.

6. Transfer outside Korea

Recipient and contactCountryItemsTiming and methodPurpose and retention
Cloudflare, Inc.
privacyquestions@cloudflare.com
United States and the countries hosting that provider's global infrastructureThe items that section 1 says are kept on the server, and the location that passes through the server in the bus and subway route search and the nearby branch search (not kept)Over the network when you use the serviceHosting and storage for the service / same retention as section 3
Anthropic PBC
privacy@anthropic.com
United States and other countriesPlace clues such as a public post's description and body textOver the network when places are researchedPlace research / 30 days for the standard API, with exceptions for legal and safety purposes
OpenAI OpCo, LLC
dsar@openai.com
United States and other countriesPublic post textOver the network when research through Claude did not succeedPlace research / response storage disabled;
abuse-monitoring records up to 30 days
Google LLC
googlekrsupport@google.com
United States and the countries hosting that provider's global infrastructureVideos, photos and text of public posts;
text to be translated;
the sentence entered in sentence search and saved-place items;
place-name and address strings;
ad consent status;
IP address;
device and advertising identifiers;
ad interactions;
inquiry emails
Over the network when you use the relevant feature and when you open the mobile appFinding places, translation, sentence search, ad consent management and receiving inquiries / for the period under Google policies and applicable law;
files deleted as soon as the analysis ends (48 hours at the latest)
Apple Inc.
apple.com/kr/privacy/contact
United States and the countries hosting that provider's global infrastructureNotification token;
notification text containing place names
Over the network when you have allowed Find & notify completion notificationsDelivering notifications / for the period under Apple policies and applicable law

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, turn off trip link sharing, 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 and lists, notes, saved videos, account-synced recent history, and that account's credits and ad-reward records are all deleted, and you are signed out.
    This cannot be undone.
    Analysis records made with that account are unlinked from it.
    For place reports made while signed in, the text you wrote and the evidence links are deleted and the reports are unlinked from the account.
    Content used to correct place information, such as a correct place name, may remain in a form that does not show whose it is.
    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.

Usage records from visitors who are not signed in are stored as irreversible one-way hashes, so KPin cannot find a specific person's records from information such as a name or an email address.
Place reports identified by a device cookie can be viewed on that device;
if you want them deleted, send the place you reported and the time of the report to the contact in section 12.
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.
However, deleted information may remain for up to 90 days in database backups made in case of failures;
backups are not used for anything other than recovery and are erased within that period.

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: traffic between you and the service is encrypted with HTTPS.
    Some Seoul Metropolitan Government public data is received over an unencrypted connection set by the body that provides it, and these requests contain no user information.
  • 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: your recent history, saved places and screen settings are kept on your device.
    You can clear them at any time through your browser settings or by clearing app data.
  • Authentication cookies: if you choose to sign in with Google, Kakao, NAVER or Apple, KPin uses a cookie to keep you signed in.
    Signing out clears it.
    KPin also briefly uses cookies needed only while sign-in is in progress.
  • Device cookie: a signed first-party cookie is used for up to one year for your confirmation that you are 18 or over and for looking up your place reports, and also to let a signed-out credit balance carry on.
    If you block or delete it, you will need to confirm your age again, and you will not be able to see your earlier reports or your signed-out credit balance.
  • Age-check refusal cookie (kpin_age_refused): if you are found to be under 18, that device's confirmation record is deleted, and until the end of that day (Korea time) only the date and the fact that the check was not passed are kept in this essential cookie, so that the check cannot be answered again the same day.
  • Trip vote cookie: when you press Like or Not for me on a trip link, it is used for up to one year so that the choices made on the same device carry on.
  • The Google Mobile Ads SDK in the mobile app starts when the app opens and may process advertising identifiers and ad interactions within the consent you provide.
    The app may show a personalized-ads consent screen and the iPhone's tracking permission prompt;
    if you decline, you can still use the service as before.

11. Children and adolescents

The service may be used only by people aged 18 or over, which is confirmed by entering your year of birth on the welcome screen.
The year of birth and the answer given are used only for that check and are not stored, and no identity document is asked for.
KPin does not knowingly collect personal information of children under 14, and if it learns that it has collected information about anyone below the minimum age, it deletes it without delay.

12. Privacy officer

To take overall responsibility for the processing of personal information and to handle users' inquiries, complaints and requests for redress relating to personal information, KPin has designated the privacy officer below.

Privacy officerHyeongjun Kim (representative)
Person responsible for location dataHyeongjun Kim (representative)
Contactsupport@kpin.place

Send requests for access, correction, deletion or suspension of processing, and any privacy question, to the contact 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.

BodyPhoneWebsite
Personal Information Dispute Mediation Committee1833-6972www.kopico.go.kr
Privacy Infringement Report Center118 (no area code)privacy.kisa.or.kr
Supreme Prosecutors' Office, Cyber Investigation Division1301 (no area code)www.spo.go.kr
National Police Agency, Cyber Investigation Bureau182 (no area code)ecrm.police.go.kr

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

When anything in this policy is added, deleted or modified, the change is announced on this page at least 7 days before it takes effect.
A change that materially affects your rights is announced 30 days before.

This privacy policy applies from November 16, 2026.

Last updated: November 16, 2026