Birth Data for Personal Good-Day Matching: Privacy and Precision

Birth data for personal good-day matching is a civil date: year, month, and day. From that date the tool takes a year branch and a day pillar and uses them only to penalize candidate days that clash those branches. Privacy means you do not owe that date to a chat, a colleague, or a relative’s screenshot. Precision means you type the date you actually have, not a season, not a souvenir animal, and not someone else’s birthday dressed as yours. The match is professional guidance. The date is sensitive because it is yours.

Key facts

The field is optional. A blank birth date yields the public almanac rank, which is a complete and respectable result.
The tool asks for a date, not an hour and not a city. Do not “improve” precision by guessing an hour. There is nowhere honest to put the guess, and the day pillar of a civil date does not require one.
A clash with the year branch subtracts 6. A clash with the day pillar subtracts 4. The year branch this product documents is the branch after Start of Spring, not the branch of 1 January and not a lunar-new-year animal from a placemat.
Two birthdays in the same January can fall on different sides of that traditional boundary. Type the civil date and let the tool resolve the branch. Do not override it with a guess.
Another adult’s date is theirs. A child’s date is not an input we want. Charts and matches for children are outside this product.
Saving a preview with an email magic link stores a reading. It does not charge a card, and it is not a reason to forward the birth date to a group thread.

Precision is the civil date

Precision is often imagined as more digits: hour, minute, hospital, longitude. For this match, extra digits are a distraction. The day pillar is the sexagenary day of the civil date. The year branch is the traditional year that contains it, which the product documents as turning at Start of Spring rather than at the Gregorian new year. If you know you were born on 2 March 1991, that date is precise enough for this field. In the locked example used by the engine, that date’s year branch and day pillar are both 未, and a candidate that clashes 未 pays the penalty. You do not need the minute of birth to see the penalty. If you only know “spring,” you do not know the date. Leave the field blank rather than trying March 20 because it feels central. A wrong date is a wrong branch pair, applied confidently. Blank is quieter and more accurate.

Near the boundary, humility beats a family story. “We always said she was a horse” may refer to a lunar festival table, a Start of Spring table, or a calendar printed for a different zone. Those tables disagree in late January and early February. The form’s job is to resolve the date you type according to its own rule. Your job is not to pre-correct the animal in your head and then pick a different civil date to force the animal. Forcing the animal is how precision theater creates a false match. If you later want a birth chart, the hour and the city matter, and the tool is BaZi, with its own blanks when the hour is unknown. Do not smuggle that project into a date field that cannot hold it.

The same birth date returns the same branches every time you type it. That repeatability is a craft property. It is not a reason to treat the date as public. Repeatability means you can check your own work. It does not mean a colleague can check it for you by posting it.

The Slack message she did not send

A producer in Amsterdam almost pastes her birth date into a production Slack so a colleague can “see why Thursday clashes.” The channel includes freelancers she has met once. The Thursday clash, if she wants it, is a six-point or four-point note on her own screen. The colleague needs the booking, not the branches. She types, “Thursday is hard on my side, Friday is clean,” and leaves the date unsent. That sentence is precise about the decision and private about the input. If she wants the colleague to run a personal match, she invites him to type his own date on his own screen. She does not collect dates for the crew. A group clash chart is not a feature. It is a privacy incident with an almanac attached. Questions about what a saved reading contains can go to Help. The birth date itself does not.

Someone else’s date

A parent’s date, a partner’s date, a client’s date: precision does not improve because you remember their birthday party. You need their consent and a real reason that is theirs. Matching a wedding day “for both of you” means each adult runs the window if each adult wants to. It does not mean you type them. Matching a parent into a move they are not taking is curiosity, not precision. A famous person’s published birthday is still not a toy for this field. We do not need their clashes, and a public biography is not consent to run their life through a planner.

Children are the hard line. Do not enter a child’s birth date to avoid a clash on a school tour, a move, or a ceremony. We do not personalize dates for children, and we do not write their charts. An adult’s own date is the only personal layer this page will help you use. If the family event must work for a child, the constraint is the child’s nap, the other parent’s shift, and the building’s hours. Those are civil. They are not a day pillar you borrow from a minor.

Privacy after the number exists

Once the date has been typed, the result may show that a candidate “clashes your birth year branch” or your day pillar. That sentence is enough for you. It is more than enough for a screenshot in a family chat. Cropping poorly can leave the date in the corner. If you share, share the chosen civil date of the event, not the birth field. An email magic link that saves your preview is a convenience for you. Forwarding the link forwards the context you saved. Treat it like a document, not like a sticker. The disclaimer is about claims. This page is about the input those claims would be tempted to decorate.

If you discover the date was wrong, type the corrected one and let the penalties move. Do not keep the old animal because you have already explained it to a friend. Precision includes revision. The friend can survive a changed preference. A clash that disappears after a correction was never a fate. It was a branch arithmetic on the digits you supplied.

Start of Spring versus 1 January is the correction that matters most for people who memorized a zodiac from a January birthday card. A card is not the tool. If your civil date is far from the boundary, the memorable animal and the tool will often agree, and you still let the tool speak. If your civil date is near the boundary, you let the tool speak even if the card disagrees. Agreement is pleasant. It is not the definition of precision.

What this is not

An hour, a minute, a hospital, or a city. Those are chart inputs, not this field.
A request to publish, screenshot, or collect other people’s dates.
A child’s birth date, for any occasion.
A lunar-new-year placemat you should force the form to match.
A required field. Blank is precise when the date is unknown.
A charge, a diagnosis, or a legal identifier. It is a traditional branch pair used as a sort key.

Send the booking, not the birthday

Opening the tool does not charge. Precision is the civil date you can verify. Privacy is leaving that date out of Slack. The Thursday decision can travel. The birth date stays on your side of the screen.