JumGuard Privacy Policy

Policy version 2026-08-01

What JumGuard processes

JumGuard processes parent account details, child-device identifiers, protection status, installed-app inventory, screen-time/app-usage summaries, parent rules and command results. When optional monitoring is explicitly enabled and the supervised device grants the required Android access, it can also process notification metadata/previews and/or recent call metadata and contact names/phone numbers on the JumGuard PHP/MySQL server selected by the operator.

What this release does not collect

Live location, geofence data, microphone audio, camera media, call audio/recordings, voicemail audio, SMS databases, typed text, passwords, screen contents, notification images/attachments and notification action/reply tokens are not collected. Notification Monitoring can collect only the notification content Android exposes after Notification access is granted; notifications marked secret and likely OTP/security codes are redacted. Firebase is used only for Cloud Messaging wake-up delivery; command details are fetched from the authenticated JumGuard server.

Accessibility and managed-device controls

Standard Protection can observe only the package name of the app that becomes active so a parent-defined rule can be enforced. Window content retrieval is disabled. Full Protection requires guardian-confirmed factory-reset enrollment and can apply Device Owner restrictions, package suspension, anti-uninstall controls, managed DNS/VPN rules and controlled release.

Notification Monitoring

Notification Monitoring is off by default. A parent must enable it and Android Notification access must be granted on the supervised device. Parents can choose app/time only, title-only, or title + full available notification text and keep selected apps private. Notification history is retained for a fixed 7 days before automatic expiry. Stored notification title/text is encrypted at rest with the JumGuard server application key.

Retention and deletion

Parents can download their data, delete child usage history, or request account deletion from the Parent Panel. Operational logs and legally required payment records may be retained only for the configured or legally required period.

Contact

Questions or deletion assistance:

Calls & Contacts Monitoring: Off by default. When the primary parent enables it and the child device grants the corresponding Android permission, JumGuard may collect recent call metadata (number/contact name, direction, time and duration) and/or contact names and phone numbers. It does not record call audio, place calls, edit contacts, collect contact photos, or bypass Android permission restrictions. Sensitive fields are encrypted at rest and deleted history follows the configured retention period.