TapeMan Privacy

Data handled by the app

• Audio selected or recorded by the user.
• Local take versions, stems, notes, tempo metadata, and imported video environments.
• Local preferences such as appearance, tape theme, routing, and effects.
• Local free-tier usage counters.
• A small rotating history of redacted device and application diagnostics.
• Files explicitly exported to an on-device, Files, or iCloud location chosen by the user.

Data collection

TapeMan has no account system, advertising SDK, third-party analytics or crash-reporting SDK, or tracking domains. The app does not upload recordings, device data, or identifiers to a TapeMan service. Diagnostic reports and issue descriptions are never transmitted automatically.

The checked-in Apple privacy manifest declares no tracking and no collected data. It declares file-timestamp and UserDefaults required-reason API use.

App Store purchases

TapeMan Pro purchases and entitlement verification use Apple's StoreKit service. Apple processes the purchase and supplies TapeMan with signed transaction status, including whether a purchase is shared through Family Sharing. TapeMan does not operate a purchase server and does not receive or store payment-card details. Free-tier usage is stored locally in the device Keychain.

Device diagnostics and issue reports

TapeMan keeps a small rotating diagnostic history locally to help investigate device-connection, audio, storage, lifecycle, and operation failures. It can include timestamps, an ephemeral session identifier, app and iOS versions, coarse workflow boundaries and statuses, audio configuration counters, and sanitized error details. It does not include recorded audio, sample or project contents, and file paths and common audio filenames are redacted. Diagnostic files are kept in the app's Application Support directory, excluded from device backups, and limited to three breadcrumb files of approximately 1 MB each.

TapeMan also uses Apple's MetricKit framework to receive crash, hang, launch, CPU, and disk-write diagnostics that iOS makes available to the app. Up to three of these Apple-generated reports are retained locally. TapeMan does not send them anywhere automatically. A small local session marker can indicate that a previous foreground session ended unexpectedly; this is only a correlation signal because an iOS termination, memory-pressure exit, or user force-quit can look similar to a crash.

When the user selects Report an Issue, they can write a description and choose whether to attach a redacted diagnostic bundle. The bundle contains a readable summary, breadcrumb events, and any locally available MetricKit reports. TapeMan opens the system mail composer or share sheet so the user can review, change, cancel, or choose where to send the report. The selected mail, sharing, or storage provider processes anything the user chooses to send under that provider's privacy terms.

Optional model download

The first time a user starts stem separation, TapeMan explains the download size and asks the user to initiate downloading the HTDemucs Core ML model from its public GitHub release. The HTTPS request necessarily exposes ordinary network information, such as the user's IP address, to the release host and its delivery infrastructure. TapeMan does not include recordings, device data, or a stable app identifier in this request. The downloaded archive is verified against a pinned SHA-256 checksum, compiled and stored locally, and can be removed from the Stem Mix screen. Separation then works offline.

Permissions

Microphone permission is requested because iOS exposes connected USB audio inputs through the audio-recording permission model. Audio is processed and stored locally.

This document describes the checked-in application. It should be reviewed whenever network code, telemetry, or another third-party SDK changes.