> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omneo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Gender

> How Omneo handles the gender profile field and considerations for inclusive data capture.

Omneo stores gender as a free-text string field (`gender`) on the profile. There is no enum restriction, you can capture whatever values are appropriate for your customer base and communication strategy.

## Common values

Most implementations use one of:

* `"male"` / `"female"` / `"non-binary"` / `"prefer-not-to-say"`
* `"M"` / `"F"` / `"X"`

Standardise on a consistent format within your implementation and document it, as this value may be used by your comms platform for personalisation (e.g., gendered salutations).

## Omneo appearance attributes vs the gender field

The `gender` field is separate from appearance attributes. Appearance attributes (clothing sizes, style preferences) are stored in `attributes.appearance` and used for in-store personalisation. The `gender` field is used for demographic reporting and, if you choose, comms personalisation.

## Considerations for non-binary and inclusive programs

If your brand serves diverse communities, consider:

* Not making gender mandatory during join
* Not using gender for communication salutations (use `first_name` instead)
* Treating size/style preferences as separate from gender identity

Omneo's flexible free-text field means you are not constrained by a fixed enum, you can adapt to your brand's values and customer expectations.