Forum Discussion

roselvaggio's avatar
roselvaggio
Verified Community Coach
13 days ago

External VA's, client data, and IP: What would you do in this situation?

Looking for some perspective from other operators who use (or have transitioned away from) third-party VA agencies. When working with an external VA agency, their staff inevitably touches customer phone numbers, addresses, payment notes, door/lockbox codes, internal pricing sheets, and custom messaging workflows. If you found yourself in a situation where you parted ways with an agency—or suspect client lists, proprietary operational workflows, or internal training templates are being reused, retained, or shared outside your agreement, how did you handle it?

Specifically:

  1. Did you rely on legal/contractual enforcement (NDAs, non-competes), or is pursuing that across borders essentially impossible?
  2. What immediate technical steps did you take to lock down data access, revoke shared credentials, and audit what was exported?
  3. How transparent were you with your clients if you couldn't verify whether contact lists were downloaded?

Curious how others have contained the fallout or structured their tech stack to prevent this from happening in the first place.

2 Replies

  • Sorry you're in this spot — once access has been shared, you can't un-share it, so most of the fix is prevention for next time.

     

    On the contract side, an NDA is worth having as a deterrent, but chasing one across borders is slow and expensive, so I wouldn't count on it to get data back. The practical steps matter more: revoke the agency's access the same day you part ways, rotate every shared login and lockbox code they touched, and check the export and login logs to see what was actually downloaded. That check is what decides whether clients need to hear anything, and what exactly to tell them.

     

    Going forward, give outside help their own logins, never a shared one, and only the customer fields that job needs — no payment notes, no full client lists, no pricing sheets unless the task requires them. A short offboarding checklist helps too, so revoking access doesn't depend on remembering it in the moment.

  • HUGEHomePros's avatar
    HUGEHomePros
    Verified Community Coach

    Let's be real, if they really wanted to do something they could. If you gave one a jobber access, they could theoretically just be in there downloading all your stuff then use it to create havoc, if that is their end goal. If a VA company is in the Philippines, then you aren't going to a Pilipino court and trying to sue them or something like that. 

    The best thing you can do is set up a 1password account (or something similar) with restricted access to all the programs they'd be using, then when you cut ties you revoke their log in to that. Anything above that requires a network security vendor or team to set up and is more expensive. Having everything in a password server though is good because they never see the actual password, they just have the 1 password for the initial login then everything else is hidden.