1. Scope
This policy applies to EQK for Mac from kuja.dev. Direct and Mac App Store releases use different billing and update systems, so their network behavior is not identical.
2. Audio and listening content
With macOS permission, EQK captures playback audio from the apps you select so it can apply EQ and route the result to your chosen output. Audio processing and analysis happen in memory on your Mac. EQK does not upload or store captured audio.
Song names, app names, listening history and local audio files remain on the Mac. Imported EQ files are read from the file you select and converted into local app settings.
3. Information saved locally
Routes, presets, headphone profiles, preferences, remembered song adjustments, licence details and similar working state are stored locally. On compatible Macs, optional Apple Intelligence refinement runs through Apple’s on-device system frameworks.
4. Licence, recovery and update functions
The direct build connects to kuja.dev to activate, refresh, deactivate or recover a licence and to check for updates. These requests use the information needed for the function, such as the licence key or purchase email, app version, an installation or device reference and limited security data.
The App Store build uses Apple billing and Apple-managed updates. Apple may process purchase, update and diagnostic information under Apple’s policies.
5. Launch count and optional product analytics
EQK sends one identifier-free launch count once per installation. It records the release channel and short app version, not a device or person.
Optional first-party product analytics use an anonymous installation identifier and coarse events that help understand whether features open or complete. No audio, song names, app names, files, payment data, advertising identifiers or precise location enter analytics.
You can disable optional analytics and delete its stored history from EQK settings. Optional analytics remain until you delete them.
6. Optional Contacts and Location access
Contacts and Location are optional and are used locally only if you choose to save Home or Work layouts. EQK can be used without granting either permission. Location and contact information do not enter EQK analytics.
7. Purchases, support and the website
Direct purchases use Razorpay and licence emails use Resend. kuja.dev keeps purchase and licence records needed for fulfilment, recovery, refunds, fraud prevention and legal or accounting duties. Payment card or bank details stay with Razorpay.
The EQK website pages use the website measurement and advertising providers described in the main kuja.dev Privacy Policy. Those website tools are separate from EQK’s in-app analytics.
8. Retention and deletion
Local routes and presets remain until you remove them or delete the app’s data. Optional analytics remain until deleted in EQK settings. Purchase and licence records remain while needed for fulfilment, recovery, refunds, fraud prevention and legal or accounting duties.
9. Changes
This policy may change when EQK or its network functions change. The effective date will be updated.
10. Contact
For privacy questions or help deleting information, email support@kuja.dev.