Why Perity does not need your real name
Privacy is one of those words tech companies have rubbed smooth. Everybody says it. Almost nobody means the same thing by it.
For Perity, privacy starts with a very plain idea: the app can help you understand your body without needing your legal name attached to every clinical detail. Your hot flashes, panic spikes, luteal rage, labs, HRT changes, sleep crashes, and doctor reports do not need to be welded to the identity you use at work, in court records, on social platforms, or with an insurer.
That matters because this is not recipe data. It is reproductive health data. In 2026, in much of the United States, that is not theoretical risk. It is legal risk, employment risk, insurance risk, family risk, and plain old creep risk.
The short version
Perity asks for a nickname, not your real name. The product is being built so clinical records are structurally separated from identity and stored in BAA-covered infrastructure, not in some random app database with your name on every row.
I cannot just open an admin screen and browse your symptoms, labs, meds, or notes. Clinical access is designed to require authentication from your side: MFA at sign-in, then a device gate before health data renders. If your device is not opening the door, Perity should not be showing the room.
When you export a report, the goal is simple: useful to a doctor, useless to anyone trying to profile you. Name, email, device ID, and direct identifiers are scrubbed from the de-identified version before it leaves the app.
That does not mean de-identification is magic. Rare combinations of facts can still be identifying. Anyone who tells you otherwise is selling confidence, not safety. But "not perfect" is not the same as "don't bother." We reduce the blast radius by not collecting what we do not need, separating what must exist, and making export choices explicit.
Why FHIR is in here at all
FHIR sounds like something a hospital procurement committee invented during a hostage situation. Unfortunately, it is also useful.
FHIR is the standard many health systems use to structure clinical data. Perity uses it because your symptoms, labs, meds, observations, and reports should be meaningful outside the app. If your data only makes sense inside Perity, then Perity owns the shape of your story. I do not want that.
So yes, under the hood, Perity maps clinical data to FHIR R4. Not because normal people should have to care about standards. Because standards are how you get out. They are how a doctor, researcher, or future tool can read the data without me sitting in the middle as the interpreter.
No venture capitalist money is part of the privacy design
This is not a moral flourish. It is structural.
When a health app raises venture money, pressure enters the room. Grow faster. Capture more. Segment users. Prove lifetime value. Turn behavior into prediction. Turn prediction into revenue. Maybe nobody says "sell the perimenopause panic graph," but the incentives know where to walk.
Perity takes no venture capitalist money. If outside funding ever happens, the plan is female angel investor syndicates only. Every person who ever touches production data is personally vetted by me. Your data is not an asset on someone's cap table.
The point
I want Perity to help you walk into a medical appointment with receipts: here is when the anxiety spikes, here is what changed after HRT, here is the sleep crash, here are the labs, here is the pattern I could not explain in twelve minutes while wearing a paper gown.
I do not want the price of those receipts to be your identity, your future insurability, or your right to keep parts of your body private from systems that have never earned your trust.
That is the line. Perity is built on it.
Join the waitlist if you want early access. Use a handle. That is enough.
— EiEi, @perityapp