Local-first direction
Files and recordings should stay on your device where the platform supports local decoding and analysis.
Privacy
Your private practice recordings should not need to become cloud jobs.
GigaChords is designed around a local-first direction: analyze on device where supported, be clear when a network feature is needed, and avoid pretending to be a copyrighted song library.
Offline-capable thinking
The desktop and mobile product should keep core practice workflows useful without requiring every song to be uploaded.
Copyright-safe messaging
GigaChords is a tool for audio you provide or are allowed to use, not a public song hosting service.
What may need network access
Some future features can be online without making the whole product cloud-first.
Accounts, optional sync, store billing, beta updates, or a future web demo may require network access. The privacy promise is to keep those boundaries obvious and avoid surprise uploads.
Plain-language policy
Tell users what happens to their file before analysis starts. If a feature cannot run locally, label it clearly and give users control.
Get early access to the chord timeline app built for real practice.
Join the beta list and help shape the first public GigaChords builds.