Privacy Policy

1. Who this policy covers

This policy describes how SAJU handles information when you use its birth charts, daily readings, account features and support. The operator and contact details appear below.

SAJU is operated by an individual based in the Republic of Korea. The operator directly handles privacy enquiries and requests to access, correct or delete information at whatsyoursaju@gmail.com.

2. Information we use

Chart details: your birth date, optional birth time or two-hour range, and selected birthplace time zone. If you select a birth city, we also store its name and city-centre longitude to calculate apparent solar time. A repeated clock time may include your first/second occurrence choice. We derive your Four Pillars and elements from these details. City searches run in your browser using GeoNames data; we do not request device GPS or a street address.

Account details: Google provides an account identifier, email and basic profile information, which may include a name and profile picture. Supabase handles authentication. We also store your chosen nickname and account timestamps. We do not request access to Gmail, contacts or Google Drive.

Browser and request data: language, saved cards, favorites and visit history may be kept on your device. Hosting and authentication providers may process IP addresses, browser information, request times and security logs to deliver and protect the service. If you contact us, we receive your email and the information you include.

Your birth date and birthplace time zone are needed to calculate your chart. Selecting a city supplies the time zone; a time-zone-only option is available if city search cannot find your location. Birth time is optional. Without it, the hour pillar is unavailable. Apparent solar-time correction requires an exact time and a city. The basic chart does not require Google sign-in, a nickname or AI permission. Do not include identity documents or health records in an ordinary support message.

3. Why we use it

We use chart data to provide the readings you request; account data to sign you in, save your chart and manage your nickname; and technical data to operate the service, prevent abuse and resolve errors. We use support messages to answer your requests.

We process the information needed to provide the services you request, including chart calculation, account access, saving a chart and responding to enquiries. Where the law requires consent, we ask for it separately; optional AI processing always requires a separate choice. We process security information to protect the service and prevent misuse, subject to the limits of applicable law. Reading this policy or accepting the Terms does not give blanket consent to other uses or international transfers. You may decline optional processing without losing access to the basic chart.

4. On your device and on our servers

A basic chart preview is calculated in your browser and its inputs can stay in browser storage. Signing in does not by itself save your preview birth details to your account: you choose which chart to save. Account charts are stored in Supabase.

When you request the full pillar interpretations or an optional AI reading, your birth inputs are sent to SAJU’s server to calculate the requested result. For AI readings, the server forwards only the calculated chart context described below. Sharing a card sends the exported image to the app or recipient you choose; that destination has its own privacy practices.

When automatic daily history is enabled, an account with a saved birth chart receives a basic reading each day, even without a visit. Supabase stores the date, daily time zone, score, summary, category readings and actions, saved-chart revision and calculation/content versions. We retain Korean, English and Spanish text. These records are automatically prepared readings, not proof that you viewed them; they do not include optional AI readings. Your device can update the account’s daily time zone when you save a chart or open Today. If no daily time zone is available, we use UTC.

5. Optional AI readings

When this feature is available, we ask for permission before sending chart information to OpenAI to write an expanded reading. You can decline and keep using the basic reading. Google sign-in is not permission for this transfer.

We send calculated pillars and elements, the reading date and daily pillar, the elemental relationship and theme, calculation-version and uncertainty notes, and the requested reading language. We do not include your entered birth date or time, birth city, longitude, time-zone identifier, name, email or nickname in the OpenAI request. A calculated chart can still be personal information.

SAJU requests no stored response through the API, but this does not eliminate provider safety logs. OpenAI’s published API rules generally allow abuse-monitoring logs for up to 30 days, or longer when required by law or reasonably needed to prevent harm. Withdrawal stops new requests and removes the saved reading associated with that permission; it cannot recall a request already sent.

SAJU does not use your chart to train its own AI model. OpenAI states that API data is not used for model training by default unless the API customer opts in. Its data-handling documentation is linked below. To report an inappropriate reading, send the date, category and relevant passage to our contact email; your full birth details are not needed.

6. Service providers and international transfers

Netlify provides website hosting and server functions. On each visit or server request, it processes connection data and the information sent for that function, including birth inputs submitted for a reading. Its infrastructure operates internationally, including in the United States. Connection and security records are subject to its applicable retention rules. Provider contact: privacy@netlify.com.

Supabase provides authentication and database storage. It receives Google account information at sign-in, nickname changes and the charts you choose to save. If you use optional AI, it also stores permission, session and saved-reading records. The project database is in Singapore (ap-southeast-1); support and security operations may involve other countries, including the United States. Active account and reading records follow the deletion rules below; provider backups and logs have separate retention rules. Provider contact: privacy@supabase.com.

Google authenticates your account when you choose Google sign-in. Gmail also hosts our support mailbox, so your address and message are processed by Google when you email us. Google operates servers internationally. Its own privacy policy governs its account, authentication and email services, including retention and regional contact options; the policy is linked below.

OpenAI receives the calculated chart context described in the AI section only when the AI feature is available and you authorize and request a reading. Processing may take place in the United States and other countries used by the provider. Its published API retention limits are described above. Provider contact: privacy@openai.com; data-handling documentation is linked below.

Website and API requests use encrypted HTTPS connections; email follows the mail providers’ delivery process. Declining or withdrawing AI permission stops optional AI transfers. You can avoid account-chart storage by not saving a chart, or delete your account to end that storage. Visiting the site still involves the hosting provider, and disabling necessary authentication storage prevents sign-in. Contact us to ask about processing locations or exercise your rights concerning a transfer. If a transfer requires separate consent under applicable law, this policy is not a substitute for that consent.

7. Other disclosures and card sharing

We do not sell personal information or share it for cross-service targeted advertising. The app does not include third-party marketing trackers. Providers described above process information for the stated functions; this is distinct from selling it to advertisers.

When you share a card, you choose the receiving app or person. Check the information shown in the image before sharing; SAJU cannot remove copies kept by a recipient. We may also disclose limited information where a valid legal obligation or lawful request requires it. We assess the authority and scope of such requests and do not treat this paragraph as permission for unrestricted disclosure.

8. Cookies and browser storage

Functional storage remembers your language, birth preview and saved items. Authentication cookies keep you signed in, and an HTTP-only AI permission cookie identifies an authorized reading session. These are separate from advertising trackers.

Use your browser’s site-data controls to view, block or delete cookies and local storage. This may sign you out and remove local previews. Clearing browser data does not delete your server account or prove that a stored AI permission record was deleted: use the data settings first to withdraw permission or delete the account.

9. How long information stays

Device data stays until you replace it, clear it in settings or clear browser storage. The language preference is kept separately; its cookie lasts up to one year. Authentication cookies and session tokens maintain your signed-in session under the authentication provider’s settings. Blocking storage may prevent sign-in or saved previews from working.

Account and saved chart records stay until replaced or the account is deleted. Deletion removes active records and linked readings, not your Google account. Device copies on other browsers and anonymous AI permissions given there must be cleared separately. Provider backups and security logs may remain under their own retention requirements; deletion is not immediate in every backup.

Automatic basic-reading history is available for 30 calendar dates, including the reading date, in the time zone recorded for that reading. Expired entries are excluded from account access immediately and removed by the next successful hourly cleanup. Failed jobs are retried; an outage can delay physical deletion. Deleting the account or its saved birth profile deletes the associated active history and pending jobs. Provider backups follow their separate retention rules.

AI permission expires after 30 days. The server stores a hashed session token, permission version and time, usage counters and the latest generated reading. A session is linked to an account only if you were signed in when you granted permission. Expired permission cannot authorize another reading. Expired records are removed by the cleanup operation triggered when new permission is granted; expiry is not a promise of deletion on that same day. You can withdraw permission to request immediate deletion of the associated active record.

Account deletion and consent withdrawal remove the relevant active database records. Clearing device data removes SAJU information from that browser. Provider backups and security logs follow separate retention rules and may not be deleted at the same time.

Support emails, attachments and copies kept by the operator are deleted within 30 days after the enquiry is resolved. If specific information is still necessary for an unresolved dispute or a legal duty, we retain only that information for the relevant purpose and period. We review that need monthly and delete it without undue delay when it ends. We do not routinely request identity documents. Google’s residual copies and technical records follow its own retention rules.

10. Your choices and rights

In data settings you can edit birth details, clear this device, withdraw AI permission and delete an account. You can also revoke SAJU’s access from your Google account. To request access, correction, a copy, deletion, restriction or an objection, contact us. Available rights and deadlines depend on the law that applies to you. We may need proportionate identity verification. You may complain to your local data protection authority and, where available, appeal a decision by contacting us.

Withdrawing consent does not affect processing that was lawful before withdrawal. The readings and scores are reflective content, not automated decisions about access to jobs, credit, insurance or other legal rights.

Send a privacy request to the contact email below, stating the action you want and, for account requests, the email used to sign in. A legally authorized representative may contact us on your behalf. We may check authorization and ask only for information reasonably needed to locate and verify the request. We will follow the applicable statutory response period and explain any lawful refusal or limitation. In Korea, you can also seek help from the Personal Information Infringement Report Center or the Personal Information Dispute Mediation Committee.

11. Children and data protection

SAJU is not designed for children and does not provide a verified parental-consent process. Do not submit a child’s personal information where the law requires parental consent that has not been validly obtained. A parent or legal representative can contact us to request access to or deletion of a child’s information.

In Korea, processing based on consent for children under 14 requires verified consent from a legal representative; other countries may apply different thresholds. If we learn that information has been processed without legally required consent, we will restrict the relevant processing and take appropriate deletion or other remedial action. These requirements are not replaced by accepting the Terms.

If you believe a child’s information has been entered without the legally required consent, contact whatsyoursaju@gmail.com. Do not include a full birth record or an unredacted identity document in the first message. The operator will first identify the affected account or record and, where needed, check the requester’s authority using the minimum information necessary. We restrict further processing and delete information that cannot lawfully be retained, then explain the action taken. This reporting process is not a parental-consent service.

12. Security and changes to this policy

We use HTTPS in the deployed service, account-based database access rules and restricted server credentials. We limit processing to the functions described here. No system can guarantee absolute security. If a personal-data incident occurs, we will investigate and provide notices or reports required by applicable law.

The effective date appears at the top of this policy. We update it when our practices change and give notice of material changes in the manner and period required by law. A new purpose or transfer that requires consent will not be authorized merely by changing this page.

Provider privacy information

Location data credits

City names and coordinates are adapted from GeoNames. We select fields and names for local search; coordinates refer to city centres.