1. What data the extension collects
Rilog DevTools is a DevTools panel for debugging web pages. While capture is on (enabled by default, controlled from the extension's popup), the following types of events are recorded for the tab you're inspecting:
| Event type | What is recorded |
|---|---|
| Network requests | URL, method, response status, request/response headers, request/response body, duration |
| Clicks | Element tag, id, class names, visible text of the element (up to 300 characters) |
| Form input | Field name/type and the entered value. Fields with type="password" and card-related autocomplete (cc-number, cc-csc, etc.) are masked before being stored |
| Console | console.warn/console.error messages, uncaught errors and unhandled promise rejections, including stack traces |
| Page location | The URL and origin of the page the event occurred on, and the event's timestamp |
The extension does not collect data that identifies you personally (your name, the browser owner's email, etc.), and does not link captured events to your identity — it simply records what happens on the tab you've chosen to capture.
2. Permissions and why they're needed
- storage — to store settings, user-defined capture rules, and the captured events themselves, locally.
- notifications — to show a native notification when an event matches a user-defined rule (e.g. a request that failed with a 5xx status), even while the DevTools panel is closed.
- Access to all sites (host permissions) — the extension is a general-purpose DevTools debugging tool and needs to be able to capture network requests and events on whichever page the developer opens and inspects.
3. Where and how data is stored
All data is stored exclusively on-device, via the browser's own chrome.storage APIs:
- Captured events — in session storage, scoped per tab.
- Settings, user-defined rules, and panel state (theme, docking, size) — in local storage.
The extension does not send this data to any external server — not to Rilog's servers, and not to any third party. No analytics or telemetry about you or your usage of the extension is collected.
5. Sharing with third parties
We do not sell or transfer captured data to third parties. We do not use data for purposes unrelated to the extension's core functionality (debugging a website), and we do not use it to determine creditworthiness or for lending purposes.
6. Controlling and deleting your data
- The Clear button in the events panel instantly deletes all captured events for the tab.
- The Ignored URLs list in Settings prevents requests to specified domains from ever being captured.
- The capture toggle in the extension's popup fully pauses recording on a given tab.
- Removing the extension from Chrome deletes all of its locally stored data.
7. A note on sensitive data
Because Rilog DevTools is a general-purpose debugging tool, it does not interpret the meaning of what it captures. Form fields typed as "password" and fields with card-related autocomplete are masked automatically, but the body and headers of network requests are captured as-is — if the site you're inspecting sends a password, an authorization token, or payment details in a request, they will be visible in the panel for as long as that data is stored locally.
If you're debugging a page where sensitive data is entered (e.g. a payment form), we recommend temporarily disabling capture from the popup, or adding that domain to Ignored URLs.
8. Children
The extension is not intended for use by children and is not directed at individuals under the age of 13. We do not knowingly collect data aimed at children.
9. Changes to this policy
We may update this policy from time to time. The date at the top of this page reflects when it was last changed. Material changes will also be noted in the extension's Chrome Web Store release notes.
10. Contact
For questions about this privacy policy or the Rilog DevTools extension, contact rilog.ceo@gmail.com.