Privacy Policy

1. Who we are and what this policy covers

Cadentia is developed and published by Roque Ribeiro under the LEVELHARD brand, in Brazil. This policy covers Cadentia for iPhone (com.levelhard.cadentia, on the App Store), Cadentia for Android (com.levelhard.cadentia, on Google Play), Cadentia for desktop (macOS, Windows and Linux, distributed on this site) and the cadentia.studio website.

For Cadentia, it replaces the corresponding section of the RoqueOS Privacy Policy. What applied there still applies here; what changed is the address.

2. The summary

The app collects no personal data at all. It asks for no sign-up, has no account, uses no tracking, shows no ads and ships no analytics or crash-reporting SDK. There is no Cadentia server receiving what you do in the app.

Everything below spells out that summary, permission by permission.

3. Microphone

The microphone is used live, on the device, in three places:

• Tuner: detects the note your instrument is playing.
• BPM detector: measures the tempo of the sound in the room.
• Multitrack recorder: records the takes you asked it to record, and they stay on the device.

Apart from what you deliberately record in the recorder, nothing the microphone hears is saved, and no audio leaves the device.

4. Camera (Strings mode)

In Strings mode with the camera on, the front camera is used to read the position of your hands, frame by frame, on the device: on iPhone through Apple’s Vision; on Android through Google’s MediaPipe Hand Landmarker, with the model files bundled in the app. The result is a set of coordinates that becomes a chord and a strum on the spot.

No image is recorded, stored or sent. The camera is only activated when you choose Camera mode, and Frets and Chords modes work without it. If permission is denied, the app stays whole in those two modes.

5. Stem separation

Separation into vocals, drums, bass and the rest uses the htdemucs model (Meta, MIT license) running on the device itself: in Core ML on iPhone, in ONNX Runtime on Android and on desktop. The song you separate is not sent anywhere, and the separated tracks stay on the device until you delete them.

On Android, the separation model may be downloaded the first time you separate a song. That download is a transfer of our file to your device, with an integrity check. Nothing of yours travels the other way.

6. Computer audio (Cadentia for desktop)

Cadentia for desktop captures the audio the system is playing in order to separate it live. The capture happens in the computer’s memory, is processed there and is not written to disk, except when you ask to separate a file from your library, in which case the tracks go to the app’s data folder.

The app asks for the operating system’s audio-capture permission the first time. Without it, the library and the instruments keep working.

7. What stays on the device

The app stores, on the device only and only for you:

• Recordings from the multitrack recorder and the exported mixes.
• Separated tracks and the list of recent songs.
• Tablature, practice playlists and the per-song settings (pitch, speed, mixer).
• Preferences: chosen tuning, reference in Hz, language, sound bank.

Deleting inside the app removes the item. Uninstalling the app removes everything. None of it passes through us.

8. RoqueOS library (optional)

If you want, you can pair Cadentia with your RoqueOS account using a short code, to list and download the songs already in your library. It is the only part of the app that uses the internet, and it is optional: without pairing, everything else works the same.

In that case, the app sends the pairing credential and the list and download requests to the RoqueOS server, and the RoqueOS Privacy Policy applies. The credential lives in the iPhone Keychain or in Android’s protected storage, and disconnecting in the app erases it.

9. The cadentia.studio website

The site is hosted on Firebase Hosting, by Google, and the domain goes through the Cloudflare network. Like any web server, both log the IP address, the page requested, the date and the browser of each visit, in technical records they keep for a short period to run the service and which we do not use to identify anyone.

The site uses Google Analytics for Firebase to count visits in aggregate: how many people opened the page, from which country, on which screen size, which sections were seen and which buttons were clicked. When you arrive, a notice asks whether Google may set an identification cookie in your browser. Until you answer, Analytics runs in consent mode: it receives page-view and click signals with no cookie and no browser identifier. If you accept, the cookie is set and later visits are counted as the same browser. If you choose essential only, nothing else is sent to Analytics. The choice is saved in your browser and can be changed under Cookie preferences, in the footer. We run no ads on that data and cross it with nothing.

The download section reads a version file from Firebase Storage to show the current version of each installer. That request sends nothing beyond the HTTP request itself.

Each click on a Cadentia for desktop download button goes through our server before reaching the file, to count how many downloads each version and each system had. The record keeps the version, the system, the date and time, the browser and operating-system family, the approximate country and the domain of the referring page. It keeps no IP address and no identifier of a person or a browser, and cannot be linked to you.

10. Children

Cadentia is rated for all ages. Since it collects no data, it collects no data from children. If you believe some data reached us by mistake, write to the e-mail below.

11. Your rights

Brazil’s data protection law (LGPD) and similar laws grant access, correction, deletion, portability and information about the processing of personal data. With Cadentia there is no data of yours on our side to access or delete; what exists is on your device and you delete it directly. The data deletion page explains how. For any request, use the e-mail below.

12. Changes to this policy

If the app starts doing something different from what is written here, this page changes first, and the date at the top changes with it. Relevant changes are announced in the release notes on the stores.