Track language preferences without collecting unnecessary personal data

Language planning usually needs an aggregate view of requested answer languages, not a detailed profile of each viewer.

A practical procedure

1. Count explicit language requests or the language of eligible questions using a stated rule.

2. Avoid inferring nationality, ethnicity or personal identity from language or names.

3. Summarise the counts for session planning and keep individual identifiers out when they are unnecessary.

Worked example: a fictional session

A fictional team records twelve Malay-answer requests and five English-answer requests without storing the viewers' names in its planning sheet.

Check the limits

A bilingual question does not always reveal the language the viewer prefers for the answer.