The Fit LibraryFit & Measurements

Body Passport

Body identity layer

A customer-owned identity layer for body measurements, fit history, and body-linked garment knowledge.

What it means Why it matters Related readings Trust & foundations FAQ

Definition

Body Passport is the identity layer within Size Passport that stores a person's body measurements, fit history and garment knowledge as a permanent, portable record owned by the individual rather than held by any brand. Size Passport is the product; Body Passport is the thing the product carries. The distinction matters when the platform talks to different audiences: a customer buys a Size Passport, an operator integrates against a Body Passport, and a regulator reads it as a personal data record with an owner and a permission model.

For the person

For customers, Body Passport means their body data becomes something they carry and control, not something they repeatedly surrender. You decide who reads it, for how long and for what. Nobody has to take your measurements again to earn the right to sell to you, and nobody keeps a copy of you after the relationship ends except by your leave. The practical test is what happens when you stop buying from a house: the record you built there does not stay there.

For the ecosystem

As a category term, Body Passport frames the company as identity infrastructure for fit data rather than a single-brand application, and identity infrastructure is a different business from tooling. Tooling competes on features and is replaced when a better tool appears. Identity infrastructure competes on trust and neutrality, and is replaced almost never, because switching costs fall on everyone who has integrated against it rather than on the operator alone.

Why it matters

Why this page matters in the wider system.

The term gives the market a human-readable name for customer-owned fit identity, and distinguishes the platform from tailoring software, e-commerce tooling and CRMs, all of which store similar numbers under a completely different ownership assumption. That assumption is the whole argument. A CRM holds measurements so the brand can serve you better next time; a passport holds them so you can serve yourself at whichever house you choose. The data can be identical and the arrangement is opposite, which is why the naming is not decoration. It also settles a question operators ask early: what happens to the record when the commercial relationship ends. Under the CRM assumption the answer is nothing, because it was never yours. Under the passport assumption the record leaves with you and the operator keeps only what you left them.

Anchors body measurements, fit history and garment-linked knowledge to the person rather than to an account at one operator.

Separates identity from any single atelier, retailer or brand system, so no operator's failure or acquisition takes the record with it.

Supports customer-controlled sharing with explicit, scoped and revocable grants rather than blanket consent at sign-up.

Keeps every contribution attributed to its source, so an operator reading the record knows whose observation they are acting on.

Remains exportable in a structured format, because a record you cannot take out is not one you own.

This idea becomes clearer through the others around it.

DefinesFit & Measurements

Size Passport

Portable fit record

Size Passport is the public product expression of the broader Body Passport idea.

RecordsFit & Measurements

Fit Memory

Longitudinal fit continuity

The record becomes valuable because it preserves what changes over time.

Depends onSharing & Access

Trusted Record System

Trusted system for shared fit records

The concept only works if the underlying system remains operator-neutral.

Questions answered clearly

Direct answers for people, search, and AI systems.

Is Body Passport the same as a customer account?

No. An account is a login surface. Body Passport is the conceptual record that persists across operators and interactions. You can close an account at one operator without losing the record, which is the practical difference — and the reason the two are named separately rather than treated as one thing.

Why not just call it a profile?

Because profile language usually implies a brand-owned or application-owned object. Passport language emphasises portability, continuity and customer control — and those are exactly the three properties that distinguish this from every fit record the industry already has. The word is doing work, not decoration.

Who controls a Body Passport record?

The customer. Access is always initiated by the individual. No brand, atelier or platform administrator can access or share a Body Passport without an explicit grant from the record holder, and every access is logged so the holder can see who read what and when.

Does a Body Passport store clothing preferences as well as measurements?

Yes. Alongside body measurements it stores fit preferences, garment history and operator-contributed fitting notes, all attributed to their source and under the customer's control. The preferences are often the harder half to reconstruct: a measurement can be retaken, but the fact that you never button a jacket is only knowable if someone wrote it down.

What happens to a Body Passport if the platform behind it closes?

The record is exportable at any time in a structured format, which is the answer to that question and the reason the format matters more than the platform. A passport that only works inside one company's software is a profile with a better name. The export is the part that makes the ownership claim true rather than rhetorical.

Is a Body Passport biometric data under GDPR?

Directly captured body dimensions do not automatically meet the Article 9 threshold, which concerns biometric data used to uniquely identify a person. But a detailed body profile can re-identify someone across platforms, so the record is treated with Article 9-level care regardless of how the threshold question resolves. Operators running body-inference models should take a legal opinion specific to their own data flows.