What it captures

The extension sends data to Skyelight when you start a thread or reply to one. It doesn’t record the pages you browse.

When you start a thread

• Location: the page address and title, and an anchor for the element: its selector, where you clicked on it, and its text.
• Content: your comment and any images you attach.
• Page context: the structure, text and styles around the element. Page context is on unless your workspace has turned it off.
• Browser and page problems, as part of page context: the browser, operating system, window size and color scheme, and anything that had just gone wrong on the page. See Page problems.
• Screenshot: only if your workspace has turned screenshots on. They’re off by default.

A reply sends only the reply. Replies never capture a screenshot or page context.

While you’re signed in with a workspace selected, the extension also asks Skyelight for the threads on the site you’re viewing, so it can draw their markers. That request sends the site’s hostname.

Page problems

When a page misbehaves, the reason is often an error the person pinning never saw. So a new thread also records, from the ten minutes before the pin, up to ten of each of these:

• Errors the page’s own code threw and nothing caught, with where in the code they happened.
• Console messages the page wrote with console.error or console.warn. Never console.log.
• Failed requests: anything the page loaded that came back with an error status, such as 404 or 500. Skyelight keeps the address without its query string, the status, and how long it took. It never sees request or response content, headers or cookies.

Before anything is sent, Skyelight removes query strings and replaces anything that looks like an email address or an access token. It doesn’t record your time zone or location.

To see errors and console messages, the extension runs a small script inside each page from the moment it loads. It keeps the last few problems in the page’s memory and sends nothing until you start a thread there. Errors and console messages need extension version 0.3.0 or later; earlier versions record failed requests only.

When a thread has problems, the Problems icon on the thread’s side rail opens them; it’s dimmed when there were none. Your coding agent gets them too, through get_item.

If an error says only “Script error.”, it came from a script loaded from another site, and the browser hid its details. The thread lists the page’s scripts from other sites it could have come from. Loading that script with crossorigin="anonymous", and serving it with CORS, shows the real error next time.

What the extension redacts

The extension redacts page context in your browser, before anything is sent:

• It never includes a value from any input, text area or select.
• It drops password and payment fields entirely, including their labels.
• It leaves out anything inside an element marked data-skyelight-redact.

A screenshot covers only the visible part of the tab, never the full scrolling page, other tabs or other windows. Form fields and marked regions are covered with solid blocks before the image is stored. If masking fails, Skyelight doesn’t keep the screenshot. See Anchoring and context.

Chrome permissions

Chrome describes the extension’s permissions in broad terms. This table lists what Skyelight uses each one for: