backstop.family / vs
Who took control from the parent. Who's giving it back.
This isn't a feature comparison. It's a comparison along one axis:
what decisions has each product taken away from the parent, and
where does Backstop put them back.
Who decides
Backstop
Bark
Gaggle
Life360
Recall
What counts as harm The taxonomy that fires alerts.
The parent You write the rules. The endpoint reads them.
Bark's model Vendor ML model, updated on Bark's schedule.
Gaggle's model + school district Vendor thresholds + district policies. Not the parent.
N/A Life360 is location-only. Included here for the data-brokerage row.
Microsoft Recall indexed everything; the "sensitive content" filter was Microsoft's model.
Where the screen contents live The most sensitive artefact.
Your child's device only Analyzed locally. Screenshot never leaves.
Bark's cloud Every screenshot / text / DM shipped to Bark for analysis.
Gaggle's cloud + district storage Cloud analysis; district retains flagged content.
Location on Life360 servers Historical location trails stored by Life360.
Local, indexed by Microsoft
Screenshots stored on device, keyword-searchable via Microsoft's index.
Hagenah's "Total Recall" and follow-up "Total Recall Reloaded" showed
same-user malware can read the plaintext.
Who else can see it On subpoena, breach, or policy change.
Nobody at Backstop can read alert bodies
Alerts are encrypted to your family key before they leave the device.
A subpoena to Backstop gets you account metadata (your email, endpoint
heartbeats, delivery destinations you configured, alert timings) and
ciphertext we can't decrypt. No screenshots — we never had them.
Bark employees; law enforcement on request Bark's privacy policy explicitly permits disclosure to law enforcement.
School staff, district administrators, contracted counselors Flag routing includes law enforcement in serious cases; see EFF "Red Flag Machine" reporting.
Data brokers (historically) Life360 was found to have sold precise family location data. See The Markup, 2021–2022.
Any process at the same user level Standard-user malware can read the index without admin or a kernel exploit.
What we monetize How the company survives.
A subscription you pay You pay us. That's it. Your LLM key you brought yourself.
A subscription you pay Bark charges parents; not known to sell data.
School district contracts Districts pay per-student. Parents are not the customer.
Historically: family location data Sold precise location to data brokers. Since curtailed under settlement pressure.
Included with Windows Not monetized directly; drives Copilot+ PC positioning.
Does the endpoint user know it's installed Covert vs. present.
Yes Process visible, Start Menu shortcut (Windows), enrollment wizard. We don't sneak.
Optional "stealth mode" available Bark offers a hidden install path.
Depends on district policy School districts vary widely in what they tell students.
Yes — Life360 icon is a value proposition The visible-tracker is the product.
Yes — Recall is a system feature The endpoint user IS the audited user.
Every claim in this table has a source. If a row is wrong, or the incumbent has since changed their policy, email us at hello@backstop.family and we'll fix it.
The pattern
Each of them took a decision that belonged to you. We give it back.
Bark took the taxonomy. Gaggle took the audience. Life360 took the raw data. Recall put the whole day's screen contents in a place other people could reach. The details differ; the shape is the same: an actor between the parent and the minor's screen, extracting decisions the parent used to make.
Backstop's design is written against that pattern. The taxonomy is yours. The analysis runs on your child's laptop. The alerts are encrypted to you. Nobody else, us included, can read them. Nobody else, us included, decides what counts.