What gets sent
When you run a request, VIBE sends your prompt plus the file context needed to answer it. Context selection is scoped to the current project.
Files excluded by your ignore rules are not read.
No training on your code
Your prompts and repository content are not used to train models, ours or a provider's. We use providers under agreements that prohibit training on customer content.
Retention
Conversation history is stored so sessions can continue, and you can delete it at any time.
Providers may hold request data briefly for abuse monitoring. We prefer zero-retention routes where available.
What stays local
Indexing, file reading, and change application happen on your machine. Changes are written only after you approve them.
Accuracy
Models make mistakes. Inspect plans and diffs before applying. The app is built to make that easy: review, open the diff, undo.
Your controls
- Ignore rules for paths that should never be read
- Session history deletion
- Approval required before any file write
- Telemetry opt-out
Questions about this policy? Write to [email protected].