# App data
Source: https://docs.aden.space/docs/help/more/app-data

Custom fields a connected app keeps on anything in Aden (tracks, albums, events, playlists, teams, users, organisations, ...), for what Aden has no field for yet. Namespaced per app, same access rules on the MCP and the API.
{/* Generated by `bun docs:publish` from docs/features/app-data.md: edit the spec, not this file. */}

## What it is [#what-it-is]

When an app you connect to Aden (ChatGPT, your own website, a tool built on the
Aden API) needs to remember something Aden has no field for, it can keep it as
app data on anything in Aden: a track, an album, an event, a playlist, a
contact, a team, an organisation, or you. A mood, an external id, a
sync status, a note for your label's own system.

Each app only sees what it saved itself. Disconnect an app and its data stays
attached to that app, never to another one.

## Using it [#using-it]

* **In ChatGPT**: ask "save the mood 'late night' on Donuts". ChatGPT confirms,
  then keeps it. Ask for it back any time.
* **From your own app**: `GET`, `PUT` and `DELETE` on `/api/v1/app-data` with
  `entityType`, `entityId`, `key` (and `value` to save). A read-only key or a
  read-only connection can read but not save.

Limits: 64 KB of JSON per value, 100 keys per app on one thing.