Privacy
Minute Matron enforces screen-time limits locally on the child's iPhone or iPad. You can manage it entirely on the device, or use iCloud sync with the parent app for remote settings and approvals. Either way, app identities stay on the child device.
Two ways to run it
A child iPad can be configured and enforced entirely on the device, with settings protected by a parent PIN. If you want to manage or approve remotely, invite the parent app to the child's iCloud share. iCloud sync carries children, devices, limits, usage summaries, and time-extension approvals between the child device and parent app.
App identities never leave the device
Apple deliberately prevents apps from exporting which apps or categories a child uses. Minute Matron honors that fully: app and category selections are opaque tokens that stay on the child device. Minute Matron only ever sees the names you choose for groups (for example “Games”), never the underlying app identities.
Usage is coarse-grained
Usage is reported only in approximately five-minute buckets via Apple's DeviceActivity framework, and stored as cumulative high-water marks per group per day. There is no second-by-second tracking, no keystroke logging, and no content inspection.
Enforcement is local
Limits are applied on the device itself; the child's iPad is the source of truth. iCloud sync is used only for distributing settings, receiving coarse usage, and handling time-extension approvals in the parent app. Existing limits keep enforcing if iCloud is unavailable.
What Minute Matron stores
With on-device management, settings and usage stay on the child device. If you use iCloud sync, Minute Matron syncs the family data needed by the parent app: your children's names, device records, group and limit settings, coarse usage marks, and time-extension requests and approvals.
No advertising trackers
Minute Matron contains no advertising SDKs and no third-party trackers. The only external service used for product behavior is Apple's iCloud service for parent sync.