Size Passport is built around customer-owned fit data.

Size Passport may store account details, Fit Passport identifiers, body measurements, garment measurements, fitting notes, QR usage, wallet-pass metadata, exports, and partner intake submissions. Some records are provided directly by the customer and others are contributed by approved operators during a fitting flow.

When a brand or atelier interacts with a customer passport, Size Passport may also store permission events, grant timestamps, and the identity of the contributing operator or organization so the contribution history remains auditable.

Size Passport uses data to operate the Fit Passport, show the customer’s current and historical measurements, support QR and wallet access, process exports, and keep an access log of who requested or received permission to contribute to the record.

We also use limited operational metadata to keep the service reliable, investigate failures, prevent abuse, and understand whether launch-critical flows such as exports, scans, and wallet issuance are working correctly.

Size Passport is permission-aware. A customer record is not automatically public to all brands or operators. Access is granted through explicit permissions, owner approval flows, or tightly scoped operational grants such as a temporary scan session.

Size Passport does not sell customer fit data. If a customer chooses to export their record or grant access to an operator, that action is treated as part of the product’s portability and consent model.

Operational records are retained only as long as needed for the service, security, auditability, portability, and legal compliance. Export artifacts may expire and be deleted after their configured retention window. Customers can also use account deletion routes where available.

Questions about privacy or partner access should be routed through the live Size Passport contact and intake surfaces so requests remain reviewable in the launch workflow.