Metafields and metaobjects can be owned by merchants or apps. Merchant owned metafields and metaobjects are open to merchants and developers, which means there are no restrictions on who can read, write, or modify them. However, you can use reserved namespaces to gain control over your application's data. ## Reserved prefixes There is a reserved prefix your app can prepend to metafield namespaces and metaobject types to take ownership of them. Using a reserved namespace ensures that your app exclusively controls all structure, data, permissions, and optional features. > Tip: > Learn more about [permissions](/docs/apps/build/custom-data/permissions). ## Create metafield definitions with reserved namespaces To establish metafield definitions within a reserved namespace, prefix the namespace with `$app`. The API will automatically convert this to a fully qualified reserved namespace like `app--{your-app-id}[--{optional-namespace}]`: - **`app`**: Indicates that this is a reserved namespace for an app. - **`{your-app-id}`**: Your app's unique API client ID. - **`{optional-namespace}`**: An optional namespace of your choosing. For example, if your app's API client ID is `123456`, you can create both: - `$app` → `app--123456` - `$app:influencer` → `app--123456--influencer` > Note > All APIs default to using a reserved namespace `$app`. **Example:** The following example creates a product metafield definition under a reserved namespace: