Privacy Policy

1. What we process, why, on what basis and for how long

Paid detailed results (analysis details and content) are deleted 12 months after payment confirmation, but the payment and contract record is kept separately for 5 years as the law requires. That record contains no date, time or place of birth, no name and no analysis content.

Periods in the table whose basis is a law (payment and contract records, enquiry and dispute records, advertising records) are required by that law; the other periods (free and paid results, share cards and so on) are the Company's own policy.

If the Company advertises, records of its advertising are kept for 6 months as required by law.

The Company never receives or stores card numbers or other payment-method details; the payment providers process them directly.

On the web we do not collect your own date of birth, your country or any ID, and the date of birth entered for a reading belongs to the person being read, so it is never used to determine your age. Section 13 describes the one case where an app member's date of birth, taken from the result they mark as their own, is used to check age for features limited to people aged 19 or older.

If you enter another person's details, you are responsible for having the authority to do so (section 3 of the Terms of Service).

The web has no accounts, so a result made on the web has no owner. Knowing a result's address (link), receiving a share link, buying the result or verifying an email address does not make you its owner. Saving by email gives you the right to find a result again and buying gives you the right to open its paid content, nothing more. The web neither receives nor stores any secret used to prove ownership of a result.

2. How information is deleted

Why a result is kept, and for how long:

• A result made without signing in (on the web, or in the app as a guest) with no email save, purchase or account owner: 48 hours from creation. Looking up its address, opening a share link or another person saving it to their list does not extend this.
• A result saved by email: 2 years from the last time it was saved by email. Looking it up again by email does not extend it, and saving by email is the right to find a result again, not ownership.
• A purchased result: 12 months from payment confirmation. If the Company confirms a full refund, the right to open it ends at that point even before the 12 months are up. Looking it up by email does not extend it, and buying is not ownership. The payment and contract record (5 years) and the consumer complaint and dispute record (3 years) are separate statutory periods with different purposes.
• (Once the app member service has started) A result made by an app member: kept without a time limit while the account is active or deactivated, and deleted when the owner deletes it permanently or deletes the account (sections 12 to 14).
• A result with no owner, no valid purchase and no email save returns to the first rule; if that period has already passed, the next cleanup run deletes it. It is not kept just because someone still has it in their saved list.

Information whose retention period has ended is deleted from the database by a cleanup job that runs once a day. If a run fails, the next run retries, so deletion can happen a few days after the period ends rather than immediately. A result with a payment still being confirmed may be kept up to 7 more days to complete that confirmation.

A payment and contract record is deleted after its retention period, once its result has already been deleted. Email links for result saving and purchases are deleted by the next cleanup after their result is deleted (with the buyer-identity exception in the table), and an email address with no remaining purpose (such as a valid opt-in to updates) is deleted.

Deleted information may remain in the database provider's backups for their retention period and disappears from backups after that.

Information in the app member service is kept for the periods in section 13 and, when you delete your account, deleted as described in section 14.

Usage statistics (PostHog) and the analytics information stored in your browser are kept and deleted as described in section 7 and the table in section 6.

Records of enquiries, refunds and disputes are kept in the support mailbox and the payment provider's console and deleted by an operator once their retention period ends. Records the payment, email and hosting providers keep themselves follow those providers' own policies; the Company cannot delete them directly.

3. Disclosure to third parties

The Company does not give personal information to third parties, except where required by law.

What passes between us and the Google, Apple and Kakao sign-in providers is described in section 12. The Company does not give these companies your personal information; it receives what you authorize and consent to at that company. The requests we send when an account is deleted or a sign-in method is disconnected are also described in section 12.

4. Service providers in Korea

The Company uses the following providers in Korea for payments.

5. International transfers

Hosting, the database, email delivery, generating replies if the AI conversation is offered and, if you allow it, usage analytics are provided from outside Korea, so personal information is processed and stored abroad as follows.

If you do not want your information transferred abroad, you can stop using the Service or ask us at support@jebub.com to delete it. The Service cannot be provided without the hosting, database and email providers, so its use will be limited. Nothing is sent to OpenAI unless you use the AI conversation, and not using it limits nothing else. Declining or withdrawing usage statistics (PostHog) does not limit the Service in any way (section 7).

Google, Apple and Kakao are sign-in services you authenticate with directly; they are not providers the Company entrusts with processing, so they are not in the table above. What our server sends to their servers is described in section 12.

City-of-birth search uses the GeoNames place data (CC BY 4.0) bundled with the Service; your searches are not sent to GeoNames. Fonts and icons are bundled too and make no outside requests.

6. Cookies and browser storage

We use no advertising cookies and no advertising trackers. The analytics tool (PostHog) is used only if you allow it; it sets no cookies and uses only the browser storage in the table above. Before you allow it, none of the "only if you allow it" entries is created and nothing is sent to PostHog.

7. Usage statistics (PostHog)

To understand feature use and where people drop off, analyse errors and conversions and improve the Service, the Company sends anonymous usage statistics to PostHog, Inc.'s analytics service (PostHog Cloud EU region) — only if you allow it. Allowing it is optional: if you do not, you can use everything (readings, payments, saving results) exactly the same way.

• Before you allow it, no analytics ID or analytics storage is created, the analytics tool is not loaded and nothing is sent to PostHog. What you did before allowing it is not sent later.
• What is sent: the "Usage statistics" row of the table in section 1.
• What is never sent: the details you enter for a reading (name or nickname, date, time and place of birth), email addresses or any transform of them (hashes), result, share or recovery links or their identifiers, payment IDs, result content, or anything typed into a field. We do not use session recording (replay), automatic click capture, heatmaps, surveys or feature flags, and no per-person profiles are created.
• Events the server confirms, such as a verified payment, are sent only for requests from a browser that allowed it, under the same anonymous analytics ID. Payments of people who did not allow it, and payments confirmed by a scheduled job without a browser request, are not sent to PostHog.
• IP address: when your browser or our server sends data to PostHog, the connecting IP address reaches PostHog as part of the connection. The Company sets the PostHog project not to store IP addresses with events, turns off IP-based location lookup (GeoIP) and asks for no location lookup on every event. According to PostHog, even with IP storage turned off the IP address may be used briefly before storage (for example to detect automated traffic).
• How long: data sent to PostHog is kept for at most 12 months from collection. Analytics information stored in your browser is kept as shown in the table in section 6.
• Declining and withdrawing: press "Decline" in the notice at the bottom of the screen, or withdraw at any time with the setting below. Withdrawing stops collection immediately, without a reload, and deletes the analytics information stored in this browser (the "only if you allow it" entries in section 6). Information the Service needs, such as your language and input drafts, is kept.
• Deleting data already sent: withdrawing stops future collection; it does not automatically delete data already sent to PostHog. To have it deleted, send the anonymous analytics ID shown in the setting below (it is still shown right after you withdraw) to support@jebub.com. Apart from that ID the Company cannot tell whose data in PostHog is whose, so without it we cannot find the data to delete. When we receive a request we delete that ID's data in PostHog; the deletion can take some time to complete on PostHog's side.
• Record of your choice: your choice and its time are stored only in this browser (table in section 6) and never sent to our server or to PostHog. It lasts 12 months, after which we ask again. Other browsers and devices are asked separately.

8. Operational logs

To investigate payment problems, server logs record only coarse categories: payment ID, product, language and browser family (for example Samsung Internet, Chrome, or whether it is an in-app browser). The full browser string (User-Agent), email addresses, dates of birth and result content are never logged. Logs are kept for the hosting provider's log retention period.

Logs of app member sign-in, code and account-deletion handling record only categories such as the outcome, step, number of attempts, platform and failure category. Email addresses, codes, sign-in tokens and sign-in provider identifiers are never logged.

9. Your rights and how to use them

You can ask to access, correct or delete your personal information, ask us to stop processing it, withdraw your opt-in to update emails and your consent to usage statistics, and ask us to withdraw a share link. A legal guardian or an authorized representative may also ask; we may then ask for proof of that authority.

• How: email support@jebub.com with what you are asking for (access, correction, deletion, stopping processing, withdrawing the opt-in, withdrawing a share).
• Requests about a web result: the web has no accounts, so include that result's link. Only people with the link can open a result, and without it we cannot tell which result you mean.
• Requests about an app member account (once the app member service has started): in the app settings you can add or disconnect sign-in methods, deactivate or delete your account (section 14) and, if the AI conversation is offered, delete your conversations and memories yourself and withdraw your memory consent. mykobi.io/account-deletion, which opens together with the app member service, lets you delete without the app (the address cannot be used before then). For access, correction or stopping processing, email support@jebub.com. Because an account is found through an irreversibly transformed form of its email address, we process the request after checking that you can use the email address of the account, for example with a code. Only the owner of a result can delete it permanently; if you saved a result that someone else owns, you can only remove it from your own list.
• Requests about information linked to an email address (saved results, purchases, opt-in): handled only when sent from that address, or when you reply to a confirmation we send to it. Links for an access request are sent only to that address.
• We never show or delete someone else's result just because a request names their email address. A deletion request by email withdraws the access and recovery path of purchases made with that address, the result links saved with it, and its contact and opt-in; it does not delete a result itself. Knowing an address, a purchase or a result link does not show that a result is yours, and deleting a result on that basis could delete someone else's.
• Deleting a whole result: a result made by an app member is deleted when the account that owns it deletes it permanently in the app or deletes the account. A result made without an account is deleted automatically when its retention period ends; to remove it earlier, email support@jebub.com. A result link alone does not prove who you are, so staff handle it through a restricted procedure only after an additional check, and even then a result owned by an app account is not deleted and no ownership is created. Deleting a result removes that result, the compatibility results made from it, their share links (withdrawn first, then deleted) and the linked email information. A compatibility result in which the same person's details were typed in again by hand cannot be identified and is not included. Payment and contract records stay for their legal period (without analysis details or content).
• Usage statistics: you can withdraw consent directly with the setting in section 7. Requests to access or delete data already sent to PostHog need the anonymous analytics ID described in section 7.
• We act on the request after checking, within the period set by applicable law, and tell you the outcome. Payment and contract records that the law requires us to keep may not be deleted during that period; we will tell you if so.

KOBI does not currently send update (marketing) emails. You can withdraw your opt-in as described above; withdrawing does not affect functional emails such as result-save and purchase links. You can opt in again at any time.

If you lose the link to a purchased result, you can get it again at Recover purchased results with the email address you paid with.

10. People under 16

The Service is not intended for people under 16. If we learn that information about someone under 16 has been processed, or a legal guardian asks us, we delete it, except records the law requires us to keep.

There is no way for someone under 16 to use the Service with a legal guardian's consent. Paid purchases and features limited to people aged 19 or older (if a meeting feature is offered) are only for people aged 19 or older. Whether you are 16 or older is decided by your own confirmation; features limited to 19+ are checked with the date of birth of the result an app member links as their own (section 13).

11. Security

• All traffic is encrypted (HTTPS).
• Results open only through hard-to-guess unique links, and result, purchase and recovery pages are kept out of search engines.
• Abuse-prevention records store IP and email addresses only in an irreversibly transformed form.
• Secret keys for the database and the payment and email services are used only on the server.
• Usage statistics are sent only if you allow it, and code checks that only the predefined items are sent and that nothing that looks like personal information is.
• An app member's email address, emailed code and sign-in tokens are stored only after conversion with separate secret keys, and the member features stay off if those keys are missing or identical.
• A code can be entered at most five times within ten minutes and cannot be reused.
• Requests to the AI conversation do not carry your email address or sign-in data.

12. App member accounts and sign-in

This section and sections 13 and 14 apply from the day a version of the KOBI mobile app with member sign-in is released. Before then the information described here is not processed, and sign-in, account deletion and the deletion page (mykobi.io/account-deletion) are not offered. The web service stays available without an account.

The Company creates an app member account so that it can recognize you in the app, keep you signed in, and let you continue personal features such as linking your own result, the AI conversation and today's reading when you change devices. The account is created the first time you sign in with one of the methods below.

• Emailed code: you enter your email address, we email a 6-digit code (sent through Resend, section 5), and you sign in by entering it. The code is valid for 10 minutes only, can be used once, and becomes void after 5 wrong entries. We do not store the email address or the code themselves, only irreversibly transformed values.
• Google sign-in: you choose and authenticate your Google account directly with Google. From the signed confirmation Google returns, we read the unique number of the Google account and, if there is a verified email address, that address. The email address is used only to find the account for the same email and is not stored as such; your name and profile photo are not stored.
• Apple sign-in (iOS): only the email scope is requested; your name is not. If you choose "Hide My Email", you receive an Apple relay address; you can then verify your real email address with a code to connect to an existing account, or continue with the relay address.
• Kakao sign-in: we check the unique number received from Kakao login. Our server reads the email from Kakao with your access token and uses it only if it is valid and verified; other items such as nickname and profile are not requested. If you did not consent to share your email or it is not verified, you confirm it with an emailed code.

The same verified email address is one KOBI account, whichever sign-in method you use. For example, if someone who signed up with email later signs in with the Google account of the same email, the method is added to the same account. To do this, the Company finds an existing account through an irreversibly transformed form of the verified email address. If a sign-in provider gives no email address, or it is not verified, you confirm it first with an emailed code. Different accounts are never merged. You can add or disconnect sign-in methods in the app settings; the last method cannot be disconnected.

Google, Apple and Kakao are sign-in providers that you choose and authenticate with yourself. The sign-in components in the app (SDKs) talk to each company directly from your device. The Company does not entrust these companies with processing your personal information; it only receives what you authenticate and consent to at that company. How they process that information follows each company's own privacy policy. Our server sends requests to their servers in only two cases.

• Sign-in checks: from Google and Apple we only download the public keys used to verify signatures and send no information about you. To Kakao we send your access token from the login to look up token information and the Kakao account information.
• Account deletion or disconnecting a sign-in method: to Apple we send a disconnect (revoke) request with the authorization code or token Apple issued, and to Kakao an unlink request with your Kakao member number. No other information such as your name, email address or results is sent. We send Google no disconnect request; you can remove the app's access in your Google account settings.

If you disconnect KOBI in your Apple settings or delete your Apple account, Apple notifies the Company and we end that sign-in (if you deleted the Apple account and have no other sign-in method, the KOBI account is deleted too).

Owning a result, saving it, buying it and saving it by email are different things.

• Owning: only the account that made a result while signed in, or that saved a result made in the app without signing in by using the one-time confirmation value the app received when the result was created ("Save to my account"), owns it. Only the owner can delete a result permanently.
• Saved results: saving another person's result to your list lets you view it and remove it from your list. You cannot delete it permanently, and it never extends how long the result is kept.
• Knowing or receiving a result address (link) or a share link, buying a result and verifying an email address do not make you the owner. A purchase gives the right to open the paid content; saving by email gives the right to find the result again.
• A result made on the web has no owner, and the web does not receive or store such a confirmation value. Moving a result made on the web into an account is not offered; it will be offered only after a safe method exists and this policy has been revised.
• When the owner deletes a result permanently, everyone's saved links to it, its share links, the right to open its paid content and its email recovery routes disappear with it.

13. What the app member service processes and how long it is kept

This information is processed only after the app member service has started. Personal features such as the AI conversation and today's reading are switched on separately from the app member service; until they are on, that information is not processed and nothing is sent to OpenAI. Memory is created and read only with your consent; you can withdraw it at any time in the app, and withdrawing deletes all memories.

If the AI conversation is offered, what you send in it is transmitted to OpenAI to produce replies (section 5). We recommend not entering sensitive information such as health, religion or political opinions, or other people's personal information.

The app does not ask for location, photo, camera or contacts permissions and does not collect such information (the app as it is when this policy is published). Push notifications, member-to-member meetings (profile, photo and region display, interest, chat, blocking and reporting) and photo or region display are features that are not offered yet. Before they are offered, this policy will be revised and announced to add the items processed, the recipients, the retention periods (including for reports and safety records) and any permissions and consents needed.

14. Deactivating or deleting an account, and records kept by law

When you delete your account, the following is deleted and cannot be recovered.

• AI conversations (messages, summaries, event notes) and memories, the context links used for conversations, requests in progress, and the transformed values that stop something you asked to be forgotten from being used again
• Every result you own (your own, someone you know and compatibility results, detailed results you bought included) with its analysis input and content, its public share links, other people's saved links to it, the right to open it and its email recovery routes. Please check what you need before deleting.
• The right to open, and the recovery route for, purchases made with the account's email address (if you bought a result that someone else owns, that result stays but this account's purchase access to it disappears), and the contact information for that email address used for result-save and purchase links (an opt-in to updates included)
• Account information, identifiers of sign-in methods, sign-in sessions and app installation data, notifications, device push information, today's readings, the date of birth and gender used for the age check, and the confirmation records

A result that someone else owns is not deleted. Only your saved link to it disappears, and the result stays under its owner's rules. The same is true if you only remove it from your list without deleting the account.

A share link stops opening the moment its result is deleted, and the withdrawn share record is deleted by the cleanup job that runs once a day, within 24 hours at the most. If an AI request had already gone to the AI provider after deletion started, the reply and memories are not stored, and only a cost record not linked to a person is kept, as described below.

Deletion starts as soon as you request it. If a deletion run stops because of an error, the cleanup job that runs once a day runs it again automatically. Deleted information may remain in the database backups described in section 2 until their retention period ends.

The records kept separately from the account because the law requires it are the following.

• Payment and contract records: the items listed as "Payment and contract records" in the table in section 1 (payment ID, product, amount, payment status and time, buyer email address and so on) are kept for 5 years from the transaction (Article 6 of the Act on the Consumer Protection in Electronic Commerce and Article 6 of its Enforcement Decree). They contain no date of birth, time of birth, place of birth, name or analysis content. When you delete a result or an account, the result reference in this record is replaced with a meaningless random value so that it is no longer linked to the result or the account; when a result is deleted because its retention period ended, the record is left as it is; either way it is not erased before the statutory period ends. The buyer email address is personal information kept for the statutory period as part of this record and is used only for restricted operator lookups. It is not used to bring a deleted result back or to link one to a new account automatically, and the existence of this record does not restore a result, ownership or access rights.
• Consumer enquiry, refund and dispute records: if such records exist they are kept for 3 years (Article 6 of the same Enforcement Decree).

The payment and contract record (5 years), the consumer complaint and dispute record (3 years) and the opening of a purchased result (12 months from payment confirmation) are separate periods with different purposes.

Records that the law does not require us to keep but that remain, with their link to the account cut, for operations are the following. Nothing is kept outside this list and the legally required records above.

• Deletion record: only a random number for each deletion request, the times it was requested and completed, the final status, the total number of attempts and a general error category (for example, disconnect retries exhausted). It holds no account number, email address (transformed forms included), sign-in provider identifier or list of providers used, result per provider, token, or result, conversation or session number. It exists to confirm that deletion finished and to run failed work again.
• AI usage records (if the AI conversation is offered): only the purpose, status, provider and model, prompt version, a general error category, token counts, cost and the date (day only) remain for cost management. The account number, conversation and message numbers, the request number the AI provider assigned, the message number the app attached, the conversation text and every other value that links to a person are erased.
• Material for retrying a disconnect: an Apple token or Kakao member number is kept encrypted only while a failed disconnect is being retried, and deleted once it succeeds or after 8 failed attempts.

When you delete your account we ask Apple and Kakao to disconnect. If they cannot be reached we retry automatically up to 8 times (the interval grows with each attempt), and the deletion of your data does not wait for the disconnect. If the app cannot re-authenticate you with Apple (for example on Android), you can remove KOBI yourself under Sign in with Apple in your iPhone settings; your right to delete is not limited if a disconnect has not finished.

• In the app: open Delete account in the settings, read the notice and confirm. To delete just one result, its owner chooses "Delete permanently".
• Without the app: at mykobi.io/account-deletion, which opens together with the app member service (the address cannot be used before then), delete with the code sent to the account's email address (valid 10 minutes, up to 5 entries). If you cannot receive the email, ask at support@jebub.com; we check who you are and handle it the same way.
• Saved or bought by email without an account: on the same page choose to withdraw email links instead of deleting an app account, and confirm the code sent to that email; only the information tied to that email is withdrawn. This choice also opens together with mykobi.io/account-deletion and cannot be used before then (until then, ask at support@jebub.com).

Withdrawing email links works as follows.

• Withdrawn automatically: the paid-content access of purchases made with that email, the way to find results again with that email, links to results you explicitly saved with that email, and the contact and opt-in link.
• Not deleted: the result itself, other people's access rights and saved links, results owned by an app account, and the payment and contract records the law requires us to keep. An email address, a purchase or knowing a result link is not proof of ownership, so deleting a whole result on that basis could delete someone else's. A result kept only because of this email returns to the ordinary retention rule in section 2.
• Payment and contract records are kept as the law requires, with their link to the result cut, and are not used to open results, find them again or prove ownership. Even if the buyer email stays in a remaining payment record, it does not restore a withdrawn link, a deleted result, access rights or ownership.
• If several people bought the result, only the requesting person's links are withdrawn and the others stay. Visiting or signing up again with the same email does not bring back withdrawn links or access.

If you want a whole result deleted: a result made with an app account is deleted only when the account that owns it deletes it permanently in the app or deletes the account, and not because someone else bought or saved it. A result made without an account is deleted automatically when its retention period ends; before then, ask at support@jebub.com and staff handle it through a restricted procedure after checking additional material. Even this procedure does not delete a result owned by an app account.

15. Privacy officer

Privacy officer: 김대민 (Representative, JEBUB Inc.)

Contact: 010-4780-7530 · support@jebub.com

16. Complaints

For advice or dispute resolution about personal information you can contact the bodies below in Korea, or the data protection authority where you live.

• Personal Information Dispute Mediation Committee: +82 1833-6972 (www.kopico.go.kr)
• Personal Information Infringement Report Center (KISA): 118 (privacy.kisa.or.kr)
• Supreme Prosecutors' Office: 1301 (www.spo.go.kr)
• Korean National Police Agency: 182 (ecrm.police.go.kr)

17. Changes

If this policy changes, the new effective date and the changes are posted on this page before they take effect. When a processing region or other international-transfer detail is going to change, the planned date and the date it applied are stated, with the date, in section 5.

Company

JEBUB Inc. (주식회사 제법)

Representative

김대민

Business registration no.

297-88-03614

Address

서울특별시 동작구 상도로 296-2, 2층 101 제이25호(상도1동)

Customer service phone

010-4780-7530

Email

support@jebub.com

Hosting provider

Vercel Inc.