Thanks for your reply. I did notice that the text you've quoted doesn't include CMMotionManager, but I think I assumed that CMMotionManager was "obviously" included in "APIs that access the device's motion data", and that the docs were mentioning only the other less-obvious ones.
In practical terms, it's obvious to the user that an app is "monitoring their motion" when the user interface is changing based on that motion.
Correct, but it's also obvious to the user that the app is accessing their location when it's flashing a blue spot on a map, yet I still get my apps rejected because my location usage string "doesn't include an example"!
So - if I'm using CMMotionManager, and not any of the other listed APIs, do I need to include the usage description string to get approved? I've just had an update approved with the string present so including it unnecessarily doesn't seem to be an issue.