A SHARE LINK IS A RECORD
Does a Bazi calculator share link include my birth details?
Yes. Inspect the part after # before sharing.
In Clear Bazi Chart, Share link includes the birth inputs in the URL fragment. A recipient can read those inputs and regenerate the chart. The fragment is omitted from the HTTP document request, but that does not make a copied link anonymous or encrypted. If you only want to recommend the calculator, send its root address without the fragment. Share handler; MDN fragment reference.
What the copied address actually contains
Our known-hour test used the synthetic Gregorian record May 17, 2008, 09:40, Europe/Lisbon, longitude −9.13934, Male, solar time OFF and the midnight boundary. The live form produced Wu Zi / Ding Si / Ding Si / Yi Si. Opening the copied link in a fresh tab reproduced those four pairs; this checks one round trip, not every supported date or browser. Synthetic test ledger.
The copied address contained fourteen input keys and no four-pillar output field. Its time was written as time=09%3A40 and its zone as zone=Europe%2FLisbon; reading those values gives 09:40 and Europe/Lisbon without a secret key. In this captured link, the encoded separators do not conceal the birth time or location settings. Synthetic test ledger.
#year=2008&month=5&day=17&time=09%3A40&zone=Europe%2FLisbonThe full captured address also preserves the calendar, sex selector, unknown-hour and lunar-leap flags, longitude, solar-time switch, day-boundary selector, repeated-hour choice and city selector. The exact keys and values are available in the ledger rather than a screenshot of a shortened address. This describes our captured implementation, not a claim about other calculators. Complete captured inputs; Share handler.
Known time, unknown time and the same-tab trap
For the second test we checked unknown birth time and recalculated without changing the date or location. The new link contained time= and unknown=true. After a full reload, the recipient view showed Wu Zi / Ding Si / Ding Si and an Hour card labelled Unknown and Not inferred. The earlier 09:40 was absent from that link, but the date, zone and longitude remained present. Synthetic test ledger.
The known and unknown links each retained fourteen keys: one emptied time value did not remove the location fields. If the aim is to hide the location, ticking unknown time is therefore insufficient for these captured links. The checkbox expresses missing time; it is not a redaction command for the rest of the record. Synthetic test ledger.
| Captured setting | Known time | Unknown time |
|---|---|---|
| Time field | time=09%3A40 | time= |
| Unknown flag | unknown=false | unknown=true |
| Year / Month / Day | Wu Zi / Ding Si / Ding Si | Wu Zi / Ding Si / Ding Si |
| Hour | Yi Si | Unknown · Not inferred |
| Zone and longitude | Europe/Lisbon · −9.13934 | Europe/Lisbon · −9.13934 |
In a separate navigation check, replacing the known link with the unknown link in an already loaded tab changed the fragment but initially left the old 09:40 result on screen. Reloading that tab then displayed Time unknown and the blank Hour card. For this build, verify a shared result in a fresh tab or reload before judging whether the fragment was applied. Synthetic test ledger.
The unknown-hour replay retained the same first three pairs in this particular case, while omitting Yi Si. That agreement is not permission to infer the missing hour, and it is not a rule that every unknown-hour date has fixed other pillars. The result itself marked strength and onset provisional; preserve that qualification if you discuss the partial chart. Synthetic test ledger.
What reached our static server?
We opened the same known-hour fragment against our own static file server. The browser displayed the expected chart, while the recorded document request target was just /, with neither the hash nor the synthetic input values. This checks the HTTP document request at that server; it does not prove that every script, browser feature or messaging service ignores a URL. Synthetic test ledger.
The request receipt records the actual request targets from this local file-only server test. It contains synthetic test traffic only. The browser still had access to the fragment and used it to calculate the chart. The result is consistent with MDN’s definition of a URI fragment; it is not an audit of every possible disclosure route.
Opening the local root address without a fragment produced No chart calculated yet and disabled Copy, Share link and Print controls. That observation distinguishes a generic calculator link from an input-bearing share link: removing the entire fragment stopped this example from preloading a personal record. It did not erase any copy of the original link that someone already held. Synthetic test ledger.
Can I send the chart without sending my time?
Pressing Copy on the known-hour result yielded text beginning BAZI CHART, followed by 2008-05-17 09:40 and Europe/Lisbon. It also included the four pairs, hidden stems, element counts and generated notes. Choosing Copy instead of Share link therefore did not remove the recorded date and time in this test; inspect the actual exported text before sending it. Synthetic test ledger.
If you need to discuss only the relationship labels, write the relevant stem pair or a redacted excerpt yourself and review it before sending. The full Copy and Share link controls do not promise that limited export. A screenshot also needs a visual review: result subtitles may show the recorded date and time. Copy and result-rendering code; Reading relationship labels.
Does deleting the fragment revoke a shared link?
No revocation feature is provided by this static input-link mechanism. Removing the fragment from your current address changes that address; it does not change an already copied message. The app’s share handler creates an address from input fields rather than a server-held access token. Treat sending the full address as sharing the included record. Share and startup handlers.
Is this a permanently saved result?
The link restores inputs and runs the current app; it does not embed an immutable result report. Keep the calculation settings and the version or checksum with an audit record when reproducibility matters. The ledger here records the app checksum used for these tests. Print is a separate browser action, not an automatically created file or an online archive. Versioned test ledger; Share and print handlers.
What concern prompted this check?
A public reader discussion cautions, ensure don’t share it with just ANY person.
That is a reader’s concern, not evidence for supernatural harm. This page answers the narrower, testable question of which recorded inputs travel in a link or copied chart. No new keyword volume or command-service research is claimed. Original reader discussion.
Scope and reproduction
Use synthetic records for a practice replay. Calculate, copy the share address, inspect its fragment, open a fresh tab and compare the visible input record with the resulting chart. For an unknown hour, confirm both the empty time field and Unknown / Not inferred output. The ledger supports these observations in this build; it does not certify universal privacy, historical-clock accuracy or predictive claims. Inputs and outputs; Request targets.