Compatibility Reading Privacy: What You Type, What You Share

A compatibility form looks casual: two dates, maybe two times, a paragraph about last week. Banks and password resets use birth dates as identifiers. A time and city are enough to build a chart and, in some places, to narrow who a person is. You are not typing a joke.

Compatibility-reading privacy means treating two people’s birth details and the situation you write as data you chose to store, not as flavor text that disappears when you close the tab. Generating a report is one decision. Forwarding it is another.

The browser format is online relationship reading explained. The wider app-policy checklist is astrology app privacy. The input list is what you need for a compatibility reading. The sequence that stores the result is how a relationship reading works.

What you are actually typing

A compatibility sitting usually includes some mix of full birth dates, optional times and cities, names or labels, a relationship type, and a written situation. Dates alone already support numerology and a limited chart or pillar comparison. Times unlock angles, houses, and the BaZi Hour pillar. The paragraph is the part that can contain other people’s words, workplaces, and private conflicts.

You do not need every field to have a useful sitting. Extra fields are not extra intimacy. They are extra surface. If a time is unknown, leave it blank. If a city is a guess, omit it. If a message thread is not required to explain the cancelled dinner, do not paste the thread.

Do I need a birth time is the yes-or-no companion. The privacy version of that page is simpler: do not invent a time to satisfy a form, and do not collect a time you were not given.

This journal cannot audit a server. A privacy policy is a claim until someone independent can see the system. Read the policy for account creation, storage, deletion, and whether a preview requires a card — then treat those answers as the vendor’s statements, not as a penetration test you performed.

A checklist before you submit

1. Whose dates are these, and do you have a decent reason to have them? A birthday they celebrate with you is different from a date you scraped.
2. Are you on a shared laptop, a work network, or a logged-in browser that is not yours? If yes, stop. Finish the sitting on a device you control.
3. Does the context box include anyone else’s private messages, health details, or money figures the question does not require? Delete those lines.
4. Will this account stay yours? A shared email or a partner’s Google login makes My Readings a shared drawer.
5. If you would be uncomfortable showing the other person the form as you filled it, that discomfort is information. Either rewrite the context or do not generate the report.

How to write context keeps the paragraph short enough to be specific and small enough to be decent. A compatibility reading for one person is the solo-use ethic; this page is the data ethic.

A fictional shared laptop

This person is invented. Chris lives with two roommates and uses the apartment laptop that stays signed into a browser profile. After a breakup, Chris enters an ex’s birth date and a long context box about the last month, creates a preview, and leaves the tab open.

A roommate later opens the same profile. The dates, the paragraph, and the preview are sitting there. Chris did not “share” the reading in a chat. The sitting was still published to the room.

A better sitting: Chris uses their own phone, their own Google account, a short context that names one moment without a message archive, and closes the session. If they want the report later, My Readings is still there on that account. The kitchen table is not a vault.

Sharing is a second publication

A screenshot in a group chat is a publication of someone else’s birth details plus an interpretation they may never have seen. So is a PDF forwarded to a parent, a friend, or an office chat. So is reading the report aloud as if the other person were a case.

If you generated the sitting together and both people want a copy, that is a shared document. If you generated it alone, keep it alone unless they ask. How to share an astrology reading is the forwarding protocol. Should we read a compatibility report together is the shared-sitting protocol.

Do not use a percentage graphic as a safer share. A number still implies two people’s data went into a tool. It travels farther because it is small.

What Whisper stores in this product

Whisper’s Relationship Reading uses Western astrology, BaZi, and numerology on the birth details you enter. It asks you to continue with Google and describe the situation you want to explore. Birth time and city are optional. The text is AI-generated for personal reflection; it is not a live consultation. A free preview requires no card. The full reading is a US$29 one-time purchase; no membership is required. The preview and any purchase stay in My Readings when you use the same account.

That account is the privacy boundary you can actually control from your side: whose Google login, which device, how short the context is, and whether you forward the page.

Create a preview only with details you are willing to store. Write the moment. Leave guessed fields blank. If you cannot say where this sitting will live, do not start it.

Questions readers ask

Is a birth date sensitive?

It can be. It is used in identity checks, and in this product it is linked to another person and a written situation. Treat the bundle as worth protecting even if a single date feels ordinary.

Does a free preview collect less?

On Whisper, the preview still uses the details you entered. Free is a payment state, not a smaller data set. Enter only what the sitting needs.

Can I delete what I typed?

Check the product account and privacy materials for current deletion and retention terms. This journal cannot certify a backend. The product page remains the place for current practice.

Editorial note

This page is a reader checklist, not a security audit. Whisper’s product details were checked against the current Relationship Reading page on October 22, 2026. Prices, terms, and privacy practices can change; the product page remains authoritative.