Effective October 25, 2026

TriggerMap Privacy Policy

This policy describes TriggerMap BETA for macOS, the testing edition of TriggerMap Pro, provided by ThumpStack Labs, LLC. It applies to version 0.1.4 and subsequent builds that link to this policy and use the practices described below.

Your kit configuration and MIDI processing stay on your Mac unless you choose to export or share information. TriggerMap BETA has no account requirement, advertising, or automatic upload of your kit or performance. Apple TestFlight separately collects beta diagnostics.

What TriggerMap processes on your Mac

TriggerMap uses connected MIDI device and port information, supported module configuration reads, kit files you select, and MIDI messages received during setup and playing checks. This can include device names and identifiers, pad and zone assignments, notes, velocity, controller values, pedal movement, and aftertouch or choke messages.

It uses this information to establish your canonical rig, translate its assignments for your selected sound library, identify unavailable articulations, and record your setup and soundcheck confirmations. Saved rigs, configuration snapshots, mappings, local diagnostic evidence, and preferences may include device or kit names and file locations. Module configuration reads do not change the module's settings.

TriggerMap also checks installed host and instrument information and reads selected library or preset files to prepare compatible mappings. It saves mapped copies or exports to the locations you authorize. macOS file permissions and folder selections control access to protected files; you can manage permissions in System Settings.

Audio, accounts, and tracking

This beta's kit checks use MIDI input, not microphone recordings. Spoken instructions are audio output. Drum sound playback and any audio or MIDI recording you choose to make in a DAW or another host are handled by that software.

The current beta does not require a TriggerMap account and does not include advertising trackers or automatically send kit settings, raw MIDI, or recordings to ThumpStack Labs. We do not sell personal information or use it for targeted advertising.

Local storage and deletion

TriggerMap keeps saved setup information and diagnostics in local application storage and writes exports to your chosen folders. These remain until you remove them. Quitting or deleting the application may leave saved profiles and exported files behind. You can remove those files yourself or contact us for help locating TriggerMap's data.

If you save files in an iCloud Drive, Dropbox, or other synced or backed-up folder, that service may copy them according to your settings and its privacy practices. Deleting a local copy may not delete backups or copies already shared. ThumpStack Labs cannot remotely access or erase files that remain only on your Mac or in services you control.

Optional automatic beta diagnostics

Builds offering “Share beta diagnostics” in Help & FAQ send workflow diagnostics only after you enable that choice. Earlier builds without that setting keep these reports local. Sharing is optional and does not affect mapping or playing.

Events contain setup command and stage categories, success/failure or blocked outcomes, durations, fixed error categories, available progress counts, module family, zone categories, selected library/host categories when available, app version/build, macOS version and processor architecture. Random installation and pseudonymous workflow identifiers connect events from the same installation. Events exclude audio, raw MIDI or note values, kit contents or names, personal paths, account information and arbitrary error text. We use them to investigate stalls, unsuccessful handoffs and setup problems.

A separate worker sends small HTTPS batches to ThumpStack Labs on this domain, hosted using Sites and Cloudflare. Network failure does not block playing. The local pending queue is limited to 1,000 events and two days. Turning sharing off clears it and stops future collection and requests; an in-flight request may complete.

The service deletes event records older than 90 days when processing new reports. Installation authorization records remain until removed through support administration. We do not store IP addresses in the event database; hosting infrastructure processes network information to deliver and protect the service. Stored reports are available only through authorized administration tools, with no public report reader.

Help & FAQ shows sharing status, delivery status and a Support ID. Include that ID for access or deletion requests to info@thumpstacklabs.com; never share authentication tokens. These diagnostics are used for reliability, not advertising or tracking across other apps.

Optional reports and support

TriggerMap keeps a bounded local diagnostic history: up to 256 recent command outcomes and durations, and up to 32 exception records with software module/function names and source line numbers. It does not include command arguments, exception-message contents, or raw MIDI in that history. Older entries are replaced as new ones arrive.

The built-in beta report is created locally when requested. It includes this recent diagnostic history and contains the app build, macOS version, processor architecture, supported host or plugin installation/version information, and rig verification summaries such as module identity, input and zone counts, and confirmation status. This report excludes audio, raw MIDI, kit contents, personal file paths, and account details. Creating the report does not upload it.

You decide whether to send a report, screenshot, kit file, or other information to us. Review files before sharing: screenshots and separately exported diagnostic or kit files may contain more information than the built-in beta report. When you contact us, we receive your email address, message, and any attachments you choose to provide. We use them to respond, investigate problems, and improve TriggerMap. Please do not send passwords, payment details, or unrelated sensitive information.

Apple and TestFlight

Apple operates TestFlight separately from TriggerMap. When you test through TestFlight, Apple automatically collects crash logs and usage information and shares them with the developer. Feedback you submit is also shared; this may be associated with your name and email address. We use this information to investigate defects and improve the app and do not share TestFlight information with third parties. See Apple's TestFlight & Privacy notice for Apple's collection, retention, and available choices.

Information we receive and retain

Information you send for support is handled by ThumpStack Labs and the service providers used to deliver and store support correspondence. We use it for support, beta administration, and troubleshooting, rather than advertising. We retain support correspondence and diagnostic copies only as needed for those purposes, resolving the reported issue, and any applicable recordkeeping obligations. TestFlight records held by Apple follow Apple's retention practices; copies we receive are retained as needed to resolve defects and support the beta.

You may ask us for access to, correction of, or deletion of personal information you have shared with us or that we received through TestFlight. We may need to verify the request and may retain information where required by law. Copies in your own files, backups, or other recipients' systems must be managed separately.

Other software and products

Logic Pro, Ableton Live, SSD, and other hosts or sound libraries have their own privacy practices. TriggerMap GO is a separate product and is not covered by this policy. The separate tester portal and visits to this website are also outside this app policy; see the website privacy notice for website visits.

Contact and changes

Contact ThumpStack Labs, LLC at info@thumpstacklabs.com for support, privacy questions, or requests about information we hold.

Updates will be published on this page with a revised effective date. If a future release changes its data practices, we will update this notice to describe those changes. This policy does not claim that planned or unreleased capabilities are already present.