Privacy Policy

Published: October 21, 2026 / Effective: October 21, 2026

Kobbokkom Company (the “Company”) applies this Policy to its apps, websites, and online features (the “Services”). The sections below are organized by function and processing purpose, not by app name. Actual processing depends on the features you use, your operating system, permissions, and consent settings. Not every Service collects every item listed below. Processing for accounts, advertising, purchases, location, or AI does not apply where those features are absent. A Service with a separate privacy policy is governed by that policy.

1. Controller and Contact

2. Information and Purposes

Function Information and purpose Where processing occurs and what is sent
On-device files and preferences Selected files and contents, file paths, conversion or compression settings, working files, screen and widget layouts, and custom phrases are used to provide features and retain preferences Files and settings processed on-device are not uploaded to Company servers. Files you save remain in your chosen location. Separate actions you choose, such as external URL requests, maps, or support messages, follow the entries below.
External resources and maps Requests for resources at a specified URL and display of a selected image’s GPS coordinates on a map The resource server receives request information such as your IP address. Choosing to view a location opens Google Maps with the selected coordinates.
Sign-in, membership, and authorization Provider account identifiers, verified email where applicable, Service member identifiers, nicknames, profile timestamps, sessions, and roles are used for authentication, member display, authorization, and account deletion Google sign-in or Sign in with Apple where supported is used. Company servers process the necessary member and session information. Store-management accounts from different providers are not automatically merged by email address. The desktop app keeps its sign-in session token in the operating system’s credential store (such as Keychain), and Company servers store only a hash of the token.
Posts, comments, and likes Post titles, bodies, previews, categories, selected apps, visibility, authors, and times; comment bodies, authors, and times; and member/post identifiers and times for likes are used to create, edit, delete, search, display, handle reports, and prevent duplicates Company servers process this information. Content you publish publicly is visible to other users.
Customer registration and queue management Complete mobile phone numbers, party sizes, names, registration and processing times, wait status, store/wait identifiers, and access credentials are used for registration, status, calls, notifications, and operational history Company servers process this information. A name is optional unless a store requires it. Customers can register without an account using an anonymous device or browser identifier. Reusable profiles, wait records, and access information may also be stored on the device or browser.
Store operations Store names, optional addresses and guides, staff names, store settings, and queue records are used for operations and owner/staff authorization Company servers process this information.
Camera and QR reading Camera images are used to read codes when you choose QR scanning QR images are processed on-device and are not uploaded to Company servers. QR reading and customer queue registration do not request GPS permission or measure device location.
Optional weather and place names Rounded coordinates are used for weather and place names after you allow approximate location access Coordinates are sent to Open-Meteo over HTTPS and may also be sent to the operating system’s reverse-geocoding provider. Background location is not requested.
In-app purchases and restoration Store-provided purchase entitlements are checked to unlock paid features Apple processes payment and account information for Apple StoreKit purchases. The Company does not receive your Apple Account password or payment card details through this process.
AI document assistant When you ask the AI, your request and conversation history, document content, selections, and page captures the AI reads, the content of references you attach or enable, writing instructions, memory, skill content, the selected model, and a conversation identifier are used to generate responses and edit documents Requests pass through Company servers to OpenRouter and the provider of the model you select. Supporting model calls that help handle a request, such as finding relevant material or judging automatic approval, take the same path. Document content is not sent unless you ask the AI. Company servers do not store request or response content; they record only the member identifier, token counts, and cost needed for credit accounting. When web search is on, search queries written by the AI are sent through OpenRouter to Exa. MCP servers you connect yourself receive the inputs of the tools the AI calls on them. Conversation history, attachments, and references are stored on the device per account.
AI credits and subscription billing Credit balance, monthly allowance usage, top-up/usage/refund history (the credit ledger), subscription status, expiry, and billing channel, App Store transaction identifiers, and Lemon Squeezy order and subscription identifiers and amounts are used to grant and deduct credits, confirm subscriptions, apply refunds, and prevent abuse Apple processes payments for the Mac App Store build, and Lemon Squeezy processes payments for direct-download builds as merchant of record. Each payment provider handles payment methods, billing addresses, and tax information; the Company does not receive card numbers. A member identifier, or a value derived from it, is sent to the payment provider to link the payment to your account.
Subscription sync and web publishing When a subscriber turns on sync, AI conversations (the 100 most recent, without attached originals or images), user skills and their text files, saved prompts, writing instructions, memory, settings, and the reference library list and original files are used to sync across devices. Documents you choose to publish and their names are used to provide read-only links Conversations, skills, and settings are stored in the Company’s server database; reference originals and published documents are stored in private Cloudflare R2 storage. Documents open in the editor are not synced. Anyone with the link can view a published document.
Error reports and bug reports When the app hits an error, the error message and location, app version, and runtime information such as operating system and device type are used to fix it. Text you write in a bug report is used to resolve the issue Reports are sent to an error-collection server operated by the Company. Document content, user folder paths, computer names, and member information are removed before sending. Automatic error reporting is on by default and can be turned off in the app’s settings. A bug report is sent when you submit it, even with automatic reporting off, and is linked to the most recent error if automatic reporting is on.
Support Information you choose to send by email or private post is used to answer your request The Company receives the message. Please do not send sensitive files or unnecessary personal information.
Security and operations Session hashes, member identifiers, expiry/revocation/last-seen times, administrator status, action types and times, API errors, and operational records are used for authentication, rate limiting, abuse prevention, and incident handling Company servers and the operational providers listed below process this information.
Web analytics and advertising Page paths and page-view information, advertising identifiers, interactions, and diagnostics are used to understand usage, deliver and measure ads, and prevent fraud This applies only to features with web analytics or advertising. Section 3 describes the scope and available choices.

Google sign-in for the web discussion board does not store OAuth access tokens or authorization codes as member data. Google profile photos and Google nicknames are not separately collected or stored; discussion-board nicknames are managed within the Service.

3. Cookies, Web Analytics, Advertising, and Choices

Website cookies and analytics

  1. The web discussion board maintains sign-in with a __Secure-forum_session cookie using HttpOnly, Secure, and SameSite=Lax. It is sent to kkom.net and its subdomains, expires with the session, and is deleted on sign-out. JavaScript cannot read its value, and the server stores only a hash of the session token.
  2. Google sign-in for the web discussion board verifies requests with a temporary forum_oauth_state cookie using the same domain and attributes. It is deleted when sign-in completes or expires after 10 minutes.
  3. The display language (ko or en) is stored in a kkom-lang cookie and browser local storage. The browser language is used if you have not chosen one. The cookie applies only to the host that sets it, uses SameSite=Lax, and lasts one year. The server uses it only to select the display language, not as account data.
  4. The production website sends page views to Google Analytics and uses _ga and _ga_NDMWN52156 cookies. Google’s processing and retention of browser, device, and network information depend on the actual property settings and Google policies. Browser settings or blocking methods can limit transmission.

Website cookies and web analytics are separate from on-device file processing or clock display. Features without third-party advertising or analytics SDKs do not perform the related advertising or app-analytics collection. Apple may provide App Store sales, usage, or diagnostic reports under your settings and its policies; this is separate from transmitting on-device file contents.

Features with advertising

For ad delivery, measurement, and fraud prevention, Google AdMob SDKs may automatically process IP addresses and approximate location inferred from them; advertising, app, and device identifiers, including device account-related identifiers where applicable; ad views, taps, and other interactions; and app/SDK performance and diagnostics. Details depend on the operating system, SDK, permissions, and consent settings. See the official disclosures for Android and iOS. The customer queue-registration website has no advertising.

App code for customer registration does not add registration names, phone numbers, party sizes, wait details, wait access credentials or secrets, or that feature’s anonymous device identifier to ad requests. These are separate from IP addresses and advertising or device identifiers processed automatically by Google’s SDK.

Advertising features using Google User Messaging Platform (UMP) check applicable consent and request ads only when permitted. When UMP requires a privacy-options entry point, you can change your choices in the advertising privacy settings. Operating-system advertising identifier and privacy permissions also apply. Without App Tracking Transparency permission on iOS, cross-app tracking ads using IDFA are not requested; only limited advertising permitted by UMP may be requested. Google’s purposes, retention, and choices are described in its Privacy Policy, notice for partners’ sites and apps, and ad settings.

4. Retention and Deletion

Information or function Retention and deletion
On-device files and preferences You can delete saved files using the operating system. Device/browser settings or app deletion can remove the corresponding local data. Separate device backups are managed by the operating system; iOS Keychain information may remain after app deletion.
Weather cache One recent result, rounded coordinates, a place name, and its timestamp are reused for up to 30 minutes. Revoking location permission or disabling weather deletes the cache and stops new requests, but does not delete requests already processed or provider logs. Clock and date display remain available without location permission or an internet connection.
Weather-provider logs Open-Meteo’s policy states that maintenance, troubleshooting, and abuse-prevention logs may contain IP addresses and geographical coordinates. Logs are deleted after 90 days and are not linked to user identities. The Company does not operate the weather server or receive these logs.
Membership and profiles Retained until withdrawal or a deletion request is processed. Separate retention may be necessary for legal duties or other users’ rights.
Posts, comments, private posts, and likes Retained as needed to provide the Service and handle disputes. Public posts and comments may remain after withdrawal with author identifiers removed.
Web discussion-board sessions and actions Sessions expire 8 hours after issuance by default. Revoked/expired sessions are removed through operational cleanup. Rate-limiting user_actions records are deleted by the daily backup task once they are 3 months old.
AI request content Not stored on Company servers. Conversations stored on the device remain until you delete them in the app or remove app data. OpenRouter and model providers retain data under their own policies.
AI feature accounts and sessions Accounts are retained until you delete the account in the app. Sign-in sessions are revoked when you sign out or delete the account.
Credit ledger and payment records Deleting an account removes member information and balances. Top-up, usage, and refund records are kept, unlinked from the account, for as long as needed for settlement, refunds, disputes, and legal retention. To prevent a new sign-up in the same month from receiving the monthly allowance again, the deleted account’s sign-in provider identifier and that month’s usage are kept together.
Subscription sync data New transfers stop when the subscription ends or sync is turned off. Conversations, skills, settings, and reference originals stored on the server are deleted when the account is deleted.
Published documents Deleted from storage within one hour after the link is closed or the account is deleted. When the subscription ends, publishing stops and the document is kept.
Error reports Details of automatic error reports are deleted 30 days after receipt. Error summaries and occurrence counts are not deleted automatically. Bug reports are kept until an operator deletes them.
Ended queue records Names, phone numbers, wait history, and related access credentials are deleted 90 days after a wait ends. This period does not apply to active waits. Store or account deletion removes related information subject to the Service structure and legal retention duties. This 90-day period does not apply to Google advertising information.
Database backups May contain Service data and are retained according to storage lifecycle and recovery needs. The configured backup retention period will be confirmed and disclosed from the production settings. Backups of the AI feature account database are kept for the most recent 7 days.
Information retained by external providers Google Analytics, Cloudflare, Google, Apple, OpenRouter and AI model providers, Exa, Lemon Squeezy, OVHcloud, and any optional email provider apply their settings, contracts, and policies. The Company reviews and updates relevant notices against its operational settings.

5. External Providers and Information Disclosure

The Company does not sell personal information. The providers below process information necessary for the relevant features. Section 3 describes information processed directly by advertising SDKs.

  • Cloudflare, Inc.: May process request, network, and security information for Cloudflare Tunnel connections to Company-hosted web/API domains, CDN, security, and incident handling. Stores AI feature reference originals and published documents in private R2 storage and serves the published-document viewer on Cloudflare Pages.
  • Google LLC: Processes authentication information, page views, selected coordinates, or advertising/device/diagnostic information for the sign-in, analytics, maps, or advertising features you use. Sections 2–3 describe each function’s scope.
  • Apple: Processes account, payment, and entitlement information needed for supported Apple sign-in, purchases, and restoration. Mac App Store subscription and credit purchases are confirmed through App Store Server Notifications and the App Store Server API. StoreKit purchases follow App Store & Privacy. Reverse geocoding and diagnostic reports follow operating-system settings and provider policies.
  • Open-Meteo and operating-system location providers: Process rounded coordinates and request information when you grant location access for weather. Place-name reverse geocoding follows Apple’s or your Android device provider’s policy.
  • OpenRouter, Inc.: Receives AI requests, forwards them to the provider of the model you select, and calculates usage and cost. The OpenRouter Privacy Policy applies.
  • AI model providers: The model developers, or hosting providers serving those models, to which OpenRouter sends requests. Models currently selectable in the app come from Anthropic, OpenAI, DeepSeek, Alibaba (Qwen), and Z.ai. Each provider’s policy governs how long request content is kept and how it is used.
  • Exa Labs, Inc.: Processes search queries written by the AI when you turn on AI web search.
  • Lemon Squeezy, LLC: As merchant of record for direct-download builds, handles payments, taxes, receipts, refunds, and subscription management, processing names, email addresses, payment methods, and billing addresses. The Lemon Squeezy Privacy Policy applies.
  • OVHcloud: Provides the virtual server that runs the AI feature API server and account database.
  • MCP servers you connect: External MCP servers you register in the app receive the inputs of tools the AI calls. Their operators’ policies govern that processing.
  • Telegram: When operator notifications are configured, delivers new-error and bug-report alerts to the operator.
  • External resource servers: Receive request information such as your IP address when you open or request a resource at a URL you specify.
  • AWS: Stores encrypted operational database backups. Current deployment documentation identifies Seoul, Republic of Korea (ap-northeast-2), as the backup region.
  • Email delivery providers: May be used only if new-post email notifications are enabled in production. The actual provider, transfer countries, and retention period must be confirmed from settings and contracts and added to this Policy before activation.

6. International Processing and Choices

Information may be transferred to or accessed from outside Korea during processing by Cloudflare, Google, Apple, Open-Meteo, OpenRouter and AI model providers, Exa, Lemon Squeezy, OVHcloud, Telegram, an external server you select, or an optional email provider. Transfer items, countries, timing and methods, recipients’ names and contacts, purposes and retention, and the method and effect of refusing transfers will be confirmed from the relevant operational settings and contracts and disclosed. On-device functions that do not need these services do not send their information to them.

Not using external sign-in avoids its authentication request. Document content is not sent to AI providers unless you use AI features, and automatic error reporting can be turned off in the app’s settings. External resources and maps open when you choose them. Revoking location permission or disabling weather stops new weather requests. Section 3 describes web-analytics and advertising choices. These choices can limit the related online feature but are separate from on-device tasks that do not need that feature.

7. Destruction

  1. Information is destroyed without undue delay when its retention period ends or its purpose is fulfilled.
  2. Database records are deleted using methods designed to make recovery difficult. Information remaining in backups is access-restricted and removed through backup rotation and disposal.
  3. Information retained for legal duties, disputes, or security is stored separately from other personal information and destroyed when its retention period ends.

8. User Rights and Requests

Within the scope of applicable law, you may request access, correction, deletion, restriction of processing, or withdrawal of consent at [email protected] or through a private post. The Company verifies the requester and considers applicable law, other users’ rights, and legal retention duties. You can also manage local data and permissions through app, browser, and operating-system settings. You can delete an AI feature account yourself from the app’s account menu. Doing so cancels Lemon Squeezy subscriptions, but a Mac App Store subscription must be cancelled separately in your Apple Account’s subscription settings.

9. Security Measures

The Company applies reasonable safeguards appropriate to each processing environment, including access controls, encryption in transit, HttpOnly/Secure session cookies, session expiry and revocation, database access controls, encrypted backups, security updates, and operational record review.