This is an English translation provided for convenience. If it differs from the Korean original, the Korean original prevails. Korean original

Kevios Privacy Policy

Effective: November 8, 2026 (Challenge Forest chat storage, past chat and report copies, and automatic checks of meetup photos and text: November 14, 2026) · Last revised: November 8, 2026

This policy applies to Kevios Town, Kevios Saju and Kevios Challenge, which are provided with a Kevios account. Changes are announced in Notices and recorded in the change history of the Korean original.

Article 1 (Purposes of Processing Personal Information)

Kevios (the "Service") processes personal information for the following purposes.

• Providing saju, compatibility, astrology and Zi Wei Dou Shu readings in Kevios Saju (calculating and showing readings from the saju information the user enters), and daily fortunes by zodiac animal (including notifications)
• Recording goals in Kevios Challenge, calculating completion rates and streaks, and providing weekly reviews
• Creating and publishing statistics on trends in Kevios Challenge pledges (analyzed after being changed so that the writer cannot be known, and only statistics that cannot identify individuals are published)
• Providing Kevios Challenge meetups (members opening, finding and joining meetups, attendance records, schedule notifications, messages between members of the same meetup, the Challenge Forest (showing avatars and account nicknames, relaying chat, and from November 14, 2026 storing chat and showing past chat), ratings and the resulting restrictions on use, finding meetups by a chosen neighborhood (dong), meetup search and popular and suggested search terms, and, for members who already joined an earlier round opened by the Operator, the meetup nickname, today's done mark, short notes and cheers), handling reports and deletion requests, and from November 14, 2026 automatically detecting obscene meetup photos and profile photos, checking meetup text against banned words, and blocking accordingly
• Member sign-up, login and identity verification
• Providing the Service and preventing misuse, abuse and opinion manipulation
• Resolving disputes and handling complaints
• Complying with relevant laws such as the Protection of Communications Secrets Act
• Counting service usage and return visits (visits by screen type and path group, return visits by random visit identifier, and totals by purpose of use, stage of use and first referral source. Not linked to member accounts)
• Calculating regional real estate interest and monthly rent and lease interest (aggregate statistics)
• Showing ads that fit the context of the screen being viewed, such as the board, post or region
• (Only with optional consent) Analyzing detailed usage behavior recorded per user (click targets, content exposure and time spent, ad impressions and clicks) and measuring ad performance. Daily totals of time spent per screen and feature use counts that do not record whose they are, and the visit counts above, are processed regardless of consent
• Suggesting and auto-completing post classifications (region, property type, transaction type, nature of the post)

Article 2 (Personal Information Collected)

Saju information in Kevios Saju is visible only to the user who entered it, is stored encrypted, and does not appear in nicknames, posts, comments or profiles on Kevios Town. It is not used for ad targeting or provided to third parties. Users are told to enter another person's information only when that person knows and agrees (Article 15(1)6 of the Personal Information Protection Act, and the user's warranty in the Terms of Service). That person can ask whether their information was entered and where it came from, and request deletion, by the method in Article 8.

Goals and records in Kevios Challenge are visible only to the user who entered them, and goal names, descriptions, notes and pledges are stored encrypted. However, when a user opens or joins a meetup, some of this is visible to others within the scope of providing Kevios Challenge meetups in Article 1 (next paragraph). Goal content and records do not appear on Kevios Town or Kevios Saju screens and are not used for ad targeting or provided to third parties. There are no fields for sensitive information such as health, and the Terms of Use ask users not to write such content. This processing is to provide the goal recording service the user requested (Article 15(1)4 of the Personal Information Protection Act). Pledges may be changed so that the writer cannot be known (pseudonymization) and then used to produce statistics on what people focus on and want to do. Those statistics are published only in a form that cannot identify individuals (Article 28-2(1) and Article 58-2 of the Personal Information Protection Act).

The photo, name, date and time, whether it is online, neighborhood, participation fee, introduction, notes, tags, category (the text typed in when "Other" is chosen), number of rounds, capacity, and numbers joined and attended of a Kevios Challenge meetup are visible to anyone, including non-members. Because the host publishes this content and any contact details they write in the introduction or notes, it is not encrypted, and if it contains faces or sensitive information such as health, it may be visible to anyone. Participants' profile photos are visible without nicknames only to logged-in members, and the same photo lets others recognize the same person in other meetups. The venue and map address are visible only to participants of that meetup and are stored encrypted. The account nickname set at sign-up is visible to message partners and to review partners who attended together. This nickname is the same as the one shown on posts and comments on Kevios Town, so others can recognize the same person. If you do not want this, you can simply not join meetups, but what others have already seen cannot be erased from their memory. Notes, skips and their reasons, completion rates, other goals and other members' ratings are not visible. For members who already joined an earlier round opened by the Operator, until that round ends their meetup nickname, today's done mark for that meetup goal and the notes they wrote are visible to participants of the same round, and cheers they send are made known to the recipient; if they do not want this to be public, they can delete their notes or leave the round. Messages are stored encrypted and the Operator does not read them, except for a single message reported by the member who received it, which is read to handle the report. When you enter the Challenge Forest, your account nickname and avatar are visible to the host and participants who are in at that time, and the time you confirmed the notice on first entry is recorded. For online meetups, the time of first entering between the start and end of the meetup is recorded as attendance and marked as done for that meetup goal, and members recorded as attending together can see each other's account nicknames and review each other even if they did not meet in the Forest. Each entry and exit is not recorded. Tags are checked by machine for banned words and contact detail patterns before saving, flagged tags are not saved, and the entered text and check results are not kept. Challenge Forest chat is checked by machine for banned words and contact detail patterns before sending, and no person reads the content in this check. Messages written before 00:00 on November 14, 2026 are only relayed to people who are in at that time and are not stored, so there is no past chat or report copy, and reports on those messages are checked only with what the reporting member wrote and sent. Messages written from that time are stored encrypted, are visible with account nicknames to the host and participants of that meetup who come in, and are also visible to people who join after they were written. Members who have not joined or have left cannot see them, and messages written by a member who left are taken down from other people's screens and shown again if they rejoin. Access closes 5 hours after the meetup ends, or immediately if participation is canceled or the meetup is closed, and after that even the host and participants cannot see it on screen. If you write sensitive information such as health, it may be visible to these people, so please do not write it, and you can delete what you wrote on the spot. Messages deleted line by line are taken down from the screen and remain in the stored copy until the retention period ends for handling reports. Pressing "Remove chat content" on the member information screen immediately deletes the stored chat written by that member, including messages deleted line by line or taken down, and only copies attached to reports in progress remain until handling is finished. The Operator does not browse or search chat as a list; when a report is made, only a copy of the reported message and up to 5 lines before and after it, or for reports made after the meetup ended or by email, up to 30 lines from 30 minutes before and after the time written, is read to handle the report. If there is no message from the named nickname in that time, no copy is made. A copy may include other members' messages and messages that were taken down or deleted. Relaying, showing and showing past chat provide the feature the user chose (Article 15(1)4 of the Personal Information Protection Act), and the notice confirmation record, checking reports after the meetup ends and retention to prevent misuse follow subparagraphs 4 and 6 of the same paragraph. To delete or change public content, edit it on the meetup screen, and if you do not want a photo, do not upload it or delete it. This processing provides the meetup features the user chose and handles reports, so separate consent is not obtained (Article 15(1)4 and Article 23(3) of the Personal Information Protection Act). Goals you use alone are not published to meetups.

Kevios Challenge meetup search looks in meetup names, introductions, tags, categories (the text typed in when "Other" is chosen) and neighborhood names. It does not look in hidden content, venues, map addresses, notes, nicknames or messages. Search term counts are totals that do not record who searched, are not matched with member or access records, and are not used for ad targeting or provided to third parties. However, if a search term contains a person's name or similar, that text may be personal information, so it is processed only as far as needed to provide popular and suggested search terms (Article 15(1)6 of the Personal Information Protection Act). Popular search terms show only words that were searched several times and appear in the names, categories or neighborhood names of currently public meetups. Suggested search terms show the names, categories and neighborhood names of currently public meetups, and these values are not stored separately. Because search terms are part of the request address, they may be left in error logs with the IP address if an error occurs, and this is processed as a service usage record.

Web push notifications are stored separately by Kevios Town, Kevios Saju and Kevios Challenge, and because this processing is to send notifications the user requested, separate consent is not obtained (Article 15(1)4 of the Personal Information Protection Act). They are used only to send notifications and not for ad targeting or statistics. A daily fortune notification contains only one line of that day's fortune for the chosen zodiac animal and a link to that fortune screen. Kevios Challenge meetup notifications contain only the meetup name, start time and a link to that screen, and are sent on the morning of the meetup and 1 hour before it starts. Message notifications do not include the message content.

The Service does not receive the email, name, profile photo or date of birth of social accounts.

By default, the Service does not collect unique identifiers such as resident registration numbers or precise GPS locations. For visit statistics, it stores a random identifier in the browser and counts visits and return visits by screen type. This identifier is not linked to member information and is stored on the server only in a form that cannot be restored (a hash). The visit identifiers of Kevios Town, Kevios Saju and Kevios Challenge are different and not connected to each other, and visit records are not matched with member or access records. If features based on precise location are introduced, separate notice and consent procedures will be put in place.

Kevios Challenge meetups use the neighborhood the user chooses and do not measure the current location. Distance is calculated from the center point of the chosen neighborhood. A neighborhood chosen by a non-member is stored in that browser. Avatar positions in the Challenge Forest are positions on screen, not real locations, and are not stored.

Article 2-2 (Automatic Suggestion of Post Classifications)

1. The Service may automatically suggest a classification for a post using the title and body of the post being written, the selected board and the region information viewed just before.
2. Suggestions are made automatically, but the user decides the final classification. Users can ignore or change a suggestion, and the reason for the suggestion is shown on the writing screen. Therefore this feature is not an automated decision completed without the user's confirmation.
3. The body analysis for suggestions is performed inside the user's device (browser), and unpublished content being written is not sent to the server.
4. The Service does not send the user's IP address to outside businesses for classification suggestions.
5. If IP-based location estimation is used for classification suggestions, the estimate is made only down to the province or metropolitan city level and locations at the city, county or district level or below are not estimated from IP. The estimate is used only for suggestions, is not stored or accumulated separately, and is not shown to other users.

Article 2-3 (Kevios Challenge Meetup Ratings and Restrictions on Use)

1. Ratings start at 100 and change according to the stars given by members who attended together (5 stars +1, 4 stars 0, 3 stars -1, 2 stars -3, 1 star -5).
2. At 70 or below you cannot open meetups, and at 30 or below you cannot open or join meetups. These restrictions apply automatically according to the score and are announced through the notification inbox. When the rating falls to 30 or below, you are removed from upcoming meetups you have joined and upcoming meetups you opened are closed, and 90 days after the date it fell to 30 or below the rating returns to 31. If you sign up again after deleting your account, the rating starts again at 100.
3. The only information used for ratings is review records, the score and the date it fell to 30 or below, and these are not disclosed to other members.
4. Users can request an explanation of the reason for a restriction, object to it, or ask for a review by a person at [email protected], and the Operator will reply within 10 days and lift the restriction or correct the score if needed.
5. A request to reveal who gave a review may be limited if it risks unfairly harming that person's interests (Article 35(4)2 of the Personal Information Protection Act).
6. Meetup use restrictions on members who break the conditions of use, such as by threats, are set separately from ratings. When the Operator checks the reported content directly and decides, the restriction applies to the sending account of that message or Challenge Forest chat and the member is notified. When restricted, the member cannot open or join meetups, is removed from upcoming meetups they have joined, and upcoming meetups they opened are closed. The Operator may also restrict only the opening of meetups by the host of a reported meetup, and the member is notified in that case too. These restrictions last until the Operator lifts them, and objections can be made as in item 4. The reporter is not disclosed.

Article 2-4 (Automatic Checks of Kevios Challenge Meetup Photos and Text)

1. From 00:00 on November 14, 2026 (Korea time), before saving, the Service automatically checks meetup photos and profile photos uploaded by members, and photos from an earlier round carried over to the next round, inside its servers, and blocks them if judged obscene. For photos from an earlier round, it deletes the same photo in that series without human confirmation and notifies the host. It also checks meetup names (including text typed in for the "Other" type), introductions and notes against banned words and blocks them if flagged. Photos are not sent outside for this check, and messages and report reasons are not checked against banned words. Photos and text uploaded before then are not re-checked all at once; text is checked only in fields that are edited, and photos only when carried over to the next round.
2. Deleted photos are not kept. Photos and text that were blocked and not received are not stored. The record kept is the time, field type, result (blocked or check failed), score band, check version and account ID; file names, hashes and entered text are not kept.
3. Records are used only to handle objections and inquiries and to inspect the checks, and are not disclosed to other members. Apart from blocking or deleting that photo or text as a result of the automatic check, accounts or meetup use are not restricted and ratings are not lowered. When the check cannot be performed, photos are temporarily not accepted.
4. Users can request an explanation of why something was blocked or deleted, and a review of the record by a person, at [email protected], and the Operator will reply within 10 days. Please do not attach photos to the email.

Article 3 (Handling of IP Addresses)

IP addresses are an item handled with particular importance in this Service.

• Reason for collection: Because this is an anonymous community, the IP address at the time of writing posts and comments is collected to prevent opinion manipulation, staged posts and abuse of multiple accounts.
• Display and transmission: IP addresses are not shown on post or comment screens, and are not included in responses sent to other users. Users can see part of their own IP record on the My Info screen.
• Internal access: Full IP addresses can be viewed only by Service administrators, and are provided when an investigative agency makes a lawful warrant or cooperation request.
• Retention period: After being kept for the period set by the Protection of Communications Secrets Act (3 months), the IP addresses of posts, comments and votes have their last parts removed so that only the first two parts (for example 175.123) remain, and access logs are deleted. The retention period may be extended due to requests from investigative agencies and the like.
• User rights: Users should be aware that even if their post is deleted, the related IP record may remain for the above retention period.

Article 4 (Retention and Use Period of Personal Information)

• On account deletion: account information (email, password, social account identifier, my neighborhood, notification devices, access logs) is deleted immediately. Posts and comments remain with the author changed to (deleted)
• IP of posts, comments and votes: masked to keep only the first two parts after 3 months (automatically every day)
• Service access logs: deleted after 3 months (automatically every day)
• Access records of the personal information processing system (staff): 1 year
• Visit count source data (hash) and detailed behavior and ad source logs (with optional consent): 13 months from collection
• Regional, monthly rent and industry interest statistics: for as long as the Service operates, after conversion into aggregate statistics that cannot identify individuals
• Report and moderation records: 3 years after handling is completed. If a dispute related to the record, such as a lawsuit, mediation or investigation, is in progress, they are kept until it ends
• 1:1 inquiries (title, content, reply): until account deletion (deleted immediately on deletion)
• Complexes chosen for real transaction alerts: until alerts are turned off or the account is deleted (deleted immediately when turned off or deleted)
• Web push notification subscriptions of each of Kevios Town, Kevios Saju and Kevios Challenge: until notifications are turned off, the push service reports that the subscription no longer exists, or the account is deleted (deleted immediately). If only daily fortune notifications are turned off on Kevios Town, the zodiac animal, delivery time and dates sent are deleted immediately
• Kevios Saju saju information and reading results: until the user deletes them or deletes the account (deleted immediately). Record of consent to the Kevios Saju Terms of Use: until account deletion
• Kevios Challenge goals and their records and notes: until the goal is deleted or the account is deleted (deleted immediately). Pledges and notifications: until account deletion (deletion can also be requested earlier at [email protected])
• Kevios Challenge meetup participation records, attendance records, time of confirming being 19 or older, venue and map address: until you leave the meetup (including leaving by deleting the meetup goal; participation records), 30 days pass after that meetup ends, or the account is deleted (deleted immediately; the venue and map address follow that meetup's entry). Records of a meetup with a report being handled are kept until handling is finished. Meetup nicknames from earlier meetups are deleted at the same times. Cheers: until the day they were sent passes, you leave the meetup, or the account is deleted. Notes: until the user who wrote them deletes them, leaves the meetup, 30 days pass after that round ends, or the account is deleted (deleted immediately). Posts hidden by a report are restored or deleted within 30 days of being hidden. Note reports: until the note is deleted, the Operator restores it, or the reporting member leaves the meetup or deletes their account (set separately from the 3 years for report and moderation records above; the Operator's handling records and the handling records of deletion requests for rights infringement and objections follow those 3 years)
• Kevios Challenge meetup photo, name (including text typed in for the "Other" type), tags, introduction and notes: until the host changes or deletes them, the Operator deletes them, or 30 days pass after that meetup ends. If the host deletes their account, meetups that have not started are deleted immediately including the venue and map address, and for meetups that have already started the photo and the host's account ID are deleted immediately and the rest are deleted 30 days after that meetup ends. Content hidden by a report is restored or deleted within 30 days of being hidden. It may remain in the delivery relay cache for up to 1 hour after deletion
• Kevios Challenge meetup profile photo: until it is changed or deleted or the account is deleted (deleted immediately; it may remain in the delivery relay cache for up to 1 hour after deletion)
• Kevios Challenge meetup ratings and reviews: the score until account deletion, the date it fell to 30 or below until it returns to 31 or above or the account is deleted, and review records for 1 year from the review date or until account deletion. If the giver deletes their account, only that account ID is deleted
• Kevios Challenge meetup use restrictions and meetup-opening restrictions: until the Operator lifts them or the account is deleted
• Kevios Challenge meetup messages: until both sides delete them, 30 days pass after that meetup ends, or the account is deleted. A copy of a reported message is kept until handling of the report is finished even if the reporting member deletes their account, and if the sending member deletes their account only the sending account ID is deleted. Handling and viewing records are kept for 3 years (access location for 1 year) without the message content, and the target account ID (including scores before and after and the reason if the rating was changed) and the administrator account ID are deleted after 1 year (even if the account is deleted within that time, they are kept until 1 year to retain access records). However, the target account ID of a handled profile report is deleted when that member deletes their account, and otherwise 3 years after handling.
• Kevios Challenge Challenge Forest chat: storage starts at 00:00 on November 14, 2026. Stored chat is kept until 30 days pass from the earlier of the time access closes 5 hours after that meetup ends and the time the meetup is closed, until that member presses "Remove chat content", or until account deletion (deleted immediately when pressed or on deletion). A reported copy is kept until handling of the report is finished even if the reporting member deletes their account or the sending member presses "Remove chat content", and if the sending member deletes their account only the sending account ID is deleted. The nickname, time and content written and sent with a report are kept until handling of the report is finished, regardless of whether they were before or after storage began. Handling and viewing records are kept in the same way as for messages, without the chat content.
• Kevios Challenge time of confirming the Challenge Forest notice: until account deletion
• Kevios Challenge reports on meetup content and profile photos: until the content is deleted, the Operator restores it, or the reporting member deletes their account (set separately from the 3 years for report and moderation records above; the Operator's handling records and the handling records of deletion requests for rights infringement and objections follow those 3 years)
• Kevios Challenge meetup block list: until it is removed or the account is deleted
• Records of automatic checks of Kevios Challenge meetup photos and text: 90 days from the date recorded. Deleted immediately if the member deletes their account (the handling records of objections follow the 3 years for report and moderation records)
• Kevios Challenge meetup chosen neighborhood and radius: overwritten when changed, and kept until 1 year after last use or until account deletion
• Kevios Challenge meetup search term counts: search terms that were searched too few times to be popular term candidates are deleted 30 days after the date last searched, and other search terms after 90 days. If searched again in the meantime, the period is counted again from that day

Article 5 (Provision of Personal Information to Third Parties)

As a rule, the Service does not provide users' personal information to third parties. The following are exceptions.

• When the user has consented in advance
• When an investigative agency lawfully requests it under relevant laws such as the Criminal Procedure Act
• When disclosing the minimum information needed to handle temporary measures under Article 44-2 of the Act on Promotion of Information and Communications Network Utilization and Information Protection

The Service does not provide advertisers, partners or data buyers with raw data that could identify a specific user, specific IP address, specific session or specific post author. When external provision is needed, it provides only aggregate statistics by region, period or topic, or de-identified statistics with reduced risk of re-identification.

Article 6 (Entrustment of Processing and Transfer Abroad)

The Service entrusts the processing of personal information as follows, and some of it is transferred abroad.

1. Method of transfer: transmission over information and communications networks when using the Service
2. The contact details of each trustee's privacy officer are published in that business's privacy policy.
3. Users can refuse the transfer abroad. However, refusing makes access to the Service itself impossible, so the Service cannot be used.
4. If a trustee is added or changed, this policy will be revised and announced before it takes effect.

Web push notifications are delivered through the push service chosen by the user's browser (for example Google LLC, Apple Inc., Mozilla Corporation, Microsoft Corporation; United States). These push services are not trustees listed above. Each time a notification is sent, the push address, encrypted notification content, time and size sent, and an indication that the Service sent it (the server public key and a contact email address) are transmitted over information and communications networks. Kevios Saju and Kevios Challenge send only to the push service addresses of these four businesses. Push services cannot read the notification content; they use it to deliver notifications and keep it according to each business's privacy policy (contact details are also in each business's policy). If you do not turn on notifications or turn them off, this transmission does not happen, and there is no restriction on using the Service other than not receiving notifications.

Article 7 (Destruction of Personal Information)

1. The Service destroys personal information without delay when the retention period has passed or the purpose of processing has been achieved.
2. Electronic files are deleted in a way that cannot be recovered.
3. Information that must be preserved by law is kept separately and not used for purposes other than preservation.

Article 8 (Rights of Users and How to Exercise Them)

• Request for access: You can request details of how your personal information is processed.
• Request for correction or deletion: You can request correction of wrong information or deletion.
• Request to suspend processing: You can request suspension of the processing of personal information.
• Account deletion: You can delete your account yourself in account settings, and account information is deleted immediately on deletion.
• However, information that must be kept by law or is needed to respond to disputes, such as IP addresses, access records and report handling records, may not be deleted immediately.

How to exercise your rights

1. Requests to exercise rights are made at [email protected], and the Service takes action and notifies you of the result within 10 days of receipt.
2. Requests can also be made through a legal representative or an authorized person. In this case, submit materials that confirm the authorization together.
3. Requests for access, correction, deletion or suspension of processing may be limited by law, for example where other laws specify that the personal information is to be collected.
4. You can delete your account yourself on the My Info screen in the Service.
5. If someone else entered your information in Kevios Saju, request it at [email protected] with your date of birth, gender and the name used, and it will be found and deleted within 10 days and you will be notified of the result.
6. Kevios Challenge goals and their records and notes can be deleted directly on the goal screen. To delete pledges, make a request at [email protected].
7. Kevios Challenge meetup content, photos and profile photos can be changed or deleted on that screen, and messages can be deleted on your side. If content uploaded by someone else contains your face or personal information, request deletion at [email protected] even if you are not a member. Notes and meetup nicknames written in earlier meetups are deleted at set times, and deletion can also be requested earlier at the same address. In the Challenge Forest you can delete your messages on the spot, stored copies are deleted at set times, and even before then you can immediately delete the stored chat you wrote with "Remove chat content" on the member information screen. To access your messages, make a request at the same address. Copies attached to reports being handled are deleted after handling is finished.
8. Kevios Challenge meetup search term counts do not record who searched, so they cannot be found and shown or deleted per user. If you believe a search term contains your name or personal information or infringes your rights, make a request at [email protected] with that text and the reason, even if you are not a member. The Service will without delay remove that text from popular and suggested search terms, delete it from the counts and keep the same text from appearing again, and will notify you of the result within 10 days.

Department receiving and handling access requests

Article 9 (Protection of Children Under 14)

The Service does not knowingly collect personal information of children under 14. If a user is found to be under 14, the account and the personal information collected are deleted immediately. Kevios Saju does not accept saju information of anyone under 14, whether the user themselves or another person. If you access the Service from India, only people aged 18 or older can sign up, and Kevios Saju does not accept saju information of anyone under 18, whether the user themselves or another person. Whether you are accessing from India is determined only from the access country of that request, which is not stored. Kevios Challenge meetups can be opened and joined only by members who have confirmed for themselves that they are 19 or older. Only hosts and participants who have gone through the same confirmation can enter the Challenge Forest. However, public meetup content can be viewed by non-members.

Article 10 (Measures to Protect Personal Information)

• Passwords are stored as BCrypt one-way hashes and the original is not kept.
• Full IP addresses cannot be accessed by anyone other than administrators.
• JWT authentication tokens are renewed every 30 minutes and invalidated immediately on the server at logout.
• Kakao login uses the standard OAuth 2.0 procedure, and Kakao real-name information is not collected.
• Saju information in Kevios Saju is kept in a database separate from Town, nicknames and dates and times of birth are stored encrypted, and access between services is only through authenticated server-to-server calls.
• Kevios Challenge records are kept in a database separate from Town, and goal names, descriptions, notes and pledges, meetup venues and map addresses, messages, Challenge Forest chat and notes from earlier meetups are stored encrypted (public meetup content and photos, and meetup nicknames from earlier meetups, are visible content and are not encrypted).

Article 11 (Cookies and Automatically Collected Information)

The Service stores authentication tokens in the browser's local storage. For visit counts it uses a random identifier kept in browser storage (localStorage) and does not link it to member accounts. If the browser time zone or access country is in Europe (the European Union, the European Economic Area, the United Kingdom, Switzerland and so on), this identifier is not created and is not included in visit or return visit counts. Detailed usage behavior recorded per user and ad performance measurement are collected only for users who gave optional consent, and there is no restriction on using the Service without consent.

To count totals by purpose and stage of use, Kevios Town, Kevios Saju and Kevios Challenge each keep in that site's browser storage the first visit date, last visit date, number of days visited, first referral source (a category such as search or direct), the number of screens by purpose of use on the 3 most recent days visited, the purpose and stage category, and a mark of the categories sent that day. Screen addresses are not stored. These values are categorized in the browser and only the categories are sent, without the visit identifier, and the Service stores them only as daily totals. The values of the three services are not connected to each other. If the browser time zone or access country is in Europe, these values are neither stored nor sent.

• Kevios Town, Kevios Saju and Kevios Challenge use the kv_lang cookie (language setting, 1 year) to remember the language you choose. Until you choose one, the first language shown is based on your access country, which is not stored.
• In Kevios Challenge meetups, the neighborhood and radius chosen by a non-member are kept in that browser's storage.
• Recent searches in the Kevios Challenge search field are kept only in that browser's storage, are not sent to the server, and can be deleted with Clear in the list. If the browser time zone or access country is in Europe, they are not stored.
• Behavior information that may be collected per user with optional consent: click targets, content exposure and time spent, ad impressions and clicks
• If personalized advertising combined with personally identifiable information, third-party advertising SDKs, or behavior collection tools of outside advertising businesses are introduced, the collection tool, items, purpose, retention period, whether information is provided, and how to refuse will be announced separately.
• Users can block cookies and data storage for this site in their browser settings so that the visit identifier and the above categories are not created or sent. In this case, some features such as login may be limited. Clearing site data creates a new identifier that does not continue previous records, and previous records are deleted when the retention period (13 months) has passed. Optional consent to detailed usage analysis and ad performance measurement can be withdrawn by request at [email protected].

Article 11-2 (Use of Pseudonymized and Aggregated Information)

The Service may pseudonymize or aggregate collected usage records and public content and use them to analyze regional real estate interest, preferred regions, monthly rent and lease market interest, industry and policy interest, and the performance of ad placements. In this case, protective measures such as minimum sample sizes and merging by region and by period are applied so that specific users are not re-identified and the behavior of a small number of users is not revealed.

Article 12 (Privacy Officer and Inquiries)

The Service designates a privacy officer as below to take overall responsibility for the processing of personal information and to handle users' inquiries, complaints and remedies for damage related to the processing of personal information.

Users can contact the above for any privacy-related inquiries, complaints or remedies for damage arising while using the Service, and the Service will reply and handle them without delay.

Article 12-2 (Remedies for Privacy Violations)

Users can apply to the organizations below for dispute resolution or counseling to obtain remedies for privacy violations. These organizations are separate from the Service, and you can contact them if you are not satisfied with the Service's handling or need more help.

In addition, a person whose rights or interests have been infringed by a disposition or omission of the head of a public institution regarding a request under Article 35 (access), Article 36 (correction and deletion) or Article 37 (suspension of processing) of the Personal Information Protection Act may file an administrative appeal as provided by the Administrative Appeals Act.

Article 13 (Changes to This Policy)

This Privacy Policy may be revised due to changes in laws, service policies or the operating environment. If there is an important change, it will be announced on the Service screen before it takes effect.

Change history

The change history is in the Korean original.