Skip to content

Collection Decisions: Permissions, SDKs, and Disclosures

Knowledge check · self-test

Collection Decisions: Permissions, SDKs, and Disclosures

## Decide What a Step Counter May Collect {.depth-l0 data-narration="suspended-until-rerecord"} A step counter can count motion on the phone. Yet a bundled library might also ask for contacts and an ad ID. The library chart shows why the app and its SDKs both need review. Use Figure 1 in the chapter to record each grant, its purpose, recipient, time limit, and user choice. For a basic daily count, accelerometer (motion sensor) samples can be reduced on the device to a step total. Raw motion need not leave the phone, and contacts do not help count steps. If a social challenge is added later, contact access becomes a new mobile data decision rather than an invisible extension of the old one. Show the purpose when the user starts step tracking, before asking for access. The same record should state when tracking stops and when a new use needs review. Collection timing matters after approval too. The step counter can stop motion access when tracking is paused and restart only after a clear action. A mobile permission that remains technically available does not require the app to collect continuously. - **Predict:** The app asks for contacts during first launch, before the user opens social challenges. Is the collection tied to the immediate step-count purpose? **Check:** No. The permission arrives before the feature that could explain it. - **Predict:** Raw accelerometer data is deleted after an on-device daily total is made. Does that reduce collection risk? **Check:** Yes. The smaller total preserves the counting result without retaining the full motion trace.

Back to the chapter →

## Decide What a Step Counter May Collect {.depth-l0 data-narration="suspended-until-rerecord"} A step counter can count motion on the phone. Yet a bundled library might also ask for contacts and an ad ID. The library chart shows why the app and its SDKs both need review. Use Figure 1 in the chapter to record each grant, its purpose, recipient, time limit, and user choice. For a basic daily count, accelerometer (motion sensor) samples can be reduced on the device to a step total. Raw motion need not leave the phone, and contacts do not help count steps. If a social challenge is added later, contact access becomes a new mobile data decision rather than an invisible extension of the old one. Show the purpose when the user starts step tracking, before asking for access. The same record should state when tracking stops and when a new use needs review. Collection timing matters after approval too. The step counter can stop motion access when tracking is paused and restart only after a clear action. A mobile permission that remains technically available does not require the app to collect continuously. - **Predict:** The app asks for contacts during first launch, before the user opens social challenges. Is the collection tied to the immediate step-count purpose? **Check:** No. The permission arrives before the feature that could explain it. - **Predict:** Raw accelerometer data is deleted after an on-device daily total is made. Does that reduce collection risk? **Check:** Yes. The smaller total preserves the counting result without retaining the full motion trace.

Back to Mobile Data Collection and Permissions: Connect Tracking, Disclosures, and Fixes