How do you control access for freelance linguists we don't employ?▼
We control the systems they reach, not their personal equipment. Each linguist signs in with MFA and sees only the projects assigned to them. Access expires when a job is delivered or after a period of inactivity, and offboarding removes them from every platform in one step. We also help you set reasonable requirements in vendor agreements, like using a supported operating system, disk encryption and no public AI tools for client content. That combination protects client data without trying to manage hundreds of laptops you don't own.
Can our linguists use machine translation or AI tools safely?▼
Yes, with the right setup. The risk comes from public tools that may keep or learn from what's pasted into them. We help you choose an approved option, often an enterprise MT engine or AI service configured not to retain content, connect it to your TMS where possible, and write a short policy on when it can be used. Some clients forbid MT entirely, so we help you flag those projects. On managed devices we can block risky public tools so the approved path is the easy one.
Do you support video remote and phone interpreting platforms?▼
We support the infrastructure: internet circuits, redundant connectivity, network quality settings, interpreter workstations, headsets and secure remote access for interpreters working from home. The interpreting platform itself, including call routing and scheduling features, belongs to its vendor, and we work with their support team on connectivity or audio issues. We monitor network performance so problems are spotted before interpreters start dropping calls, and we help remote interpreters set up quiet, secure home workstations.
Our healthcare clients want a BAA. What does that mean for IT?▼
If you handle protected health information for healthcare clients, they'll often treat you as a business associate and expect HIPAA-aligned safeguards. On the IT side, that means access controls, MFA, encryption, logging, secure file exchange, backups and an incident response plan, plus making sure your own vendors who touch that data are covered. We support those requirements and document them. Whether a specific arrangement makes you a business associate, and what your agreements should say, are questions for your counsel.
How do we answer client security audits?▼
We start by putting the controls in place that audits usually check: MFA, access reviews, logging, encryption, secure file transfer, vendor management for linguists, incident response and an AI use policy. Then we keep documentation current so your operations lead can answer questionnaires accurately. We can join calls with a client's security team to explain technical details. Your answers represent your company, so you review and sign off; our job is making sure what you say matches how systems actually work.
What happens if a linguist's account is compromised?▼
We disable the account, revoke active sessions and check the TMS logs to see which projects and files were accessed. Because access is scoped to assigned jobs, the exposure is usually limited and easy to describe. We reset credentials, confirm MFA is in place and look for related phishing aimed at your staff. Then you and your counsel decide whether any client needs to be notified under your contracts. We provide the technical facts, including timelines and file lists, so that conversation is grounded.