Exactly what the browser integrations do.

Safari

Embedded Safari Web Extension

• Safari support comes from the embedded ActualFocus Safari Web Extension.
• The Safari extension currently requests `nativeMessaging` and `tabs` permissions.
• Its content script runs on normal `http` and `https` pages so it can read the current page URL and page title from the visible page.
• The current implementation sends the active page URL and page title locally to ActualFocus so the app can derive the domain and URL scheme.

Chrome

Chrome Web Store extension + local bridge

• Chrome support comes from the public ActualFocus Chrome extension on the Chrome Web Store.
• The Chrome extension currently requests the `tabs` permission.
• Its host permissions are limited to the local bridge endpoints on `127.0.0.1:41073` and `localhost:41073`.
• The current implementation reads the active tab URL and title, then posts them locally to ActualFocus while the app is running.

What stays local

Stored versus transient browser data

• ActualFocus persists the browser name, domain, URL scheme, and page title while a session is running.
• Full URLs are used transiently for local browser-to-app delivery and are not stored or sent off-device.
• Browser metadata stays local unless you explicitly export your local data.
• Browser domains only count when a browser is actually frontmost in ActualFocus.

When it matters

How browser activity fits into sessions

• Browser setup is optional. The app still works without it, but website-aware classification is less specific.
• The browser path can send the current active page locally while ActualFocus is running so connectivity is available.
• ActualFocus is designed to persist browser metadata during active sessions rather than become a continuous off-device browsing log.
• Background tabs do not earn focus credit by themselves. The frontmost browser context is what matters.

What it does not do

Boundaries that should stay boring and explicit

• It does not record audio.
• It does not record webcam video.
• It does not log keystrokes.
• It does not send raw page content off-device.
• It does not turn your browser history into a remote activity feed by default.

Your control

Optional setup, reversible later

• You can skip browser setup entirely and still use ActualFocus.
• You can turn off the Safari extension from Safari settings.
• You can remove the Chrome extension from Chrome like any other extension.
• If you remove browser support, the app still works, but website classification and browser-specific recap detail become less specific.

If you want the broader data boundary, use Privacy. If you want the official contact path, use Support. If you want the code itself, use the public browser repository.