Start here
The free tool below runs entirely in this browser — no account, nothing stored or transmitted. Redact anything you would not want kept before you type it.
Open the companion tool →Why developer tools require separate data mapping
Inline code suggestions, workspace indexing, and cloud telemetry often collect file context, project directory names, and adjacent code snippets by default.
Mapping which files are excluded, disabling telemetry and model training on your code, and isolating sensitive secrets protects both personal and workplace assets.
The protocol
- List every code assistant plugin, IDE extension, and command-line tool installed.
- Inspect telemetry, codebase indexing, and model-training toggles in settings.
- Verify that .gitignore and assistant ignore files exclude .env, API keys, and private data.
- Review the vendor's data retention policy and enterprise privacy commitments.
- Establish a team or personal checklist before opening repositories with AI tools enabled.
What the tool does
Create a cloud code assistant data and privacy audit It runs locally in this browser and sends nothing.
Limit first: This is a preparation aid, not authentication, legal, financial, medical, or emergency advice. It cannot inspect accounts, verify identities, contact an organization, or guarantee an outcome.
Open the companion tool →One human next step
Review your organization's internal code governance policy or the plugin vendor's terms of service. For workplace environments, consult your security or legal team before indexing proprietary code repositories.
Research log and safety checks
AI-assist path: not used for a verdict. This builder organizes the reader's own records and directs them to an independent source; it does not infer authenticity or legal rights. §6.10: not a frontier-pace topic.
§0.5 protection result: category is data-privacy-exposure; crisis-adjacent: no; fear/urgency/scarcity toolkit used: no. The protective function is free and the paid feature is convenience only.