Do not submit machine-translated privacy labels as-is
Nutrition labels and Data Safety wording must match facts in your privacy policy. Machine translation that turns “device ID” into another data type is a different declaration.
Nutrition labels and Data Safety · Privacy policy · Localization · Telegram @hagee66
Labels are declarations, not copy polish. Machine translation can draft; it cannot be the submission.
Three terms to verify by hand
- Identifiers: advertising ID, device ID, account ID must not become “we collect nothing.”
- Location: coarse vs precise must not be dropped in translation.
- Sharing: data sent to ad or analytics services must not read “stored only on device.”
After review, policy link, Apple nutrition labels, and Google Data Safety must share one set of facts. Languages may differ; facts may not.
Goee can flag conflicts between translations and your SDK table. We will not invent a “safer” collection scope or promise label approval.
FAQ
Q: Only a Chinese policy—can we machine-translate for the English store?
A: Translate first, then have someone who knows what the app collects fix factual errors. Do not submit unedited bulk machine output.
Q: Labels are short—can they still be wrong?
A: Shorter text makes wrong categories easier. Even one line should be checked against the SDK table.