Clarification on Disk Space APIs - volumeAvailableCapacityForImportantUsageKey

Our application uses Disk Space API, specifically volumeAvailableCapacityForImportantUsageKey to determine the available free space on the device. However, we are facing challenges in understanding the reasoning criteria that an application needs to satisfy to use this API effectively.

As part of our application requirement, we present an information modal to the user when disk space is low. Additionally, we log available disk space information and upload the logs to the cloud under certain conditions. We initially thought that E174.1 from the Privacy Manifest Files documentation fits our purpose. However, we are concerned about potentially violating the guideline:

"Information accessed for this reason, or any derived information, may not be sent off-device."

Could someone please provide additional clarity on how to navigate this fine line and ensure that our application aligns with the recommended practices and guidelines while handling disk space-related functionality?

Thank you in advance for any insights or guidance you can provide!

NOTE: We upload the logs to our server for troubleshooting and it may happen without user knowledge. Logs are encrypted and may contain the disk free space information

It doesn’t look like a “fine line” to me - you’re not allowed to send the data off the device, except under the “bug reporting” exception, and that requires that the user interacts with the process of sending the report, not just silently sending the logs in the background.

Clarification on Disk Space APIs - volumeAvailableCapacityForImportantUsageKey
 
 
Q