---
url: /errors/dek_not_found.md
---
# `dek_not_found`

`dek_not_found`

## Description

No active data encryption key exists for the subscriber requested through the
GDPR enforcement fetch API.

## HTTP Status

`404 Not Found`

## `doc_url` Format

The `doc_url` value is an absolute URL and changes by environment:

`<docs-base-url>/errors/dek_not_found`

## Typical Causes

* A DEK has not been provisioned for the subscriber.
* The supplied subscriber ID identifies an unknown subscriber.

## How To Fix

1. Verify that the subscriber ID is correct.
2. Ensure the creating bounded context provisions the DEK before emitting
   personal data.
3. Retry the fetch after provisioning succeeds.