LeftOff logo LeftOff

Privacy

Private by default, readable on purpose.

LeftOff stores your saved place in the browser so it can restore the exact reading position when you come back. The goal is simple: keep your reading trail on-device, clear, and easy to understand.

Last updated: March 24, 2026

Permissions

LeftOff currently requests these Chrome extension permissions:

  • contextMenus to add the save action to the page context menu
  • storage to save leftovers in the browser
  • tabs to reopen saved leftovers from the popup

The current manifest does not request optional permissions or host permissions outside its content-script scope.

Content Script Scope

The extension currently runs on normal web pages matching:

  • https://*/*
  • http://*/*

This is broad host access across normal web pages. It is intentional for the current MVP and should be disclosed clearly anywhere LeftOff is published.

What LeftOff Stores

To restore where you left off, LeftOff stores this data in chrome.storage.local:

  • the page URL
  • selected text
  • selected text context
  • DOM location metadata
  • scroll position
  • titles and timestamps used in the popup

The extension currently keeps this information on-device in the browser profile. LeftOff does not transmit saved leftovers to a remote server.

User-Facing Behavior

  • LeftOff only saves a position when the user highlights text and invokes the save action.
  • When a saved page is revisited, the content script attempts an automatic restore after page load.
  • Restore may scroll the page, reselect saved text, or fall back to the stored scroll position.
  • LeftOff does not run on restricted browser pages such as chrome://.

Scope And Limitations

  • LeftOff runs on normal http and https pages that match its content-script scope.
  • It does not run on restricted browser pages such as chrome://.
  • Restore quality may degrade on pages that substantially rewrite their DOM after the position was saved.

Current Privacy Position

LeftOff is currently designed around browser-side storage for saved leftovers. If the storage model, scope, or product behavior changes, this public page and the internal policy docs should be updated in the same change.