Privacy Policy

LayoutPilot is built for local frontend inspection and visual review. Its processing happens in the user's browser and starts only when the user activates the extension for the current tab.

Local-first visual tooling

Designed to inspect layouts, mark issues, and export review assets without sending your data elsewhere.

LayoutPilot is a Manifest V3 Chrome and Edge extension for frontend developers, designers, and QA reviewers. It helps inspect page layout, compare spacing, create visual annotations, copy or download annotated screenshots, and generate printable review reports directly in the browser.

Local-only No backend No tracking No third-party sharing User-controlled activation

Overview

This policy explains how LayoutPilot handles technical page data while supporting local layout inspection, visual annotation, screenshot, and report workflows inside the browser.

LayoutPilot does not operate a backend service, does not send inspected page data or screenshots to external servers, and does not share or sell user data.

Single purpose

LayoutPilot has one purpose: help frontend developers, designers, and QA reviewers inspect visual layout details and create local review artifacts for the page they are actively working on.

The extension runs on a page only after the user activates it from the browser extension UI for the current tab.

Data handled locally

To provide its inspection and review features, LayoutPilot may process technical data locally such as:

  • page structure and element metadata from the active tab
  • computed layout and style information, including size, spacing, colors, typography, classes, and selectors
  • visible-tab screenshots used for copy, download, snapshot, and printable report features
  • review annotations, area marks, pen marks, notes, colors, and temporary review state
  • language preference, last selected mode, and lightweight extension settings

This processing happens inside the browser on the user's device.

Data we do not collect

LayoutPilot does not collect or transmit data to a company backend because it has no backend.

  • no analytics or telemetry
  • no advertising identifiers
  • no cross-site tracking
  • no profiling
  • no sale of data

How data is used

Technical data is used locally and only to support the extension's visible features, including:

  • highlighting and inspecting elements in the active tab
  • showing spacing, dimensions, style details, selectors, and copied layout context
  • creating visual annotations, area marks, and pen marks for review workflows
  • copying or downloading annotated images and generating printable review reports
  • preserving local preferences needed for the tool between sessions

Local storage

LayoutPilot uses the browser's extension storage for lightweight local data such as installation time, selected language, last selected mode, and review color preferences.

Review annotations and visual marks are maintained in the active page session so the user can inspect, export, or print the current review without relying on remote infrastructure.

Third-party sharing

LayoutPilot does not share inspected page details, screenshots, annotations, preferences, or generated review artifacts with third parties. It does not sell data and does not make local review data available to advertisers, data brokers, or external analytics providers.

Remote code

LayoutPilot does not execute remote code. Its JavaScript, HTML, CSS, images, and related assets are packaged with the extension itself.

The extension's scripts are loaded from extension resources, not from remote servers, and the product is not designed around externally hosted executable code.

Permissions

LayoutPilot uses browser permissions only to provide its inspection, review, and responsive preview features. These permissions allow the extension to run on the user-selected tab, inject the inspection/review UI, capture the visible tab for user-triggered exports, and save lightweight local preferences.

These permissions are used only for the extension's stated purpose. They are not used for tracking, advertising, analytics, or background data collection.

When the user enables Responsive Preview, LayoutPilot may create a temporary rule for the current tab so the selected page can load inside the preview iframe when frame-related headers would otherwise block it. This rule is limited to the active tab, applies only while Responsive Preview is active, and is removed when the preview or tab is closed.

LayoutPilot does not read, collect, store, or transmit request/response bodies, credentials, browsing history, personal data, or page content through this permission.

activeTab scripting storage declarativeNetRequestWithHostAccess

User control

The user chooses when LayoutPilot is activated, which browser tab is involved, which review marks are created, and when screenshots, downloads, clipboard copies, or printable reports are generated.

LayoutPilot does not silently inspect unrelated tabs and does not upload generated review artifacts.

Last updated

May 30, 2026