Privacy Policy

English reference translation. This English version is provided for reference only. The Korean version is the binding version, and if the two versions differ, the Korean version prevails. This policy is effective from November 19, 2026; the provisions on paid payments (Section 1.A(8)) are effective from November 26, 2026.

Atelier Launch (the "Service") is operated by Atelierlaunch (representative: Jung Sung Hun, the "Operator"). In accordance with Article 30 of the Personal Information Protection Act (개인정보 보호법), the Operator establishes this Privacy Policy to protect users' personal information and to handle complaints promptly.

1. Purposes of Processing and Items of Personal Information Processed

A. Personal information processed without consent (conclusion and performance of a contract)

The information below is essential to provide the service when a user signs up or directly uses a feature, so it is processed without consent under Article 15(1)4 of the Personal Information Protection Act (conclusion and performance of a contract, or measures requested by the data subject in the process of concluding a contract). The Operator bears the burden of proving that the information is essential (Article 22(3) of the same Act).

(1) Sign-up and login

ItemPurposeHow collected
Email address (ID), sign-up timeIdentifying members, login, responding to inquiriesSign-up screen, Google or Kakao account login
Google account link information (account number assigned by Google, time linked)Login with a Google accountGoogle account login (if the user chooses it)
Kakao account link information (member number assigned by Kakao, time linked)Login with a Kakao accountKakao account login (if the user chooses it, from November 4, 2026)
Password (only an irreversibly transformed value)LoginSign-up, password recovery
Recovery code (transformed value only), time created, time last usedRecovering access when the password is forgottenSign-up, account screen, password recovery
Login records (session number, time created, expiry time)Keeping you logged in (30 days)Automatically at login
Usage status: time the free full version was used, number of quick checks used, credit grant and usage records, time of account deletion request or suspensionManaging free limits and credits, processing account deletion, responding to abuseAutomatically during use

(2) Idea validation and one-page plan (viewable only by you)

ItemPurposeHow collected
One-line idea (up to 2,000 characters) or area of interest, who it is for, why you want to build it, project title (only the idea is required; the rest only if you want to enter them)Creating AI validation results (problem statement, competitor research, assumptions, business viability, stop criteria, etc.), your project listNew idea screen
"Things to fix" added at each step (up to 500 characters), the idea chosen from candidates suggested by the AIReflecting them in the next step's resultsValidation screen (only if you want to enter them)
Step results generated by the AI, validation report, AI response summary (URLs of web sources consulted, usage)Showing, downloading and revisiting results, handing off to developmentAutomatically during validation
One-page plan (summary, features, screens, tasks for people, costs), the first draft written by the AI, number of revisionsCreating, revising and finalizing the plan, putting it into the development repositoryPlanning screen
Requests for the plan draft (up to 300 characters). Not stored; used only in the AI requestReflecting them in the draftPlanning screen (only if you want to enter them)
Answers to the plan questions (who will use it, the moment they look for it, how they do it now, narrowed target, must-have items, how it makes money, form, deadline, cost, assumptions to check first, requests; if the verdict is "stop", what you want to keep and the changed idea). Personal information patterns are masked and the answers are encrypted when storedTailoring the plan to your situation, continuing to answer laterQuestions on the planning screen (only if you want to answer; all can be skipped)
Experiment records: experiment conditions (hours available per week, whether you can post in communities, names of communities you already use), numbers entered for each task (number of posts and comments found, visits, sign-ups, etc.), sign-up page URL, notes. Community names, URLs and notes are encrypted and visible only to youChoosing the next experiment task on the task screen, showing progress for each assumptionTask screen (only when entered)
Sign-up page: service name, one-sentence description of what it is, description, pain question and three pain lines, three feature lines, price, target, social media URLs for launch news (Instagram, Threads, X, YouTube, Naver Blog and Kakao Open Chat only), theme. Stored encrypted; once published, anyone who knows the page URL can see itPublishing the sign-up page the user created and showing the counts of visits, interest and answersTask screen, validation screen (only when you create one)
If you save a Virtual Residents result: the service URL that was read, the map read from the public page at that URL (content and position of text, buttons, links and input fields), result numbers (average star rating, number of residents who clicked through to the end, number of residents who left on the first screen), time and method of saving. Screenshots are not storedRevisiting past results in your project's Residents tab, comparing how the numbers changed after fixes"Save this result" on the Virtual Residents result screen, "Send them in again" on the Residents tab (only when you click)
If you keep My Resident: answers chosen for 10 questions (age group, type of work, interests, habits when looking at a service), the name you gave itHaving My Resident browse along every time you enter a URL, showing My Resident on the residents' home screen"Keep My Resident" on the Virtual Residents result screen (only when you click)
My Resident's browsing records (if you keep My Resident): URLs of services that other users entered publicly into Virtual Residents and that match its interests, the stars My Resident gave, whether it clicked through to the end, where it left and why, device type, time spent, what it said while browsing and its answers to questions (text generated by the engine). Screenshots and maps are not storedViewing recently browsed places on My Resident pageAutomatically once you keep My Resident (once an hour, and when you open My Resident page)
If you receive My Resident news emails (turned on by default when you keep My Resident): the email address you signed up with, when emails were sent and whether sending succeededSending a summary of places My Resident browsed every Monday morning (not sent in weeks with no browsing), notifying you right away when it clicks through a place to the end (up to one email per day)Automatically when you keep My Resident. You can turn it off anytime with "Stop receiving emails" in the email or the switch on My Resident page

(3) Quick check before sign-up (only when you click start on the home screen, from October 7, 2026)

ItemPurposeHow collected
One-line idea (up to 2,000 characters)Creating the pre-sign-up quick check result (idea summary, problem statement, similar services), moving it to that account's projects upon sign-upHome screen
Quick check result generated by the AI, AI response summary (URLs of web sources consulted, usage)Showing part of the result, revealing all of it upon sign-upAutomatically during the quick check
Preview verification value (transformed value of a token kept only in the browser)Showing the result only in the browser where it was started, moving it after sign-upAutomatically when the quick check starts

(4) Handing off to development (only if you want)

ItemPurposeHow collected
GitHub access token (scope "repo", encrypted, up to 1 hour)Creating one new repository in the user's account and uploading the package files (validation report, plan, roadmap, instructions), attaching a progress-signal webhook to that repository (from October 15, 2026), building and downloading the APK of the store appGranting permission on the GitHub screen after "Connect with GitHub" (also "Reconnect GitHub to turn on" in the Development tab, and "Connect GitHub" for the APK)
GitHub ID (login name)Building the repository URL, showing the connected accountReceived from GitHub with the token above
Repository name, visibility, default branch, commit number, number of files uploaded, progress step, time, error type, answers about prerequisites (paid Claude subscription, whether you have a GitHub account, etc.)Continuing after closing and reopening the window, reopening the created repository, daily creation limitInput on the handoff screen, automatic
Transformed value of the first-instruction URL (prompt_url), time first opened, "I opened it" (web/app)Delivering the first instruction to Claude Code, checking progressAutomatic on the handoff screen
Progress-signal webhook number, signing secret (encrypted), progress records for each checkpoint (checkpoint, status, the one-line summary Claude wrote in the commit message, preview URL, screenshot path (encrypted), commit number, time received) (from October 15, 2026)Showing development progress in the Development tabReceived from GitHub through the repository webhook (not received if no webhook is attached)
"Email me when a check is waiting" on/off (from October 15, 2026)Checkpoint notification emailsDevelopment tab (only when turned on)
Sign-up for "Email me a check-in in 3 days", and the scheduled and actual send timesSending one email reminding you to check the "To-dos this week" in the validation reportReport screen (only if you sign up; off by default)

(5) Operations monitoring and managed service (only if you want)

ItemPurposeHow collected
Service URL entered by the user (only public URLs starting with https)Opening it once an hour (every 5 minutes if the managed service is on) to check whether it is up and how fast it respondsOperations screen
Check results (success or failure, response code, response time, error type, time); for the managed service, also whether /health is OK and its version value; checks on this week's to-dosShowing uptime, recent records and to-dosAutomatic checks, operations screen
Notification method (email on/off) and member email addressSending emails about service outages and recovery, and notices about low credits or suspension of the managed serviceEmail notifications turn on when the managed service is turned on (can be turned off on the operations screen)
Operations summary: the key flow extracted by code from the finalized plan and validation report (up to 5 lines), key assumptions (up to 3), names of key steps. Decision criteria (sign-up rate threshold, number of visits needed for a decision)Basis for operations reports, step names in the connection snippet, numeric verdictsAutomatic. Decision criteria on the operations screen
Daily, weekly and monthly operations reports (numbers for that period, observations and suggestions written by the AI), reactions to reports (👍/👎)Interpreting operations numbers, suggesting what to try nextManaged service, automatically every day (AI)
Daily to-dos (title, reason, text to paste into Claude Code), backup candidates, done / reason for removal (preset options)Showing today's to-dosSame as above, operations screen
Choice of promotion channels, promotional post drafts (AI), date postedDrafts of posts for the chosen channelsOnly when the managed service's promotion feature is turned on, automatically after the daily report (AI)

(6) Store app operations (only if you want, from October 16, 2026)

ItemPurposeHow collected
Minimum and latest versions, Google Play and App Store URLsUpdate notices in the app (the app reads them from a public URL)Operations screen
Store numbers copied in by the user (new installs per week, average star rating, number of ratings, crash rate)Showing the change from the previous weekOperations screen
Store description draft (AI)Helping write the store listing textOperations screen, AI (Anthropic, Section 4)
Pasted review textCreating reply draftsOperations screen, AI. Not stored (phone number and email patterns are masked before being sent to the AI); only the daily count is recorded

(7) Sending feedback (only if you want)

ItemPurposeHow collected
Feedback written by the user (up to 500 characters), feedback type (inconvenience, strange result, feature suggestion, other), type of screen it was sent from (home screen, validation, planning, etc.), member number (only if logged in), time sentChecking inconveniences, improving the serviceThe round "Send feedback" button at the bottom right of every screen (can be sent without signing up)

(8) Paid payments: validation and Fix Order (only when you pay, from November 26, 2026)

ItemPurposeHow collected
Payment number (a random number generated by the Operator), product purchased (quick check, full validation, continue to full version, Fix Order), price and actual amount paid, Groble payment identifier, payment status (before payment, paid, used, refunded), payment, use and refund times, member number. For validation, the project number and the number of the validation started with that payment; for Fix Order, the Virtual Residents result number and the numbers of the selected fix candidatesConfirming payment, starting the purchased validation and using Fix Order, processing refunds, handling disputesThe payment number is created when you click "Pay"; the amount paid, identifier and times are received through a notification signed by Groble when payment is completed

B. Personal information processed without consent (service protection and statistics)

The information below is needed to protect the service from abuse and to fix errors. It is processed under Article 15(1)6 of the Personal Information Protection Act (legitimate interests of the personal information controller), as a case where this interest clearly overrides the user's rights and the processing does not go beyond a reasonable scope.

ItemPurpose
Value of the connecting IP transformed (hashed) in a way that changes daily. When signing up for launch notices, starting a free validation, entering a recovery code, sending feedback before sign-up, or clicking a site or opening a share link counted for the Virtual Residents home screen boardPreventing abuse (launch notice sign-ups 20 per day, free full version 2 per day from the same connection, free quick check 6 per day, beta full version 3 per day, recovery codes 5 per 15 minutes, feedback before sign-up 5 per day, board reactions counted once a day per person)
Transformed value of the member number. When the password is entered incorrectly while creating a new recovery codePreventing abuse (5 per 15 minutes)
Transformed (hashed) value of the email address. When sending email confirmation or password reset emailsPreventing email abuse (5 emails per 24 hours to the same email address)
Connecting IP and request path. For account requests such as login and sign-upPreventing password guessing and sign-up abuse (login 10 per 15 minutes, sign-up 10 per day)
Value of the connecting IP transformed in a way that changes daily, temporary page number, referral source. When visiting the home screen. When opening the Virtual Residents screen, the temporary page number and referral source (only the domain of the referring site, from November 18, 2026), and whether this browser has opened it before and whether it has run a check (yes or no)Estimating visit counts
What the visit analytics tool (PostHog) collects: URLs of screens viewed (with the part after the question mark and share numbers removed), where you came from, time spent, where you clicked and scroll position, screen size and browser type, screen recordings (with all text and input masked), a random number that distinguishes this browser, and the names and option codes of screen events among the usage records above. From November 6, 2026Improving the service by seeing which screens people stay on and which they leave (Section 10)
Usage records (below). Email addresses, idea content, titles, service URLs, repository names and GitHub IDs are not included; for members, only the member numberService improvement, cost management statistics
Service access and error records (Cloudflare processing logs). Passwords and idea content are not recordedChecking errors, security

C. Personal information processed with consent

CategoryItemsPurposeLegal basis
Launch notice sign-up (waitlist)Email address, time of consent (required). Willingness to pay (whether you would like to buy credits (1 credit is about 1,000 won) after launch and continue using the service through development) (optional). Answers to check questions (where you got stuck, development experience, whether you have a paid Claude subscription, whether you have a GitHub account, as preset option codes), referral source (utm) (if you answered the check)Sending service launch notices, deciding features and pricing, service improvement statisticsConsent of the data subject (Article 15(1)1)
Development tab early access sign-upEmail address, time of consent (required). Whether you are currently building a service ("Yes" or "Just starting") (optional). Referral source (utm)Sending development tab early access invitation emails, trial guidance and feedback requests, and free pass notice emailsConsent of the data subject (Article 15(1)1)
"Make My Resident" opening notice sign-upEmail address, time of consent (required). Answer chosen in the window ("Notify me when it opens" or "I'm interested"), referral source (utm)Sending one email announcing that "Make My Resident" has openedConsent of the data subject (Article 15(1)1)
GitHub repository creationTable in Section 3Creating a repository in the user's own GitHub accountConsent of the data subject (Article 17(1)1, Article 28-8(1)1)

D. Information not processed

We do not receive real names, phone numbers, unique identifiers such as resident registration numbers, sensitive information, payment information, location information, GitHub passwords or secrets of the user's service. Therefore there is no possibility of sensitive information being disclosed. We also do not process pseudonymized information.

2. Processing and Retention Periods of Personal Information

InformationRetention period
Member information (email address, sign-up time, password and recovery code (transformed values), usage status, credit records)Until account deletion. When you delete your account, use stops immediately and you are logged out, and shared URLs and sign-up pages are also closed right away. For 6 days you can log in again to undo the deletion; after that, the data is permanently deleted by the cleanup job (within 7 days at the latest)
Login records (sessions)30 days (extended once a day while in use). Ended on logout, password recovery or account deletion
Pre-sign-up quick check (idea, result, preview verification value)24 hours. If you do not sign up, the hourly cleanup job deletes it (within 25 hours at the latest). If you sign up, it is moved to that account's projects and follows the row below
Ideas, step results, reports, plans, plan question answers, experiment records, sign-up pages (content and counts by date), development progress records, saved Virtual Residents resultsUntil the member deletes them. When you delete a project, you can restore it for 30 days, after which it is permanently deleted. If you delete your account, deleted within 7 days
Kept My Resident (answers chosen for the questions, name)Until the member deletes their account. If you delete your account, deleted within 7 days
My Resident's browsing recordsUntil the member deletes their account (up to 200 records per person; beyond that, the oldest are deleted first). If you delete your account, deleted within 7 days
IP transformed value for counting sign-up page visits once a dayTwo days. Deleted by the daily cleanup job (within three days at the latest)
AI response summary (URLs of web sources consulted, usage)Cleared 30 days after the step ends (the report remains)
Plan creation count records (for the daily limit)2 days
GitHub access token (encrypted)Up to 1 hour. Deleted immediately and revoked on GitHub once the repository and webhook are created. Connections for building APKs and unfinished connections are deleted and revoked by the hourly cleanup job after 1 hour. Deleted immediately on account deletion
GitHub connection verification value (state, transformed value)Cannot be used after 10 minutes; deleted by the hourly cleanup job
First-instruction URL (prompt_url, transformed value)Stops opening after 7 days and is deleted in the next cleanup job. Deleted immediately on account deletion
Handoff records (GitHub ID, repository name, visibility, commit number, step)Same as the project. Deleted 30 days after the project is deleted, or within 7 days of account deletion (the repository itself on GitHub belongs to the user and is not deleted)
Repository creation count records (for the daily limit, without repository names)2 days
Operations monitoring URL, last check result (including the /health version value), notification methodUntil disconnected (check records are also deleted immediately on disconnection). Deleted 30 days after the project is deleted, or within 7 days of account deletion
This week's to-do checksSame as the project. Deleted 30 days after the project is deleted, or within 7 days of account deletion
Operations summary, decision criteriaSame as the project (kept even after disconnection). Deleted 30 days after the project is deleted, or within 7 days of account deletion
Operations reports (numbers, AI text, reactions), choice of promotion channels and promotional post draftsUntil disconnected (no separately set period; deleted immediately on disconnection). Deleted 30 days after the project is deleted, or within 7 days of account deletion
Sign-up for the check-in email in 3 daysDeleted 30 days after the scheduled send time (deleted immediately if turned off before sending). Also deleted 30 days after the project is deleted, or within 7 days of account deletion
Daily to-dosTo-dos completed, removed or replaced: 90 days from that day; unused backup candidates: 14 days from the day they were created. To-dos still open: until disconnected. Deleted immediately on disconnection, 30 days after the project is deleted, or within 7 days of account deletion
Individual check results (failed checks, results of checks run manually)7 days. Deleted immediately on disconnection
Outage records (status changes), notification records, daily uptime numbers13 months. Deleted immediately on disconnection
Store numbers, description drafts, version settingsUntil disconnected (deleted immediately on disconnection). Deleted 30 days after the project is deleted, or within 7 days of account deletion
Review reply draft count records (without text)2 days
Feedback content1 year. On account deletion, the member number is deleted so that the sender cannot be identified
Waitlist information (email address, time of consent, willingness to pay, check answers, referral source)6 months after the launch notice is sent. If the notice has not yet been sent, 1 year from the sign-up date. Without delay if you click the "Remove me from the list" link in the launch notice email or request withdrawal
Early access sign-up information (email address, time of consent, whether you have a service, referral source)6 months from the sign-up date. Without delay if you request withdrawal
"Make My Resident" opening notice sign-up information (email address, time of consent, chosen answer, referral source)1 year from the sign-up date. Once the notice is sent, 30 days after that. Without delay if you request withdrawal
Domains on the Virtual Residents village board (without the path or anything after the question mark)30 days from the last day it was entered publicly. Daily reaction counts used for the board ranking (numbers only) are kept for 8 days
Abuse-prevention transformed values (IP, member number, email address)24 hours
Login and sign-up request count records (including IP)1 day after the last request
Visit count estimation hashesDeleted after being aggregated into the next day's visit count (a number) (around 24 hours)
Daily usage signal numbers (Section 11)13 months. Deleted immediately on disconnection
Daily transformed values of web visits and app install numbers (Section 11)Deleted after being aggregated into numbers the next day (around 24 hours)
Usage records (statistics)3 years from the date recorded. On account deletion, the member number is deleted so that it cannot be identified whose record it is
Operator admin records (credit grants and withdrawals, suspensions, recovery code reissues; member number and type of action only)3 years (numbers of members who deleted their accounts are not linked to other information)
Paid payment records: validation and Fix Order (Section 1.A(8))5 years (Article 6 of the Enforcement Decree of the Act on the Consumer Protection in Electronic Commerce (전자상거래 등에서의 소비자보호에 관한 법률)). Kept separately for this period even if you delete your account or project, and deleted by the cleanup job after the period ends
Processing logs (Cloudflare)7 days
Backups (Cloudflare D1 automatic restore points)Deleted information remains in automatic backups for up to 30 days and then disappears
Retention by processors (Anthropic, email delivery provider)Section 5

The information preserved separately under law is the paid payment records (validation and Fix Order). They are preserved under Article 6 of the Act on the Consumer Protection in Electronic Commerce and Article 6 of its Enforcement Decree (records on payment and on the supply of goods, etc., 5 years), and during that period they are used only to confirm payments, process refunds, handle disputes and comply with legal obligations.

3. Provision of Personal Information to Third Parties

The Operator processes personal information only within the purposes stated in Section 1 and does not provide it to third parties except in the following cases.

The entrustment of processing in Section 4 means work is assigned on the Operator's behalf, and the recipients do not use the information for their own purposes, so it is not provision to a third party.

Provision at the user's request: GitHub repository creation (handing off to development)

RecipientPurposeItemsRecipient's retention period
GitHub, Inc. (United States). The user's own GitHub accountCreating the new repository requested by the user and uploading the package filesProject title, one-line idea, target, validation report, finalized plan, roadmap, instruction files. Repository name and visibility (private by default)Until the user deletes the repository on GitHub (subject to GitHub's terms and privacy policy)

4. Entrustment of Personal Information Processing

The Operator entrusts the following tasks to others in order to provide the service. Processors use personal information only for the entrusted tasks and not for their own purposes. Personal information protection obligations are set out in the entrustment contracts (each company's data processing terms).

ProcessorEntrusted tasks
Cloudflare, Inc.Operating the web service (hosting), database storage, processing logs and backups, relaying AI requests, name resolution (DNS lookup) for operations monitoring URLs
Anthropic, PBCAI processing (Claude API) that creates idea validation results, plan drafts, operations reports and to-dos, promotional post drafts, store description and review reply drafts, and Virtual Residents Fix Orders; web search for competitor research
PostHog, Inc.Visit analytics: which screens people stay on and leave, screen recordings (text and input are masked). Email addresses, member numbers, ideas and IPs are not sent
Waffle (waffleweb.co)Ad display and visit analytics on the Virtual Residents screen (Section 10). Service URLs, result content, email addresses and member numbers are not sent
Plus Five Five, Inc. (Resend)Sending email confirmation emails, password reset emails (when requested), checkpoint notification emails, report check-in emails after 3 days (once, if you signed up), pre-sign-up result link emails (when requested), operations outage and recovery notification emails, managed service low-credit and suspension notice emails, and My Resident news emails (if you receive them)

5. Overseas Transfer of Personal Information

A. Overseas transfer for entrusted processing and storage

To conclude and perform the contract for providing the service, personal information is entrusted for processing and stored overseas as follows (Article 28-8(1)3 of the Personal Information Protection Act, disclosed in this policy).

Recipient (contact)Country of transferItems transferredWhen and how transferredPurpose of useRetention period
Cloudflare, Inc. (sar@cloudflare.com)US corporation. Requests are processed at the Cloudflare data center near the user, and the database is stored in a data center in a region determined by Cloudflare. AI requests are passed on to Anthropic through a data center in the eastern United States (relayed only, not stored)All items in Section 1Sent over an encrypted network each time the service is usedHosting, storage, logs, backups, relaying AI requestsSame as Section 2
Anthropic, PBC (privacy@anthropic.com)United StatesIdea (or area of interest), target, reason, chosen candidate, things to fix, requests for the plan and answers to the plan questions (after personal information patterns are masked, sent together when the plan is created), previous step results, validation report, idea entered in the pre-sign-up quick check. Managed service operations reports and to-dos: usage numbers by period (visits, page views, sign-ups, logins, number of payments and total amount, numbers of feedback items, errors and key steps, counts by top referring places (domains), tracking tags and most-viewed paths, number of app opens, uptime and number of outages, store numbers entered by the user), operations summary (key flow, assumptions, step names), one line from the previous report and its reaction, titles and reasons of removed to-dos. Promotional post drafts: numbers for the past 7 days (visits, sign-ups, payments, number of feedback items), first 3 lines of the operations summary, recent drafts. Store description drafts: project title, plan summary (or the one-line idea if there is none), target, feature list (up to 6), search keyword candidates and names of other apps from the validation report, name and subtitle of recent drafts (after personal information patterns are masked). Review reply drafts: pasted review text (after personal information patterns are masked). Virtual Residents Fix Order (if purchased): the text of each section of that service's public page (up to 1,000 characters per section, after personal information patterns are masked) and the names of the chosen fixes. Email addresses, passwords and member numbers are not sentEach time a validation step or plan draft is created (once validation starts, the remaining steps run in order, and the server continues even if you close the screen; when you click "Next" or "Create"; for the quick check, when you click start on the home screen; for the first text of a sign-up page, once per project when it is first created, with the validation report sent). Operations reports and promotion drafts are created automatically by the server every day after 9 a.m. (Korea time) while the managed service is on; store description and review reply drafts when the user clicks create. Fix Order once, when payment is confirmed. All sent over an encrypted network (HTTPS, Anthropic API)Generating AI results, web search for competitor researchDeleted within 30 days of receipt (up to 2 years if flagged as a policy violation)
Plus Five Five, Inc. (Resend, support@resend.com)United StatesRecipient email address, email subject and body (email confirmation link, password reset link, checkpoint name and link, report to-do check-in notice and link (idea and to-do content are not included), pre-sign-up result link (idea and result content are not included), outage and recovery notification content (service URL, outage type, possible causes, diagnostic text), low-credit and suspension notices, My Resident news (My Resident's name, age group and occupation, URLs of services browsed, stars, where it left and why, what it said))Sent over an encrypted network each time an email is sentSending emailsThe retention period of sending records follows Resend's privacy policy
PostHog, Inc. (privacy@posthog.com)Germany (PostHog EU Cloud, Frankfurt)Visit analytics items in Section 1.B. Email addresses, member numbers, idea content and IP addresses are not sentSent directly by the user's browser over an encrypted network each time a screen is viewedVisit analytics (service improvement)Screen recordings 30 days; other visit records follow PostHog's retention policy. If the Operator stops using the tool, the project is deleted and the data is deleted with it

How to refuse and consequences

B. Overseas transfer based on user consent (GitHub)

GitHub repository creation in Section 3 sends information to GitHub, Inc. in the United States, so separate consent is obtained before the repository is created, under Article 28-8(1)1 of the Personal Information Protection Act.

C. Information sent directly by the user's browser (external fonts)

All screens load the font (Pretendard) from jsDelivr (cdn.jsdelivr.net). At that time, the user's browser sends the connecting IP address, browser information and the address (domain) of the page visited directly to jsDelivr and its CDN providers. jsDelivr processes this information under its own policy, and the Operator does not receive it.

6. Procedures and Methods for Destroying Personal Information

7. Rights and Obligations of Data Subjects and Legal Representatives, and How to Exercise Them

8. Measures to Ensure the Security of Personal Information

9. Installation, Operation and Refusal of Devices that Automatically Collect Personal Information (Cookies, etc.)

10. Behavioral Information

From November 18, 2026, one ad slot from Waffle (waffleweb.co) is placed at the very bottom of the result screen on the Virtual Residents screen (atelierlaunch.kr/residents). The Waffle code on this screen sends Waffle the screen path (the result number after the question mark is not sent), the domain of the referring site, whether the device is a mobile phone, whether it is a return visit, time spent, and whether the ad was shown and clicked. Service URLs, result content, names, email addresses and member numbers are not sent. Waffle states that it uses the connecting IP and device information only as an anonymous key mixed with the date and does not store them (Waffle code documentation, checked November 18, 2026). When there is no Waffle ad, partner ads such as Kakao AdFit appear inside a separate window (iframe) at Waffle's address, and those ad companies may show personalized ads under their own policies. If you do not want ads, you can block them with your browser's ad-blocking feature, and there is no disadvantage in using the service. No ad tools are used on any other screen. The visit analytics tool for service improvement (PostHog, EU servers) has been used since November 6, 2026. The items collected are listed in Section 1.B, overseas transfer and how to refuse in Section 5, and browser storage in Section 9. All text and input are masked before sending, and information that identifies people (email address, member number) and IP addresses are not sent. Visit counts themselves are also counted on the server using the transformed values in Section 1.B.

11. Information the Operator Processes on Behalf of Users (usage signals of users' services, from October 16, 2026)

When a user turns on the managed service in the Operations tab and puts the connection snippet into their own service or app, the Operator receives usage signals from the people who use that service (the "end users") on behalf of the user and organizes them into numbers. The party responsible for this processing (the personal information controller) is the user who runs that service, and the Operator is the party entrusted with the processing (the processor). Users must describe this processing in their own service's privacy policy and in the store's privacy disclosures (the connection snippet explains this).

ItemPurposeHow collected
Event name (visit, sign-up, login, payment, feedback, error, key step, app open, opened from notification), cleaned path (numbers and IDs removed), referring domain, tracking tags, payment amount (number only), timeShowing the user the numbers of visits, sign-ups and key stepsSignals sent by end users' browsers, apps and servers
Web: IP address (first 64 bits for IPv6), browser information, daily transformed value (hash) made with the dateCounting daily unique visitsSame as above. Original IPs are not stored
App: app version numberShare by version, update noticesSent by the app
App: daily transformed value (hash) made from a random install number created when the app is first launchedCounting daily unique usersSent by the app. Original install numbers are not stored. Not linked to advertising IDs, device IDs or accounts

12. Privacy Officer and Complaint Handling

13. Remedies for Infringement of Data Subjects' Rights

You can report personal information infringement and get counseling from the agencies below.

14. Changes to the Privacy Policy

Effective date: This policy applies from November 19, 2026. The provisions on paid payments (Section 1.A(8)) apply from November 26, 2026.

View the Terms of Service