Illustrative idea · STUDENT PRIVACY
Review location-sharing consent
Keep student location sharing limited to a clear, agreed school purpose.
Treat a location signal as a prompt to check—not proof of arrival.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
For a family and school that have explicitly agreed to a limited arrival check, receive a location signal from a student’s device and compare it with the configured school area. Location can be inaccurate, delayed, or shared by another person. Obtain informed, age-appropriate consent, explain who sees the result, collect no more location detail than necessary, and require an authorized adult to verify the signal before contacting anyone or relying on it for a safety decision.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
A consented device sends a possible school-arrival signalA documented location purpose, approved device sharing, and a narrowly defined school area
“Review a possible arrival without continuously tracking a student or overstating the precision of location data.”
Work through the request.
Clear tasks, with review where it matters.
- Obtain informed permission for this location use
- Check the signal’s time and identity
- Interpret the school boundary cautiously
A restricted arrival signal with timestamp, uncertainty note, and adult-review status.
What this workflow could do
Receives a device location update, compares it with a defined school boundary, records a possible arrival, and prepares notices for selected adults.
Review points proposed in this idea
A geofence match can be wrong and must not be presented as proof that a student entered school safely. Use informed permission, avoid retaining precise coordinates, restrict recipients, and make a person verify the status before taking action or reassuring others.
How the idea could work
Select an illustrative task to explore its proposed role. No workflow runs here.
-
Explain the purpose, location precision, recipients, retention, and how sharing can be stopped.
-
Confirm which device sent it and whether the update is current, expected, and attributable to the student.
-
Treat proximity as an uncertain signal, not confirmation of entry or student safety.
-
Avoid retaining raw coordinates and share only a minimal status with approved adults.
-
Require an authorized adult to confirm an uncertain or consequential arrival status.
Step 1 of 5
Obtain informed permission for this location use
Explain the purpose, location precision, recipients, retention, and how sharing can be stopped.
Proposed setup considerations
These are planning notes for the concept, not instructions for a currently available template.
- 01
Document consent and withdrawal options
Set age-appropriate permission, a narrow purpose, approved recipients, and an easy stop process.
- 02
Use minimum location precision and retention
Keep only the status and time needed for the task and delete coordinate data promptly.
- 03
Test boundary and stale-signal cases
Check drift, delayed updates, device sharing, and unavailable location scenarios.
- 04
Keep safety decisions with people
Make clear that an alert is not confirmation and require an adult to verify before action.
Read the prelaunch status
Published templates and verified customer availability remain pending.
A little help with the whole task
A little less busywork.
A little less busywork.
A little more room for you.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation