If you have ever joined a video call from a link, you know the moment. The page loads, and before anything useful happens your phone puts up a box asking whether this site can use your camera and microphone. You have about two seconds to decide, you are usually standing outside, and you have no idea what the site will do with a yes.
Watching a live inspection does not do that. No box, no decision, no two seconds. People notice, and a fair number of them assume they missed a prompt or that one is coming later. Neither is true, and the reason why is the single most useful thing to understand about the page you are looking at.
The prompt is not a policy, it is a consequence
Browsers do not ask for your camera because a site requested politely. They ask because the page called a function that, if allowed, would start capturing from the camera. No call, no prompt. The permission box is an alarm on a specific door, and it only rings when somebody tries the handle.
A video call page tries the handle immediately, because a call with one-way video is not a call. So the prompt is unavoidable there — it is not the site being nosy, it is the site doing the thing it exists to do.
The inspection viewer page never tries the handle. It has no code path that reaches for a camera, because it has nothing to do with one. It receives video and plays it. That is the entire job.
The part that is enforced, not just omitted
Leaving the code out would be a promise. What actually holds this up is one level lower, and I want to be specific about it because "we just do not use your camera" is the kind of sentence anybody can write.
When you acknowledge the recording notice, the server issues your browser a credential for the live session. That credential is created with permission to publish set to false — not omitted, set to false. It is not an ability the page declines to use. It is an ability the page has been refused. If someone rewrote the viewer page tomorrow to try to send video, the server would reject it, because the credential it was given does not carry the right.
That inversion is the whole trick, and the side effect is the one you care about: a page with no ability to publish has no reason to ask for a camera, and your browser therefore never asks you.
What the line under the video means
While you are watching there is a line of small text under the picture that reads: watch only, your camera and microphone are never used.
Plain text, no icon, nothing clever. It is there because the absence of a prompt is easy to miss, and somebody watching their own house get inspected should not have to infer their privacy from something that did not happen. It states the fact where you are already looking.
There is one other thing that line quietly tells you. Because your microphone is not in play, nothing said in your kitchen while you watch goes anywhere. The audio on the recording is the inspector's, picked up by the inspector's phone.
What this does not protect you from
I would rather say this plainly than let you assume more than is true.
The inspection itself is recorded. Video and audio, by the inspector's phone, kept by the inspection company. The notice you acknowledged before watching says so. Your camera being off does not make the inspection unrecorded; it makes you unrecorded.
If you are standing next to the inspector, you are on the recording. The notice reaches the person holding the link. It does not reach whoever is in the driveway. Telling the people physically present that a phone is recording remains the inspector's job, and a good one does it before they climb. If you are on site and you would rather not be picked up, say so. It is a normal thing to ask.
A person can still be identified by the property. The address is on screen. That is deliberate — it is how you confirm the link is yours — but it is not anonymity and nobody should sell it as such.
Why a contractor gives this up willingly
From the contractor's side, a one-way viewer is less capable than a video call. They cannot see your face, cannot read whether you are following, cannot get a nod. Some of them miss that.
They take the trade anyway, and the reason is the permission prompt itself. A prompt in a driveway is where people stop. A meaningful share of anyone asked to allow a camera just closes the page, and a viewer who closes the page is a viewer who goes back to being told about their roof rather than shown it. Removing the prompt is the difference between a feature people use and a feature people are offered.
There is a longer version of that argument, written to contractors, in no app, no account, and why.
The one thing you can send
Since the page cannot publish, it might seem like nothing at all can travel from you back to them. Almost right. If the inspector has questions switched on, a button appears reading "I have a question about this," and tapping it saves the still frame you were looking at for them to review afterwards.
It sends a picture of their own video, taken from your screen. It does not send text, audio, or anything from your camera. It does not buzz their phone mid-walk. What happens to those flagged moments, and how a good inspector handles the questions that stack up behind them, is in homeowner questions during inspection.
The rest of the model — what is kept, who can open it, how long it lives — is written out on the security page, and the viewer sequence from the other side is on the how it works page.
InspectStream records what an inspector observed. It is not a public adjusting service and does not prepare, negotiate, or advise on insurance claims.