Release checklist: Before App Store submission, verify this page against the exact production build, backend behavior and every third-party SDK. App Store Connect disclosures must match actual data practices.
DjAi Studio is designed around user-selected audio files. Music files should remain under the user’s control, and any temporary working copies should be stored separately and cleaned up when no longer needed. The app does not provide a commercial music catalog; users are responsible for audio they have the right to use.
Permissions
DjAi Studio works with user-selected audio files. File access should be limited to files the user imports or chooses, and any temporary working copies should remain app-controlled and be cleaned up when no longer needed. The app does not require a commercial music-provider account for its core mixing workflow.
Data minimization
Our product goal is to request and process only information needed for the feature the user chooses to use. Permission prompts should appear in context and explain why access is needed.
Third-party services
If analytics, crash reporting, AI services, cloud storage, advertising or other third-party SDKs are included in a production build, their data practices must be evaluated and reflected in this policy and in App Store Connect before release.
Data deletion and privacy requests
If the released version of DjAi Studio creates an account or stores server-side user data, the final product must provide the appropriate account/data deletion path. Users may also visit our Privacy Choices page or contact us.
Security
We use reasonable technical and organizational measures appropriate to the services we operate. No method of storage or transmission can be guaranteed to be completely secure.
Contact
Questions about DjAi Studio privacy can be sent to info@safeandsecurefamily.com.