Measure the room.
Keep it local.

What the request form stores

When you request early access, SpeakerSheesh stores the email address you enter, your consent, computer and phone platforms, speaker setup, description of the room problem, microphone category, and whether you are open to structured product testing.

If your link includes campaign parameters, the site also stores utm_source, utm_campaign, and utm_content. A visit using speakersheesh_qa=1 is labelled internal_qa so our own tests can be separated from genuine requests.

Basic first-party analytics

The site records a small, fixed set of events: landing-page view, demo start, selected demo scenario, form start, and completed request. Events may include campaign parameters and non-sensitive choices such as computer or phone platform after submission.

The analytics endpoint does not receive your email, room-problem text, speaker description, microphone choice, IP address, user agent, audio, music, or device identifiers from the application. SpeakerSheesh does not set an analytics cookie, create a persistent browser identifier, use session replay, or use third-party advertising trackers.

What the calibration apps do

The phone measurement app and computer companion communicate over a locally authenticated, encrypted session. Raw microphone captures are deleted after success, failure, cancellation, or recovery unless you explicitly enable encrypted diagnostic retention.

Room Profiles, verification results, blinded choices, and evidence bundles remain local to your computer. Local music used for auditioning is not uploaded by this site.

Why SpeakerSheesh stores it

Early-access details help us prioritize platform support and select a useful range of computers, phones, rooms, and speaker systems for testing. First-party events show whether the explanation and demonstration are understandable.

Questions or deletion

To ask about your information or request deletion, email support@ardsaor.com.