if you are in immediate danger

this page is not where you start. contact crisis support and a DV advocate first — then return here for technical proof on synthetic reference data only.

  • US suicide & crisis lifeline: 988
  • US national DV hotline: 1-800-799-7233
  • victim safety comes before documentation — exporting Google Takeout, pulling backups, or screenshotting shared location can notify a controlling partner via login alerts or family sharing.
  • preserve without confronting. do not tell the abuser you found a SmartTag pairing or saved shelter Wi-Fi until an advocate says it is safe.
// reference investigation

brooks-ipv-tech — partner tracking / coercive tech trail

Brooks IPV case BRV-IPV-2026-0612 on S. Brooks — Google timeline contradicting shelter alibi · AirTag-class bluetooth pairings · coercive home Wi-Fi credentials · iOS/Android location history + significant places. Fully synthetic.

what this proves

  • all eight ipv-tech primary engines produce deterministic, fixture-locked output — verified by npm run check:flagship (280/280 fleet · 8 for this scenario).
  • every output is generated 100% locally in your browser — location databases, Takeout fragments, and Wi-Fi configs never upload.
  • shared Google timeline contradicting shelter alibi, AirTag-class bluetooth pairings, coercive home-network credentials, and iOS significant locations surface without sending a survivor's device to a server.

primary engines locked to this fixture

build the case binder

runs all eight primary engines on the synthetic evidence zip and opens a self-contained html binder. uses the default binder renderer for ipv-tech — no upload.

runs all 8 primary engines locally on the synthetic evidence zip · opens a self-contained html binder · no upload

download the synthetic evidence

MIT-licensed, fully synthetic. includes iOS consolidated.db, Routined Cache.sqlite, android location_history, Google Takeout Records.json, bluetooth pairing exports, and coercive Wi-Fi configs — no real victim coordinates.

built deterministically from scripts/fixtures/build-brooks-ipv-tech.mjs. seed: brooks-ipv-tech:v1.

methodology

ipv tech is not always a stalkerware APK — start with iOS consolidated.db for learned locations, reconstruct movement chains, pull android GPS + Google Takeout timeline, surface bluetooth tracker pairings and coercive Wi-Fi credentials, then summarize Routined significant and frequent locations for advocate review. read the full intimate partner violence — tech trail guide →

after the playbook

run each primary locally — or export findings from the binder — then drop every csv/json into fatcousin-multi-tool-super-timeline-correlator. one timestamp-sorted timeline across Google timeline alibi gap, AirTag-class bluetooth pairings, coercive Wi-Fi credentials, and iOS significant locations — still zero upload.

synthetic scenario only · no real victim · no real coordinates · grading rubric

ready