Alt DevTools privacy policy
Updated
This policy covers the ALT-DEV TOOLS Chrome extension (item ID jgnnmodcgocnepddcgpnacohblfmhbga), published by Coding Frontend. Alt DevTools inspects the page you choose in Chrome’s side panel. Inspection data stays in your browser. Pro licensing and purchases use the CodingFrontend.in website and license service.
What the extension reads and why
When you connect an inspection target, Alt DevTools uses the tab’s URL and page content to display elements, styles, console output, source files, network traffic, and site storage. Depending on the tools you open, this can include request URLs, headers and bodies, cookies, stored values, and page runtime data. These can contain personal information or credentials. Alt DevTools does not upload inspected content or browsing activity to Coding Frontend or use it for advertising or analytics.
Optional advanced inspection uses Chrome’s debugger to inspect network traffic and scripts, run user-entered console expressions, record performance, or emulate a device. Chrome shows a debugging banner when attached. You can pause or close an inspection. If you request a source file or a web app manifest, the extension may fetch it from the site serving that resource; the site receives the ordinary information sent with that request.
What stays on your device
Inspection logs and imported profiles are held in memory for the inspection session. Chrome extension storage keeps panel preferences, per-site capture settings, saved response overrides, and your Pro license and activation state. Saved overrides can include a resource URL and the edited content you supplied. You can remove them in Sources. Removing the license clears its saved details after deactivation; uninstalling clears the extension’s local storage.
Reports, network archives, copied requests, and performance files are exported only when you choose. Review them before sharing: copied requests and raw profiles can contain credentials, URLs, and other sensitive data. Alt DevTools does not send those exports to Coding Frontend.
Pro activation and license verification
When you activate, verify, or deactivate Pro, the extension sends your license key, product identifier, and a browser instance label or activation ID to CodingFrontend.in over HTTPS. Our service receives ordinary connection information such as the IP address. Activation records include a keyed hash of the license, the product and activation IDs, status, and verification timestamps. None of these requests include inspected page content.
Checkout, email, and service providers
If you buy Pro on CodingFrontend.in, we use the contact and billing details you submit, such as your name, email address, phone number and billing country, along with any coupon, order total and payment reference, to process the purchase, keep transaction records, and support it. The website uses a session cookie to connect your browser to the order.
- Cloudflare hosts the site and license service. Its infrastructure handles requests and connection data as part of delivering and protecting those services.
- Our payment processor handles payment details entered in its payment window. Coding Frontend uses the payment reference and confirmation to fulfill the order and does not receive full card numbers or security codes.
- Our email provider delivers your license and invoice to the address you submit and handles emails you send to us.
The extension does not sell user data or use it to determine creditworthiness or for lending. Website visits and support requests are also covered by the Coding Frontend website privacy policy.
Chrome Web Store Limited Use
Alt DevTools uses information received from Chrome APIs in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Privacy questions and requests
Contact Coding Frontend to ask about your data or request access, correction, or deletion of records we hold. We may need to keep some payment or invoice records for accounting or legal obligations. If you send a report to support, remove credentials and other sensitive information first.