Privacy
RiffWright privacy
Updated November 3, 2026. RiffWright is provided by Niche-Knack Apps LLC, Ohio, United States. Contact support@nk.tools.
This notice explains the information used by the app and its optional features. Direct downloads, store editions, and separately identified beta builds can have different purchase, demo, update, and diagnostic flows. A feature described here may not be available in every edition.
Your music stays on your device
Songs, riffs, takes, imported audio, microphone recordings, mixes, custom instruments, and exports are stored on your device. Audio editing and analysis run there. Nothing is uploaded or synced. Exports and shares send the files you choose to the destination you select.
The microphone is used when you choose to record or monitor an input, and when you measure audio timing. The timing measurement recording is neither saved nor sent. MIDI input from USB or Bluetooth devices stays on the device. You can remove microphone permission in your device settings; that prevents new recording but does not erase existing takes.
Local work remains until you delete it or clear the app's data. Uninstalling may remove it. Export anything you want to keep before uninstalling. RiffWright disables Android cloud backup and automatic device-to-device transfer of its app data. On other platforms, your operating system's backup settings may apply.
Android builds keep diagnostic, crash, and not-responding logs on the phone. You can export or clear them in Settings. They are never uploaded automatically; review a log before choosing to share it with support.
Never collected
Release editions need no account and offer none: no email address, name, or password is asked for. No analytics, advertising, crash reporting service, or tracking. No location: Android 11 and older ask for location permission only because the system requires it for Bluetooth MIDI scanning, and RiffWright never reads a location. No contacts, photos, files outside the app's own folder, or clipboard reads. No payment-card details: Lemon Squeezy, Google Play, Apple, or Microsoft handle payment.
Store editions and the App Store trial
On iPhone, iPad, and Mac, buying RiffWright or starting the free 30-day trial is an App Store purchase handled by StoreKit and verified on the device. The Google Play edition buys through Google Play Billing, verified on the device. These editions send nothing about the purchase or trial to Niche-Knack and have no key entry. Microsoft distributes and updates the Microsoft Store edition; buying it uses a license key, as described under purchases below.
Releasing a device and browser activation
Releasing a device after a device-limit refusal sends the license key and the identifier of the device being released to nk.tools. Direct downloads show the installation identifier beside the key box. If a device cannot reach nk.tools, you can enter the key and that identifier at nk.tools/activate in a browser elsewhere and paste the returned grant into the key box; nk.tools receives them from the browser, and the app sends nothing.
Updates
Direct downloads check nk.tools for a signed update catalog when opened and at most every six hours while open, and download an installer only when one is offered. The check carries no identifier or credential; the server sees the IP address and the HTTP client's user agent. Store editions are updated by their store.
Sound packs
Sound packs are not on sale in Release editions. Pack previews ship inside the app or are rendered on the device; listening makes no request.
Demo verification
Direct, Google Play, and Microsoft Store editions that use the online demo service contact nk.tools when the demo first starts, and when the original period needs to be recovered after reinstallation, a lost record, or a clock check. The request contains the app, platform, a fresh request identifier, and a one-way, product-specific digest derived from a device identifier. The device identifier is the Android ID on Android, the machine id on Linux, the MachineGuid on Windows, and the IOPlatformUUID on a Mac. The raw value is never sent or stored, and the digest differs for each Niche-Knack product.
The service keeps the digest and original start and end dates, including after the period ends, to prevent reinstallation from creating another demo. This record is pseudonymous, not anonymous; it identifies the same app/device combination. It does not contain your work, name, email address, or payment-card information. A website visit or download does not start the demo. Store-managed trials may use the store's own records instead.
Purchases and licenses
Direct downloads and the Microsoft Store edition buy a license key through Lemon Squeezy; the Google Play, iPhone, and Mac App Store editions buy through their store. The payment provider processes payment details under its own policy. For a direct purchase, Niche-Knack receives the contact, product, order, and license information needed to deliver access, restore it, and handle refunds or disputes.
Entering a license key in a direct download or the Microsoft Store edition sends that key, the app and platform, a device identifier, and a device name to Niche-Knack's license service over HTTPS. The service verifies the purchase and authorized device before returning a signed license. On Android, the device name is the phone's maker and model, such as "Samsung SM-A146U1". On a computer, it is the operating system and the first four characters of the installation identifier, such as "Linux computer 3f0b". The computer's host name is never sent. The installation identifier is a random value the app creates on first run, not a hardware identifier. The app keeps the license locally; activation, restoration, or releasing a device may require another connection. The Google Play, iPhone, and Mac App Store editions verify their store's signed purchase on the device and send nothing about it to Niche-Knack.
Support, diagnostics, and connection information
If you contact support, Niche-Knack receives your reply address, the message, and any name, order reference, report, or attachment you choose to send. Review a report before sending it. Support information is used to answer the request and troubleshoot the problem; it is not sent to website analytics. See the support privacy terms.
Release editions do not automatically upload the beta program's diagnostic reports. Separately identified beta editions require explicit diagnostic agreement and follow the beta privacy notice, including withdrawal controls and the 30-day retention period for raw beta reports. That policy is separate from voluntary support messages.
Servers contacted by the app can receive ordinary connection information, such as an IP address, request time, and client information. Niche-Knack uses operational records for delivery, security, and troubleshooting. This website's cookie-free analytics are described in the company privacy information; they are separate from your app content.
Keeping and deleting information
If you created a shared Niche-Knack support account, use the dedicated account deletion form. Sign in with that account and confirm. This requests deletion across the shared account, not just RiffWright; it does not remotely erase your local work, cancel store billing, or erase device-based demo verification records.
Local work remains on your device until you delete it or remove the relevant app data. Export what you want to keep before uninstalling. Device backups and destinations you choose for exports or sharing may retain separate copies. Deleting one local copy does not remove those copies.
For questions about information held by Niche-Knack, email support@nk.tools. Identify RiffWright and the account or support request, if any. Do not send passwords, complete license keys, or raw hardware identifiers. Verification may be needed before discussing records associated with a person or purchase.
Demo verification records remain after the demo ends. There is currently no user-facing control to delete the server's demo record; contacting support does not automatically erase it or restart the demo. License, purchase, security, or dispute records may also need to be retained for their stated purpose or legal obligations. Ask support about the records involved and any available access, correction, or deletion options.
For information sent to a store, cloud-storage provider, connected assistant, or another service you selected, contact that provider too. This notice does not change their retention or privacy policies.
Back to RiffWright · Company license, privacy, and refund information