Agency data isolation
Every query is scoped to your agency at the database level, not just hidden in the interface — there’s no path that lets one agency see another’s data outside the agency-connection feature you choose to turn on yourself.
Data isolation between agencies in Trackr isn’t a matter of hiding things in the interface — every job, client and financial query is scoped to your agency at the point it’s made. There’s no path that lets one agency see another’s data, outside the agency-connection feature you explicitly choose to turn on yourself.
Why isolation is structural, not a setting
In a lot of software, “your data is separate from other customers’ data” really means a permission flag somewhere that could, in theory, be misconfigured or switched off by mistake. That’s not how it works in Trackr. Every query for a job, a client, a note or a financial assessment is scoped to the requesting agency at the point the query is made, not filtered out of a shared result set afterwards. There’s no admin toggle to accidentally leave off, because there’s no broader pool of cross-agency data for a toggle to hide in the first place.
What it means for the people actually using Trackr
Staff, field agents on the native iOS and Android apps, and clients logging into their own portal all sit on the same underlying system, but none of them can see past their own agency’s boundary. A field agent working a job for Agency A has no path to Agency B’s jobs, even though both agencies might be running on the exact same Trackr infrastructure at the same time. Client logins work the same way — a client only ever sees the jobs and records that belong to the agency relationship they’re part of, regardless of how many other agencies happen to be using Trackr.
Where agencies do share visibility — and why that’s opt-in
The one deliberate exception is the agency-connection feature: two agencies that genuinely work together, for example a referring agency and a subcontracted agency handling the on-the-ground work, can choose to connect their accounts and share specific job information across that connection. Both sides have to opt in for that to happen. Outside of a connection either agency has actively set up, there’s no default visibility into another agency’s data at all.
Why this matters for process serving, repossession and debt collection
Agencies in this space are frequently competing for the same referral work from the same law firms, finance companies and debt collection clients, sometimes while also subcontracting to each other on individual jobs. That combination — competitors who are occasionally also collaborators — makes data isolation more than a technical checkbox. A firm referring sensitive defendant, asset or financial information to an agency needs confidence that using a shared platform doesn’t mean that information is visible to a rival agency also using it. Structural, database-level isolation is what makes that a straightforward “no” rather than a policy promise.