This revision (v3.3) takes effect on 17 December 2026. Until then the current policy applies, and version 3.2 also takes effect on 15 December 2026. This text includes the changes in version 3.2. The changes are set out directly below, followed by the full revised text. View the current policy
v3.3 notice — counting reactions without a name
Proposed v3.3 · announced 2026-11-17 · takes effect 2026-12-17 · CELESTRY
We are adding the counting of reactions tapped while reading, without a name, to Section 1. No new personal information is collected. What is stored is which chapter it was, which of the three was chosen and the screen language; it is not linked to an account, a session, a reading number or an IP address. The rest is the same as version 3.2.
The Section 1 table gains one row.
| Category | Items collected | Required or optional | Purpose | Retention |
|---|---|---|---|---|
| Anonymous reaction counts | The reaction you tap while reading (which chapter, which of the three you chose, the screen language) — not linked to an account, session, reading number or IP address | Automatic, in a form that cannot identify anyone | Counting which sentences miss | Three months, as with access logs |
The paragraph below the Section 1 table gains this sentence: "A reaction tapped while reading is counted without a name: only which chapter it was and which of the three was chosen. The count holds no account, session, reading number or IP address, so who tapped it cannot be worked out."
The version history in Section 11 gains this sentence: "This is version 3.3, announced on 17 November 2026 and taking effect on 17 December 2026. It adds the counting of reactions tapped while reading, without a name, to the Section 1 table and the paragraph below it."
Privacy Policy
Proposed v3.3 · announced 2026-11-17 · takes effect 2026-12-17 · CELESTRY
This English version is provided for reference. The Korean version is the binding text; if the two differ, the Korean version governs.
Lama Works (the "Operator") handles personal data in the CELESTRY service as set out below. This policy is written under Article 30 of the Personal Information Protection Act of Korea.
1. Purposes and data collected
| Purpose | Data | Required or optional | Use | Retention |
|---|---|---|---|---|
| Reading generation | Birth date, birth time, birthplace, sex used for the calculation | Required | Generating your reading | Until the validation research ends or you ask for deletion |
| Polishing the wording of readings | The chapter titles and bodies of the reading as the engine wrote them (no birth date, birth time, birthplace, name or contact details are sent) | Required (when a reading is made) | Polishing the sentences so they read more easily | Only the request is sent; the polished text is kept in the Operator's database |
| Research participation | Answers you leave while reading (walk ratings, answers to check questions) | Optional, only when a signed-in account has agreed | Validation research to improve the interpretation sentences | Until the validation research ends or you ask for deletion. If you stop taking part, later answers are not collected |
| Anonymous reaction counts | The reaction you tap while reading (which chapter, which of the three you chose, the screen language) — not linked to an account, session, reading number or IP address | Automatic, in a form that cannot identify anyone | Counting which sentences miss | Three months, as with access logs |
| Launch updates | Email address (typed in, or provided by a Google account) | Optional | Sending launch and development updates | Until you unsubscribe or ask for deletion |
| Account (Google sign-in) | Email address, profile name, profile picture, Google account identifier | Required | Identifying you and signing you in; saving and reopening readings | Until you delete the account |
| Account (Kakao sign-in) | Kakao account email with its verified and valid flags, nickname, profile picture, Kakao member number | Required | As above | Until you delete the account |
| Account (Naver sign-in) | Email address, nickname, profile picture, Naver user identifier | Required | As above | Until you delete the account |
| Account (email sign-up) | Email address, password (stored only as a one-way hash), whether the email address is verified | Required | As above | Until you delete the account |
| Account, all providers | Time of the age-14 confirmation, preferred language, consent records | Required | Legal confirmation, screen language, evidence of consent | Consent records are kept de-identified for the statutory period after deletion |
| Profile | Nationality, place of residence | Optional | Tailoring content | Until you delete the account or ask for deletion |
| Journal and memory (My Place) | Date, title, text and tags of journal entries you write; memories kept automatically from Reflect together conversations (with AI consent) | Optional (with journal storage consent) | Keeping and rereading your journal | Until you delete them or your account |
| Reflect together (AI conversation) | What you write in the conversation and the AI's replies | Optional (with AI consent) | AI replies grounded in your journal | The conversation is not stored; only the memories kept automatically from each conversation remain under "Journal and memory", and you can edit or delete them |
| Orders and payments | Order number, product, amount paid, payment status and time, the payment gateway's transaction identifier, the purchased reading and its reference number | Required (when you buy) | Providing and reopening purchased readings; confirming, canceling and refunding payments; statutory record keeping | Under the Act on Consumer Protection in Electronic Commerce: contract, withdrawal and payment records 5 years; complaint and dispute records 3 years |
| Marketing | Email address, time of marketing consent | Optional | News and new-product announcements (may include advertising) | Until you unsubscribe or delete the account |
| Access logs | Time of access, device and browser type, country-level location, session identifier | Collected automatically | Operating the service, finding errors, usage statistics | 3 months |
Reading data is never linked to a name or contact details. Email addresses are stored separately from reading and research data and are not joined to them. Birth information is never placed in public results or analytics properties. When you create an account, reading data and account data live in separate tables, and the account side holds only a reference number pointing to a reading. Research answers are not stored together with account details. Nothing is collected for research while you are signed out. A reaction tapped while reading is counted without a name: only which chapter it was and which of the three was chosen. The count holds no account, session, reading number or IP address, so who tapped it cannot be worked out.
Card numbers and other payment-method details go directly to the payment gateway; the Operator does not receive them.
2. Transfer of personal data abroad
To run the service, the Operator entrusts data processing to the companies below, which store or process data outside Korea.
The data transferred, the recipient and its contact, the country, the purpose and the retention period are listed in the table below. Transfers take place over the internet: for hosting, while you use the service; for Reflect together, each time you send a message.
If you refuse the transfer for hosting, the service cannot be provided. The transfer to Anthropic happens only if you give AI consent in Reflect together; if you do not, or withdraw it in My Place, nothing is transferred. Only Reflect together is then unavailable; the rest of the service works as before.
The transfer for polishing the wording of readings happens when a reading is made, and once more when the reading is opened if no polished text was kept from that time. What is sent is only the chapter titles and bodies the engine wrote; the birth date, birth time, birthplace, name and contact details are not sent. The polished text is kept in the Operator's database, and a reading whose polished text is kept is not sent again.
This transfer is part of making a reading and cannot be refused on its own. If you would rather not have it, do not make a reading; the rest of the service works as before.
| Recipient (contact) | Country | Data | Purpose | Retention |
|---|---|---|---|---|
| Vercel Inc. (privacy@vercel.com) | United States | Access logs and the input carried in each request | Web hosting and server execution | For as long as the service is provided |
| Anthropic, PBC (privacy@anthropic.com) | United States | What you write in Reflect together, and the name, coordinates, reading findings, recent journal entries and saved memories sent with it | Generating 함께 돌아보기 (Reflect together) replies, only with AI consent | Deleted within 30 days of receipt (up to 2 years if flagged as violating its usage policy) |
| Anthropic, PBC (privacy@anthropic.com) | United States | The chapter titles and bodies of the reading as the engine wrote them. No birth data, name or contact details are sent | Polishing the wording of reading text (free and paid readings) | Deleted within 30 days of receipt (up to 2 years if flagged as violating its usage policy) |
3. Outsourced processing
The Operator entrusts hosting, data storage, payment processing, generating Reflect together replies and polishing the wording of readings to the companies below. The database sits on servers in Seoul, Korea; the company operating it, Supabase Inc., is a US company. When email sending begins, a sending provider will be added and this policy will be updated. Processors are bound by contract to handle personal data safely and are supervised.
| Processor | Company country | Data location | Work entrusted |
|---|---|---|---|
| Vercel Inc. | United States | United States | Web hosting and server execution |
| Supabase Inc. | United States | Seoul, Korea (AWS ap-northeast-2) | Database and sign-in session storage |
| Toss Payments Co., Ltd. | Korea | Korea | Payment processing, cancellation and refunds |
| Anthropic, PBC | United States | United States | Generating Reflect together replies, only with AI consent |
| Anthropic, PBC | United States | United States | Polishing the wording of reading text (free and paid readings) |
4. Provision to third parties
The Operator does not provide personal data to third parties, except where required by law.
5. Deletion procedure and method
Data is deleted without delay when its retention period ends or its purpose is fulfilled. Electronic files are erased in a way that cannot be recovered.
When you delete your account, this is the order: the Kakao or Naver connection is unlinked, sign-in information is deleted, the account's personal data is cleared, the list of saved readings and the profile are deleted, and the Supabase authentication account is deleted. The Kakao member number and the Naver user identifier are also deleted. Consent records and order records are kept in a form that cannot identify you for the period the law requires.
6. Rights of data subjects and legal guardians
Anyone may view, correct, delete and download their personal data. With an account, you do this yourself on the My Info screen. Without an account, or to delete reading data, send a request to the contact below. Requests are handled without delay.
Each consent may be refused. Refusing the reading consent means a reading cannot be generated. Refusing any other consent only disables that feature and carries no other disadvantage.
7. Children under 14
The Operator does not collect personal data from children under 14. Age is confirmed when an account is created. If data from a child under 14 is found to have been collected, it is deleted without delay.
8. Cookies
A session cookie keeps you signed in and a language cookie remembers your screen language. No advertising cookies are used. You can refuse cookies in your browser settings, but you will then not stay signed in.
9. Security measures
All communication is encrypted. The sign-in session is kept only in a cookie that browser scripts cannot read. The database cannot be reached from the browser; only the server accesses it. Access rights are kept to the minimum needed for operation.
10. Privacy officer
Send questions, complaints and requests to exercise your rights to the privacy officer below. You may also report a privacy violation to the Personal Information Infringement Report Center (privacy.kisa.or.kr, 118).
11. Changes to this policy
Changes are announced on this page at least 7 days before they take effect. This is version 3.3, announced on 17 November 2026 and taking effect on 17 December 2026. It adds the counting of reactions tapped while reading, without a name, to the Section 1 table and the paragraph below it. Version 3.2, effective 15 December 2026, added the transfer to an external language model that polishes the wording of readings to the Section 1 table and Sections 2 and 3. It adds the transfer to an external language model for polishing the wording of readings to Sections 1, 2 and 3. Version 3.1, effective 3 November 2026, was announced on 27 October 2026. It splits the row "Reading generation and anonymized research" in the Section 1 table into "Reading generation" and "Research participation". Version 3, effective 29 October 2026, was announced on 21 October 2026 and corrected on 22 October 2026 to say that memories are kept automatically from each conversation rather than only when chosen. Version 2, effective 10 September 2026, did not list what is collected for an account created with an email address, for the journal and memory, for Reflect together, or for orders and payments, and did not name Toss Payments or Anthropic among processors and transfers. Version 1, effective 24 August 2026, had no sections on accounts, transfers abroad, outsourced processing, deletion, rights or the privacy officer.