# `LawfulBasis`

Your lawful reason for using personal data, under GDPR: `consent`, `legitimate_interests` and so on.

Use it to record why you hold a person's data. Which one applies is a legal decision for you to make, not something Jadpo checks.

## Shape

One of these 6 values:

`LawfulBasis.consent`, `LawfulBasis.contract`, `LawfulBasis.legal_obligation`, `LawfulBasis.legitimate_interests`, `LawfulBasis.public_task`, `LawfulBasis.vital_interests`.

## Example

```jadpo
LawfulBasis.consent
```

`text.parse(raw, as: LawfulBasis)` reads one from text that comes from outside. Text that isn't one at all fails `malformed`, such as `legitimate interests`, `6(1)(f)` or `f`.

## Good to know

- `==` tells you whether two are the same. `<` and `list.sort_by` don't take it.

## In JSON

A string, in a request, a response or `json.write`:

```json
"consent"
"legitimate_interests"
```

## Details

<details>
<summary>Text form, storage, how it is shown, and operations</summary>

`LawfulBasis` is in the group Other with a published standard, and has been in Jadpo since 0.1.0.

### Text form

`text.from` writes one standard text form, the same form `text.parse` reads back: `consent` and `legitimate_interests`.

### How it is stored

It is stored in one column named for the field, of type `text`. `legitimate_interests` is stored as `'legitimate_interests'`.

### How it is shown to people

`text.format(value, locale:)` shows it to people in their locale.

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `consent` | `Consent` |
| `legitimate_interests` | `Legitimate interests` |

### Operations

It also takes `text.parse`, `text.from`, `text.format`, `json.read`, `json.write` and `==`. [How every standard type behaves](/docs/every-standard-type-meets-one-contract.md) says how they work.

</details>