Privacy Policy

1. Processing Entity

2. Processing Purposes and Legal Grounds

• Member identification, login, and account security: entering into and performing the service agreement
• Storage and synchronization of roasting records and analytics requested by the User: performance of the service agreement
• Payment, refunds, and customer support for paid subscriptions: performance of the agreement and obligations under the Act on the Consumer Protection in Electronic Commerce, Etc.
• Receiving and responding to inquiries: taking action at the User’s request
• Shared AI-model training: separate optional consent. Declining does not change contracted features or prices. See the AI Data Use Notice for details.
• Community profile, posts, reports and blocks, activity points, in-site notifications and Honor Roasters: performance of the service agreement with members who chose to join the community. Showing the quality tier and Honor Roaster participation are optional settings the member turns on. Records of staff actions (hiding, honor selection) serve abuse prevention and report handling.

3. Data Processed and Collection Channels

For email registration, the password is stored as a hash that cannot be reversed. The Company does not receive social-account passwords for accounts registered or logged in through Google or Naver. If only a social account is linked, the account cannot be accessed with a Service-specific password.

The Company does not maintain a separate organization-membership system. Accounts are maintained per User.

4. Retention and Use Period

• Member information and account-linked service records are used while membership remains active. The account-deletion procedure in this revision deletes the account email, roasting records, social connections, and training copies, while retaining order number, amount, payment status, plan, and payment identifier. Before 12:00 a.m. Korea Standard Time on October 1, 2026, the public Policy is the short notice; the Company does not represent that deletion under that notice already deletes those fields.
• The most recent login time is included in account information. The application does not store per-User IP access histories as account information.
• While backup copies remain, they may contain personal information. Each type of backup has its own retention, and one number of days is not represented as the deletion deadline for all data. Backups are not an exception to destruction obligations. Automated backups of the member database (Amazon RDS) are kept for 7 days and then deleted automatically. Manual snapshots taken before maintenance are not deleted automatically and remain until the Company deletes them.
• Community: in-site notifications are deleted by a daily job 90 days after they are created. The profile, posts, comments and images, reports, blocks, bookmarks, and activity-point and honor records are kept until the member removes them or deletes the account. No period is set for community items other than notifications, and they are not processed automatically by age. Item-by-item handling and what account deletion removes follow Part 2, Articles 4 and 5 of the Community Rules and Privacy Addendum.
• Training copies collected under optional consent are retained for up to two years from the first collection of each record. They do not share a retention period with original records stored in the Service.
• Consent and withdrawal records are kept separately from training copies to verify the fact of consent. They are not retained indefinitely and separately from member information.

Under Article 6 of the Act on the Consumer Protection in Electronic Commerce, Etc., the following transaction records are retained only for the periods below and are not used as a basis to retain complete original roasting records long-term.

• Agreement or withdrawal records: 5 years
• Payment and service-supply records: 5 years
• Consumer complaint or dispute-handling records: 3 years
• Display and advertising records: 6 months

5. Destruction Procedure and Method

Personal information is destroyed without delay when its retention period ends or the processing purpose is fulfilled. Electronic files are deleted so they cannot be restored or reproduced. Records retained under law are separated from other personal information and used only for the required purpose.

When an account registered by email requests deletion under this revision, the Service verifies the password and deletes the account email, roasting records, social connections, and training copies. If a destruction record cannot be prepared, the request fails and data is not deleted. Order number, amount, payment status, plan, and payment identifier remain; the card billing key and raw payment response are deleted. An already paid subscription ends when its service period expires. Merely setting a scheduled effective date does not mean destruction or restoration verification is complete. Before that verification, this procedure is not represented as an operating public Policy.

An account linked only to a social account is not processed through this account-deletion screen and must submit the request to Customer Support. Disabling login alone is not treated as completion of personal-information destruction.

6. Service Providers and Third-Party Disclosure

The Company does not sell personal information. Except where required by law, it does not provide a User’s personal information for a third party’s own independent business purpose.

• Payment: PortOne creates the payment session, and NHN KCP processes card authorization. The User enters card information directly into the payment window. The Company does not store the full card number and stores only order number, payment amount, payment status, plan, and payment identifier. This relationship is not treated as the same type as a User logging directly into an authentication window.
• Customer inquiries: the web form does not send email. Inquiries are submitted directly through [email protected], phone, or KakaoTalk. That email address is an individual Google account, and Google LLC is the contracting entity under the terms applicable to that account. It is separate from the agreement used for Google login. The country where that mailbox is stored has not been verified.
• File storage: installer files are kept in Cloudflare object storage. That storage-location setting is not displayed as one specific country. Member data and database backups are separate from installer-file storage. The member database server is in the Seoul region; the Seoul region is the data location. The cloud contracting entity is Amazon Web Services Korea LLC, whose corporate location is the Republic of Korea. The corporate location is not represented as the Seoul region.
• Social login: when a User selects Google or Naver, that provider performs authentication and the Company stores only the fields stated in Section 3.
• KakaoTalk support: when a User contacts the KakaoTalk channel, that conversation follows Kakao’s processing standards. Service account-registration information is not automatically transferred into the conversation.
• Community: community data and images are stored in the member database above. Automatic translation is off, so posts are not sent to any translation provider, and no member information is provided to partner-benefit businesses. Processing entrusted for the community and processing in transit are described in Part 2, Article 6 of the Community Rules and Privacy Addendum.

For optional AI training, the Company does not entrust training data to an outside provider so that provider can train its own independent general-purpose model. Processing entrusted to provide the core Service is kept distinct from training based on optional consent.

7. Overseas Transfers

When Google login is selected, the User’s browser requests authentication from Google. The requested scopes are openid and email; profile is not requested. The Company server sends Google the authorization code and client information needed for login configuration, not the password or roasting records. The Company receives and stores the email address and account identifier. Email-verification status is used only to reject an unverified registration and is not stored separately. Even if a profile response contains a name or image, the Company does not store it. When Naver login is selected, the browser moves to Naver’s authorization address. That request has no separate scope value. The Company stores the identifier and, when returned, the email address. If no email address is returned, an internal service address is used as the account email. The countries of storage and retention periods of both login providers, and the contracting entity for each OAuth project, have not been verified. Those agreements are separate from Google LLC’s agreement for the inquiry-mail account.

This authentication serves a purpose different from optional AI training. The authentication provider is not described as the Company’s processor. Naver login is not described as an overseas transfer identical to Google login. The verified domestic-region location of the member database and overseas error analytics are not described as one item.

For card payment, card information that the User enters into the payment window passes through PortOne for authorization by NHN KCP. The Company stores order number, payment amount, payment status, plan, and the payment identifier needed for a refund, but not the full card number. This payment flow differs from a User logging directly into Google or Naver. Publication of this Policy is not by itself treated as consent to each type of processing.

If a service error occurs, error information may be sent to Functional Software, Inc. d/b/a Sentry to identify the error. Its storage location is Iowa, United States. Under the current plan, collected errors have a default retention period of 30 days, and backups created by Sentry are deleted 90 days after creation. Even if no new errors are later sent, previously received error information may remain until its retention period expires. Error information may include query values in a request URL or values being processed. The Company does not represent that all access and processing occur only in the United States.

8. Rights of Users and Legal Representatives

A User may request access to, correction or deletion of, or suspension of processing of the User’s personal information. Account information and optional AI consent can be changed directly in Settings; other requests are submitted through Customer Support below. After verifying identity, the Company acts without delay to the extent required by law.

Children under 14 are not eligible to register. The Company does not collect date of birth at registration and does not operate a legal-representative consent procedure for children under 14. If the Company learns that personal information of a child under 14 has been collected, it deletes that information without delay.

9. Cookies and Storage

• Authentication tokens needed to maintain login are stored in browser storage. They are deleted on logout.
• Installer-download authorization uses a cookie named rp_download_auth. It is valid for 24 hours, uses the /download path, and is set as HttpOnly. The original authorization code is not placed in the cookie.
• A User may refuse by blocking cookies or clearing browser storage. Persistent login or authorized downloading may then be restricted.

10. Security Measures

• Passwords are stored as bcrypt hashes; plaintext is not retained.
• Reading and changing service data is limited to the authority of the logged-in account.
• Administrative features are limited to accounts with administrative authority.
• Training-data extraction creates new records only from permitted fields and does not place an account identifier in those records.
• Users are instructed not to send a full card number, password, or payment-authentication information to Customer Support.

11. Privacy Contact

커피익스플로러’s Customer Support handles requests for access, correction, deletion, or suspension of processing and receives privacy complaints. The web inquiry form is not a submission channel. Requests received by email or phone are handled through this contact.

• Email: [email protected]
• Phone: 070-8628-9532

12. Changes to This Policy

Document version 2026-10-09 applies beginning October 9, 2026. Material changes are announced on the website before taking effect. Change history remains in this document and the previous-notice page. The legal basis for an overseas transfer is not established solely by this effective date. Operational verification of destruction procedures and whether AI-training collection is enabled are also separate from this effective date.

Revision history

• Revision 2026-10-09 (revised October 9, 2026; effective October 9, 2026): added community processing (Articles 2, 3, 4 and 6) and the member database's automated backup retention (Article 4).
• Revision 2026-09-27 (published September 27, 2026; effective October 1, 2026): replaced the short notice with the formal Policy. The earlier short notice is in the previous notice archive.