Orki Music Player
Privacy Policy
Effective date:
Your music can stay on your device. Google Drive and in-app feedback are optional. This policy explains what each feature sends, how the information is used, and your controls.
Local playback does not require a Google account or a media upload. Google Drive and feedback are optional. Feedback is sent only when you submit it. Connecting an account authorizes access to account and permitted file information; uploading or restoring audio requires you to confirm a transfer.
1. About this policy
Orki Music Player (the “Application”) is provided by Shenzhen Shuji Technology Co., Ltd., operating as ByteSailor (“we,” “us”). This policy covers the Application, including its optional Google Drive backup and restore feature and optional in-app feedback. Our Terms of Service describe the conditions for using it.
You do not need to register a ByteSailor account for local playback. Connecting Google Drive is a separate, optional authorization. Using the Application or accepting its terms does not, by itself, authorize access to your Google Drive or an upload of your files.
2. Local media and device permissions
- Audio, video and storage access: the Application reads permitted local media to scan your library, play files, display their information, and carry out media-management actions you request. When you confirm a Drive transfer, it also reads selected audio for upload or saves restored audio on your device.
- Notifications: these provide playback controls, media-library notices, and the status and controls of submitted cloud transfers, subject to your Android settings.
Permissions are requested through Android and can be managed in device settings. Refusing or withdrawing a permission can limit the feature that needs it. Local playback does not require uploading the audio or video itself; analytics and diagnostics are described separately in section 6.
The Application does not request precise device location. Network services may receive your IP address, which can indicate an approximate location.
3. Optional Google Drive backup and restore
When access and transfers happen
When you connect and authorize a Google account, the Application reads account details, storage quota and file information available under that authorization to show your connection and cloud library. Audio is uploaded or restored only after you confirm the selected files. The backup selection may initially include all eligible songs; you can change it before confirming.
Submitted tasks may continue in the background or resume after an interruption. This continues work you already submitted; it does not automatically upload newly discovered songs.
| Data | Purpose and scope |
|---|---|
| Selected audio | Supported MP3 files are transferred as original audio, including tags, artwork and lyrics already embedded in those files. |
| Song edits and custom covers | Application song information, including title, artist, album and whether fields were edited, is stored with the backup. An actual custom JPEG cover is stored as a separate attachment. Embedded artwork remains part of the original audio. |
| Google account information | Account identifier, email address, display name, profile-picture information and storage quota identify the connected account and show its available storage. |
| File information | File identifiers, names, types, sizes, timestamps and checksums help display the cloud library, verify transfers, avoid duplicate uploads and associate cloud files with local songs. |
Playlists, favorites, playback history and manually added lyrics are not backed up. Lyrics embedded in an audio file are included because they are part of that original file.
Permissions and file access
The Application requests only the Google Drive drive.file permission. It does not grant access to your entire Drive. The Application can list and restore supported MP3 files already authorized for it, including its own backups and authorized files created outside the Application.
External audio is read-only within this feature. The Application updates or deletes only backups it created; associated cover attachments are deleted only after their ownership and association have been verified. Moving a file into a folder does not, by itself, grant the Application access to it.
Where the data goes
Your device connects directly to Google Drive over HTTPS. Audio and custom cover attachments are stored in your personal Drive and use your storage. ByteSailor does not receive or store your audio or Google account details on its own servers through this feature. It does not provide public music distribution or cross-user sharing.
Limited Use of Google data
We use Google user data to provide the account, backup, restore, verification and file-management features described here. We do not sell it or use it for advertising, marketing, or training artificial intelligence or machine-learning models.
Orki Music Player’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and the applicable Google Workspace user data policy. General provisions elsewhere about service providers, disclosure, retention or business transfers do not expand these permitted uses.
4. Storage and retention
| Data location | What is retained |
|---|---|
| Your Google Drive | Completed backups and their attachments remain until deleted by you or otherwise handled under Google’s policies. They do not have an Application-imposed 24-month expiry. |
| Application storage | Connection caches, transfer records and file associations support display, verification and recovery. They may remain after disconnection; no fixed automatic expiry is promised. |
| Task temporary files | Files belonging exclusively to a task are cleaned up after success or explicit cancellation. Paused or retryable tasks may retain audio, information snapshots and covers needed to resume. Remote attachment cleanup requires verified ownership and working access; it may be deferred when the result of an earlier operation is uncertain. |
| Public device storage | Restored audio that has already been published to device storage remains independently of the task and the Application. Manage it using your device’s file or media tools. |
| Submitted feedback | Completed feedback has no fixed automatic expiry. We review whether it is still needed and periodically clean up failed, incomplete or invalid uploads. Deleted objects have a 7-day soft-delete recovery period. Support copies and service records are managed separately. |
| Diagnostics and support | These are retained as needed for the purposes in section 6, applicable service settings, legal obligations and resolving requests. Google’s service-specific retention practices are described in its privacy documentation. There is no single 24-month rule for all Application data. |
5. Disconnecting and deleting your data
- Disconnect in the Application: disconnection stops unfinished cloud tasks and attempts to revoke access. If revocation fails, the Application tells you. Local connection caches, task records and file associations may remain.
- Revoke through Google: use Google Account connections to review and remove the Application’s access. This changes access permissions, not the existence of your saved files.
- Delete cloud files: manage and delete them in Google Drive. Within the Application, you can explicitly confirm permanent deletion of backups it created. The Application verifies associated cover attachments before cleaning them up; attachment cleanup can be delayed or fail separately. External audio cannot be deleted through this feature.
- Delete local media: use your device’s file or media-management tools to remove restored files.
- Delete local Application records: Android’s “Clear storage” or “Clear app data” control removes local Application data. It also resets other settings and media-library records, not just Drive records.
Disconnecting, revoking access or uninstalling does not delete completed cloud backups or public downloaded files. Stopping or ending a transfer also preserves copies already completed.
For submitted feedback, email support@bytesailor.com with your feedback reference and necessary locating information. See the feedback retention and deletion explanation, including the 7-day soft-delete recovery period. This request does not delete your personal Google Drive files.
For questions or requests about information processed by ByteSailor, email support@bytesailor.com. This contact route does not automatically delete files in your personal Drive or on your device.
6. Diagnostics, service operation and support
The Application uses Google Analytics for Firebase, Firebase Crashlytics, Performance Monitoring, Remote Config and Cloud Messaging to understand usage, diagnose errors, monitor performance, deliver configuration and support notifications.
This processing can include device and operating-system information, app version, device or installation identifiers, IP address, network information, installation and permission events, playback activity and related media information, crash reports and diagnostic logs. Notification delivery uses a messaging token, which may also be included in service-operation reporting. Identifiers and event-level records are not necessarily anonymous.
If you contact us, we process your email address, message and any information you choose to provide so we can respond and resolve the request. We do not use the Google account email obtained for Drive access to send marketing messages.
The Application version with the Drive feature does not include AdMob advertising. If you use an earlier ad-supported release, its advertising service may process advertising identifiers and ad interactions as described in Google’s advertising privacy information. This does not permit using Google Drive data for advertising or marketing.
7. In-app feedback
Feedback is optional. When you choose to submit it, we receive your category and description, the photos or videos you select, and any email address or WhatsApp number you provide. Diagnostic logs are sent only if you enable that option. Basic app and device information, including the app version, Android version, device brand and model, and interface language, is included with the feedback even when logs are off. Please check attachments for personal information before sending.
Firebase Authentication assigns an authentication identifier without requiring a registration screen. When available, we also include the Firebase Analytics app-instance identifier and may use it to relate your feedback to app activity to investigate the issue. If that identifier is unavailable, feedback is stored separately without it. These technical anonymous flows do not mean that a submission containing identifiers, contact details or identifiable attachments is completely anonymous. Submitting feedback does not change the app's Analytics settings.
We use this information to handle feedback, diagnose problems, contact you when necessary, and protect the service. We do not use feedback for AI classification, automated AI replies or AI training in this feature. Only authorized personnel may handle it. If you provide contact details, we may follow up by email or WhatsApp; those communications also involve the relevant communication service provider.
We use Cloud Storage for Firebase, Firebase Authentication and Firebase App Check with Play Integrity. Feedback files are stored in developer-managed private buckets in the United States (us-east1), separately from your personal Google Drive. They do not use your Drive storage allowance. This location statement applies to the feedback buckets, not to all data processed by Google or its SDKs.
Completed feedback has no fixed automatic expiry. We retain it for handling feedback and investigating issues, periodically review whether it is still needed, and remove it when its purpose ends or in response to applicable deletion requests. We periodically remove failed, incomplete or invalid uploads. Deleted objects remain recoverable under a 7-day soft-delete policy. Authentication and other service records, downloaded support copies, emails and WhatsApp communications are managed separately. We retain those records as needed for support, security and applicable obligations, and remove our support copies when their purpose ends. Uninstalling the app does not delete submitted feedback.
To request deletion, email support@bytesailor.com with your feedback reference and the information needed to locate it. We may need to verify that the request concerns your data. We will explain any recovery period or information that must be retained.
The app keeps one draft and a fixed submission snapshot in private app storage. Work already submitted may continue while the app process runs; after a process interruption, you can retry manually. Local draft, attachment and submission files are cleared after success or explicit discard. A small rotating local diagnostic log contains timestamps, fixed component and event codes, severity and exception class names. It excludes your feedback text, contact details, identifiers, file paths and tokens. These local logs are uploaded with feedback only when you enable the diagnostic attachment option.
8. Third-party services and disclosures
Google processes data under the policies applicable to its services. These links provide more detail:
- Google Privacy Policy — including Google Play services and Google Drive.
- Google Drive Terms of Service.
- Privacy and Security in Firebase — including Analytics, Crashlytics, Performance Monitoring, Remote Config, Cloud Messaging, Cloud Storage, Authentication and App Check with Play Integrity.
- WhatsApp Privacy Policy — when you choose WhatsApp for support follow-up.
- Google API Services User Data Policy and Google Workspace user data policy.
For information we process, we may use service providers to operate the Application and handle support, and disclose information when required by law or necessary to protect security and legal rights. Google user data remains subject to the restrictions in section 3; this paragraph does not authorize broader sharing or marketing use.
9. Security and your rights
We use reasonable technical and organizational safeguards, including HTTPS for Drive transfers. No storage or transmission method is completely secure. Google and other service providers may process information in countries other than your own, subject to applicable data-protection requirements.
Depending on your location, you may have rights to access, correct, delete or obtain a copy of your personal information, or object to or restrict processing. Contact support@bytesailor.com to make a request. We may need to verify your identity to handle it.
You can manage device permissions in Android settings and Drive access through the controls above. Uninstalling stops further processing by that installation of the Application; it does not automatically erase information already held by a service provider, your cloud backups or public device files.
10. Children
The Application is not directed to children under 13, or the minimum age required by applicable local law. We do not knowingly collect personal information from children in that group. If you believe a child has provided personal information to us, contact us so we can investigate and take appropriate action.
11. Changes and contact
We will update this page and its effective date when this policy changes, and provide additional notice where required. New uses of Google user data that require consent will be disclosed and presented for consent before those uses begin; continued local playback is not a substitute for that authorization.
Provider: Shenzhen Shuji Technology Co., Ltd. (ByteSailor)
Privacy contact: support@bytesailor.com