Stemy Privacy Policy

Last updated: October 16, 2026

Stemy is a local-first macOS music-production app. It collects no data automatically, contains no analytics, telemetry, crash-reporting, or advertising SDKs, transmits no usage or crash data anywhere, and does not track you. Your audio, projects, and analysis stay on your Mac. The only information that ever reaches Stemy's developer is what you explicitly choose to send through the optional Contribute Training Data feature.

Stemy is developed and provided by Music Masters Unlimited LLC, the data controller for the limited information described in this policy. This policy describes exactly what Stemy stores on your device, the optional features that send data off your device (and where it goes), the permissions Stemy requests, and your choices. This policy is intended to describe how the shipping app actually behaves; if you believe any statement here is inaccurate, contact us and we will correct it. It describes the Mac App Store edition of Stemy; other editions show their own policy in the app under Help → Privacy Policy.

Summary

• Automatic data collection: none. Stemy has no accounts, sends nothing to the developer in the background, and has no analytics.
• Data the developer receives: only the opt-in Contribute export, which you assemble and email yourself. It contains abstract audio measurements and a genre label you set yourself — never your audio, titles, filenames, or personal information.
• Several optional or default-on features contact third parties on your behalf (Apple, ListenBrainz, NOAA, GitHub, Homebrew, your plugin vendors). In every case the data goes to that provider under their own privacy policy — not to Stemy's developer.
• All audio processing and AI run on your device. Audio leaves your Mac only if (a) music recognition runs — it is on by default, and you can turn it off in Settings (an acoustic fingerprint goes to Apple), (b) you choose to share a project via iCloud (the audio goes to your own iCloud and to people you invite) or add a stem version to a project someone has shared with you (it goes to their iCloud), or (c) you use speech dictation or legacy lyric transcription in a locale or macOS version without an on-device speech model, in which case Apple's speech-recognition service may receive the audio (see Permissions → Speech Recognition).

What We Collect and Don't Collect

Automatically collected by the developer: nothing. Stemy does not create an account, assign you an advertising or device identifier, run analytics, or transmit usage or crash data anywhere.

The only developer-collected data is the opt-in Contribute Training Data export (described below). It is off by default, you trigger it manually, and you send it yourself by email. Because that data does reach the developer and is kept to improve Stemy's models, we disclose it here and in Stemy's App Store privacy label.

Everything else either stays on your device or, for the optional features below, goes to a third-party provider on your behalf — never to Stemy's developer.

Data Stored on Your Device

Stemy stores nearly all of its data locally, under your Mac's Application Support folder. Except for the optional features described later, none of it is sent anywhere.

• Audio, stems, and project folders — your imported source audio, separated stems, stem versions, recordings, and freeze and other renders.
• Analysis results — BPM, key, chords, sections, loudness, mix-health, and similar measurements, all computed on-device.
• Groove card — the source you choose for each project's groove reading (stored under the project's internal identifier); a cache of the drum-hit times detected in your audio, one file per audio file read, named and identified only by a one-way hash (no file names or paths), at most 256 files with the oldest removed first; and the groove folders you allow or add (their locations and, in the Mac App Store edition, file/folder access bookmarks), until you remove them in the Groove card or reset your preferences. To compare grooves, Stemy reads the note timing of groove files in Ableton Live's User Library and in the folders you add, on your Mac only; it does not open Ableton's own bundled grooves.
• Project organization — task boards, markers, notes, tags, collections, and project metadata.
• Lyrics — both auto-transcribed lyrics and lyrics you type, stored with the project.
• Collaborator details — if you add collaborators or import candidates from macOS Contacts, their names, emails, phone numbers, organization, avatar image, and the macOS contact identifier are stored locally to populate a collaborator list.
• AI-assistant transcripts — your questions and the assistant's answers about a project, saved per project; the assistant panel's conversation (its last 200 messages); up to 50 replies you save; and the text in its message box that you have not sent.
• Plugin and effect data — plugin chains, effect presets, and a local index of your installed plugins. This edition hosts Audio Unit plugins only; it does not load VST3 or CLAP plugins.
• Sample library (Crate) — file paths, audio features, similarity embeddings, tags, and ratings for samples you add. This is a separate local database from your projects. When you use Extract kit from drum stem on a drum track, Stemy saves each drum hit it extracts as a short audio file in its Application Support folder and adds it to this library. Stemy also keeps, among your preferences, which samples you have auditioned and when you last did.
• Calibration data — the BPM, key and energy corrections you make on projects, which Stemy can learn from to adjust future detection, and Mix Health's learned genre targets: per-genre averages of the spectral balance of the mixes it analyses, plus each analysed file's own spectral balance, kept under that file's path. Settings → Storage → Reset Calibration Data clears both.
• Preferences and profile — onboarding answers, chosen library folders, UI settings, keyboard-shortcut overrides, the export window's history for each project (its last 10 export settings, with the project's title and the stems chosen) and its saved export defaults, the last instrument you picked in each instrument family, the locations of groove files you loaded yourself (their file paths and, in the Mac App Store edition, file access bookmarks), so the groove picker can offer them again, and a producer taste profile aggregated from your own projects, library, and assistant use. Stemy does not count which setup steps you view or skip.
• Connected-service credentials — if you add a ListenBrainz token (for scrobbling), it is stored securely in the macOS Keychain (and is not synced to iCloud Keychain).
• Identifiers — the only app-generated persistent identifier is a random install ID, and it is created only if you use the Contribute feature, solely so repeat submissions from the same install can be recognised and de-duplicated. It is not connected to your name, account, or device; it is a pseudonymous identifier, not an advertising or hardware identifier. There is no advertising identifier and no device/hardware identifier.
• Crash reports — when the app crashes, Apple's MetricKit hands the next launch a crash diagnostic (exception type/signal, termination reason, thread call stacks, app version). Stemy keeps the most recent 25 under Application Support/Stemy/Diagnostics/Crashes/ so you can review them in Settings → Connections → Crash Reports. They never leave your Mac unless you explicitly export one (Copy JSON / Reveal in Finder). Clear All in that section deletes them, and so does Settings → Storage → Reset Projects.

Project and task titles are also added to your Mac's local Spotlight search index so you can find them in system search; this stays in the local operating-system index.

Personalization history

To suggest your usual choices back to you, Stemy keeps a local history of how you use a few features: the export settings you commit and the export presets you pin or make a project's default; the plug-ins you add to chains and the automatic chain tools you run (Auto-Master, auto-build, repair, streaming previews); how you use the assistant (which commands, explanations and buttons you use, and how long each question was — never what you typed); who you credit on projects, assign tasks to, add as a contact or dismiss from the Contacts list's Reconnect suggestions; the grooves you apply from the groove picker or export from the Groove card; and whether you took, changed or dismissed a suggestion. Its entries hold the settings you chose, internal identifiers, plug-in names, the file name of a groove you load yourself, and your project's genre, tempo and key (and, for exports and streaming previews, its loudness; for exports, its length) — never people's names or emails, notes, file paths, preset names, or the text of your prompts. The history is kept in a file named UserBehavior.sqlite beside your library.

• What it is used for: only these suggestions (including how your plug-ins are ranked and the order of close grooves on the Groove card), the collaboration history on your contacts, and the Studio Activity calendar in Catalog Insights — never training, analytics, or advertising. How often and how recently you add each plug-in is read from this history; Stemy keeps no separate plug-in usage counts. A summary of your assistant use (how often you use it, your most-used commands and most-explained cards) is also kept in your taste profile inside your library, which Project → Export → Data Export (CSV)… includes.
• It never leaves your Mac. It is not sent to Stemy's developer or any third party, and it is not included in iCloud sharing, .stemyarchive project archives, or the Contribute export.
• The on-device assistant (Apple's on-device model) may use what was learned — for example your most-used commands or frequent collaborators — as context, only while the matching Show suggestions setting is on.
• Your controls (Settings → General → Personalization): turn learning off or pause it (nothing new is added to the history); see what has been learned; forget any single item, a whole category, or all recorded activity; exclude a project; and export the history as JSON. Forgetting a category also clears what Stemy keeps for it among your preferences (for plug-ins, the last instrument picked in each family; for grooves, the locations of groove files you loaded yourself), and resetting clears them all. Muted suggestions (including contacts you hid from Reconnect) and excluded projects are settings rather than history: forgetting and resetting leave them. They stay until you remove them from their lists, except that a Reconnect snooze ends on its date, deleting a project clears its exclusion, deleting a contact lifts their Reconnect snooze, and Settings → Storage → Reset Projects clears every exclusion and every Reconnect snooze. Deleting a project also removes its history, its export history and saved export defaults, and its Groove card source choice; deleting a contact removes theirs, including Reconnect dismissals. Every feature works with Personalization off.
• Deleted history is overwritten in the file, not just hidden. Stemy keeps no record of what you deleted.

Optional Features That Send Data Off Your Device

Each feature below is either off by default or runs only when you take an action. In every third-party case, the receiving party is that provider — Stemy's developer does not receive or retain any of this data.

Contribute Training Data (opt-in; you email it)

Stemy includes an optional feature (Settings → Contribute) that helps improve its genre and analysis models. It is off by default and never runs unless you turn it on and explicitly send a file.

If you opt in, Stemy builds a file (JSON) that contains, for each project whose genre you set yourself: that genre label, its source ("user"), detected BPM and key (with a key-confidence value) and the track's duration, and a vector of abstract DSP measurements (tempo/rhythm regularity, low-end ratios, spectral shape, resonance, harmonicity, dynamics, and similar scalars), timbre summaries (MFCC statistics), and—unless you turn it off—a learned audio embedding (a fixed list of numbers; still not audio). Each record also carries a random per-record ID. The file also includes the random install ID, app version/build, a record count, a schema version, and the export date.

• Only genres you set yourself are included. Projects whose genre Stemy filled in automatically (from file tags, Apple Music, Shazam, iTunes Search, or its own analysis) are left out.
• No audio, song titles, filenames, file paths, names, or contact information are included.
• The file contains measurements and summaries, not audio, and they cannot reasonably be used to reconstruct a recording.
• You choose which projects to include; Stemy prepares the file and you send it to the developer (musicmastersunlimited@gmail.com) from your own email app or the system share sheet (you can also save a copy). Stemy performs no automatic upload — nothing leaves your Mac until you send or share it.
• The data is used only to improve Stemy's models. It is never sold, never used for advertising, and never used to track you.
• The random install ID is not linked to your identity or any account inside the file itself. One thing to know: because you send the file from your own email, the developer sees the email address you send it from, and repeat submissions can be recognised as coming from the same install and sender. That is inherent to emailing the file, not something the app adds.
• Contribute runs on your consent. Nothing is created or sent unless you turn the feature on and send the file yourself. You may withdraw consent at any time by turning the feature off, and you can ask us to delete a submission you have already sent (see Data Retention).

Music Recognition (ShazamKit) — on by default

To fill in missing title/artist/album information, Stemy can identify a track using Apple's Shazam service: when you add or import a track (including while you review an import), when it looks up artwork or metadata for a project (including at launch), when a title is cleaned, when you open the Split Stems sheet, and whenever you ask it to identify a track. Apart from Clean Title and a track you ask it to identify, this is controlled by the Audio Fingerprinting setting (Settings › Connections › ShazamKit), which is on by default.

• Sent to Apple: an acoustic fingerprint generated from up to roughly 12 seconds of your audio (a longer excerpt — up to about 30 seconds — for some signature-building operations). Apple returns title/artist/album/ISRC and an Apple Music link.
• You can turn this off in Settings. Clean Title, which also runs after each import while "Auto-clean titles on import" is on, has its own ShazamKit switch; turning off Audio Fingerprinting does not turn it off. (A separate on-device duplicate-detection feature builds a local fingerprint database and does not contact Apple.)

Artwork and Metadata Lookup (Apple iTunes Search) — on by default

When artwork or metadata is missing, Stemy looks it up via Apple's iTunes Search API. This is controlled by the "Look up missing artwork" setting, which is on by default. It runs automatically on import, at launch for every project still missing artwork, and when such a project's card is shown.

• Sent to Apple: the cleaned track title and artist as search terms. Stemy then downloads the cover image from Apple's image servers. No audio and no account are sent.

Apple Music Catalog Lookup

Once Stemy has your Media & Apple Music permission, it looks songs up in the Apple Music catalog (via MusicKit) without asking again: to fill in a genre when a song is imported (by its ISRC), to clean titles — including the automatic clean after each import (a title and artist, or an ISRC) — and to tint a project's page and library card from its cover art (by ISRC). Only these search terms are sent: no audio and no account. Stemy asks for the permission when you run Clean Title yourself, use Apple Music in the assistant, or press Grant Access in Settings; in the Mac App Store edition, allowing access when you import from your Music library grants it too. To stop these lookups, turn off "Look up missing metadata", "Auto-clean titles on import" (or Clean Title's "Apple Music catalog" stage) and "Tint chrome from artwork" in Settings.

Music Library

If you import songs, a reference track or your taste from your local Music library, Stemy reads the library's metadata (titles, artists, albums, genres, play counts, ratings, loved songs, playlists, dates, file locations), its artwork, and the audio of the songs you import. Once you have granted access, artwork lookup can also use matching artwork from your library. Reading your library happens on your Mac, and your taste data (playlists, loved songs, ratings, play counts) never leaves it. Songs you import then get the same lookups as any other imported file (music recognition, artwork and metadata lookup, Clean Title), as described above.

Lyrics (stays on your device)

Stemy does not look up lyrics online. Lyrics come from tags already embedded in the files you import, from lyrics you type, or from transcribing your own audio (see Speech Recognition under Permissions).

Scrobbling (ListenBrainz)

If you paste a ListenBrainz token in Settings and enable scrobbling, Stemy submits your listening activity to your own ListenBrainz account at api.listenbrainz.org.

• Sent to ListenBrainz: track title, artist, album, and a timestamp ("now playing" on track change, and a completed listen at 30 seconds or 50% of the track), authorized by your token.
• This runs only after you supply a token and while scrobbling is switched on, and the data goes to your ListenBrainz account, not to Stemy's developer.
• Switching scrobbling off stops capture, not just upload: while it is off, Stemy does not record what you play, and turning it off discards any plays still waiting to be sent. Nothing from that period is uploaded when you switch it back on.

iCloud Project Sharing (CloudKit) — user-initiated

Stemy can share a project through Apple iCloud so collaborators can review it. This feature is available in the app; it uses your own private iCloud database and requires a signed-in iCloud account (the iCloud-sync setting is on by default). It is not a background sync of your whole library — data leaves your Mac only when you explicitly share a specific project, or add a stem version or comment to a project someone has shared with you (that goes to their iCloud).

• Uploaded to your iCloud when you share a project: project metadata (title, artist, album, genre, year, detected BPM/key, chords, sections, loudness/mastering stats), the project's artwork, the original imported source-mix audio file, the project's stems (unless you choose to share the mix only), and — if you use them — per-stem audio versions and text comments (labelled with your name as it appears on the share).
• This data lives in your iCloud account. People you invite read it from there with their own iCloud sign-in and can download copies to their Macs; it is not copied into their iCloud accounts. It is encrypted in transit and at rest by Apple, and Stemy's developer has no access to it. Lyrics and AI-assistant transcripts are not part of a shared project.
• A share is a one-time copy, not a live sync: later edits to the project are not sent to collaborators (stem versions and comments you add are).
• Turning off iCloud sharing in Settings stops new shares. It does not withdraw shares you already created — use Stop Sharing on each project for that — and it does not delete what is already in your iCloud. Deleting a shared project removes its iCloud copy.
• Stemy will not upload a recording that came from your Music library, as the project's audio or as a stem version. A project classified as a reference or an import rather than your own work can't be shared, and a stem you marked as a reference is left out of a share.

Push Notifications (APNs) — registration at launch

Stemy registers with Apple's Push Notification service when it launches, so shared projects can appear automatically. Registration gives the app a device token from Apple; the token goes to Apple, not to Stemy's developer, and registration itself carries no message content and none of your data.

Weather-Driven Visualizer (Apple WeatherKit + Location) — off by default

One visualizer can tint its sky using live weather. It is opt-in and off by default, and additionally requires Location permission.

• Sent to Apple (only when enabled): your approximate location (kilometer accuracy) to Apple WeatherKit, which returns cloud cover, visibility, and daylight. Nothing is stored off-device. When the toggle is off, Stemy makes no WeatherKit call.

Space-Weather Visualizer (NOAA) — no personal data

A separate visualizer layer can react to public space-weather data. It is controlled by a setting that is on by default and can be turned off.

• Sent to NOAA: nothing about you. Stemy makes plain requests to public NOAA endpoints (services.swpc.noaa.gov) with no query data, no account, and no identifiers. (As with any network request, NOAA can see your IP address.)

Plugin Update Checks (your installed plugins)

Stemy can check for updates to your installed third-party audio plugins. It checks once, shortly after launch, when its last check is more than a day old or the previous session found updates, and whenever you trigger a check. Recurring background checks default to "never"; they run only if you opt into a daily/weekly schedule. Turning off Plugin Support in Settings stops the launch check.

• If you opt into a daily/weekly schedule, those checks run automatically in the background (via the system background scheduler), not only when you explicitly trigger them.
• Sent to third parties: requests to each plugin's own update server (Sparkle appcast), the GitHub Releases API (api.github.com), and the Homebrew cask API (formulae.brew.sh), plus vendor sites for plugin icons. These requests reveal to those providers (and via your IP) which third-party plugins you have installed. No audio and no account data are sent. Requests are HTTPS-only.
• Stemy does not download plugin installers: to install an update, it opens the vendor's website in your browser or the vendor's own app.

Model and Resource Downloads (incoming only)

When a feature needs a machine-learning model that isn't already on your Mac, Stemy downloads it over HTTPS from huggingface.co or github.com.

• These are downloads: the request carries no user data. Models that ship inside the app are never fetched, and Stemy contacts no developer-operated server at runtime.

Permissions We Request

Stemy requests these macOS permissions. Most of the data they unlock stays on your device; where data goes to Apple, it is noted explicitly.

• Microphone — to record audio (stems and instruments) directly into your projects, and for voice dictation in the assistant and search. Recordings are saved locally and are not uploaded.
• Speech Recognition — to turn speech into text. This is not always on-device:
• The AI-assistant voice command path is forced on-device (audio is never transmitted).
• The search-bar dictation path is on-device where your language has an on-device model, and may otherwise be processed by Apple's speech-recognition service.
• The legacy lyrics-transcription path (used only on macOS versions earlier than 26) may send the audio to Apple for transcription. On macOS 26 and later, lyric transcription runs on-device.
• In all cases, any audio that leaves the device goes to Apple, not to Stemy's developer.
• Contacts — to suggest collaborators from your address book. The contact details Stemy reads are stored locally and are never sent to iCloud or any network service. The one exception: when you add a collaborator to an iCloud share, the email address you enter goes to Apple's CloudKit so Apple can look that person up.
• Location (When In Use) — used only by the opt-in weather visualizer to fetch local weather from Apple WeatherKit. It is off by default. (Stemy asks for location permission only after you turn the feature on. While it is off there is no location prompt, no location is read, and no weather request is made.)

• Apple Music / Media Library — to read your local Music library on your Mac (the songs you import, with their audio and details; artwork for your projects; and, for taste profiling, playlists, loved songs, ratings and play counts); once you grant it, to look songs up in the Apple Music catalog by title and artist or ISRC (see Apple Music Catalog Lookup above); and, when you ask the assistant, to browse your library and to search and play the Apple Music catalog (your search term goes to Apple).

• Notifications / Push — Stemy registers with Apple's Push Notification service at launch so shared projects can appear automatically (see Push Notifications (APNs) above). The registration token goes to Apple, not to Stemy's developer.

Stemy holds the outbound-network entitlement only; it never acts as a network server or listener on your Mac.

Third-Party Services and SDKs

Stemy contains no analytics, telemetry, crash-reporting, advertising, or tracking SDKs of any kind — not as a dependency, not as an import, not as a bundled binary. There are no SDKs from Google, Facebook/Meta, or any data broker. The app's bundled software components are limited to on-device computation, user-interface, audio-codec, and local-database libraries, none of which perform networking.

The network endpoints Stemy contacts at runtime, all over HTTPS, are:

• Apple — iTunes Search (artwork/metadata), ShazamKit (music recognition), Apple Music/MusicKit (catalog lookup), WeatherKit (weather, opt-in), iCloud/CloudKit (project sharing), and the Push Notification service (APNs registration at launch).
• ListenBrainz / MetaBrainz (api.listenbrainz.org) — scrobbling, only when you add a token.
• NOAA (services.swpc.noaa.gov) — public space-weather data for a visualizer; no personal data.
• GitHub (api.github.com), Homebrew (formulae.brew.sh), and your plugin vendors' update servers — plugin update checks. Stemy does not download plugin installers: to install an update, it opens the vendor's website in your browser or the vendor's own app.
• Model hosts — huggingface.co, github.com — for downloading machine-learning models (incoming only).

Plugin-vendor websites and service settings pages open in your browser only when you click them; those are not requests made by the app.

Identifiers and Tracking

• Stemy contains no advertising identifier (no IDFA / App Tracking Transparency), no device or hardware identifier, and performs no cross-app or cross-site tracking. No data is shared with data brokers.
• The only app-generated persistent identifier is the random install ID — a pseudonymous value created only when you first use the Contribute feature, and used only to recognize repeat submissions from the same install. It is not connected to your name, account, or device, and it leaves your Mac only inside a Contribute file you choose to send.
• Other identifiers on your device are your own service credentials (for example a ListenBrainz token you paste, if you use scrobbling), stored in the macOS Keychain. Such credentials go to that service on your behalf, never to Stemy's developer.
• Stemy's privacy manifest declares no tracking and no tracking domains, consistent with the above.

AI Processing

All AI and machine-learning features in Stemy run on your device:

• The conversational assistant and every text feature (title cleaning, mix-health explanations, plugin classification, sample-search query rewriting) use Apple's on-device FoundationModels. No conversation data, project details, or audio is sent to any cloud AI service.
• Audio processing — stem separation, key/tempo/section/chord analysis, similarity search, and mix-health DSP — runs locally using on-device machine-learning frameworks (CoreML and MLX). In non-App-Store (Developer-ID) builds, stem separation may run via a local helper subprocess on your Mac; this is local computation and sends nothing over the network.

The only AI-related network activity is the incoming download of model files described above, which carries no user data. All inference runs on your Mac.

Data Retention

• Local data — kept until you delete it. Settings → Storage → Reset Projects removes your projects and all the audio Stemy keeps for them — its copies of imported songs and of the audio from imported project archives, stems, stem versions, recordings, instrument takes, frozen, bounced and pitch-shifted audio, renders and streaming previews — and project caches (including the Groove card's drum-hit cache). It also removes the Arrangement cache, which keeps DAW Arrangement undo across restarts. For stems you merged while Keep originals on merge (Settings → Storage) was off, the default, that cache holds their original files — a merge moves them there, even from your own folders — so the reset deletes those originals too. Stemy also deletes them by itself once they are older than Backup Retention or the cache grows past Backup Cache Size (Settings → Storage → DAW Arrangement; 30 days and 500 MB by default): at launch, and as soon as you lower either setting. It removes the assistant's conversation, the unsent text in its message box and the replies you saved; the crash reports in Settings → Connections → Crash Reports; the Spotlight entries, delivered notifications and pending task reminders of the projects and tasks it deletes; each project's export history and saved export defaults, the Groove card's source choices, the locations of groove files you loaded yourself, and your Personalization history with its project exclusions and Reconnect snoozes (other muted suggestions stay). It does not delete files outside Stemy's own folders: the original files you imported, your exports, and files Stemy wrote beside stems it uses from your own folders (such as a merged mixdown) stay where they are, apart from originals a merge has already moved into the Arrangement cache. It preserves your sample library (Crate) and the drum hits you extracted into it with Extract kit from drum stem; your calibration data (your BPM, key and energy corrections and Mix Health's learned genre targets, which keep each analysed file's spectral balance under its path), which Settings → Storage → Reset Calibration Data clears; downloaded models; custom themes; saved genre reference profiles; and the groove folders you added. It does disconnect ListenBrainz scrobbling — your ListenBrainz token is deleted from the Keychain. The random install ID and the saved file/folder access bookmarks for your own files and folders (which encode the absolute paths of files and folders you have granted access to) also persist across Reset Projects; bookmarks for files inside the folders it deletes are removed.
• Sample library (Crate) — removed separately via Reset Crate Library, which also clears the record of which samples you auditioned. It leaves your audio files on disk untouched, including the drum hits you extracted with Extract kit from drum stem.
• ListenBrainz token — stored in the macOS Keychain; removed when you clear it in Settings (Remove token), and when you run Reset Projects or reset your preferences.
• iCloud project data — lives in your iCloud account until you delete the project (deleting a project removes its iCloud copy). Stop Sharing ends collaborators' access but does not delete it. Stem versions and comments you add to a project someone has shared with you are stored in that person's iCloud.
• Contribute files — created and stored by you. Submissions you send are kept while they remain useful for improving Stemy's models. To have a submission deleted, email musicmastersunlimited@gmail.com and include the install ID shown in Settings → Contribute; we will delete the submission and confirm by email.

Security

Almost all of your data never leaves your Mac, which is the main protection Stemy offers. Data that does move is protected in transit: Stemy's network requests are HTTPS-only, shared projects are encrypted in transit and at rest by Apple iCloud, and service tokens you add are stored in the macOS Keychain. Contribute submissions reach us through your own email. No system is perfectly secure, but Stemy is designed so that there is very little of your data outside your own device and accounts to protect.

Your Rights and Choices

Because Stemy is local-first, you control your data directly:

• View, export, or delete your data on your Mac at any time; use Project → Export → Data Export (CSV)… to export project data as CSV.
• Turn off automatic enrichment — to stop sending fingerprints and search terms to Apple when you import, turn off "Audio Fingerprinting" (ShazamKit) and "Look up missing metadata", "Look up missing artwork" and "Auto-clean titles on import" in Settings. Clean Title has its own ShazamKit and Apple Music catalog switches.
• Turn scrobbling off, or clear your ListenBrainz token, to stop scrobbling.
• Use Stop Sharing on a project to withdraw collaborators' access, and turn off iCloud sharing in Settings to prevent new shares.
• Keep the weather visualizer off (the default) so no location is sent to Apple.
• Reset Projects, Reset Crate Library or Reset Calibration Data to delete local data.

If your jurisdiction grants you additional rights over personal data, you can exercise the data-management controls above, and you may contact us at the address below. Nothing in this policy limits any non-waivable statutory rights you may have. If you are in the EU/UK, you have rights under the GDPR/UK GDPR (access, rectification, erasure, restriction, portability, and objection) and the right to lodge a complaint with your supervisory authority; if you are a California resident, you have rights under the CCPA/CPRA. We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under California law.

Children's Privacy

Stemy collects no personal data automatically and requires no account, so it does not collect personal information from children — including children under 13. Stemy is not directed to children under 13. If you believe a child has sent us a Contribute file, contact us at the address below and we will delete it.

Who We Are

Stemy is developed and provided by Music Masters Unlimited LLC, the data controller responsible for the limited information described in this policy.

Changes to This Policy

We may update this policy from time to time. Material changes will be reflected in the "Last updated" date above and noted in the app's release notes before they take effect for data already submitted.

Contact

• Privacy questions: musicmastersunlimited@gmail.com
• General/developer contact: musicmastersunlimited@gmail.com
• Postal address: Music Masters Unlimited LLC, 1206 Sienna Hill Dr, Houston, TX 77077, United States

App Store Privacy Label (Summary)

Stemy's App Store privacy label declares exactly one collection path — the opt-in Contribute export described above — and matches Stemy's privacy manifest:

This produces a "Data Not Linked to You" label for Other Data and Identifiers, with no "Data Used to Track You." Everything else Stemy does — model downloads, plugin-update checks, NOAA visualizer data, iTunes/Apple Music lookups, ListenBrainz scrobbling, and iCloud project sharing — is either inbound-only, carries no personal data, or goes to the user's own connected account, and is therefore not declared as developer collection.