Sharing
No sharing feature exists in this build. We do not describe one, and we do not describe what one would or would not carry.
Every claim ABA Media Platform makes about security and privacy, in the exact words that were approved — including the one still open and the one that was withdrawn.
Every security page you have read was written to reassure you. That is why you skimmed it.
A page that lists only reassurances is discounted on sight, and it deserves to be — the interesting sentence is always the one that is missing. So this page carries the whole file: what is protected, what crosses the boundary anyway, what is still open, and what was claimed and then withdrawn.
How to read this page
Each statement below is owned by one file. Every other mention of the same fact anywhere — a page, a post, a graphic — is the same words, not a rewrite of them. When a fact changes, every instance moves in one edit.
A paraphrase is a defect. Two statements of one security fact, edited at different times, drift apart; and a page that contradicts itself on security is worse than a page that says nothing, because once one claim is wrong a reader discounts all of them.
The statements
Your audio never leaves your machine. It is decoded and analyzed in your browser, and it is never transmitted.
S3 is mandatory wherever this appears. Stating what does cross the boundary is what earns belief in the rest.
The measurements do travel: every completed report is handed to the page that embeds the tool, and for signed-in members the host stores it against their account. The audio is not part of that — the measurements and the file name, nothing more.
The file name is named deliberately. Master filenames routinely carry client, artist and version information, so an earlier wording — "only the numbers" — was imprecise in exactly the way a reviewer catches, and was corrected.
There is no fetch, XMLHttpRequest, WebSocket or sendBeacon anywhere in the build, and the page makes no external request of any kind. The only outbound path is a postMessage to the page that embeds it.
A structural fact rather than a policy promise, which is why it is the strongest sentence available — and why it is never softened into "we don't upload your files".
Saved clips are held in your browser's own storage (IndexedDB) — up to six clips within a 420 MB budget, oldest evicted first. Browser storage is not encrypted: anyone using that browser profile can replay them.
The second sentence never appears without the first, and the first never appears without the second.
The page never sends a member id. The host derives the member from the signed-in session on the server.
No account is required to analyze a master. Without one, appraisals are kept in that browser's own storage; signing in is what makes them follow you to another browser or another machine.
Appraisals you made before signing in are added to your account when you sign in. A row leaves this browser only once the account has confirmed it, so nothing is discarded — if the account cannot be reached, the appraisals stay where they are and the app says so.
An earlier version of this described a silent wipe, and it cost the site owner two appraisals before it was corrected. That is what the correction record below is for.
Clear removes the appraisal from the account permanently. It is not a local hide.
Appraisals belong to the account, not the person at the keyboard. If you sign in as a client and run evaluations, that client will see them. Clear them before you sign out.
The app acts on messages only from the site it is published on. A page that embeds it anywhere else cannot supply the member name it displays or the appraisal list it shows — it will show only the history held in that browser.
What this does not claim, stated because a security section that lists only reassurances is discounted on sight: it is not a defense against the site you are already on. A page that embeds the tool controls the frame around it and could draw anything it liked without involving the tool at all. The guarantee is narrower and exact.
Still open
The report is posted to whichever page embeds the tool. On museguitarist.com that is your own site. Any other site that embeds the tool would receive the reports run inside it — the audio, never.
This is the outbound mirror of S11, and it is a hardening item that has not been closed. The reason it is still open is a real observed failure rather than a shortcut: a mismatched target origin is dropped silently, so a wrong guess loses a reader's results with no error anywhere. It is never presented as resolved, and closing S11 did not close it.
Withdrawn
They stay on the page they were withdrawn from, struck through, with the reason. A file that hides its own corrections is asking to be trusted rather than checked.
The page loads its webfonts from a third party, which is a request on every page load. It carries no audio and no measurements — it is a static stylesheet URL — but it does disclose the visitor's IP address. Self-hosting the fonts would remove it.
Resolved by inlining the font faces into the build, so the assembled file contains no external address at all. It is kept here, struck, because pages published before that build carried it — and because a reviewer checking the old citation should find out from us that it has moved, not from the discrepancy.
Not approved
No sharing feature exists in this build. We do not describe one, and we do not describe what one would or would not carry.
Browser storage is not encrypted. We do not imply otherwise, and that includes implying it by leaving it out.
They counted matches no harness had ever run. Removed from the product, and replaced with figures a test file actually backs: agreement with pyloudnorm within 0.05 LUFS, and with the Python core within 0.5 points.
The genre profiles behind that score are declared heuristics. The score may not appear inside a claim of accuracy, and it does not.