Privacy Policy

This policy applies equally to the CookLog mobile app and website (cooklog.kr). Because both services share the same account and server, they are governed by a single policy.

Information Collected: Social login account identifiers and email, cooking logs and reviews, community posts and comments, voice coach conversation records, app and website usage records and error logs, optionally entered gender and age group, inquiry details, pre-registration email · Article 2

Purpose of Use: Account management, saving cooking logs, personalized recommendations, AI guidance and voice coach during cooking, analysis of app and website usage status and bug fixes, app launch notifications, displaying website advertisements · Article 3

Third-Party Provision: None provided. Reviews, photos, and cooking logs are viewable only by the user. Only posts and comments directly uploaded to the community are visible to users within the selected disclosure scope · Article 5

Entrustment of Processing: Servers and storage are hosted on AWS (Seoul, domestic), AI features on Google Gemini, coach memory organization on Anthropic Claude, inquiry emails on Gmail, usage analysis on Google Analytics (web) and PostHog (app), error analysis on Sentry, AI request records on Langfuse · Article 6

Overseas Transfer: Questions and reviews used for AI features, voice and conversations of the voice coach, website usage records, and advertising identifiers are transmitted to Google (USA); coach conversation records and review comments used for coach memory organization are transmitted to Anthropic (USA); app usage and error records and AI request records are transmitted to PostHog and Sentry (Germany) and Langfuse (Ireland). On screens receiving YouTube videos and thumbnails, connection information (such as IP) is transmitted to Google. Accounts, cooking logs, reviews, photos, and community posts are stored domestically in Seoul · Article 7

Advertisements and Behavioral Information: Advertisements are displayed only on the website (Google AdSense). Google may display ads tailored to interests using advertising cookies, which can be turned off in browser settings. There are no advertisements in the mobile app. Cooking logs and reviews are not used for advertising · Article 12

User Rights: Account deletion within the app and web, changing nickname, gender, and age group within the app, deleting community posts and comments and changing the disclosure scope, turning off usage analysis and error reports. Deletion of individual records, withdrawal of pre-registration, and requests for access, correction, suspension of processing, and data portability will be processed via email within 10 days · Article 9

Inquiries and Grievance Handling: cooklog.official@gmail.com · Article 15

Lee Hyun-woo (hereinafter referred to as the "Company") values the personal information of users of CookLog (hereinafter referred to as the "Service") and complies with relevant laws and regulations, including the Personal Information Protection Act.

Personal Information Controller: Operated under the individual name of Lee Hyun-woo, not as an individual business enterprise.

Service Name: CookLog, formerly CookPilot — Service name changed on 2026-08-20

Scope of Application: CookLog mobile app and website cooklog.kr

Email: cooklog.official@gmail.com

This Privacy Policy guides users on what personal information the Service processes, for what purposes, and what rights users can exercise regarding their personal information.

This Policy shall apply from August 25, 2026.

A. Member Registration and Authentication

For Use Without Logging In

Recipe viewing, cooking progression, and the voice coach can be used without member registration. In such cases, the Company does not create an account and does not store cooking records or coach conversations on the server. The automatically generated information (connection logs, app usage and error logs) set forth in Paragraph J below remains, and the app's analysis and error collection tools generate a random identifier for each installation to distinguish records (Article 12). When using the voice coach, voice data is transmitted to Google (Paragraph M), and inquiries made as a non-member receive the entered email address and name (Paragraph G). Posts and comments uploaded to the community as public can be viewed without logging in (Paragraph K). Storing cooking records, writing reviews, customized recommendations, text AI queries, YouTube conversion, writing posts and comments in the community, and giving applause and following can be used after member registration.

The name and nickname received from the provider are not stored. The nickname displaying the user within the service is automatically generated by the Company upon registration, and members can change it directly at any time in profile settings.

Available login methods may vary by iOS app, Android app, and website. Logging in with the same social account constitutes the same account regardless of which platform was used for registration.

Information commonly generated upon registration includes the internal user identifier within the service, login provider, nickname (automatically generated by the Company and modifiable by the member), registration time, and the time of confirmation of age 14 or older and the version of the processing policy applied at that time. Login status is maintained via a token issued by the Company (valid for up to 14 days), and the server does not store this token separately.

Member registration is provided exclusively via social login. Since the Company does not provide self-managed email and password registration, it does not collect or store passwords. Passwords reside solely with each social provider, and the Company receives only the results (tokens) verified by the provider.

The Company requests only the minimum scope necessary for authentication during social login and does not receive gender, date of birth, or phone number from social providers. Even if a provider includes a name, nickname, or profile picture URL in the authentication information, the Company does not store them.

B. Profile — Gender and Age Group (Optional; Consent is not required)

Optional Items

Gender and age groups are optional items collected only from users who have consented to their collection. The Company asks directly on the app's 'My Info' screen and does not receive them from social login providers. All features of the service can be used without changes and recommendations will continue to be provided even if you do not consent or enter them.

• Items Collected — Gender (choose among Male, Female, or No Selection), Age Group (choose among Teens, 20s, 30s, 40s, 50s, or 60s and older)
• Purpose of Use — Personalization of recipe recommendation results. These are not yet reflected in current recommendations (Article 13), and the decision criteria in Article 13 will be revised and notified prior to initiating reflection
• Method of Collection — Direct selection by the user from the presented options. Date of birth and exact age are not collected
• Skipping — You may proceed without entering, in which case the Company records only the time the guide screen was displayed to prevent repeating the same question. This time record does not contain gender or age group
• Withdrawal of Consent — Entered values can be deleted and consent can be withdrawn at any time. Upon withdrawal, stored values are erased
• Retention Period — Until withdrawal of consent or membership withdrawal

C. Information Generated During the Course of Service Use

• Cooking Reviews — Star ratings, comments, notes for the next cooking session, attached photos, cooking date and time, number of servings cooked
• Cooking History — Recipes cooked, cooking date and time
• Personalized Recipes — History of changes to ingredient quantities and cooking steps
• Favorites — List of recipes saved by the user
• Recommendation Reactions — Content of ingredient adjustment proposals suggested by the service, whether they were accepted, rejected, or modified, and applied quantities
• Today's Recommendation History — Recipes selected and shown by date and reasons for recommendation
• Voice Coach Conversation Records and Coach Memory — Paragraph M below
• Credits — User tier, attendance check, YouTube conversion usage, and refund history
• Community — Uploaded posts (photos, body text, linked cooking records and recipes, visibility scope, upload time), comments, applause, follow and block relationships, reported targets and reasons for reporting, and time of consent to community disclosure (Paragraph K below)
• YouTube Conversion Request History — Requested video, request time, processing results

D. AI Features

Generative AI is used in the following features of the service, and the following information is transmitted to the AI for each feature. Anthropic's Claude is used for coach memory organization, and Google's Gemini is used for other features.

• Text Questions During Cooking (Members) — Questions entered by the user or converted via speech recognition, recipe name, guide text and precautions for the current cooking step, timer information
• Voice Coach — Microphone audio and the recipe, ingredients, cooking steps, and progress status of the current cooking session (Paragraph M below)
• Next Cooking Ingredient Adjustment Recommendations (Members) — Original ingredients of the corresponding recipe, up to 30 recent reviews, and up to 5 reviews of that recipe (recipe name, category, star rating, cooking date and time, comments and next cooking notes within 200 characters each, ingredient adjustments at that time, internal review number)
• Today's Recommendations (Members) — Up to 20 favorite recipe names and up to 30 recent reviews (recipe name, star rating, cooking date and time, comments and next cooking notes within 120 characters each). Automatically processed every day at dawn (Article 13)
• Coach Memory Organization (Members) — Voice coach conversation records (speech of the user and coach), recipe name and ingredients of that cooking session, and review comments. For cooking sessions conducted without the voice coach, only the recipe name, ingredients, and review comments are transmitted if review comments exist. Processed by Anthropic's Claude (Paragraph M below)
• YouTube Recipe Conversion (Members) — Public video URL entered by the user and public information of that video (title, channel name, description)
• Recipe Generation (Members) — Search queries (within 40 characters) requesting dishes with no search results

AI requests do not include names, emails, or member identifiers. However, since content directly written or spoken by users in questions, reviews, and coach conversations is transmitted as is, users are advised not to enter or speak personal information or health information unrelated to cooking.

Text questions during cooking and their answers are not stored on Company servers. For AI response quality inspection and error analysis, the Company records AI raw requests and responses, used models, and processing times for text questions, next cooking recommendations, today's recommendations, and recipe generation in Langfuse (Articles 6 and 7), and these records do not contain member identifiers. Voice coach and YouTube conversions are not included in these records.

The website's YouTube recipe conversion feature transmits only the public video URL entered by the user and that video to generative AI to organize recipes. Account information and cooking records are not transmitted in this process, and since conversion results are automatically generated outputs, original videos and product labeling must be checked together.

E. Voice Input and Voice Coach

App handles voice during cooking in two ways. In either method, the Company does not store original voice data on servers.

• Voice Commands and Questions — Pressing the 'Speak' button causes the speech recognition feature of the user's device (Apple's speech recognition for iOS, and the speech recognition service set on the device for Android, typically Google) to convert voice into text. The Company receives only the converted text to process commands or answer questions, and does not receive voice data through this path. Whether that feature transmits voice to servers of providers such as Apple and Google for recognition depends on the device and operating system, and such processing is subject to the respective provider's privacy policy (Paragraph 7, Item B).
• Voice Coach — When the voice coach is turned on, Company servers receive a disposable access token from Google (valid for up to 30 minutes), and the app uses that token to connect directly to Google's real-time voice AI (Gemini Live), continuously transmitting sounds entering the microphone in real time until the coach is turned off or the app screen is exited. Because data is not sent only when asking questions, voices of people nearby may also be transmitted. Google recognizes the voice, generates the coach's answers in voice, and returns a transcript of the user's and coach's speech. Camera video and photos are not sent, and the user's name, email, and member identifier are not transmitted to Google. The voice coach can be used without logging in.

Recipe names, servings, ingredients used in the current cooking session (including substitutions and omissions), total cooking steps, current step, and timer status are transmitted to the voice coach. When turning on the coach again during the same cooking session, up to 8 statements exchanged immediately prior and the conversation summary organized by the coach, along with content related to that recipe among the coach memories below if the user is a member, are transmitted. For iOS apps, Company servers transmit this information to Google included in connection settings when turning on the coach, and Android apps transmit it directly after connection. When skipping steps or when timers end during cooking, the corresponding guide sentences are also sent to the coach.

• Voice Coach Conversation Records (Members) — Whenever the voice coach is turned off (whether turned off by the user, upon finishing or stopping cooking, or when leaving the app), the app sends the transcript of conversations had up to that point in that cooking session (speech of the user and coach), conversation summaries organized by the coach, ingredient substitution history, and recipe information to Company servers. The Company retains only members' records on domestic (Seoul) servers and uses them to organize coach memories linked with reviews of the same cooking session. Records in a non-logged-in state are not stored on servers.
• Coach Memory (Members) — Every day at dawn, the Company selects preferences (seasoning, spiciness, texture), ingredient substitutions and reasons therefor, cooking environment (heat level, tools, number of people), failures and causes, and cooking result ratings from conversation records and reviews, organizes them into coach memories per member, and informs the coach of relevant memories the next time the voice coach is turned on. Memories are stored on Company servers (Seoul), and the task of extracting memorable content from conversation records and reviews is performed by Anthropic's Claude (Article 7, Paragraph L).

F. Notifications

Currently provided notifications are limited to cooking timer notifications reserved and processed entirely within the device, and no information is transmitted to servers for this purpose. Since the Company does not yet provide remote push notifications, it does not collect push tokens.

G. Customer Inquiries and Privacy Requests by Video Rights Holders

When making inquiries via customer support within the app or website, or via email, inquiry types, titles, contents, and response histories are collected. To receive answers via email, email addresses are provided. Non-logged-in users must provide an email address (mandatory) and name (optional) and consent to the collection and use of personal information in order to make inquiries. If a member does not provide an email address, answers can be viewed only via customer support within the app and website, and the Company does not send them to the account's email instead.

When an email address is provided, the Company sends confirmation emails of receipt (name or nickname, inquiry title, type, number) and response emails via Gmail. If the user replies to those emails or makes direct inquiries via Company email, those contents are also stored in Gmail.

Rights holders of YouTube videos or their agents can request to make converted recipes from those videos private using a separate form on the website. In such cases, names, YouTube channel names, contact email addresses, reporter qualifications (rights holder or agent), original video URLs, scope of requests, and additional explanations (optional) are collected, along with consent to the collection and use of personal information and rights holder verification. Confirmation emails of receipt include video URLs, channel names, and request scopes.

The Company directly processes inquiry receipts and responses without outsourcing them to external customer support providers. Files cannot be attached to inquiries, and authentication tokens, AI conversation contents, other reviews and photos, and device information are not automatically attached to inquiries.

H. Pre-registration for Launch Notifications — Website

Consent separate from member registration

Pre-registration is a separate consent to receive notices regarding app launch news. It is independent of member registration or account creation, and pre-registration consent remains intact even upon membership withdrawal. If you wish to clear both together, please follow the instructions in Article 9 below.

• Email Address — Address to receive app launch notifications. Names, dates of birth, and contact information are not collected
• Stores to Receive the App — One or more of Google Play and App Store. This is to guide launch notifications along with corresponding store links
• Time of Consent and Version of Consent Document — Records to verify when and which version of the policy was consented to
• Anti-abuse Identifiers — Values converted from requested IP addresses into forms that cannot be reversed back to original addresses. Original IP addresses are not stored
• Age 14 or Older Confirmation Results — Only the fact of confirmation is recorded, and dates of birth are not collected

When applying for pre-registration in a logged-in state, application details are linked to the corresponding account, allowing subsequent verification of application status with the same account. When applying without logging in, applications are not linked to accounts and notifications are sent solely.

I. Information Automatically Generated and Collected

• Access IP address, access time, request path, and processing results
• Device type and model, operating system and version, app version or browser type, language, time zone, telecommunication carrier, screen size
• App Usage Records — Login methods, recipe views and search terms (number of search terms only for iOS apps), cooking start, completion, and suspension, review submission status, star ratings, and number of photos, recommendation exposures and reactions. For Android apps, app execution, switching, installation, updates, and community usage (feed views, post views and creation, number of photos, applause, comment creation, follows and blocks, reporting status and target types. Internal identifiers of posts opened, applauded, or commented on, and members followed or blocked are sent together, while body text, comments, and reporting reasons are not sent) are also included. Distinguished by random identifiers generated by PostHog for each installation, and Android apps link them with member identifiers when members log in (Article 12)
• Website Visit Records — Visited pages, time spent, clicked features, traffic sources. Distinguished by analysis identifiers issued to browsers by Google Analytics and not linked to accounts
• App Errors and Crash Records — Error details and occurrence locations (stack traces), app operation logs immediately prior to errors, app, device, and operating system information, random identifiers generated for each installation. Collected via Sentry (Article 12)
• Server Error Records — When server errors occur, error details, request URLs, and server information are sent to Sentry. Request headers and bodies, IP addresses, and member identifiers are not sent
• Information for Ad Serving — Website advertising cookies and pages where ads are displayed. Collected directly by Google as the advertising business entity and not stored on Company servers. Since ads are not served in mobile apps, advertising identifiers are not collected in apps (Article 12)

J. Information Not Collected

Company does not collect device location information (GPS, etc.), contacts, address books, or payment information, and does not process unique identifying information (resident registration numbers, etc.) pursuant to Article 24 of the Personal Information Protection Act. Sensitive information under Article 23 of the same Act, such as health and allergies, is not separately requested or collected. However, if users directly write or speak such information in reviews, inquiries, or voice coach conversations, it may be included and processed in those records; thus, users are advised not to write or speak them if they do not wish to do so. Shooting location information contained in attached photos is removed prior to storage (Article 10).

K. Community — Information Disclosed to Other Users

Information directly disclosed by users

Community is a feature where users share cooking photos and stories uploaded by themselves with other users, and is the sole place in this service where user-written content is visible to others. Upon uploading the first post, consent to disclosure is obtained once and the time is recorded. Reviews, cooking records, and photos are not disclosed unless uploaded directly to the community.

• Scope of Disclosure — Users choose one of 'Public' (all users including non-logged-in individuals), 'Followers Only' (members following the author), or 'Private' (author) for each post, and can change it even after uploading.
• Information Visible in Posts — Photos (1 to 10 images), body text, author nickname, upload time, number of applauses, and number of comments. When cooking records are linked, dish names, star ratings left at that time, and personal recipe version numbers are also displayed. Review comments and notes are not transferred to posts.
• Using Review Photos in Posts — Only review photos selected by users are copied as community photos when uploading posts. Original review photos remain private as they are, and are not deleted even if posts are deleted.
• Photo Files — Community photos, like review photos, are stored in storage inaccessible arbitrarily from the outside. Access URLs valid for 1 hour are provided only to people capable of viewing posts, preventing individuals outside the scope of disclosure from opening them even if they know photo URLs.
• Comments — Visible to people capable of viewing posts along with nicknames. Comments can be deleted by authors themselves and post authors.
• Profile — Nicknames, number of posts, number of followers and following, and posts matching viewers' scope of disclosure are displayed. Who gave applause and lists of followers and following are not shown to other users.
• Blocking — Blocking causes posts, comments, and profiles of both parties to become invisible to each other and disconnects follows. Blocking facts are not notified to the counterpart.
• Reporting — Reporters and reporting reasons are viewed solely by operators and are not notified to authors of reported targets. Posts and comments reported by three different individuals are automatically hidden and reviewed by operators (Article 13).

If other users have separately saved posts already viewed via screen captures or other means, the Company cannot retrieve them. Posts and comments can be deleted at any time within the app, and upon deletion, they are no longer visible to other users and photo files of posts are also deleted together (Article 9).

The Company shall destroy the relevant personal information without delay once the purpose of processing has been achieved.

The Company does not provide users' personal information to third parties.

Cooking reviews, attached photos, personal recipes, and cooking logs written by a user can only be viewed by the writer themselves and are not disclosed to other users. However, posts, comments, and nicknames directly uploaded by the user to the community are visible to other users within the disclosure scope selected by the user (Article 2, Paragraph C). Since users disclose these themselves, this does not constitute the Company providing personal information to third parties.

If the Company is required to provide a user's personal information to a third party, it will notify the user in advance of the recipient, purpose of provision, items provided, and retention period, and obtain separate consent.

However, exceptions are made when there are special provisions in statutes or when investigative agencies make a request in accordance with the procedures and methods prescribed by statutes.

The company specifies matters concerning the secure management of personal information in writing upon entering into an entrustment contract and supervises whether the trustee complies with them. If the contents of the entrusted tasks or the trustee is changed, it will be disclosed through this Policy.

The company requires all third parties that receive users' personal information, including the above business operators, to protect personal information at a level equal to or higher than that specified in this Policy. This applies not only to trustees, but also to all related companies that can access users' information, such as analysis tools, advertising networks, external software development kits (SDKs) included in the app, and their parent and subsidiary companies. The company does not transmit users' personal information to business operators that do not guarantee this level of protection, and does not allow the transmitted information to be used for purposes other than those specified in this Policy.

Scope of Analysis and Advertising Tools

The company does not use session replay (tools that reproduce users' screen operations as they are) anywhere in the app or website. Google Analytics 4 is used on the website and PostHog is used in the app for usage analysis, and Sentry is used for error analysis (Article 12). Google (AdSense) is the sole advertising business operator, and advertisements are displayed only on the website. There are no advertisements on the mobile app.

The Company transfers personal information overseas for the following functions and, pursuant to Article 28-8 of the Personal Information Protection Act, discloses the recipient, country, items transferred, purpose, method, retention period, and refusal method as follows.

A. AI Functions — Cooking Questions, Voice Coach, Recommendations, YouTube Conversion, Recipe Generation

Recipient: Google LLC, Privacy Inquiry: googlekrsupport@google.com

Country of Transfer: United States

Time and Method of Transfer: Transmitted via network at the time the user asks a question during cooking, turns on the voice coach, opens the next cooking recommendation, or requests video conversion or recipe generation. The transmission of the voice coach is separately described in 'Voice Coach (Gemini Live)' below. Today's Recommendations are automatically transmitted by the company server every dawn.

Items Transferred: Function-specific items under Article 2, Paragraph D — question text, voice coach microphone voice and conversation, recipe, ingredient, and cooking step information, recent reviews (ratings, comments, memos) and bookmarked recipe names, public video URLs entered by the user, and search queries requesting recipe generation. If the voice coach is used, the device IP address is also transmitted.

Purpose of Transfer: Providing cooking question guidance, real-time voice coaching, today's recommendations and next cooking ingredient recommendations, video recipe conversion, and recipe generation for dishes not found in search.

Retention and Use Period: 55 days from the date received by Google. The Company uses the Gemini API under Google's paid use conditions. Google does not use the received requests and responses to improve its products, but uses them solely to detect fraudulent use.

Refusal Method and Effect: If you do not use text AI questions, voice coach, next cooking recommendation, YouTube conversion, and recipe generation, the corresponding transfer will not occur. Since Today's Recommendations are automatically applied to members with reviews and bookmarks, you may request the suspension of processing pursuant to Article 9 if you do not wish for it. Refusing will prevent you from using the relevant function, but other functions can be used as is.

Voice Coach (Gemini Live) under Paragraph A

Since the user's voice is continuously transmitted overseas while the voice coach is turned on, that transfer is described separately. This applies equally to non-logged-in users.

Recipient: Google LLC, Privacy Inquiry: googlekrsupport@google.com

Country of Transfer: United States

Time and Method of Transfer: 1. When the user turns on the voice coach, the company server requests a one-time access token from Google. At this time, for the iOS app, the company server sends the recipe and progress information below, the immediate previous conversation, and coach memories together in the access settings. 2. The app connects directly to Google using that token (for the Android app, the app sends the recipe and progress information, immediate previous conversation, and coach memories at this time), and continuously transmits microphone voice in real time until the coach is turned off or the app screen is left. When steps are skipped during cooking or a timer ends, the guide sentences are also sent. All transmissions are made via an encrypted connection.

Items Transferred: Voice entering the microphone (including voices of surrounding people), recipe name and servings, ingredients used in the current cooking (including substitutions and omissions) and all cooking steps, current step and timer status, step and timer guide sentences, up to 8 immediately exchanged utterances and conversation summaries if the coach is turned on again, coach memories related to the recipe if the user is a member, and device IP address. Camera video, photos, name, email, and member identifier are not sent.

Purpose of Transfer: Real-time voice recognition, generation of coach answers and voice synthesis, transcribing user and coach speech into text, and determining app operations such as timers and step navigation.

Retention and Use Period: 55 days from the date received by Google under Gemini API paid use conditions. Google does not use the received voice and conversations to improve its products, but uses them solely to detect fraudulent use.

Refusal Method and Effect: If you do not turn on the voice coach, no transfer occurs, and even after turning it on, turning it off stops the transmission from that point. Turning off the app's microphone permission in device settings also prevents transmission. Even if you do not use the voice coach, other functions such as viewing recipes and proceeding with cooking can be used as is.

B. Voice Recognition for Voice Commands and Questions — Device Function, Not Company Transfer

Voice commands and questions made via the 'Speak' button are processed by the user device's voice recognition function (Apple for iOS, and Google generally for services set on the device for Android), and the Company does not receive voice through this path or send it overseas. Whether that function transmits voice to servers of providers such as Apple and Google for recognition depends on the device and operating system, and in this case, such transmission is a processing between the user and the voice recognition provider. If you do not use this function or disable microphone and voice recognition permissions in device settings, no transmission occurs. Unlike this, the voice coach is a function provided by the Company where voice is transmitted to Google, which was described in Paragraph A.

C. Login, Video Playback, Inquiry Emails, Usage Status and Error Analysis, AI Request Records, Advertising

The above transfers are transmitted via the network at the time of using the corresponding function (app usage and error logs are collected by the app and transmitted at short intervals), and the retention period follows the table in Article 4. The contact information for personal information inquiries of recipients is Google LLC googlekrsupport@google.com, PostHog, Inc. privacy@posthog.com, Functional Software, Inc. compliance@sentry.io, and Langfuse GmbH · ClickHouse, Inc. privacy@clickhouse.com.

The policies of each provider apply to information transmitted during the social login process. Apple Privacy Policy, Google Privacy Policy, Kakao Privacy Policy, Naver Privacy Policy

D. Organizing Coach Memories — Claude

Recipient: Anthropic, PBC, Privacy Inquiry: privacy@anthropic.com

Country of Transfer: United States

Time and Method of Transfer: Every dawn, the company server automatically transmits coach conversation logs and reviews that have not yet been organized via an encrypted connection.

Items Transferred: Cooking coach conversation logs (user and coach speech), recipe names and ingredients of that cooking, and review comments. For cooking done without a voice coach, only the recipe name, ingredients, and review comments are sent when there is a review comment. Name, email, and member identifiers are not sent.

Purpose of Transfer: Extracting facts to be kept as coach memories from conversation logs and reviews (Article 2, Paragraph M).

Retention and Use Period: Deleted within 30 days from the date received by Anthropic. Commercial use conditions of the Claude API. Anthropic does not use received requests and responses for model training, and retains them for up to 2 years only if automatically detected for violating usage policies.

Refusal Method and Effect: Since organizing coach memories is automatically applied to members who use the voice coach or leave comments on reviews, you may request the suspension of processing pursuant to Article 9 if you do not wish for it. If you use the voice coach without logging in, conversation logs are not saved on the server, so no transfer occurs. Refusing will prevent you from using coach memories, but other functions including the voice coach can be used as is.

Information Stored Domestically

Account information, cooking records, reviews, attached photos, community posts, photos, comments, cooking coach conversation logs and coach memories, customer inquiries, and pre-registration emails are stored in domestic (Seoul) servers and storage, and backups are also kept in storage in the Seoul region. The Company does not replicate or back up this data to other countries. However, information necessary for the processing of Paragraphs A, C, and D above is transmitted to the respective countries for such processing.

During the social login process, the Company receives only the minimum information necessary for authentication, and no information is transmitted to the provider before clicking the login button.

• Destruction Procedure — Personal information for which a cause for destruction has occurred is selected and destroyed with the approval of the Privacy Officer.
• Electronic Files — Permanently deleted in a manner that makes recovery and reproduction impossible.
• Attached Photos — Upon member withdrawal, all photo files of the member are deleted from the storage. Photos that were attached to reviews and then removed, or uploaded but not submitted, are also deleted together.
• Community Photos — When a post is deleted, the photo files of that post are deleted; upon member withdrawal, all community photo files of that member are deleted. Photos uploaded to be included in posts but not used are also deleted upon withdrawal.
• Coach Memories — Upon member withdrawal, the memories of that member are deleted.
• Records Sent to External Services — Records sent to PostHog, Sentry, and Langfuse are automatically deleted after the retention period of each service (Article 4) expires, and if deletion is requested prior to that, they are removed from the respective services.
• Pre-registration Email — Deleted within 30 days from the date the launch notification is sent, and also deleted from backup copies within the same period.
• Backup Copies — Stored in a separate storage in the Seoul region and deleted keeping only the most recent 14 days' worth. Even if the backup is restored, the information of users who have already withdrawn is not revived.

Users may at any time request access to, correction, deletion, or suspension of processing of their personal information, and may withdraw their consent.

What Can Be Done Directly in the App

• Change nickname
• Cancel bookmarks
• Delete community posts and comments, change post visibility, cancel applause and following, block and unblock other members (Settings > Blocked Users)
• Delete input values for gender and age group and withdraw optional consent
• Turn off usage analysis and error report transmission — Settings > Privacy
• Turn off cooking timer notifications — Settings > Notification Settings
• Delete account — Delete account and records stored on the server at once

The function to delete reviews, photos, cooking records, personal recipes, and coach conversation records one by one is not yet available in the app. If individual deletion is desired, it can be requested through the method of 'Exercising Rights via Inquiries' below, and the Company will delete them within 10 days after confirmation.

When an account is deleted, account information, gender and age group, cooking records, reviews and attached photos, personalized recipes, bookmarks, recommendation reactions, today's recommendation records, credit history, cooking coach conversation records and coach memory, community posts, photos, comments, applause, follows, blocks, and report records are all deleted and cannot be recovered. Kakao login connection is also disconnected together. Google, Naver, and Apple login connections can be disconnected in each provider's account settings.

Even after deleting the account, the following information remains as follows:

• Customer inquiries and private requests — Disconnected from the account and retained until the period in Article 4
• YouTube conversion request records — Disconnected from the account, leaving only the video and processing results
• Withdrawal processing records — Leaving only the internal identifier and withdrawal time (Article 4)
• Records sent to PostHog, Sentry, and Langfuse — Deleted when each retention period ends, and deleted earlier upon request
• Backups — Replaced by new backups and disappear within a maximum of 14 days
• Information remaining on the device — Deleted when the app is deleted (Article 12)

In cases of use without login, accounts and cooking records are not created on the server. Since app usage and error records remain as identifiers created for each installation, transmission can be turned off in settings, and deletion of already sent records can be requested via inquiry. Automatically generated connection records are deleted according to the period in Article 4.

What Can Be Done on the Website

Even if the app is not installed or the app cannot be accessed, the account and records stored in that account can be directly deleted from the page below.

https://cooklog.kr/account/delete

Withdrawal of Consent for Pre-registration

Since launch notification pre-registration is a reception consent separate from membership registration, it is not withdrawn together even if the account is deleted. To withdraw pre-registration, please apply via the email in Article 15 below. The Company destroys the corresponding email address immediately upon confirming the application.

Right to Request Personal Information Portability

Users may request the transmission of their personal information to another personal information processor pursuant to Article 35-2 of the Personal Information Protection Act.

• Method of requesting transmission — Apply through in-app inquiries or the contact information in Article 15 below.
• Transmittable items — Account information, cooking history, cooking reviews, bookmarks, personalized recipes, cooking coach conversation records, posts and comments uploaded to the community. Information analyzed and processed and generated by the Company and information of other users are excluded.
• Transmission format — JSON or CSV file
• Processing period — Within 10 days from the date of request after identity verification
• Confirmation of transmission details — Transmission date and time, recipient, and items are recorded and retained, and notified upon request through the same contact information.
• Grounds for refusal — Requests may be refused if there is a concern of infringing upon the rights of other users or if identity cannot be verified, and the grounds will be notified via email.

Exercising Rights via Inquiries

The above rights may also be exercised through email (cooklog.official@gmail.com) or in-app inquiries, and the Company will take necessary measures and notify the user of the results within 10 days from the date the request is received, after verifying whether the requester is the user themselves or a legitimate agent.

Users may also exercise their rights through a legal representative or a delegated person. In this case, a power of attorney pursuant to Form No. 11 of the Notice on Methods of Processing Personal Information must be submitted.

• Transmission Segment Encryption — All communications between the app/website and the server are encrypted using HTTPS.
• Encryption at Rest — Databases, storage, and backup data are encrypted. Since the Company does not retain its own passwords, there is no inherent risk of password leakage.
• Access Control — Personnel with access to personal information are restricted to the minimum, and databases are not exposed to external networks.
• Retention of Access Logs — Access logs of the personal information processing system are retained for at least one year and protected against forgery and tampering. Access logs are managed separately from general service operation logs.
• Protection of Photo Files — Photos attached to reviews are stored in a storage space that is not arbitrarily accessible from the outside, and a viewing path valid only for a short time is provided exclusively to the individual. Community photos are also stored in the same storage space, provided that a viewing path valid for one hour is granted only to those authorized to view the respective post (Article 2, Item (k)).
• Removal of Location Information from Photos — All metadata included in files, such as shooting location (GPS coordinates) and shooting device information, are removed from review attachment photos and community photos prior to storage.
• Pseudonymization of IP Addresses — IP addresses used to prevent pre-registration abuse are converted into an irreversible format and stored, while original addresses are not retained.
• Session Protection — Website login cookies are rendered unreadable by scripts and transmitted exclusively over encrypted connections. App login information is encrypted and stored in the device's secure storage (iOS Keychain and Android Keystore).
• Restriction of Log Recording — Authentication tokens, review contents, speech recognition sentences, and raw AI Q&A transcripts are not recorded in server logs. Request headers and bodies are not transmitted to error analysis tools (Sentry).
• Voice Coach Access Protection — The Company's Google API key is not embedded in the app. The server issues a one-time-use, short-lived access permission, and the app connects to Google strictly using that permission.
• Minimization of External Scripts — External scripts loaded on the website are limited to Google Ads (AdSense) and usage analysis (Google Analytics), and social provider scripts are not loaded. YouTube video players are loaded as isolated frames rather than scripts (Article 12).
• Blocking External Connections — External sources accessible by the browser are predetermined via a content security policy, and connections to destinations not listed are blocked.
• Self-Hosting of Fonts — Fonts used on the screen are served directly from the Company's server rather than loaded from an external font service. The mere receipt of fonts prevents users' connection information from being transmitted externally.

The Company does not allow membership registration for children under the age of 14. Recipe viewing and cooking progression without login can be used without entering personal information. However, since the voice coach can be used without logging in and voice is transmitted to Google while in use (Article 2, Item (m)), children under the age of 14 must not use the voice coach without the consent of a legal representative.

The Service requires users to independently verify that they are 14 years of age or older prior to membership registration and pre-registration. When registering via social login, users must confirm that they are 14 years of age or older in the confirmation window that opens after clicking the login button for the provider's login procedure to begin, and if not confirmed, neither login nor account creation will occur. The time of confirmation and the applied version of the privacy policy when creating the account are recorded in the account, and the question is not asked again for accounts with a record. The website does not even receive login requests made without this confirmation on the server, and the server does not create accounts without confirmation. Pre-registration can also be applied for only by agreeing to the confirmation of being 14 years of age or older, and the server does not accept applications that have not gone through this confirmation. The Company does not collect separate personal information such as date of birth or resident registration number in this procedure.

If the Company learns that personal information of a child under the age of 14 has been collected, it shall destroy the information without delay.

Cookies Used by the Website

The website uses the following cookies. The first three are necessary to use the service, the _ga series is for analyzing usage status, and the rest are issued by Google for serving advertisements.

Mobile apps do not use web browser cookies. Since no advertisements are served in the app, the device's advertising identifiers (Android Advertising ID · iOS IDFA) are also not read. Instead, the app's analytics and error collection tools create a random identifier upon each installation and store it on the device (see 'App Usage Analysis' and 'App and Server Error Analysis' below).

Web Browser Local Storage

Separately from cookies, the website stores the following values in the browser's local storage (localStorage). The values contained in the local storage remain only in the user's browser, are not transmitted to the company's server, and are not used to identify the user.

The YouTube video player (see 'YouTube Video Player and Thumbnails' below) and Google advertising scripts may also independently use browser storage, which is managed by Google in accordance with its own policy, and the company does not read these values.

Methods to Refuse the Storage of Cookies and Local Storage

Users can refuse the storage of cookies through their browser settings. However, refusing the first three cookies will make the login function unavailable, while browsing recipes without logging in remains available as is. Even if analytics and advertising cookies are refused, there are no restrictions on using the service.

• Chrome — Settings > Privacy and security > Third-party cookies (or Cookies and other site data)
• Safari — Settings (Preferences) > Privacy > Manage Cookies and Website Data
• Edge — Settings > Cookies and site permissions > Manage and delete cookies and site data
• Firefox — Settings > Privacy & Security > Cookies and Site Data
• To clear stored cookies, select the cookies item in each browser's browsing data deletion menu.
• Using Incognito mode (Private Browsing window) deletes cookies together when the window is closed.
• Local storage is managed separately from cookies — It is cleared by selecting 'Cookies and other site data' (Chrome · Edge), 'Website data' (Safari), and 'Cookies and site data' (Firefox) together in the browsing data deletion menu. Clearing it does not restrict service usage.

Website Usage Analysis (Google Analytics)

Google Analytics 4 is used to understand how the website is used. The purpose is to aggregate which pages are opened most and which functions are used to improve the service, and it is not used to identify users or for ad selection. Google signals (cross-device tracking) and ads personalization signals have been turned off.

The website's analysis identifier is not linked to member identifiers or emails, and content directly written by users, such as reviews and inquiry details, is not sent to Google Analytics. App usage analysis is subject to the PostHog item below.

• Refusal Method — Collection can be prevented by refusing cookies according to the browser-specific cookie blocking guide above, or by installing the Google Analytics Opt-out Browser Add-on provided by Google (tools.google.com/dlpage/gaoptout). Refusing will not restrict service usage.

App Usage Analysis (PostHog)

PostHog is used to understand app usage and improve the service. The purpose is to aggregate which screens and features are used, where cooking is interrupted, and how much recommendations are accepted, and it is not used for ad selection. Screen recording (session replay) is not used.

The analytics identifier is a random value created by PostHog when the app is installed. Since the Android app links this identifier with the member identifier when a member logs in, records from before logging in may also be merged into that member's records, and logging out uses a new identifier. The iOS app does not link with member identifiers. Review comments, memos, and AI question and coach conversation contents are not sent, but search terms entered in the search bar (only character count for the iOS app) and review star ratings are sent. PostHog can estimate country and city-level locations using the received IP address.

• Refusal Method — Turning off 'Send usage analytics' in the app's Settings > Privacy will stop sending them from that point on. This setting is turned on by default, and turning it off does not restrict service usage.

App and Server Error Analysis (Sentry)

Sentry is used to find and fix the causes when the app freezes or a server error occurs. Error records do not include the user's name, email, or member identifier, and screen captures and screen recordings are not sent.

• Refusal Method — Turning off 'Send error reports' in the app's Settings > Privacy stops sending app error records. This setting is turned on by default, and turning it off does not restrict service usage. Server error records do not contain information identifying users.

Online Personalized Advertising and Behavioral Information

To provide the service for free, the company displays Google advertisements (AdSense) on the website. Advertisements are only on the website and are not displayed on the mobile app. Google may collect user website visit information (behavioral information) to select advertisements and measure performance, and displays personalized advertisements tailored to interests if the user consents. This behavioral information is collected and stored by Google in accordance with its own policy, and the company does not receive it or store it on the company's server.

Account information, cooking records, reviews, and AI query contents stored by the company are not used for ad selection, nor are they transmitted to Google for advertising (transmission for AI features is pursuant to Article 7, Item Sub-clause). Member identifiers and advertising cookie identifiers are not linked, and usage analysis (Google Analytics) records are not used for advertising. The company does not accept membership registrations from children under 14 years of age and does not engage in personalized advertising targeting children. A list of advertising technology partners with which Google shares information during the ad serving process and Google's manner of using advertising information can be found on the Google Advertising Privacy Policy and Google Advertising Technology Vendors pages.

Personalized ads can be refused through the following methods. Refusal does not restrict service usage, and ads will continue to be displayed as non-personalized ads unrelated to user information.

• Web (Common) — Turning off 'Ad personalization' in Google Ad Settings (adssettings.google.com) causes Google to stop personalized ads across all sites, including this site.
• Web (Browser) — Blocking third-party cookies according to the cookie storage refusal method above prevents doubleclick.net advertising cookies from being stored.
• Mobile App — Since there are no ads in the app, there is nothing separate to refuse. The app does not read the device's advertising identifier.
• Even in the refused state, advertising operators process the minimum information necessary for ad serving (IP address, browser type, pages where ads were displayed).

YouTube Video Player and Thumbnails

The YouTube recipe page includes a YouTube video player so that the original video can be watched on the spot, and video thumbnail images are displayed on recipe lists and channel pages. Since this player and thumbnails are fetched by the user's browser by directly connecting to Google servers (youtube-nocookie.com and i.ytimg.com, respectively), the user's IP address and browser/device information are transmitted to Google during that process. The company does not receive this information or store it on the company's server.

• The player is loaded with an address that uses fewer cookies (youtube-nocookie.com). If the video is not played, Google does not leave viewing history, and if played, Google uses playback information and browser storage in accordance with its own policy.
• The company does not transmit member identifiers, cooking records, or reviews to the player, and does not insert different videos per user.
• Refusal Method — Connections do not occur if YouTube recipe pages and channel pages are not opened. Even if pages are opened, playback information is not transmitted unless the video is played. Third-party content can also be blocked with browser extensions, in which case videos and thumbnails are simply not displayed while other functions remain available as is.
• Processing that takes place on YouTube is subject to Google's Privacy Policy and YouTube Terms of Service.

Ingredient Purchase Links on Website Recipe Pages (Coupang Partners)

Coupang Partners affiliate product links for each ingredient are displayed on the website's recipe pages. Unlike the advertisements above, these links are product links determined solely by ingredient names regardless of the user and do not constitute personalized advertising. Since links are determined only by ingredient names, user account information and cooking records are not transmitted to Coupang, and different links are not shown to different users. However, because product photos displayed alongside the links are fetched directly by the user's browser from Coupang's image server (thumbnail.coupangcdn.com), opening a recipe page displaying product photos transmits the user's IP address and browser information to Coupang. The company does not receive this information. After the user clicks a link and moves to Coupang, Coupang's privacy policy applies. Purchases made through these links may earn the company a certain amount of commission, and that fact is concurrently disclosed on the pages where links are displayed. This link is not present in the app.

Information Stored by the App on the Device

The app stores the following information on the user's device for functionality. Information stored on the device is not sent to the company's server unless sent directly, such as when a user submits a review or sends voice coach conversation records (Article 2, Item Sub-clause), and is deleted together when the app is deleted.

Even if you log out or withdraw membership, some information other than login information may remain on the device, so please delete the app to clear everything. If device backup functions (iCloud Backup, Android Auto Backup, etc.) are turned on, some of the above information may be included in the user's backups.

Recipe Photos Fetched by the App from Original Sources

The app directly fetches public recipe photos from the Ministry of Food and Drug Safety Food Safety Korea server (foodsafetykorea.go.kr) and YouTube recipe thumbnails from the YouTube thumbnail server (i.ytimg.com). During that process, the device's IP address and app information are transmitted to the respective servers, and the company does not receive this information. Other recipe photos are fetched from the company's storage (AWS Seoul Region). This connection does not carry member identifiers or cooking records.

Pursuant to Article 37-2 of the Personal Information Protection Act, the Company discloses the criteria, procedures, and methods of decisions made automatically without human intervention as follows.

A. Today's Recommendations

• Decision criteria — The member's bookmarked recipe names (up to 20) and recent reviews up to 30 items (recipe name, star rating, cooking date and time, comments, and the next cooking memo). Gender and age groups are not used.
• Decision procedure — ① Every early morning, the Company retrieves the above items of members who have records of registration, reviews, bookmarks, or attendance checks within the last 30 days ② Generative AI selects 3 from the recipe list and writes reasons for recommendation ③ Adding 3 popular recipes (based on the number of reviews and bookmarks in the last 30 days) and 2 random recipes to these, the Company displays them on the app home screen. AI is not used for members without reviews and bookmarks.
• Decision method — 3 personalized recommendations are selected by generative AI (Gemini by Google LLC), and there are no separately determined score rules. Name, email, and member identifier are not included in the information transmitted to AI.

B. Next Cooking Ingredient Adjustment Recommendations

• Decision criteria — The original ingredients of the relevant recipe, the member's recent reviews up to 30 items, and reviews of that recipe up to 5 items (star ratings, comments, next cooking memo, and ingredient adjustments at that time). Gender and age groups are not used.
• Decision procedure — ① When a member opens the cooking setting screen, the above items are retrieved ② Generative AI suggests portion adjustments, additions, and omissions for each ingredient, and attaches the reviews and reasons that served as the basis ③ The server checks the format and scope, filters out suggestions previously rejected by the member, and displays them on the screen ④ The member accepts, modifies, or rejects them.
• Decision method — Suggestions are created by generative AI (Gemini by Google LLC), and the server only performs checks and filtering. They are not reflected in the recipe until the member accepts them.

C. AI Guidance and Voice Coach During Cooking

• Decision criteria — Questions entered or spoken by the user during cooking, guidance text and precautions of the current cooking stage, recipe name, and timer information. The voice coach also uses the ingredients, overall stages, progress status, immediate previous conversation, and the member's coach memory of the current cooking.
• Decision procedure — Text questions are handled by ① transmitting the question and current stage information ② generative AI creating answer sentences ③ displaying them on the screen and reading them aloud by voice. The voice coach is handled by ① conversing with the user in real time ② AI answering by voice, and directly executing app operations such as starting, extending, or pausing the timer, moving stages, and recording ingredient substitutions according to the user's speech.
• Decision method — Generative AI (Gemini·Gemini Live by Google LLC) determines answers and app operations. Cooking completion is not processed by AI and can only be done by the user via a button. Name, email, and member identifier are not transmitted.

D. Coach Memory Organization

• Decision criteria — Cooking coach conversation logs, recipe names and ingredients of that cooking, review star ratings, comments, memos, and ingredient substitution history
• Decision procedure — ① Every early morning, conversation logs and reviews that have not yet been organized are retrieved ② AI extracts preferences, ingredient substitutions and their reasons, cooking environments, failures and causes, and ratings, and integrates them into each member's memory ③ The next time the voice coach is turned on, memories related to that recipe are transmitted to the coach.
• Decision method — The company server extracts facts directly spoken by the user using Claude by Anthropic, PBC, and organization is performed according to rules determined by the company server.

E. Community Popularity Ranking and Accumulated Report Blending

• Decision criteria — For popular feeds, the number of claps and posting time of posts uploaded within the last 7 days (30 days if there are few posts) and viewable by viewers. For blending, the number of reports from different members.
• Decision criteria — Popular feeds are displayed in order of the most claps, and ties are displayed in reverse chronological order. If three different members report a post or comment, it is automatically blended so that it is not visible to other users, and an operator checks it to maintain or revert the blending. The blended post continues to be visible to the author themselves.
• Decision method — Processed only according to established rules without using AI. Gender, age group, and cooking history are not used.

Use of training data — The Company does not train AI models with users' personal information. The Gemini API is used under Google's paid terms of service, under which Google does not use received requests and responses to improve its own products (Article 7, Item A). The Claude API is used under Anthropic's commercial terms of service, under which Anthropic does not use received requests and responses to model training (Article 7, Item D).

Does not constitute a significant impact

Since the above decisions merely suggest what to cook, guide cooking methods, or determine the exposure order of community posts, they are not decisions that have a significant impact on a user's rights or obligations, unlike employment, loans, or insurance. Nevertheless, the Company provides the following rights exercise procedures identically.

F. Rights of Users

• Request for explanation — You can request an explanation of why a specific recommendation or answer was generated. Replies will be provided within 15 days from the date of request.
• Request for re-processing — You can request a human to review and re-process. Results will be notified within 30 days after completion, and if there is a justifiable reason, it may be extended for up to 60 days with the reason notified in advance.
• Refusal — For next cooking recommendations, if you refuse the suggestion, it will not be reflected, and for AI questions and voice coaches, you simply do not need to use them. For blended posts and comments, you can request a re-review using the contact information in Article 15. If you do not want Today's Recommendations and coach memories, you can request the suspension of processing using the contact information in Article 15. Neither restricts the use of other functions.

Methods of exercise are the contact information in Article 15 or in-app inquiries.

The Company transmits advertising information only when the User has given prior consent, pursuant to Article 50 of the Act on Promotion of Information and Communications Network Utilization and Information Protection, Etc. (hereinafter referred to as the "Information and Communications Network Act"). Currently, the advertising information transmitted is limited to one type: an app launch notification sent to those who have applied for pre-registration.

• Consent to receive advertising information and consent to receive it at night from 9:00 p.m. to 8:00 a.m. of the following day shall be obtained separately.
• Advertising information shall be accompanied by the indication "(Advertisement)", the sender's name and contact information, and instructions on how to refuse reception and withdraw consent to reception.
• Users may withdraw their consent to receive at any time via the email specified in Article 15; upon withdrawal, transmission shall be immediately suspended and the corresponding email address shall be destroyed.
• The processing results of the consent to reception, refusal of reception, and withdrawal of consent to reception shall be notified within 14 days from the date the expression of intent is received.
• The Company shall verify whether the consent to reception is maintained every two years from the date of consent.
• Notifications necessary for the provision of the service, such as the end of a cooking timer and responses to inquiries, do not fall under advertising information and shall be sent regardless of consent to reception.

Notifications shall not display private contents such as AI conversation contents, reviews, and memos.

The Company is in charge of overall tasks concerning the processing of personal information, and designates a Privacy Officer as follows to handle user inquiries, grievance handling, and damage relief related to the processing of personal information.

Privacy Officer: Lee Hyun-woo

Position: CookLog Operator

Email: cooklog.official@gmail.com

Inquiries, complaints, and damage relief related to the protection of personal information can be submitted through the email above or via in-app inquiries, and the Company will respond and process them without delay.

Users may request access to personal information pursuant to Article 35 of the Personal Information Protection Act to the above contact point. The Company does not operate a separate department for receiving access requests, and the Privacy Officer directly receives and processes them.

To seek relief for personal information infringement, users may apply for dispute resolution or consultation to the organizations below.

If you are dissatisfied with the company's measures regarding Article 35 (Inspection), Article 36 (Correction and Deletion), and Article 37 (Suspension of Processing) of the Personal Information Protection Act (개인정보 보호법), you may file an administrative appeal.

This Policy applies from August 25, 2026.

If there are additions, deletions, or modifications to the contents due to changes in laws and regulations or the service, they shall be notified through this page from 7 days prior to the enforcement of the changes (this page can also be opened from the app's settings screen). However, in the event of significant changes to user rights, notice will be given 30 days in advance.

Revision History

• v1.0 (Effective August 25, 2026) — Current. Initial enforcement. This is an integrated policy governing both the app and the website.

You can check the CookLog Terms of Service in the Terms of Service.