What it does
Most people already keep some record of their intimate life: a note on a phone, a line in a diary, a spreadsheet of dates. The awkward part is that those notes are not only about them. They describe someone else in detail, and that someone usually has no idea the notes exist and no say in what they contain.
M.BODYCOUNT starts from that asymmetry. You record what you want, as precisely as you want, and every single field carries its own control over who may see it. The control on its own does nothing: the person a card describes gets a page where they read what has been written about them, value by value, and decide field by field what is allowed to leave.
A spreadsheet can hold the same dates. What it cannot do is give the other person a vote.
One card per person, four ways to read the archive
Each person gets a card: names, dates, places, physical and personal traits, and nine emotional dimensions of the relationship, from desire to autonomy. The same archive can then be read as a list, as a timeline, as a map of where things happened, and as a constellation in which distance from the centre carries a meaning you choose.
Six privacy levels, one per field
Every field carries its own control: only me, only me and the other person, only people you both know, everyone except a chosen list, only a chosen list, or public. Only me is where every field starts. The rule is enforced inside the database rather than in the interface, so what the screen promises and what actually leaves cannot drift apart.
The other person reads the card, and decides
Whoever a card describes can open it and see the fields with the values inside, not a list of labels, because a yes given to a list of labels is a signature on a blank page. They answer one field at a time, and nothing leaves without that yes. Ethnicity, religion, skin colour and health data sit in a separate block with their own explicit consent, since a yes given above does not count for those.
Who it is for. Adults who keep track of their intimate life and would rather not do it behind someone’s back.
What it is not. Not a dating app and not a social network: there is nobody to browse, nothing to publish, and no public score.
Where it stands
It is a working prototype: it runs end to end, with the full consent model, the review page, the comparison and the messaging in place. What stops it from going online is not code.
The privacy policy, the cookie policy and the terms are drafts, with placeholders where the legal identity of the operator belongs. Production email has no provider. There is no deploy configuration and no domain. An application that handles data about people’s sex lives cannot go live with placeholder legal texts, so the work that remains is small in lines of code and large in everything else.
The interface is Italian only: an English version does not exist yet.