AI coding editors: data policy and company-code checks

Basic check order

1. Start with the official app or extension page and avoid repackaged AI editor installers.
2. Read product privacy, terms, enterprise controls, and model-training settings before using work repositories.
3. Check whether prompts, file contents, terminal output, screenshots, or workspace metadata are sent to a cloud service.
4. Separate personal experiments from company repositories, customer code, secrets, and production logs.
5. For teams, require admin-managed accounts, auditability, approved extensions, and offboarding rules.

Cautions and operating tips

• AI coding tools often create a data-policy question before they create a download-safety question.
• Do not paste secrets, API keys, customer data, or unreleased code into tools that have not been approved.
• Browser extensions, local agents, and MCP tools can expand the permission surface beyond the editor itself.

Related official download guides