MIDI Recorder — Privacy Policy

Last updated: 2026-07-31

This policy covers the MIDI Recorder app on both Android and iOS. The two apps share the same code and behave the same way; where a platform differs, it is called out below.

Summary: MIDI Recorder is an offline app. It does not collect any personal data, and it contains no networking code at all — there is no server behind it, and nothing is ever sent to us. On Android it additionally does not hold the INTERNET permission, so it is technically incapable of reaching the network. The only data that ever leaves the app is through the optional Pebble smartwatch integration (Android only): if you turn it on, the app shares your recording status with the Pebble companion app on your phone, which relays it over Bluetooth to your own watch (see below).

What the app stores on your device

Everything the app keeps lives on your device and is removed when you uninstall it. Specifically:

Your MIDI recordings (.mid files) — on Android, saved into a folder you choose through the system file picker; the app only reads and writes inside that folder. On iOS, saved into the app's own Documents folder, which you can browse and export from the Files app.
Your settings (tempo, metronome options, auto-connect preferences, etc.) — stored in the app's private settings storage (SharedPreferences on Android, NSUserDefaults on iOS).
Paired device info — the Bluetooth / USB identity of keyboards you have connected, so the app can reconnect to them automatically. Kept locally only.
In-app purchase state (see below) — a single flag indicating whether the "Full Version" unlock has been purchased. No payment details are stored.

Pebble smartwatch integration (optional, Android only)

MIDI Recorder can optionally connect to a Pebble smartwatch so you can start and stop recording from your wrist and see the current status at a glance. This feature is off by default and is only active once you enable it. It exists on Android only — the iOS app has no Pebble integration and shares nothing with any other app.

When it is enabled, the app shares the following with the Core Devices Pebble companion app installed on your phone, which relays it over Bluetooth to your paired watch:

whether a recording is currently in progress, and how long it has been running;
the name of the connected MIDI / Bluetooth device, and how many devices are connected.

This information travels only between your phone and your own watch. MIDI Recorder does not transmit it to any server — the app has no internet access. The Pebble companion app is a separate product with its own privacy policy. The integration relies on the Bluetooth and companion-device permissions already listed below; it requires no new permissions.

Permissions and why the app asks for them

Every permission is used strictly for the feature it belongs to. The app does not use any of them for advertising, analytics, or profiling.

On Android:

Permission	Purpose
`BLUETOOTH_CONNECT`, `BLUETOOTH_SCAN`	Required to discover and connect to BLE (Bluetooth Low Energy) MIDI keyboards. `BLUETOOTH_SCAN` is declared with the `neverForLocation` flag, so the app does not request any location permission and does not derive your physical location from Bluetooth scan results.
`FOREGROUND_SERVICE`, `WAKE_LOCK`, `POST_NOTIFICATIONS`	Keeps recording and playback running with the screen off, and shows the status notification while a session is active.
Companion Device permissions (`REQUEST_COMPANION_*`)	Enable auto-reconnect when your keyboard powers on. The device pairing is stored on your device by Android itself.

On iOS the app asks for one permission: Bluetooth (NSBluetoothAlwaysUsageDescription), used to find and connect your BLE MIDI keyboard. It also declares the bluetooth-central background mode so recording keeps running while the screen is locked. It does not ask for location, notifications, microphone, contacts, or access to your photos.

In-app purchase

The app offers a one-time in-app purchase ("Full Version" unlock). The transaction is handled by the platform's own store — Google Play Billing on Android (under Google's Privacy Policy) and Apple StoreKit on iOS (under Apple's Privacy Policy). In both cases the app never sees your payment details and only stores a local flag that the purchase exists; there is no server-side receipt check, because there is no server. No other third-party SDKs are used — no analytics, no crash reporting, no ads.

Changes to this policy

If this policy changes, the updated version will appear on this page, and the "Last updated" date at the top will reflect the change. Material changes will also be noted in the app's release notes on Google Play and the App Store.

Contact

Questions about this policy? Email midirecord.support@sykero.fi.

Data controller: Tuomas Airaksinen Software Oy (Business ID 3592153-9), Finland.