Repository navigation
IG Guard v4.6
IG Guard 4.6 — Security and family dashboard update
A redesigned family interface, weekly alert summaries and stronger authentication for pairing, parent controls and temporary unlocks. The same APK supports parent and child roles.
Highlights
- Choose your role first, then use dedicated Overview, Alerts/Permissions, Family/Unlock and Settings sections.
- Modern minimalist light/dark themes, clearer text contrast, smooth navigation and a fixed connection-status area.
- Parent charts show daily alert totals and alert types over the last seven calendar days, using real data.
- Clearer Android permission guidance, including help for restricted settings.
- Invitations no longer contain the parent master password. Parent commands are signed, and temporary unlock codes cannot be calculated from the invitation token.
- Fixes for sender impersonation through message text, stale parent controls, overdue reporting and failed key-rotation recovery.
Installation — migration required
This release uses a replacement APK signing key. Older installations signed with another key normally cannot update in place.
- Save any records or settings you need before uninstalling. Uninstalling deletes local app data; this release does not automatically migrate it.
- Install this signed APK on both phones and select the appropriate roles.
- On the parent phone, create a new family using a new master password.
- Send a fresh V43 invitation. Compare the complete security code displayed on the parent's own phone with the child phone, alongside the four matching symbols, before confirming pairing.
- Complete the child phone's Android permission setup. Confirm a child report arrives and test a temporary unlock code while both devices are connected.
Old invitations and old unlock codes should not be reused. A new temporary code must be delivered to the child phone before it works, and expires 15 minutes after generation.
Requirements and verification
Android 8.0 or newer. The signed release workflow passed, including 54 Android regression tests and 13 build/contrast checks.
Android controls special-access approval. Play Protect and banking apps may still show warnings; signing is not an assurance of their acceptance. Real-device checks of Instagram detection, Samsung permissions, live delivery and background scheduling remain necessary.
IG Guard changelog
4.6 — 2026-11-04
Changes since the published 4.5 release. Source: 50c7638. Release label/tag and APK versionName: 4.6; workflow #45, versionCode 145.
Added and improved
- Role-first entry, separate parent/child setup, fixed connection status and four navigation sections for each role.
- Minimalist native interface with light/dark themes, improved contrast, licensed fonts/icons and transitions that respect disabled system animations.
- Parent dashboard charts for the last seven calendar days: daily alert totals and totals by alert category. Routine heartbeat, pairing-success and test messages are excluded from chart counts.
- Guided Android notification/accessibility setup and conditional restricted-settings help.
- Empty states based on real app data; removed the sample trust-list default without deleting explicitly saved user lists.
Security
- V43 invitations carry a salted password verifier and parent public key instead of the parent's plaintext password.
- Full pairing security code binds the family token, password verifier and parent public key. Deep-link, pasted and clipboard invitations all require explicit confirmation; retain the original four matching symbols as an additional check.
- Parent control commands require valid signatures, family scope, timestamps and authenticated replay identifiers. Unencrypted relay messages and unsigned parent commands are rejected.
- Temporary unlock codes use secure randomness and signed encrypted delivery. They expire 15 minutes after generation and must reach the child phone before use.
- Family replacement clears previous authorization, identity and temporary-unlock state. Key rotation preserves the intended family history.
- Disabled app backups/device-transfer extraction of private data and cleartext network traffic; protected internal refresh broadcasts across supported Android versions.
Fixed and simplified
- Removed independently published key/value caches that could mix encryption keys or trust-list state during concurrent updates.
- Consolidated pairing validation and application; reject malformed invitations and consume external links once.
- Prevented message-body prefixes from overriding sender identity or claiming trusted status.
- Fixed stale parent dialogs/actions surviving a role or family change.
- Check offline deadlines while the parent stream remains open; use child report send time instead of replay receipt time, and establish a deadline from initial pairing reports.
- Retain the current family when a rotation publish fails; retry the same pending transition. Old-channel reports no longer erase pending recovery state.
Build and validation
- Replaced the exposed historical APK signer with private GitHub Actions Secrets.
- Added signing checks for Base64, keystore access, alias and private-key password, with cleanup and no credential output. Both shared and separate passwords are supported.
- Successful signed build: workflow #45, versionName
4.6, versionCode145. - 54 Android regression tests and 13 build/contrast checks pass. Android lint was checked with zero errors; non-fatal resource/API/style warnings remain.
Migration and compatibility
- The replacement APK signing identity normally requires reinstalling older installations; uninstalling deletes local app data. There is no automatic signing-key or app-data migration in this release.
- Update both phones, create a new family with a new parent master password, and pair using a fresh V43 invitation. Do not reuse old invitations or old deterministic unlock codes. Compare the complete security code on both phones.
- Android 8.0/API 26 or newer is required. Special permissions remain controlled by Android.
- Signing and these changes do not guarantee Play Protect or banking-app acceptance. Instagram metadata, Samsung permission behavior, live relay delivery and background operation still need real-device validation.