Translate safely: protecting privacy and consent when using automatic translation

You press send on a translated survey and then someone replies with their life story in the free-text box — in a language nobody on your team reads.

Automatic translation makes that moment less scary, but it does not remove the responsibility you have for peoples privacy and consent. Small teams in schools, councils and charities can put simple safeguards in place that protect participants without turning every form into a compliance project.

Why translation changes the privacy question

Automatic translation speeds up access. It also changes who sees what. When a participant writes something sensitive in a language your team does not understand, the text becomes intelligible to staff or third party tooling only after translation. That introduces a few risks:

• Identifiable information is exposed in translation, increasing who can read names, addresses or health details.
• Third party translation services may process text outside your usual systems.
• Consent statements can be mistranslated, meaning people might agree to something they did not understand.

Understanding those risks helps you design surveys and workflows that keep translation useful and safe in practice.

What to watch for in responses

Not all translations create the same level of risk. Watch for these common problem areas.

• Identifiable information: names, addresses, phone numbers, date of birth, national identifiers. If you do not need them, do not collect them.
• Third party data: mentions of other people, organisations, or witnesses. These names become part of your records once translated.
• Sensitive topics: health, immigration status, safeguarding issues, crime reports and financial hardship. These often require special handling.
• Consent language: any question that asks for agreement to share data, contact the participant later, or make decisions based on the response needs especially clear translation.

A practical rule of thumb is to assume any free-text box might contain something sensitive and design accordingly.

Survey design to minimise risk

Good survey design prevents many problems before translation is needed. Here are straightforward steps you can take.

• Only ask for identifiers when you absolutely need them. If you only need to contact people for follow up, ask for an email or phone number as an optional field rather than a full name and address.

• Prefer structured options over free-text. Use multiple choice, checkboxes and drop-downs for things like service use, referral reason or satisfaction ratings. Structured data stays consistent across languages and is easier to review.

• If you must collect free-text, be explicit about scope. Add a single-line hint such as Please tell us about the appointment itself, not names or contact details and present that hint in the participants language.

• Avoid file uploads unless essential. Uploaded documents can include scanned IDs or forms with sensitive material. If uploads are necessary, give clear instructions and route these to a secure queue for manual review.

• Separate consent from other questions. Put consent statements on their own page or at the top of the form so they are less likely to be missed. Make the translated consent text visible before the participant proceeds.

• Provide an option to request a human translator. Sometimes automatic translation is not good enough for consent or safeguarding. Let participants opt for a human review or a phone call in their language.

Practical secure review workflows for small teams

You do not need a complex process to keep translation safe. Even teams of one or two people can follow these practical steps.

1. Create a secure review queue

Collect responses in a place that has access controls. Make a single inbox or dashboard where responses flagged as sensitive are separated from ordinary feedback.

1. Limit who sees translated free text

Designate a small group of trusted reviewers who will read translated sensitive responses. Fewer eyes reduce accidental exposure.

1. Pseudonymise before translation when possible

If responses include personal identifiers that are not required for translation quality, replace them with placeholders like [NAME] or [ADDRESS] before sending to an external translation tool.

1. Use human review for high-risk cases

If a response mentions safeguarding, legal matters or serious health issues, do not rely solely on automatic translation. Escalate to a trained staff member or arrange for an accredited interpreter.

1. Keep an audit trail

Log who viewed a response, when and why. This helps if questions arise about how sensitive information was handled.

1. Set retention and deletion rules

Decide how long translated copies of responses are kept. Delete temporary translated text once the action requiring the translation is complete.

1. Secure any third party services

If your translation workflow uses an external service, check its data handling. Prefer services that process text securely and offer clear data retention policies. If commercial translation is not an option, keep translations in-house or anonymise text first.

How to explain safeguards to participants

Keeping people informed builds trust. A short, clear explanation in the participants language is usually enough.

• Keep it simple. Start with We will translate responses so we can read them in our language. Then add one sentence about purpose and one about rights.

• Explain choices. Tell participants they can opt out of automatic translation and request a phone call, or leave contact details if they want a human follow up.

• Be transparent about privacy. Say whether translations are done by an automated service and whether those translated copies are kept. Use plain language, not legalese.

• Include a contact method. Give a phone number or email where people can ask about consent, translation quality or data deletion in their language if possible.

Example short notice you can adapt for any language

We will translate your answers so we can understand them. Translations are done automatically, but if you prefer a person to read your response or the matter is sensitive please tick the box to request a call.

This kind of small addition often keeps someone from inadvertently sharing something they did not mean to, or it gives them a safe route for follow up.

Handling sensitive disclosures

Sometimes a response contains something that needs immediate attention. Have a simple plan that staff can follow without delay.

• Flag and escalate: If a response mentions harm, risk or abuse, tag it as urgent and notify the designated safeguarding lead or manager immediately.

• Pause automatic pipelines: For urgent cases, stop automatic sharing or translation to third parties until a human has reviewed the original language if possible.

• Use trusted interpreters: For safeguarding or legal cases, use qualified interpreters rather than relying on automatic translation.

• Offer direct contact: Provide a clear path for the participant to contact you in their language, such as a community liaison, multilingual volunteer or interpreter service.

• Redact and anonymise for wider use: If you want to use quotes in reports or public materials, remove names and identifying details first and confirm the participants consent.

A simple checklist for small teams

• Remove unnecessary identifiers: Check your form and delete fields you do not need.
• Prefer structured responses: Use choice questions where you can.
• Add guidance for free-text: Write a short hint in the participants language about what to include and what not to include.
• Include a visible consent statement: Show translated consent before the participant proceeds.
• Offer an opt-out or human review: Let people choose not to use automatic translation for sensitive responses.
• Create a secure review queue: Separate responses that may need special handling.
• Limit reviewer access: Give sensitive responses to a small trusted group.
• Escalate urgent cases: Have a named person to contact for safeguarding or legal risk.
• Keep an audit log and deletion policy: Record access and clear translated copies when they are no longer needed.
• Communicate clearly: Tell participants how translations are handled and who to contact.

Final thoughts

Automatic translation is a practical way to let more people take part in your surveys and forms. It does not have to mean greater risk if you design your questions thoughtfully, limit what you collect, and set simple secure review steps. Small changes up front often prevent bigger headaches later and help people trust that their words are being handled with care.

If you are unsure about legal or regulatory requirements in your area, check with a data protection officer or legal adviser. For everyday community work, these straightforward safeguards are usually enough to balance accessibility and protection without adding heavy bureaucracy.