Privacy controls you can actually find

Privacy settings fail when they read like a contract negotiation. We surface warnings when a feature needs network access or sends audio off-device, in plain language at the moment of use.

Analytics and optional enhancements are labeled separately from core translation flows. Defaults favor transparency: you should understand what is on-device versus what leaves it.

Downloads for offline content show intent clearly—what you are storing, roughly how much space it takes, and how to remove it.

Policies will evolve with regulation and product reality; the goal is that controls remain discoverable and understandable after each update—not hidden behind nested menus.