Privacy
Last updated 27 June 2026
Reins keeps a team in sync on what their AI coding assistants are doing. This page explains what it records, how that information is used, and the controls you have.
What Reins records
When you connect Reins to your AI coding assistant, it receives the activity your assistant already produces as you work, the requests you make and the steps it takes, and uses it to keep your team’s shared status current.
What your teammates see
Your teammates never see your raw conversations with your AI assistant. Reins turns that activity into short, high-level summaries: what you’re working on, recent milestones, and a profile of how you like to work. The underlying raw text is used only to produce those summaries and is never shown in the interface.
Secrets are masked
Before anything is stored, Reins scans for credentials such as API keys, tokens, and private keys, and masks them, so a secret that appears in your activity never lands in the stored record or any summary.
Where your data lives
Your data is stored on the Reins instance your team runs, inside your team’s workspace. Workspaces are isolated, so one team cannot see another team’s data. If your team has enabled decentralized backup, only the distilled summaries are included; raw text never is.
Your controls
- Your working-style profile is yours. Edit or remove any item in it at any time.
- You can clear handoffs and notifications directed at you, individually or in bulk.
- Removing your access removes your identity from the workspace.
Open source, your infrastructure
Reins is completely open source. Feel free to run your own instance with your specific AI provider, so your team’s data and the model it’s sent to stay entirely under your control.
What Reins does not do
Reins does not sell your data or use it for advertising. It exists for one purpose, keeping your team in sync.
Questions
For data requests or questions, reach the team that operates your Reins instance.