PlaysoloistWindsDiziPrivacy
Dizi Privacy Policy
Last updated: 19 July 2026
This policy covers Dizi: Flute Tuner & Lessons, bundle identifier com.uptrail.dizi.
Microphone and local practice data
Tuning, key finding, long-tone checks, and phrase grading process microphone input live on your device. Dizi does not upload raw microphone data or practice recordings. A recording is created only when you choose the separate Record tool, and that file remains in the app container. Phrase attempts, independent kaoji runs, and teacher-report details remain local. The service can accept only a bounded lesson-progress summary for synchronization; it does not receive phrase-attempt, kaoji, or teacher-report evidence.
Anonymous installation identity and Sign in with Apple
On first use, Dizi creates a random anonymous installation UUID and stores it locally. When you are not signed in, Dizi may send that UUID in the X-Device-Id service header for anonymous entitlement and bounded progress requests. It is not an advertising identifier, is not derived from a hardware identifier, and is used only to keep one installation’s service records separate from another’s.
Core tuning and practice require no account. Network Coach and cloud receipt linking require Sign in with Apple. Dizi requests no name or email scope. Apple supplies an app-specific pseudonymous identifier; our regional service stores that identifier, profile creation and last-seen times, and a revocable session record. Sessions expire after 30 days.
Coach
When you invoke network Coach, Dizi builds a bounded request from synthesized recent-practice metrics: take count, average cents offset, average stability, and the lowest-stability note targets. Version 2.3.7 has no free-text Coach input. The app-generated request passes through our regional service in Sydney to an AI-processing provider solely to generate a reply. Raw audio, recordings, the complete practice database, and per-frame microphone evidence are not sent. Dizi does not store Coach request or reply text in its application database.
Purchases and service records
- Subscription verification — after Sign in with Apple, Apple's signed transaction and subscription-notification data may be processed to link Pro access across devices and handle renewals, expiry, revocation, and refunds. Records include pseudonymous transaction identifiers, product, status, signed-event and expiry times, and notification identifiers; not your name, email, card details, or audio.
- Service limits — monthly Coach counters enforce the allowance shown in the app and are set to expire after 70 days. Notification-deduplication events are set to expire after 35 days. Active entitlement, transaction-ordering, profile, and progress records remain until account deletion or until no longer operationally or legally required.
- Operational logs — service function logs are retained for one month for security and reliability. Application code does not intentionally log Coach request text, Apple identity tokens, session tokens, receipts, or audio.
Deletion
Use Settings → Delete Account & Data to request deletion of the profile, sessions, Coach counters, cloud progress, entitlement, notification, and transaction-binding rows linked to your service identity, and to erase local SwiftData practice rows and private recording files. If cloud deletion succeeds but local cleanup is interrupted, Dizi marks cleanup as pending and offers a retry without restoring the deleted cloud account. Deleted rows may remain temporarily in encrypted rolling backups before backup expiry, but are not available through the live service.
What we do not do
- No advertising, cross-app tracking, or third-party analytics SDKs.
- We do not sell personal data or use Coach requests to build an advertising profile.
- We do not upload practice audio.
Children
Dizi is not directed at children under 13. Version 2.3.7 synthesizes Coach requests from bounded practice metrics rather than accepting user-entered free text.