
Knowledge check · self-test
Check: Purpose, people, and proof
Purpose, people, and proof: test withdrawal, bystander capture, minimum collection, and rights across copies.
Purpose, people, and proof: test withdrawal, bystander capture, minimum collection, and rights across copies.
Test first setup, a second adult, a visitor, a child, a lost phone, a new purpose, a new partner, withdrawal, export, deletion, and account closure. Follow the choice through device, app, service, reports, and partner copies. A changed screen is not proof if the old path still runs.Use a short person-by-person walk-through. Ask what the parent sees, what the sitter sees, what a visitor sees, and what the child can understand later. Show the choices before data starts to move. Let each adult find the same stop route without help.After a stop, create one event at the device. Look for it in the app, live service, saved history, report, and partner path. It should appear only where the remaining choice allows it. Mark any copy that cannot be removed and explain why before asking for agreement.Repeat the walk-through after a new feature, person, receiver, purpose, device, or storage period. Keep the old choice and the new choice with their times. Name who fixes a path that ignores the state. If the team cannot trace the change across every copy, the product must not claim that withdrawal is complete.Close with five plain checks. Can the person say yes to one use and no to the rest? Can they change that choice in the same place? Does the device get the new state? Do saved jobs stop as well? Can staff show the time when the change took effect?Try each check with the network off and then back on. A queued event must not slip through under an old choice. Try it with two adults who hold two roles. One person's choice must not silently erase the rights of the other. Save the result in words that a new user can read.
Test comprehension and reversibility. After the user sees the consent flow, ask what the device collects, why it collects it, who can see it, how long it is kept, and how to turn it off. Then observe whether they can actually find the dashboard, withdraw a choice, export data, and request deletion without help. Those tasks are stronger evidence than a screenshot because they show whether consent is understandable, actionable, and maintained after setup.
Back to IoT Privacy: Purpose and Data Boundaries: Consent by Roles and Data Paths