How this actually works, in plain terms
A connected suite means more data flows between tools than a single standalone app. That's exactly why we built hard limits into the system from day one, not as a policy document nobody reads, but as rules the software itself enforces.
The core rule
Before any piece of information becomes visible to your team, we ask one question: what would a coordinator or crew member actually do differently because they saw this? If there's no clear action, it doesn't get surfaced. That single filter eliminates most of what makes data collection feel invasive.
Who sees what
See the full operational and relationship picture for a move: obligation status, timeline pressure, communication preferences, and flagged sensitivities that call for a proactive touch.
See only what affects the physical job — access constraints, special item handling, inventory status. Never budget information, never emotional or relationship signals. That split isn't a permissions setting someone could accidentally change — it's enforced at the system level.
Never see the internal service notes or system-generated signals your team uses. They see their own move status and progress — nothing about how they're being tracked internally.
What we will never do
The system is built to never generate inferences about race, ethnicity, religion, immigration status, or similar categories — even indirectly through address or name patterns.
We don't build a running "customer difficulty" or "risk" score that persists across moves. Operational signals expire when a move completes.
Emotionally sensitive tools (like family support check-ins) only ever pass a presence flag into the shared system — never a transcript, summary, or sentiment score.
Infrastructure & Support
Our infrastructure and processes are built to meet SOC 2 standards — not added on after a customer asked.
One consistent hosting jurisdiction across every account and every module, regardless of where a move originates or ends.
Every company we work with gets a real point of contact who knows their account — not a shared support queue.
One household, one verification
When a household is already verified through one module, every other connected module recognizes them automatically. They confirm who they are once, and never re-enter information a different part of the suite already has. This isn't just convenience — fewer re-entry points means fewer places for information to be mishandled.
We're glad to walk through the specifics with whoever on your team needs the details.
Talk to Us