算Birthmath

Effective [Effective date] · v2

Privacy Policy

This page explains what Birthmath, a saju app ("we", "the service"), keeps, where it keeps it, for how long, and how to delete it. It covers visitors everywhere, including notices required in Korea, California, and the EU.

The short version: your name, birth date, birth time and birthplace are computed in your browser and stored only on your device. There's no account, no ads and no payment. The only things that reach our server are encrypted data you choose to share or back up, preview cards and text with no names or birth dates, error reports with no birth data or names, and the standard access logs every website gets.

1. What stays on your device

The name or nickname, birth date, calendar type, birth time, birthplace and gender you enter, your saved people, the links you made (with their delete keys), and your settings (language, light or dark mode) are kept in your browser's local storage. Charts, readings, compatibility, the year report and the cards you save are all made on your device.

None of this is sent to an outside server, and it's deleted from your device right away when you use the app's delete buttons or clear this site's data. We can't see it.

Heads up: older long result links (like #/r/s.1995.5.15...) carry the birth date inside the link itself. The part after # is never sent to the server, but anyone you paste that link to can read it.

2. What our server handles, why, and for how long

The personal information our server handles is: encrypted share links, invite replies and backups (we never have the key), link preview card images and preview text, error reports, and access logs (IP address, browser details, time). The first five rows below exist only if you use that feature.

Preview cards and preview text aren't encrypted, because messaging apps show link previews without the key. That's why they never include names, birth dates or birth times, and the server strips every digit from preview text. A card does show your sign image (like Great Mountain) and the two characters of your Day pillar (like 丙午). Cards you save with the save button (where you can choose to show a name) are made on your device and never uploaded.

ItemWhat's storedWhyHow long, and deletion
Share linkYour chart, encrypted on your device (ciphertext only), a short link code, the link type and language, creation and expiry times, a hash of the delete key, and preview text (sign image names, and for compatibility the pairing name and relationship type; no names or numbers)So the person you send it to can open the same result, and for link previewsDeleted by a daily cleanup 1 year after creation. The creator can delete it any time with the delete key saved on their device.
Preview card imageA PNG made when you share: your sign image name and one line about it, the two Day pillar characters, and element colors (for compatibility: both sign image names, the pairing name and the verdicts). No names, birth dates or birth times. Not encrypted.Link previews in messengers and social appsDeleted with its share link (1 year at most)
Invite replyThe reply from the person you invited (their birth details or a result summary), sealed on their device so only your device can open it, plus the time it arrivedDelivering the reply to youDeleted with its invite link (1 year at most)
Backup codeYour saved people and links, encrypted on your device with a key made from your recovery phrase, and the time you last saved. The phrase itself never reaches us.Moving your list to a new deviceUntil you delete it. Deleted automatically 1 year after you last saved.
Error reportThe error message, code location (stack), error type, browser details (User-Agent), the screen name with data removed (like /r), language, app build, and time. Birth details, names and link keys are removed before sending, and IP addresses aren't stored.Finding and fixing bugsDeleted automatically after 30 days
Access logsIP address, requested address, time, browser detailsDelivering the site, security, and blocking abuseKept and deleted by our host, Netlify, under its own policy. We don't store them ourselves.

3. Why we can't read what you share

A share link looks like site/s/code#k=key. Your browser creates the key, and it lives only after the #, which browsers never send to the server. The server only ever holds ciphertext without the key, so neither we nor our host can read the birth details inside.

The flip side: anyone who has the full link, key included, can open it. Send links only to people you trust, and delete them when you're done. If a link holds someone else's birth details, ask them first.

4. Local storage (similar to cookies)

  • What it is: your browser keeps a small amount of data on your device. Unlike cookies, it isn't sent to the server automatically.
  • Why: so your saved people, settings and the delete keys for your links are there next time. We use no cookies, and no tracking or advertising cookies of any kind.
  • How to refuse: clear or block this site's data in your browser settings. Readings still work, only saving stops. Local storage is strictly necessary for the features you use, so it doesn't need a consent banner.

5. What's collected automatically

Like any website, our host receives standard access logs when you load a page (IP address, requested address, time, browser details). Netlify processes these to deliver the site, for security and to block abuse, under its own policy. We don't use them to identify or profile anyone.

To stop abuse of the share features, our server turns your IP address into a short hash and counts requests in memory for up to 10 minutes. IP addresses are never written to storage or error reports.

Fonts (Pretendard, Noto Serif KR and others) are served from this site too, so no font service receives your IP address.

We use no analytics, no ads and no tracking pixels. Because we don't track you, the site works the same whether or not your browser sends Do Not Track or Global Privacy Control signals.

6. Selling and sharing

We do not sell or share personal information, and we don't give it to anyone for advertising. If a legal authority asks, the server only holds ciphertext without keys, so we have no birth details to hand over.

7. Service providers

We rely on the company below. It only does the job listed and doesn't use the data for anything else.

ProviderJob
Netlify, Inc. (101 2nd Street, San Francisco, CA 94105, privacy@netlify.com)Hosting and delivering the site; storing share links, invite replies, backups, preview cards and error reports; the daily expiry cleanup; blocking abuse

8. International transfers

Under Korea's Personal Information Protection Act, these transfers rely on Article 28-8(1)(iii)(a): storage and processing needed to provide the service you request, disclosed in this policy. The table lists the five things Article 28-8(2) requires.

Recipient (contact)CountryDataWhen and howPurpose and retention
Netlify, Inc. (101 2nd Street, San Francisco, CA 94105, privacy@netlify.com)United States (storage and processing). Pages and access logs may pass through Netlify delivery servers (CDN) in the country nearest you.The items in section 2 (encrypted shares, replies and backups, preview cards and text, error reports, access logs)Sent over the internet (HTTPS) when you load the site and each time you use a featureThe jobs in section 7. Retention as in section 2.
  • How to opt out: don't use share links, invites or backup codes. Anything you already made can be deleted with the app's delete buttons or by emailing us.
  • What happens if you opt out: charts, readings, compatibility and the year report all still work. Only sharing and moving to another device stop.
  • Loading the site itself goes through Netlify's US servers, so access logs can't be opted out of except by not using the site.
  • For visitors in the EU and UK, transfers to the US rely on Netlify's data processing agreement with Standard Contractual Clauses: https://www.netlify.com/pdf/netlify-dpa.pdf

9. Legal basis (EU and UK visitors)

We store share links, invite replies, backups and preview cards because you ask us to (performing the service you request), and error reports and access logs for our legitimate interest in keeping the app working and secure. Local storage on your device is strictly necessary for the service, so it doesn't need a consent banner.

10. Your rights and how to use them

  • On your device: delete any time with the app's delete buttons or by clearing this site's data.
  • Share links and cards: tap Delete on the device that made the link and it's gone. Backups: tap Delete the box. Lost that device? Email us the link and we'll remove it.
  • Depending on where you live (for example under GDPR or California law), you can ask to access, correct, delete, or restrict your data, or object to its use, and we won't treat you differently for asking. We can't identify you by name or account, so to find a specific link or backup we need its code.
  • Send requests to the contact below. We'll answer within 10 days, usually sooner. An authorized agent or legal guardian can also ask for you.
  • Please ask before you make or send a link with someone else's birth details.
  • EU and UK visitors can complain to their local data protection authority. Korean visitors can contact the Personal Information Infringement Report Center (118, privacy.kisa.or.kr) or the Personal Information Dispute Mediation Committee (1833-6972, www.kopico.go.kr).

11. Children

This is a general-audience service for people 13 and older (14 and older in Korea, 16 and older in the EU and UK). It isn't directed to younger children, and we don't knowingly collect their information. If we learn a child's data is on our server, we'll delete it. Parents and guardians can reach us at the contact below.

12. How we protect data

  • Birth details never go to the server. Shares, backups and invite replies are encrypted on your device with AES-GCM before they're sent, and the keys never reach us.
  • Delete keys and backup access values are stored only as hashes.
  • Every connection uses HTTPS.
  • Error reports are scrubbed twice (before sending and before saving) to remove dates, times and link keys, and are deleted after 30 days.
  • Rate limits block guessing and abuse.
  • Only the operator can access server storage.

13. What we don't do

  • No accounts, logins or payments. If payments are ever added, we'll update this policy before they start.
  • No processing of sensitive categories (health, religion and so on), and no automated decisions that affect you.
  • The public site has no AI chat. If we ever add a feature that sends your chart to an outside service, we'll ask first and describe it here.

14. Who we are and how to reach us

We haven't appointed a separate privacy officer, so under Article 31(2) of Korea's Personal Information Protection Act the operator's representative serves as the privacy officer and handles all requests.

  • Operator (data controller): [Operator name]
  • Privacy officer (representative): [Representative name]
  • Phone: [Phone number]
  • Email: [Contact email]

15. Changes to this policy

We'll post changes on this page and on the app's home screen at least 7 days before they take effect (30 days if a change works against you). Current version: v2, effective [Effective date].

16. Previous versions

Previous versions, and what changed, are listed below.

  • v2: Current version (effective [Effective date]). Added the legal basis and country for international transfers, served fonts from our own domain (Google Fonts and jsDelivr removed), listed every item the server handles (preview text, invite replies, access logs), added a phone line for the privacy officer, and made the age rules consistent.
  • v1: First draft (before an effective date was set). Fonts loaded from Google Fonts and jsDelivr, and it didn't yet state the legal basis for transfers or a phone number for the privacy officer.