Redev Privacy Policy
Last updated: July 25, 2026
Redev ("the extension") is a developer tool for inspecting and debugging React applications, with an AI chat assistant integrated into its Chrome DevTools panels. This policy describes what data the extension handles and where that data goes.
The short version: Redev has no servers, no telemetry, and no analytics. The developer of Redev never receives, stores, or has access to any of your data. Data leaves your browser in exactly one case: when you ask the AI assistant a question, the relevant debugging context is sent to the AI provider you explicitly configured. If you configure a local provider (such as Ollama running on your own machine), nothing leaves your computer at all.
Data handled by the extension
Inspected page content ("website content")
When you open the Redev panels in Chrome DevTools, the extension reads data from the page being inspected: the React component tree, component names, props, state, hooks, rendering performance measurements, and — when the page publishes source maps — original source file contents. This data is displayed to you inside DevTools.
When you ask the AI assistant a question, the parts of this data needed to answer it (for example a component subtree, a source code excerpt, or profiling measurements), together with your question, are sent to the AI provider configured in Settings → AI. They are sent only when you submit a question, and only to that provider.
User activity during profiling (optional)
If you enable "Record user interaction events while profiling" in Settings → AI (off by default), profiles additionally record interaction event types (for example click, scroll, key event) and their timestamps to help correlate interactions with renders. Key values, input text, and event targets are never recorded. This data is part of the profiling context that may be sent to your configured AI provider when you ask a question about a profile.
Settings and credentials
Your preferences (panel settings, chosen AI provider, base URL, model name, enabled skills) are stored locally in your browser profile using extension storage. If you sign in to an AI provider (for example with an OpenAI account), the resulting tokens are stored locally in your browser and are sent only to that provider to authenticate your requests. The developer of Redev never receives your credentials.
Where data goes
| Data | Destination |
|---|---|
| Everything you inspect | Displayed locally in DevTools |
| Chat questions + debugging context | Only the AI provider you configured, only when you ask |
| Settings and credentials | Stored locally in your browser |
| Anything at all | Never to servers operated by the Redev developer — none exist |
Data sent to an AI provider is processed under that provider's own terms and privacy policy (for example OpenAI's, or no third party at all when using a local Ollama instance). Choose a provider you trust with the content of the pages you debug.
What the extension does not do
- No telemetry, analytics, crash reporting, or usage tracking of any kind.
- No selling or sharing of data with third parties.
- No use of data for advertising, profiling, creditworthiness, or lending.
- No collection of browsing history, location, or personal information.
- No remote code: all executable code ships inside the extension package.
Data retention
The Redev developer retains nothing, because nothing is ever transmitted to the Redev developer. Locally stored settings and conversation state can be removed at any time by clearing the chat, signing out of a provider, or uninstalling the extension. Retention of data you send to an AI provider is governed by that provider's policy.
Changes
Changes to this policy will be published on this page, with the "Last updated" date revised.