Effective: August 25, 2026 · Revised: October 25, 2026 (payment and order records stay for 5 years after account deletion, with only the account link removed) · Previous revision: October 22, 2026 (sign-up path record added — once, when you sign up: the platform, app version, update number, the path and utm values of the address opened just before signing up, and whether you arrived through a referral link; deleted together with your account) · Previous revision: October 16, 2026 (website sign-in with Kakao and Google — four sign-in cookies; information entered without signing in stays only in the browser and is moved to your account at sign-in; the daily letter does not send birth information; how website referral registration is verified) · Previous revision: October 15, 2026 (social sign-in items aligned with what is actually stored — Kakao nickname; Google email, name and profile photo URL; the same day, a section on website cookies (the visit-statistics cookie _ga) added; reading request log added — member ID, reading type, request time, whether newly generated, whether the request limit was exceeded, kept for 3 days; the same day, wording corrected — the member ID is not among the values sent to KakaoPay (payment is not open yet)) · Previous revision: October 14, 2026 (app usage events now include a home card coming into view — only the card name (tomorrow’s letter); the same day, website point payment — KakaoPay payment processing entrusted and payment record storage added) · Previous revision: October 13, 2026 (website usage records now include opening the get-the-app page — only whether a referral code was attached and the coarse route the visitor came through, stating that the address of the page just before arrival is sent; the same day, the result of notification registration in app usage events now includes where notifications were switched on), October 12, 2026 (app usage events now include the result of the referral-code step — filled in or skipped, and the check result; the code value is not sent), October 11, 2026 (five actions added to app usage events — getting stuck during onboarding, the first result screen, opening a section of My Saju, the result of notification registration, the in-app review request; the same day, deletion timing added for in-app news (notices of points you received)), October 4, 2026 (banner ads stated explicitly, banner impression record added; the same day, storage of in-app feature suggestions), October 3, 2026 (relationship status and work situation also used for the order of readings on the app home), September 30, 2026 (calendar anniversary and schedule notes and diary storage, items kept for 1 year after account deletion to prevent abuse, device authenticity check, consent to promotional notifications, screen navigation record, and website usage records added), September 23, 2026
The Korean text is the binding version. This translation is provided for convenience; if anything differs, the Korean original prevails.
솔러스 (the “Company”) processes the personal data of 99jeomjip users as follows.
We collect only what the Saju calculation needs — birth date, birth time (optional), sex, birthplace (city level — choosing just a province is fine, and cities outside Korea are accepted), and a name or nickname (optional). Profiles for family and friends use the same fields, and a nickname is enough. For your own profile you may optionally choose a relationship status (single, in a relationship, married) and a work situation (student, job-seeking, employed, business owner, freelancer, taking a break) so that the advice in your readings fits your situation. Leaving these unset does not limit your use, and you can change or clear them in your profile at any time. When you sign in with a social account, we store the values that account hands over at sign-in — for Kakao, the account identifier and nickname; for Google, the account identifier, email, name and profile photo URL; for Apple, the account identifier and, if you agree to provide it, your email. The nickname, name and profile photo URL are values the sign-in service passes along with the rest; we do not show them on screen or put them into readings, and they are deleted together with your account. Signing in with Kakao or Google on the website collects only the same items as in the app; no new information is collected.
The Bond Map and the two-person compatibility link on the website are processed separately from the app. All we receive is the name you want to be called (a nickname is recommended) and the eight characters of the Saju calculated from the birth date and time you enter (or a marker when the hour is unknown). Your birth date, birth time, sex and birthplace are not stored — they disappear from the browser once the calculation is done, and neither the map owner nor other participants can see them. The name, birth date, birth time (or “unknown”), sex and birthplace you enter on the website without signing in remain only in that browser’s storage and are not sent to the server. The calculation also runs inside the browser. They disappear when you press “Clear my information” or when the browser clears site data — Safari on iPhone and iPad may delete them by itself if you do not visit this site for more than 7 days. The daily letter is picked in the browser from a set of pre-written sentences that is downloaded, so no birth information is sent in order to view the letter.
Website usage records. To see how the website is used, we send to Google Analytics the path of the page visited, the address of the page just before arrival, and the fact that one of six actions occurred (seeing a result, tapping the share button or the get-the-app button, creating a map or link, arriving at an address carrying a referral code, opening the get-the-app page). A record of opening the get-the-app page additionally carries whether a referral code was attached and the route the visitor came through, as only one of: our website, an in-app browser such as KakaoTalk or Instagram, a campaign link, another site, or typed directly. We do not send birth dates, names (nicknames), referral code values or map addresses; the part of the address after the question mark and after # is removed before sending, leaving only the campaign tags that tell where a visitor came from (utm values attached to ad and post links, and the ad click ID). This record carries a browser-level identifier, so it can be linked to that browser. In the EU, EEA, UK and Switzerland this record is not stored.
Website payment. When you buy points on the website, to confirm and refund the payment we store, linked to your account, the order number, the item bought (point pack), the payment amount, the payment time, the payment method (KakaoPay) and the payment approval number that KakaoPay returns. For the payment, we send KakaoPay only the order number, the item name and the amount. The member ID is not sent. We do not store card numbers, card details or KakaoPay account details.
Calendar and diary. When you register an anniversary (name, solar or lunar date and whether it is a leap month, type, notification on or off) or a schedule note in the calendar, or write a diary entry (a mood and one line), it is stored in your account so you can continue after changing phones. Anniversary names, notes and diary entries are text you write yourself, so we recommend not writing other people’s personal information or sensitive content. This text is not used to generate readings or for AI.
Feature suggestions. When you send a message through “Suggest a feature” in the app, we store that message together with the time sent, the app version, the platform (iOS or Android) and the app display language, linked to your account. It is used only to improve the app, and not for generating readings, AI or advertising. We do not reply through this box, so no contact details are collected — if you need an answer, please email the contact address below. Because it is text you write yourself, we recommend not writing personal information such as your name, contact details or birth date.
Device authenticity check. When you receive a referral reward on Android, we receive a verdict value (Google Play Integrity) confirming that the request came from an unmodified app and device. It is used only for the verdict and is not stored, and it contains no name or birth information. When you register a referral code on the website, instead of the device authenticity check it goes through an automated-input check (Cloudflare Turnstile), and so that the same account cannot receive the reward again, we store a one-way hash of the signed-in account’s unique ID.
Reading request log. Each time a reading is opened in the app or on the website, to prevent excessively frequent requests and to manage cost, we record the member ID, the type of reading opened, the request time, whether that request newly generated the reading, and whether the set request limit was exceeded. Birth date, birth time, birthplace and name are not part of this record.
Sign-up path record. Once, when you sign up, to see in what environment and through what route people sign up, we store, linked to your account, the platform (iOS, Android or website), the app version and update number, the path of the address opened just before signing up and the campaign tags (utm values) attached to that address, and whether you arrived through a referral link. The referral code value, the rest of the address, and your name and birth information are not included, and the record is neither sent outside nor used for advertising.
Device and usage records. If you turn on notifications, we store the device token for sending notifications, the platform (iOS or Android), the app display language and the app version. If the app stops unexpectedly, the error record and the device and app version information are sent to an error-reporting service — account identifiers and names are not sent. In addition, the usage records in section 4 below (which screens and features were used in the app, and their accompanying values) may be collected, and you can turn this off at any time under More in the app.
When you join a Bond Map or a compatibility link, we ask you to confirm separately that you agree to the processing described above and that you are 14 or older. Without consent you cannot join, but use of the app and of the website’s other calculation tools is unaffected. Persons under 14 may not join.
Birth information collected is used only for the Saju calculation and for generating readings. Relationship status and work situation are used only to tailor the advice in readings and to choose the order of readings shown on the app home. The order is decided on the device and is not used for advertising or provided externally. Birth information and reading content are not used for advertising or marketing, and we do not sell any personal data. However, to measure advertising performance, usage records within the scope of section 4 are sent to Google — birth information, names and reading content are not part of that.
Anniversaries, schedule notes and diary entries are used only to store and show them to you and to ring, on your device, the anniversary notifications you turned on. The device authenticity check value and the “items kept after account deletion” in section 5 are used only to prevent rewards from being obtained fraudulently. The reading request log is used only to prevent excessively frequent requests and to manage the cost of generating readings. The sign-up path record is used only to improve the service and find the cause of errors.
The nicknames and eight characters received through a Bond Map or compatibility link are used only to show the results of that map or link. They are not used for any other purpose or linked to an app account. The same applies to a two-person link made on the app’s compatibility screen — the link carries only the name to be called and the calculated eight characters, and who made the link is not stored. To keep to the daily limit on the number of links that can be made in the app, we separately count, per account, only the number made that day, and this count is deleted three days later.
An external AI model (DeepSeek, China) is used to write the reading sentences. It does not receive identifiable information such as your name, original birth date or birthplace — only the calculated chart composition (the eight characters, element distribution and so on) and the relationship status and work situation you chose. Generated readings are stored in a form shared across the same chart composition, and your name is combined with them only on your device at display time. Calendar anniversaries, schedule notes and diary entries are not sent to the AI.
The website’s calculation tools (quick Saju, compatibility, Bond Map, almanac) use no external AI model. The sentences on screen are fixed, pre-written text, and what you enter is not sent to any AI.
We use Google AdMob for banner ads and rewarded ads. In regions where no consent procedure is required (including Korea), ads are requested in non-personalized mode only. In the EU, EEA and the UK, we ask for your consent before showing ads, and personalized ads may be served only if you consent. If you do not consent, ads are still served non-personalized and the app’s features are unaffected. You can change your consent at any time in the app’s ad privacy settings.
On iPhone and iPad, the first time ads are prepared we ask once for App Tracking Transparency (ATT) permission. If you allow it, it is used to measure the performance of ads shown in this app. Every feature works the same if you do not allow it, and whether ads are personalized is decided by the consent procedure above, not by this permission.
To decide where to promote the app and to see on which screen or feature use stops, we send to Google (Firebase and Google Ads) the fact that an action occurred in the app and its accompanying values, and the names of the screens moved between.
This collection can be turned off at any time under More in the app, and turning it off stops the collection itself.
Promotional notifications such as point events and new-product announcements are sent only if you have consented to receive promotional information. We put “(광고)” (“advertisement”) at the start of the notification and also tell you how to refuse receiving them. Between 9 p.m. and 8 a.m. the next morning, they are sent only if you have separately consented to night-time receipt. You can give and withdraw consent at any time in the app’s notification settings, and once withdrawn we stop sending from that point.
Non-promotional notifications (the morning notification, registered anniversary notifications, and service notices such as updates and maintenance) are turned on and off in the notification settings, separately from this consent.
The website uses four strictly necessary cookies for sign-in and the Google Analytics cookies for the website usage records (visit statistics) in section 4. All are set directly by 99jeomjip.com and cannot be read by other sites. The sign-in cookies are not used for advertising or visit statistics.
| Name | Purpose | Retention |
|---|---|---|
| __Host-sb-at | Keeping you signed in (necessary) | 1 hour |
| __Host-sb-rt | Keeping you signed in (necessary) | 30 days, renewed to another 30 days on each use |
| __Host-kauth | Checking that a Kakao sign-in request was not forged (necessary) | 10 minutes, deleted immediately when sign-in ends |
| __Host-gauth | Checking that a Google sign-in request was not forged (necessary) | 10 minutes, deleted immediately when sign-in ends |
| _ga, _ga_TVWKLFQ1SF | Visit statistics that count visits from the same browser as one (Google Analytics) | Up to 2 years from the last visit — a browser may shorten this (for example, Chrome: 400 days) |
You can block or delete cookies in your browser settings (Chrome: Settings → Privacy and security → Third-party cookies / Site data; Safari: Settings → Safari → Advanced → Website Data). Blocking the sign-in cookies means you cannot sign in, but the calculations and the daily letter that work without signing in are unaffected. Blocking the visit-statistics cookies only leaves you out of the statistics, and every feature works the same; in the EU, EEA, UK and Switzerland the visit-statistics cookies are not set.
The information collected is erased when you delete your account (profiles, viewing history, points, settings, anniversaries, schedule notes, diary entries, feature suggestions, notification consents, sign-up path record, and in-app news (notices of points you received — deleted automatically after 90 days)). Once the 30-day grace period after a deletion request has passed, it cannot be recovered. Payment and order records (order number, product, amount, order status, payment method, order and payment times) are kept for 5 years under the Act on Consumer Protection in Electronic Commerce, and then destroyed. When you delete your account, only the link between these records and your account is removed. After that, these records alone cannot tell which member placed the order (the payment provider’s transaction number remains), and they are erased 5 years after the order date.
What is moved when you sign in. The profile you entered without signing in (name, birth date, birth time or “unknown”, sex, birthplace, and the relationship status and work situation if you chose them) is moved to your account’s profile the moment you sign in with Kakao or Google. If the same person already exists in the account, no new one is created and the account’s version is kept. The profile that was moved is deleted from the browser. Anything that could not be moved (when the account already has a different profile of yourself, or the storage count was exceeded) stays in the browser, and the screen asks you what to do. Retention and destruction after the move are the same as for the account information above (destroyed when the account is deleted).
What remains after you delete your account, to prevent abuse. We keep, for 1 year from the day the account was actually deleted (the day the 30-day grace period after the deletion request ends), an identifying hash of the device that received a referral reward or a sign-up free voucher, and a one-way hash of the unique ID of the sign-in account (Kakao, Google, Apple) that was referred. A hash cannot be turned back into the original value, is not linked to name, email or birth information, and is used only to check whether the same device or account is receiving the referral reward and the sign-up free voucher again. It is destroyed when the period ends. For accounts already deleted before this policy was revised, it is kept for 1 year from the date of revision.
The notification device token is deleted when you turn off notifications or delete your account, and when a device can no longer receive notifications it is removed from the sending list. Feature suggestions are deleted 2 years after the day they were sent, even if the account is not deleted. The reading request log is deleted automatically within a day once 3 days have passed. Error records are deleted 90 days after collection, and the usage records in section 4 are deleted when the retention period set by Google (up to 14 months) has passed.
Nicknames and eight characters on a Bond Map or compatibility link, including those made in the app, are deleted automatically 180 days after the day they were created. Before then, the map owner can delete the whole map and each participant can delete their own entry immediately with the delete button on the result screen. Deleted information cannot be recovered.
| Processor | Service entrusted |
|---|---|
| Supabase Inc. | Data storage and server operation; storage of website Bond Maps and compatibility links (Seoul region) |
| Google LLC | Advertising (AdMob), advertising performance measurement and usage record analysis (Firebase, Google Ads), website usage record analysis (Google Analytics), Android device authenticity check (Play Integrity) |
| DeepSeek | Writing reading sentences — only the calculated chart composition is sent (section 3) |
| Expo (650 Industries, Inc.) | Sending notifications (Expo Push) — promotional notifications only if you consented |
| Functional Software, Inc. (Sentry) | Collecting error reports |
| Apple Inc. · Google LLC | In-app purchase processing and receipt verification |
| KakaoPay Corp. | Website point payment processing and payment cancellation and refunds |
| Cloudflare, Inc. | Website hosting and automated-input check (Turnstile) — when creating a map or link and when registering a referral code on the website |
This document is updated when the entrusted items or the processors change.
Of the processors above, Supabase stores information in the Seoul region, but the companies below process it abroad. The time of transfer is when you use the relevant feature, the method is transmission over the internet, and the retention period is until the purpose of the entrustment ends.
| Recipient | Country | Items transferred | Purpose |
|---|---|---|---|
| Google LLC | United States | Ad request information, the usage records in section 4 (including screen names), the advertising identifier if allowed on iOS, the Android device authenticity check request, website usage records (section 1) | Serving ads and measuring ad performance, preventing fraudulent reward collection |
| DeepSeek | China | Calculated chart composition (the eight characters, element distribution and so on) | Writing reading sentences |
| Expo (650 Industries, Inc.) | United States | Notification device token, notification text | Sending notifications |
| Functional Software, Inc. | United States | Error records, device and app version | Identifying the cause of errors |
| Apple Inc. · Google LLC | United States | Payment receipts | Payment processing and verification |
| Cloudflare, Inc. | United States | Website connection information | Website hosting and automated-input prevention |
The usage records in section 4 are not transferred if you turn them off under More in the app. The device authenticity check happens only when you receive a referral reward, and if you refuse it you cannot receive that reward (the app’s other features are unaffected). Notifications and error reporting each stop when you turn off notifications or delete the app. The rest is processing necessary to provide the service, so if you refuse it you cannot use the relevant feature.
You can view, edit and delete your information within the app at any time. Account deletion is under More → Delete account in the app; if you cannot access the app, see the Account Deletion Guide. Anniversaries, schedule notes and diary entries can be edited or deleted one by one on their own screens.
Information on a website Bond Map or compatibility link has no account, so you delete it yourself with the delete button on the result screen. If you have lost the link, send your nickname and the creation date to the address below and we will delete it after verification.
Contact: help@99jeomjip.com
Name: Kim Seongyeop
Contact: help@99jeomjip.com · 0507-2097-2420