Terms of Service

This is an English translation provided for reference only. The Korean version is the binding version, and it prevails if the two versions differ. This translation follows the Korean Terms effective November 26, 2026 (version 2026-11-26).

Article 1 (Purpose)

The purpose of these Terms is to set out the conditions and procedures for using Atelier Launch (the "Service") provided by Atelierlaunch (representative: Jung Sung Hun, the "Operator"), and the rights, obligations, and responsibilities of the Operator and Users.

Article 2 (Definitions)

  1. "User": a Member or Non-member who accesses the Service and uses it under these Terms
  2. "Member": a person who has signed up with an email address and password and uses the Service
  3. "Non-member": a person who uses the Service without signing up. This includes people who use the pre-sign-up Quick Check on the home screen and people who have only applied for the launch notice email (the "Waitlist Applicants").
  4. "Project": one idea entered by a Member, together with the validation results, plan, hand-off, and operations check records that belong to it
  5. "AI Output": validation step results, reports, draft plans, titles, operations reports and to-dos, draft promotional posts, and draft store descriptions and review replies that the Service creates with generative AI
  6. "User Content": ideas, descriptions, and points to fix entered by a Member, and plans that a Member has edited or finalized
  7. "Credits": usage rights that the Operator grants free of charge, which are used up when using features beyond the free scope (Full Validation, One-Page Plan, Hand-off to Development, operations management, and so on)
  8. "Paid Validation": a Quick Check or Full Validation that a Member buys one at a time beyond the free scope (Article 11)
  9. "Fix Order": a paid product that, based on Virtual Residents results, writes up what to fix first on the first screen of a service (up to three items), how to fix it, and instructions to give to Claude

Article 3 (Operator Information and Posting of the Terms)

  1. The Operator posts the following information and these Terms on the Service's first screen and login screen so that Users can easily see them. The Terms may be made viewable through a linked screen.
    • Trade name: Atelierlaunch (representative: Jung Sung Hun)
    • Business registration number: 367-35-01904
    • Mail-order business report: exempt (Article 2(1)1 of the Notice on the Criteria for Exemption from Mail-Order Business Reporting (통신판매업 신고 면제 기준에 대한 고시), fewer than 50 mail-order transactions in the previous year)
    • Business address: 1st floor, 129-3 Myeongan-ro 18beon-gil, Dongnae-gu, Busan (Allak-dong)
    • Contact (email): atlier.skill@gmail.com (inquiries and refund requests are received by email)
    • Chief privacy officer: Jung Sung Hun
    • Service address: https://atelierlaunch.kr
  2. Before payment, the Operator separately shows important information, such as the price, withdrawal of subscription, and refund conditions for Paid Validation and Fix Order, and has the User confirm it.

Article 4 (Amendment of the Terms)

  1. The Operator may change these Terms to the extent that doing so does not violate relevant laws such as the Act on the Regulation of Terms and Conditions (약관의 규제에 관한 법률) and the Act on the Consumer Protection in Electronic Commerce, Etc. (전자상거래 등에서의 소비자보호에 관한 법률).
  2. When changing the Terms, the Operator announces the changes and the effective date on the Service screen starting 7 days before the effective date (starting 30 days before if the change is unfavorable to Members), and also notifies Members and Waitlist Applicants by email.
  3. If you do not agree to the changed Terms, you may delete your account or withdraw your application before the effective date. If the Operator gave notice together with the statement "if you do not express refusal by the effective date, you will be deemed to have agreed," and the Member continues to use the Service without expressing refusal, the Member is deemed to have agreed to the changed Terms.

Article 5 (Interpretation of the Terms)

Matters not set out in these Terms and the interpretation of these Terms follow relevant laws and regulations and general commercial practice. If the meaning of the Terms is unclear, it is interpreted in favor of the User.

Article 6 (Provision and Change of the Service)

  1. The Operator provides Members with the following.
    • Idea validation: Full Validation (problem statement, competitor research, assumptions, business viability, stop criteria, and so on), Quick Check, and report download as Markdown. Validations beyond the free scope (Article 11) are sold one at a time (Article 12)
    • One-Page Plan: the Member edits and finalizes an AI draft
    • Hand-off to Development: creates a project repository in the Member's GitHub account and delivers first instructions so the Member can continue building with Claude Code. Receives development progress signals from the repository and shows them in the development tab, and for store apps, helps build and download the Android install file (APK) (Article 20)
    • Operations check: checks the service address entered by the Member every hour and shows whether it is up, its response speed, and this week's to-dos (Article 21)
    • Operations management service (only when the Member turns it on): checks the service address every 5 minutes and sends outage and recovery alerts by email, summarizes as numbers the usage signals sent by the Member's service or app, provides daily, weekly, and monthly operations reports and to-dos written by AI, draft promotional posts (when the promotion feature is turned on), and for store apps, draft store descriptions and review replies and version (update) guidance (Article 21)
    • Virtual Residents: reads the first screen of a public service address entered by the User and shows how virtual visitors look around and where they leave. What to fix first based on the results, and how, is sold one at a time as "Fix Order" (Article 12)
    • Waitlist: launch notice applications and notice emails (Article 22)
  2. Non-members can use the pre-sign-up Quick Check on the home screen. If they do not sign up, the result disappears after 24 hours.
  3. The Service is currently in beta. Validations beyond the free scope (Article 11) and Fix Order are paid (Article 12). Features, screens, and limits may change during the beta. Major changes unfavorable to Members are announced in advance.
  4. Claude Code, GitHub, and the Claude GitHub App are services provided by their respective companies and are subject to each company's terms and the Member's own plan. The Member bears their usage fees (for example, a paid Claude subscription).

Article 7 (Suspension of the Service)

  1. The Operator may temporarily suspend the Service for reasons such as equipment maintenance, outages, or outages of external services (Cloudflare, Anthropic, GitHub), and announces this in advance on the Service screen where possible.
  2. When ending the Service, the Operator announces it on the Service screen and by email starting 30 days in advance, and lets Users download reports during that period. Credits granted free of charge are not refunded, Paid Validations that have been paid for but not yet started are refunded in full, and purchased Fix Orders remain viewable until the Service ends.

Article 8 (Member Sign-up)

  1. A person who wants to sign up applies by entering an email address (ID) and password on the sign-up screen, checking "[Required] I agree to the Terms of Service," and pressing "Sign up." Sign-up is completed when the Operator accepts the application.
  2. Personal information is processed in accordance with the Privacy Policy. Separate consent is not obtained for personal information strictly necessary for sign-up, and the Privacy Policy is shown on the sign-up screen.
  3. Persons under 14 years of age cannot sign up.
  4. The Service does not send email verification messages and uses the email address only as an ID. You must not sign up with another person's email address.

Article 9 (Account Deletion and Loss of Membership)

  1. Members may delete their account at any time with "Delete account" on the account screen. On deletion, the Member is logged out immediately and use stops, and all data, including ideas, reports, and plans, is permanently deleted within 7 days. It disappears from automatic backups after up to 30 days.
  2. On account deletion, remaining Credits are lost, and deleted data cannot be restored. Because payment records are kept separately as required by law, you may still request a refund through the Operator's contact after deleting your account, as long as it is within the period in Article 12. Please download any reports you need before deleting your account.
  3. If you delete only a single Project, it can be restored for 30 days, after which it is permanently deleted.
  4. GitHub repositories created by the Member belong to the Member and are not deleted even when the account is deleted.
  5. If a Member violates Article 16, the Operator may restrict or suspend use in accordance with Article 17.

Article 10 (Notices to Members)

  1. When the Operator notifies a Member, it does so through the email address the Member entered at sign-up or through the Service screen.
  2. Matters to be announced to many Members at once may be posted on the Service screen for 7 days or more in place of individual notice. However, matters that significantly affect Members' rights and obligations are also notified by email.

Article 11 (Free Usage Limits and Credits)

  1. Users who have not signed up may use Quick Check on the home screen for free as many times as shown on the Service screen.
  2. Members may use Full Validation once for free (once per account), and Quick Check 3 times a month for free. Quick Check uses are renewed on the 1st of every month, Korea time. Validations that ended in failure and paid validations are not counted toward the free uses.
  3. Other free scopes, such as the number of One-Page Plan creations and the number of repository creations, and the number of uses remaining, are shown on the Service screen.
  4. To prevent abuse or manage AI costs, the Operator may set an overall daily limit and a daily number of free starts per internet connection. When the daily AI cost cap is reached, new validations and plan creation may be paused for that day, and in that case Paid Validations that have been paid for but not yet started can be started as they are on the next day.
  5. The Operator may grant Credits free of charge. The features that use Credits and the number used are shown on the screen where the feature is started, and Credits are deducted when the feature succeeds to the end and are not deducted if it fails. Credits granted free of charge cannot be exchanged for cash or transferred to another person, and are lost on account deletion. The Operator does not sell Credits for money.

Article 12 (Purchase, Withdrawal of Subscription, and Refunds for Paid Validation and Fix Order)

  1. What you buy: Additional validations after using up the free uses (Article 11) and Virtual Residents Fix Orders are bought one at a time. Prices are stated on the Service screen and in this Article.
    • 1 Quick Check: 1,900 won (KRW)
    • 1 Full Validation: 4,900 won (KRW) (includes the One-Page Plan and Hand-off to Development for that Project)
    • 1 Full Validation continued from a Quick Check result: 2,900 won (KRW)
    • 1 Virtual Residents Fix Order (for one Virtual Residents result): 990 won (KRW)
  2. Payment: Payment is received on the payment screen of Groble (groble.im). Groble provides the payment methods and receipts. The Operator receives only the payment number, product, payment amount, and payment, use, and refund times, and does not receive payment method information such as card numbers.
  3. Where it is used: A purchased validation can be started once in the Project for which it was bought. If a started validation fails because of a problem on the Operator's side, it can be started again with the same payment. A Fix Order is bought for one Virtual Residents result that you have saved to your account while logged in, and once payment is confirmed it is written right away and attached to that result. If the AI cannot write it, a version written by rules is provided, and a purchased Fix Order can be viewed in your account until you delete the Project that contains that result.
  4. Withdrawal of subscription: Within 7 days from the date of payment, you may withdraw your subscription for a validation that has not yet been started and receive a full refund. Because a validation is digital content for which the AI starts producing results as soon as it is started, withdrawal of subscription is restricted after it has started under Article 17(2)5 of the Act on the Consumer Protection in Electronic Commerce, Etc. Because the validation starts as soon as payment is completed, the Operator displays this fact next to the payment button and lets you try it in advance with the free Quick Check. A Fix Order is also digital content that is written and delivered as soon as payment is confirmed, so withdrawal of subscription is restricted after receipt under the same provision, and before payment the Operator shows the impact numbers of the fixes and part of the content for free so that you can check it in advance.
  5. Exceptions: If a started validation did not complete and cannot be completed by starting it again, or if a paid Fix Order is not visible, the Member may request a refund even after receipt. If the result differs from the advertisement or screen description, or was performed differently from the contract, you may withdraw your subscription under Article 17(3) of the same Act within 3 months from the date of receipt, or within 30 days from the date you became aware of that fact.
  6. How refunds work: Refund requests are received at the Operator's email (atlier.skill@gmail.com), and refunds are returned through Groble to the payment method used. The Operator starts the refund process within 3 business days from the date the request is received. Overpayments (amounts charged by mistake) are refunded in full. A refunded Fix Order is no longer visible.
  7. If less than the price was paid, for example with a coupon: The validation does not start right away, and the Operator checks and informs you.

Article 13 (Protection of Personal Information)

  1. The Operator processes only the minimum personal information necessary to provide the Service, and the details follow the Privacy Policy.
  2. Whenever personal information is sent to a third party, such as when creating a GitHub repository at the User's request, the Operator informs the User separately each time and obtains consent.

Article 14 (Obligations of the Operator)

  1. The Operator does not do anything prohibited by law or by these Terms, and makes efforts to provide the Service continuously and stably.
  2. The Operator maintains security measures to protect Users' personal information and User Content.
  3. The Operator does not disclose User Content, use it for promotion, or use it for AI training without the Member's consent.
  4. If an opinion or complaint submitted by a Member is justified, the Operator handles it promptly and informs the Member of the result by email or on the Service screen.

Article 15 (Management of Members' IDs and Passwords)

  1. The recovery code shown once at sign-up is the way to regain access if you forget your password. If you have also lost your recovery code, please contact the Operator. The Operator creates a new code only when it can confirm your identity.
  2. Members manage their own passwords and recovery codes. You must not tell them to others or lend your account, and if you learn that someone else is using your account, please change your password right away and tell the Operator.
  3. The Operator is not responsible for damage caused by a Member's careless management of their password and recovery code. However, this does not apply if the Operator acted intentionally or negligently.

Article 16 (Obligations of Users)

Members and Non-members must not do the following.

  1. Signing up or applying with another person's email address, or using another person's account
  2. Creating multiple accounts or using automation tools to repeatedly use the free limits
  3. Sending mass requests with automation tools or placing excessive load on the Service, or scraping the Service
  4. Entering other people's personal information or trade secrets without permission
  5. Planning or validating an unlawful service (for example, fraud, illegal gambling, unauthorized collection of personal information, or copyright infringement), or using the Service to prepare for one
  6. Trying to bypass the AI's safety measures, or inserting instructions into input to use the Service for purposes other than its intended purpose
  7. Registering an address you have no authority over for operations checks, or using operations checks to attack or monitor other services
  8. Exploiting security vulnerabilities or interfering with the operation of the Service

Article 17 (Restriction and Suspension of Use)

  1. If a Member violates Article 16, the Operator may issue a warning, restrict some features, or suspend use. The Operator does only as much as necessary, considering the severity of the violation and whether it is repeated.
  2. The Operator informs the Member of the reason and period by email in advance. However, if the harm to other Users or the Service is serious and the matter is urgent, the Operator restricts first and informs right away.
  3. Members may raise an objection through the Operator's contact, and the Operator lifts the restriction if the reason is valid.
  4. Even while use is suspended, Members may request account deletion and data deletion through the Operator's contact.

Article 18 (Nature of AI Output)

  1. Validation results, reports, draft plans, titles, operations reports and to-dos, draft promotional posts, and draft store descriptions and review replies are output created by generative AI (Anthropic's Claude), and the Service indicates this on the screen and in downloaded reports.
  2. AI Output is reference material. It may contain content that is untrue or outdated, or sources that do not exist. Members must check numbers, competing services, sources, and legal and tax content themselves, and AI Output is not legal, tax, or investment advice. We recommend checking with a professional before important decisions.
  3. Guidance based on the check questions on the introduction screen is also reference information.
  4. Due to the nature of AI, similar output may be produced for other Members.
  5. Unless the Operator acted intentionally or negligently, the Operator is not responsible for damage resulting from decisions a Member made by relying on AI Output or guidance as is without checking it.
  6. Incorrect or inappropriate AI Output can be reported through "Send feedback" or the Operator's contact.

Article 19 (Copyright and User Content)

  1. User Content and AI Output created from a Member's Project belong to the Member. The Operator does not claim any rights to them.
  2. The Operator uses User Content and AI Output only to the extent necessary to provide the Service (storage, display on screen, AI processing, and uploading to repositories at the Member's request).
  3. Members must enter only content to which they hold the rights.
  4. The rights to the Service itself (screens, text, prompts, and package composition) belong to the Operator. The Atelier skill files included in hand-off repositories are under the MIT License, so Members may freely modify and use them.

Article 20 (Hand-off to Development and GitHub Repositories)

  1. Hand-off to Development proceeds only when the Member personally authorizes the GitHub connection and agrees to the content to be sent to the repository. With the authorized permissions, the Operator does only the following.
    • Creating 1 new repository and uploading the package files
    • Setting up 1 webhook (push notification) on that repository to receive development progress signals. To set up the webhook again from the development tab, the Member must authorize the GitHub connection again.
    • For store apps, if the Member connected GitHub to build an APK: running the APK build workflow in that repository, and checking the run records and result files so the Member can download them. The Operator does not store the APK, and each time it is downloaded, the Operator fetches it from GitHub and passes it on as is. GitHub Actions usage for running the workflow is subject to the Member's GitHub plan.
    Once the repository and webhook are created, the connection is cut immediately, and connections for APK builds and connections that were not finished are kept for up to 1 hour only.
  2. The created repository is in the Member's GitHub account and is owned by the Member. The Operator does not delete or modify the repository other than for the tasks in paragraph 1, and the repository and webhook remain even after account deletion. The Member manages the repository and webhook under GitHub's terms.
  3. The Member chooses the visibility (private by default). If created as a public repository, anyone can see the idea and reports.
  4. After the repository is created, the output the Member builds with Claude Code or other tools, and its operation, are the Member's responsibility.

Article 21 (Operations Check and Operations Management Service)

  1. Members must register only addresses of services that they operate or are authorized to check.
  2. The Service accesses the registered address once every hour (up to once per minute when the Member presses the button) and checks only the response code and response time, without reading the response body. When the Member turns on the operations management service, it checks every 5 minutes, also accesses /health at the same address, reads only up to 64KB of the response body, and uses only the health status and version value.
  3. Check results are reference information. There may be outages between check intervals, or errors that occur only on the Operator's check route, and the Service does not guarantee that it will find every outage.
  4. When the Member turns on the operations management service and puts the connection snippet into their service or app, the Operator receives the usage signals sent by that service (event counts such as visits, sign-ups, and payments) on the Member's behalf, summarizes them as numbers, and uses these numbers to create operations reports, to-dos, and drafts. The Member must disclose this processing in their own service's privacy policy, and the details follow Section 11 of the Privacy Policy.

Article 22 (Launch Notice Applications and Withdrawal)

  1. Entering an email address and agreeing to the collection and use of personal information completes the application for the launch notice. Persons under 14 years of age cannot apply.
  2. You must not apply with another person's email address.
  3. Applicants may withdraw their application at any time through the "Remove me from the list" link in the launch notice email or through the Operator's contact, and on withdrawal the information is deleted without delay.
  4. Processing of application information follows the Privacy Policy.

Article 23 (Damages and Liability)

  1. If the Operator causes damage to a Member intentionally or negligently, the Operator compensates for that damage.
  2. In the following cases, the Operator is not responsible unless it acted intentionally or negligently.
    • When the Service cannot be provided due to natural disasters or equivalent force majeure
    • Outages or policy changes of external services not managed by the Operator (Cloudflare, Anthropic, GitHub, Claude Code, and so on)
    • Damage caused by the Member's fault (violation of the Terms, careless account management, use of unchecked AI Output, and so on)
  3. No provision of these Terms reduces the Operator's liability for its intentional acts or gross negligence, or the liability the Operator must bear under law.
  4. If a Member violates these Terms and causes damage to the Operator or another person, the Member compensates for it.

Article 24 (Dispute Resolution)

  1. If a dispute arises, please first tell the Operator through its contact. The Operator responds promptly from the date of receipt, and if it is difficult to handle right away, informs you of the reason and the handling schedule.
  2. Users may apply for mediation to dispute mediation bodies such as the Korea Consumer Agency (call 1372 with no area code).

Article 25 (Jurisdiction and Governing Law)

  1. These Terms are governed by the laws of the Republic of Korea.
  2. If a lawsuit is necessary, it is brought in the court having jurisdiction under the Civil Procedure Act (민사소송법).

Supplementary Provisions

  1. These Terms apply from November 26, 2026. Until then, the previous Terms of Service (Korean) apply.
  2. Previous Terms can be viewed in the October 20, 2026 version (Korean) and the October 6, 2026 version (Korean).

View the Privacy Policy