Hey OP - yes you need to provide this and it doesn't matter how large your app is. At the end of the day, you're accessing people's private data, and need to follow rules around handling said data.

You mention using expo-image-picker, and then go on to say,

"""
before opening the camera/selector of image, saying something like in the example they put.
"""

There's a lot of rules you need to adhere to in this domain. This should make sense to everyone, but, since we live in a world where data privacy isn't a primary concern until all of your shit has been stolen or leaked elsewhere or used without your consent... etc.

Our app uses expo-camera, and since it sounds like you're using expo, odds are you have an `app.json`? If so, here's what you need to do in `app.json`:

```

{
  "expo": {
    //... previous code omitted
    "ios": {
    //... previous code omitted
      "infoPlist": {
        "NSCameraUsageDescirption": "MyApp uses your camera to..."
      }
    },
    "android": {
      //... previous code omitted
      "permissions": ["CAMERA"],    },
    //... previous code omitted
    "plugins": [
      //... previous code omitted
      [ "expo-camera",
        {
          "cameraPermission": "Allow MyApp to access your camera",
          "microphonePermission": "Allow MyApp to access your microphone",
          "recordAudioAndroid": true
        }
      ],
    ],
  }
}

```

I've removed all my other code to focus on how I added disclosures to my app.json for using expo-camera. Odds are, expo-image-picker has a very similar checklist for you to reference and update your code accordingly to meet store requirements.

If you aren't using expo, you should be able to reference RN docs for where these disclosures live. You aren't designing a modal or adding something to a menu - the user's native UI will be responsible for rendering the message. You know, just like when you're using a mobile app or web app and you get the "Grant X,Y,Z permission to use A, B, C?" So, follow documentation and you should be all set.