gunjanjaswal/RenderLens_Privacy_Policy.html

## RenderLens_Privacy_Policy.html
RenderLens — Privacy Policy
Last updated: 2026-04-22

RenderLens is designed with a zero data collection philosophy.

What we collect
Nothing. RenderLens does not collect, transmit, sell, or share any personally identifiable information, browsing history, page content, cookies, form data, or telemetry.

How it works
All processing happens locally in your browser:

When you click Capture, RenderLens reads the rendered DOM of the active tab via document.documentElement.outerHTML.
The service worker fetches the same URL a second time with fetch() to obtain the raw, un-executed HTML the server returned.
Both HTML strings are stored in Chrome's session storage, scoped to the current tab, and are automatically discarded when the tab is closed or the browser restarts.
The diff viewer compares the two strings locally in an extension page.
No data ever leaves your machine. There are no analytics pixels, no third-party SDKs, no remote endpoints, no cloud sync.

Permissions, and why each is needed
Permission	Why it's required
activeTab	Read the rendered DOM of the tab you explicitly click Capture on.
scripting	Inject the one-line content script that returns the outer HTML.
storage	Keep the captured raw/rendered pair in session storage so the diff page can read it.
<all_urls> (host_permissions)	Refetch the page URL to obtain the server-sent raw HTML. Only fired when you click Capture.
Credentials on refetch
When RenderLens refetches the page URL to get raw HTML, the request is sent with credentials: "include" so that authenticated pages (dashboards, intranet apps) return the same HTML your browser originally received. The response is parsed locally and never leaves your machine.

Children
RenderLens does not knowingly collect any data from anyone, including children under 13.

Contact
Questions or concerns: Gunjan Jaswal — hello@gunjanjaswal.me
	RenderLens — Privacy Policy
	Last updated: 2026-04-22

	RenderLens is designed with a zero data collection philosophy.

	What we collect
	Nothing. RenderLens does not collect, transmit, sell, or share any personally identifiable information, browsing history, page content, cookies, form data, or telemetry.

	How it works
	All processing happens locally in your browser:

	When you click Capture, RenderLens reads the rendered DOM of the active tab via document.documentElement.outerHTML.
	The service worker fetches the same URL a second time with fetch() to obtain the raw, un-executed HTML the server returned.
	Both HTML strings are stored in Chrome's session storage, scoped to the current tab, and are automatically discarded when the tab is closed or the browser restarts.
	The diff viewer compares the two strings locally in an extension page.
	No data ever leaves your machine. There are no analytics pixels, no third-party SDKs, no remote endpoints, no cloud sync.

	Permissions, and why each is needed
	Permission Why it's required
	activeTab Read the rendered DOM of the tab you explicitly click Capture on.
	scripting Inject the one-line content script that returns the outer HTML.
	storage Keep the captured raw/rendered pair in session storage so the diff page can read it.
	<all_urls> (host_permissions) Refetch the page URL to obtain the server-sent raw HTML. Only fired when you click Capture.
	Credentials on refetch
	When RenderLens refetches the page URL to get raw HTML, the request is sent with credentials: "include" so that authenticated pages (dashboards, intranet apps) return the same HTML your browser originally received. The response is parsed locally and never leaves your machine.

	Children
	RenderLens does not knowingly collect any data from anyone, including children under 13.

	Contact
	Questions or concerns: Gunjan Jaswal — hello@gunjanjaswal.me
No results found