INLEVEL9 (인레벨나인, the "Company") complies with the Personal Information Protection Act of Korea and related laws in providing the LEVEL11 software, the website (level11.co.kr) and the account service, and processes personal data as described below. The Korean text of this policy governs; this English text is a translation for reference.
LEVEL11 is a tool in which AI models read and edit your code. This policy therefore covers not only ordinary account data but, in detail and for each way of running a model, where the code and prompts you send to a model ("Input") and what the model returns ("Output") go, and how long they are kept.
1. What is collected and why
The Company stores personal data on its servers only for users who create an account. If you use LEVEL11 without an account, with BYOK or a local model, nothing is stored on the Company's servers.
| Category | Items | Purpose | How |
|---|---|---|---|
| Account | e-mail address, account ID (a random identifier), plan, sign-up time, last-seen time | sign-up and sign-in, applying the plan, answering support requests | the app's sign-in screen |
| Sign-in | hash of the one-time code (expires after 10 minutes), hash of the device token, device description (app version, operating system, computer name), issue, last-use and revocation times | password-less sign-in, per-device access control | generated at sign-in |
| Security | number of sign-in-code requests (per e-mail and per IP address, in a one-hour window), number of support tickets (per e-mail, one-hour window) | preventing abuse of code sending and ticket submission | recorded by the server |
| Usage | per-request metadata: request ID, model, requested model, whether streamed, response status, input, output and cache token counts, cost, duration, time; daily and monthly totals | enforcing plan limits, calculating fees, reconciling against provider billing | recorded by the gateway |
| Model Input and Output | prompts, attached code and files, rule files, tool results, model responses (account mode only) | relaying the call to the model you chose; not stored on the Company's servers (see section 2) | requests sent by the app |
| Billing | Toss Payments billing key, masked card label (issuer and partial number), billing interval (monthly or yearly), subscription period, invoices (month, plan, fee, usage, overage, total, status, payment reference), billing event log | charging paid plans, refunds, tax filing | the checkout page and Toss Payments responses |
| Support tickets | e-mail address, category, subject, body, app version, account ID (if signed in), submission and reply times, status | answering requests, handling disputes | the website's contact form |
| Invitations | invited e-mail address and note | admitting sign-ups while invitations are required | entered by the operator |
The Company's gateway does not store prompts, files, conversation content or model responses. Usage records contain only numbers such as token counts and cost. The app contains no usage-analytics (telemetry) tooling; the Company does not collect which features you click or which files you open.
2. How model Input and Output are processed
Where Input and Output go depends on the way you chose to run the model.
| Mode | Path of Input and Output | What the Company sees | What remains outside the Company |
|---|---|---|---|
| Account mode | app → Company gateway → Cloudflare AI Gateway → the model provider you chose → back along the same path | the gateway relays the request and records only metadata such as token counts and cost; bodies are not stored | request and response bodies in Cloudflare AI Gateway logs for up to 30 days; the provider processes the request under its API terms |
| BYOK | app → model provider (Anthropic, OpenAI, Google) directly | nothing; the Company's servers are not involved | the provider processes it under your own API agreement |
| Local model | app → model server on your computer | nothing | nothing; it never leaves your computer |
Account mode in detail.
- Requests carry only the account ID and plan as metadata, never the e-mail address. Model providers do not receive your e-mail address.
- The Company's gateway relays request bodies without reading them and records only the model, token counts, cost and response status.
- Cloudflare AI Gateway keeps request and response bodies in its logs for operations (incident analysis) and billing reconciliation (matching the providers' invoices against the Company's metering). Logs are kept for up to 30 days and older entries are deleted daily. The Company's operators look at the logs only as needed for incident analysis or reconciliation.
- The model providers (Anthropic, OpenAI, Google, xAI, Alibaba Cloud, Cloudflare Workers AI) process requests under their own API terms. To the Company's knowledge, content sent through their APIs under those terms is not used to train models, and providers may retain requests for a limited period for abuse monitoring and legal compliance. See each provider's policy in the table in section 5.
- The Company does not train AI models on your Input or Output, and does not make your content available to third parties for training.
Other people's personal data in your Input. Code or files you send to a model may contain other people's personal data (a database dump, a log file, a customer list). Whether to send such data to the Service is your decision, and as the controller of that data you must comply with the laws that apply to it. The Company does not process it beyond what the model call requires. Do not send data that the law specially protects, such as resident registration numbers, card numbers or health information, through account mode; handle it with BYOK or a local model. Personal data in Input may reappear verbatim in Output.
What the app stores on your device. Sessions (conversation history), checkpoints, settings, rule files, agent presets, MCP configuration, BYOK keys and integration credentials (encrypted with Keychain on macOS and DPAPI on Windows), and the device token issued at sign-in are all stored only on your computer. Nothing is sent to the Company's servers until you explicitly upload it. The gateway has a per-user settings and session store (/sync/*, on Cloudflare R2), but the app currently shipping does not upload anything to it. If the app gains a sync feature, this policy will be updated and announced.
MCP servers and integrations. MCP servers and integrated services you add receive the arguments of the tool calls the agent makes to them (file paths, search terms, data and so on). They are third parties governed by their own privacy policies. The Company does not receive that data.
Automatic updates and the website. The app fetches update information from releases.level11.co.kr every six hours; that request carries only the app version and operating system. The website and download server run on Cloudflare, whose ordinary access logs (IP address, request time, browser information) may be kept on Cloudflare's infrastructure for security and incident response. The Company places no analytics tools or advertising trackers on the website.
3. Retention
| Items | Retention |
|---|---|
| account data, device tokens, usage records | until the account is closed; deleted without delay after a closure request |
| sign-in code hashes | 10 minutes after issue, or immediately on use |
| sign-in-code and ticket request counts | expire after the one-hour window and are deleted afterwards |
| billing records (invoices, billing events, billing key, card label) | under the Act on Consumer Protection in Electronic Commerce, records of contracts, withdrawals, payments and supply for 5 years; the monthly usage totals on which an invoice is based are kept for the same period; the billing key is deleted at Toss Payments on request when the plan is cancelled or the account closed |
| support tickets | 3 years from the day the ticket is resolved (closed), as records of consumer complaints and dispute handling under the same Act |
| Cloudflare AI Gateway request logs (request and response bodies, token counts, cost, account ID) | up to 30 days; deleted daily |
| requests retained by model providers | per each provider's API policy (table in section 5) |
| e-mail sending records (Resend) | per Resend's retention policy |
Records that must be kept by law are stored separately from other data for that period and used only for that purpose.
4. Disclosure to third parties and outsourcing
The Company does not sell or disclose users' personal data to third parties, except:
- when you choose a model and send a request, so that your Input reaches that model provider (sections 2 and 5);
- when an investigative authority or court requires it by lawful process;
- with your separate consent.
The Company outsources processing to the companies below in order to run the Service. Those outside Korea are also listed in section 5.
| Processor | Outsourced work |
|---|---|
| Toss Payments Co., Ltd. (Republic of Korea) | card registration, payment authorisation, refunds |
| Cloudflare, Inc. (USA) | hosting the gateway, database, storage and website; relaying and logging model calls through AI Gateway; running Workers AI models |
| Resend, Inc. (USA) | sending sign-in codes and notification e-mails |
5. Transfers abroad
The Company transfers personal data abroad as follows in order to provide the Service. Transfers take place over the network in the course of using the Service, at the moment you sign in or send a request.
| Recipient (contact) | Country | Items | Purpose | Retention |
|---|---|---|---|---|
| Cloudflare, Inc. (www.cloudflare.com/privacypolicy) | USA | every server-stored item in section 1 (account, sign-in, security, usage, billing, support tickets, invitations), model request and response bodies, access logs | hosting the gateway, database (D1), storage (R2) and website; relaying and logging model calls through AI Gateway; running Workers AI models (DeepSeek, GLM, Qwen 3.8 27B) | stored items as in section 3; AI Gateway logs up to 30 days |
| Anthropic, PBC (www.anthropic.com/privacy) | USA | request and response bodies sent to Claude models, account ID | model inference | per the Anthropic API terms; API input is not used for training |
| OpenAI, L.L.C. (openai.com/policies/privacy-policy) | USA | request and response bodies sent to GPT models, account ID | model inference | per the OpenAI API terms; API input is not used for training |
| Google LLC (policies.google.com/privacy) | USA | request and response bodies sent to Gemini models, account ID | model inference | per the Google Cloud / Gemini API terms; API input is not used for training |
| xAI Corp. (x.ai/legal/privacy-policy) | USA | request and response bodies sent to Grok models, account ID | model inference | per the xAI API terms |
| Alibaba Cloud (Singapore) Private Ltd. (www.alibabacloud.com/help/en/legal) | Singapore | request and response bodies sent to the Qwen 3.8 Max model, account ID | model inference | per the Alibaba Cloud Model Studio terms |
| Resend, Inc. (resend.com/legal/privacy-policy) | USA | e-mail address, sign-in code, content of plan and ticket notification e-mails | sending sign-in codes and notifications | per Resend's retention policy |
A model request reaches a provider only when you choose that provider's model. The DeepSeek, GLM (Z.ai) and Qwen 3.8 27B models are hosted by Cloudflare Workers AI, so nothing is transferred to DeepSeek, Z.ai or Alibaba Cloud for them. In BYOK and local-model modes there is no transfer abroad in which the Company is involved. You may refuse these transfers; in that case account mode cannot be used, and LEVEL11 remains usable with BYOK or a local model.
Domestic outsourcing. Payments are outsourced to Toss Payments Co., Ltd. (Republic of Korea). Card numbers and expiry dates are held by Toss Payments; the Company receives only a billing key and a masked card label. Toss Payments receives the account ID (as the customer key), the amount and the order name.
6. Deletion
Data is deleted without delay when its retention period ends or its purpose is fulfilled. Electronic files are deleted irrecoverably. When an account is closed, the account row and its tokens and usage records are deleted; billing records and support tickets that must be kept by law are stored separately for the periods in section 3 and then deleted. Cloudflare AI Gateway logs expire automatically under the 30-day retention and are not deleted early on account closure.
7. Your rights
You may exercise the following rights at any time by writing to contact@inlevel9.com from the account e-mail:
- Access: Settings → LEVEL11 account in the app and the account page on the website show your e-mail, plan, today's and this month's usage, the registered card label and invoices; other items are provided on request.
- Correction: for example changing the e-mail address.
- Deletion and suspension of processing: a request to close the account. The app currently has no closure button; request it by e-mail. Records that must be kept by law are excluded.
- Revoking a device token: signing out in the app revokes that device's token immediately.
- Refusing transfers abroad: use BYOK or a local model instead of account mode.
The Company acts on a request within 10 days of receiving it and reports the result. Requests through a representative require a power of attorney. Exercising your rights never leads to worse treatment in the Service.
Limits on correcting Output. Because the Company neither stores nor controls model Output, correcting or deleting personal data contained in Output is done by you on your own computer. The Company cannot guarantee that a model will produce accurate statements about any particular person.
Automated decisions. The Company makes no decision with legal or similarly significant effects on you solely by automated processing. Plan limits and anti-abuse throttling are applied automatically, but account termination is decided by a person.
8. Security measures
- Device tokens and sign-in codes are stored only as SHA-256 hashes salted with a server secret (pepper), never in plain text. The raw token is handed to the app once, at issue.
- Model providers' API keys never reach the user's device, and the gateway holds no provider keys either: it authenticates to AI Gateway with a single Cloudflare token. Secrets are kept in Cloudflare Workers' encrypted secret store.
- All communication is encrypted with HTTPS.
- Sign-in codes are six digits, valid for 10 minutes, limited to 5 attempts, and sending is limited to 3 per e-mail address and 20 per IP address per hour.
- Model request metadata carries only the account ID, never the e-mail address.
- The gateway does not store request bodies. The only place bodies remain is the Cloudflare AI Gateway log, and access to it is limited to authorised operators.
- The operations admin API is protected by a separate secret token and used only by authorised operators.
- BYOK keys and integration credentials stored by the app are encrypted with the operating system's secure storage (Keychain on macOS, DPAPI on Windows) and injected into commands the agent runs only as environment variables.
- In the event of a personal-data breach, the Company notifies affected users and the Personal Information Protection Commission without delay as the law requires.
The Company takes reasonable protective measures, but no system can be completely secure. You should also keep your device, e-mail inbox and API keys safe.
9. Cookies and automatic collection
The website (level11.co.kr) sets no cookies and uses no analytics or advertising scripts. The website's account page and contact form keep the device token issued by sign-in code in the browser's local storage (localStorage) to stay signed in; the token is never put in a URL and is deleted on sign-out. It is not used for tracking. The LEVEL11 app stores the device token issued at sign-in in its settings file on your computer to keep you signed in; it is deleted when you sign out. The app has no telemetry or crash-reporting tooling.
10. Children under 14
The Company does not create accounts for children under 14 and deletes any such data without delay on becoming aware of it.
11. Privacy officer
- Name: Kwangsup Ahn (안광섭), Representative
- E-mail: contact@inlevel9.com
- Address: 3F, 3 Yeongdeungpo-ro 19-gil, Yeongdeungpo-gu, Seoul, Republic of Korea
Complaints about personal data may also be filed with the Personal Information Infringement Report Center (privacy.kisa.or.kr, 118), the Personal Information Dispute Mediation Committee (kopico.go.kr, 1833-6972), the Supreme Prosecutors' Office cybercrime unit (spo.go.kr, 1301) or the National Police Agency cyber bureau (ecrm.police.go.kr, 182).
12. Changes to this policy
Changes are announced on the website at least 7 days before they take effect. Material changes, such as new data items, purposes, retention periods or recipients abroad, or a change in how model Input and Output are processed, are announced at least 30 days in advance and also sent to the account e-mail.
Business information
- Business name: INLEVEL9 (인레벨나인)
- Representative: Kwangsup Ahn (안광섭)
- Business registration number: 735-23-01161
- Mail-order business registration number: 2026-서울영등포-0851
- Address: 3F, 3 Yeongdeungpo-ro 19-gil, Yeongdeungpo-gu, Seoul, Republic of Korea
- Customer service: +82 10-7659-8163
- Contact: contact@inlevel9.com
This policy applies from 29 October 2026.