Repository navigation
Use Cases
This page gives realistic ways to use TrackerDetector in daily life. These are examples of workflow and judgment, not guarantees of threat detection.
Before a meeting, keep scanning on while you approach and wait nearby. If tracker or rogue infrastructure alerts repeat in that area across different days, treat that pattern as a higher-risk signal and change meeting plans.
During field work, leave scanning active and review grouped alerts by type after moving between locations. Repeated high alerts tied to movement can help you decide when to rotate routes, change devices, or delay sensitive calls.
When arriving at a hotel or temporary office, review Wi-Fi and Bluetooth measurements for unexpected devices with strong signal. If unknown devices remain close while your position changes, that is a useful indicator to escalate your own safety steps.
Run scanning before entering and after leaving a meeting point. If the same tracker-style alerts persist across movement and time, consider changing transport plans or meeting location.
Use the app for several normal days to learn what is usual near home and work. Once a baseline is known, unusual repeated alerts become easier to spot and discuss with someone you trust.
Keep scans active during daily travel and review alerts by type in the Status page. If the same alert family appears repeatedly across different locations, document the timeline and consider formal reporting.
Check for rogue access point and identity mismatch alerts in public places. If a known network name appears with unexpected hardware identity, avoid connecting until you can verify the network through another trusted source.
Use GPS Security when location confidence matters for your route or evidence log. If GPS trust alerts repeat while sky visibility is good, rely on additional references and avoid single-source assumptions.
- Build a baseline first: run for several normal days before treating low alerts as suspicious.
- Use grouped alerts: patterns over time are usually more useful than one isolated event.
- Export logs when needed: keep CSV or KMZ files if you need to share a timeline with trusted support.