WEBSITE SESSION RELAY

Privacy notice.

Website Session Relay shares a site's login state with a local relay for workflows you authorize. Contact: info@logicaflow.dev.

What the extension accesses

For sites you connect, the extension reads cookies, including HttpOnly cookies, website URLs and localStorage/sessionStorage from permitted matching tabs. It stores connected-site settings, sync status, license state and diagnostics locally. These records can contain sensitive data.

Optional browser profile

Browser profile transfer requires a separate choice for each website. It reads supported User-Agent, viewport, language, timezone, client hints and reported hardware/GPU values. The local relay stores the profile and applies supported values in a separate browser workflow; those values may be visible to the website you visit. This does not copy physical hardware or your entire browser identity. You can disable this choice under Advanced for the website.

Local storage and encryption at rest

Session updates go to the numeric loopback relay on your computer (127.0.0.1), not a LogicaFlow hosted session store. Local loopback transmission between the extension and companion on the same computer is covered by Chrome Web Store User Data FAQ #16 transmission exceptions for local interprocess communication.

Saved session records (session.enc and browser-profile.enc) are encrypted at rest using AES-256-GCM. The master key is generated locally and protected by your operating system keychain or keystore (Windows DPAPI, macOS Keychain, Linux Secret Service via NapiKeyringProvider).

Degraded key mode: If native OS keystore facilities are unavailable, the relay fails closed and refuses to run by default. An unencrypted key stored on disk is used only if you explicitly opt in by starting the relay with the --allow-degraded-key flag or the LOGICAFLOW_DEVTOOL_ALLOW_DEGRADED_KEY=1 environment variable.

Managed storage-state file exports: A plaintext storageState file (for compatible headless browsers such as Playwright) is not written by default. It is created only for websites you have shared in the extension when requested via export_playwright_storage_state. The plaintext file is saved to the private .exports directory with restricted permissions (POSIX mode 0600 or Windows user-only ACL) and remains available for your connected MCP workflow until it is deleted on Disconnect (purge-site), purge-all, or Kill Switch pause.

Legacy migration: Earlier unencrypted session files are automatically inventoried, sealed into AES-256-GCM ciphertext, verified, and deleted. Status reports fullyEncrypted: false until all legacy files are resolved.

Standard storage-state exports restore cookies and localStorage; sessionStorage and IndexedDB are not restored by that export format. Because of the external destinations and AI client workflows below, we do not make blanket claims such as "all data is encrypted", "never leaves your device", or an unconditional "zero-egress guarantee".

External network requests (no zero-egress guarantee)

While there is no LogicaFlow hosted session store, using the relay is not a "zero egress" system. External network requests occur in four specific flows:

• Destination websites: Keepalive pings, browser actions and automation scripts contact the external websites you explicitly select.
• AI clients and model providers: Your MCP AI client receives requested tool results (which can include cookies, tokens or page content). Your AI client may transmit those results to its configured cloud model provider (such as Anthropic or OpenAI). Review your AI client's and provider's policies before connecting confidential sites.
• License authority and payment: Free tier requires no network requests. Paid Standard activation and periodic validation contact Lemon Squeezy (merchant) and LogicaFlow's signed license authority (license.logicaflow.dev) with your license key, instance activation ID and release build metadata. Responses can contain purchase-related name/email. Lemon Squeezy handles checkout data under its own policies. The license authority records feature entitlements, device activations, subscription dates and build history; it does not receive or store license keys, cookies, or website sessions.
• Diagnostics and support: If you choose to share diagnostics, the optional macOS helper creates an editable Apple Mail draft, or you can attach log.txt manually. Sending the email transmits reports through your email provider.

This website

This static site does not include analytics, advertising scripts, embedded social widgets or an account database. Demo media is served from this site. The hosting provider receives normal website request information, such as IP address and user-agent, to serve and protect the site. Following a LinkedIn or X link takes you to that provider's site.

Your controls and data lifecycle

You choose which sites to connect and when data is retained or erased. Control actions have distinct effects:

• Kill Switch / pause: Pauses relay tool operations, closes active automation browsers, and deletes managed unencrypted exports in .exports. Encrypted session files on disk are retained. Pausing does not revoke your login session on the website server, nor does it recall copies previously exported outside the relay.
• Disconnect (in extension): Removing a site in the extension triggers purge-site on the relay if connected. If the relay is unreachable, the extension removes the site locally and warns that the relay copy remains until purged. Disconnecting does not log you out of the website inside Chrome or on the website's server.
• purge-site: Deletes that domain's encrypted session file, browser profile, and managed storage-state exports from the relay, and closes its automation browser. It does not terminate the remote website session.
• purge-all: Deletes all stored session files across all sites, purges the master key from the keystore, closes all automation browsers, and leaves the relay paused. It does not log out remote websites or clear Chrome's internal cookies.
• Website logout: Signing out on the website inside Chrome or on its server terminates the session remotely; however, local saved relay files remain until the logged-out state is synchronized or purged.
• External copies: Files, scripts or exports copied outside the relay's managed .exports directory cannot be recalled, tracked, or purged by any relay action.

Support and diagnostics

Diagnostics are generated locally. You choose whether to share them. The optional macOS email helper receives your selected diagnostic report through a private local file and opens an editable Apple Mail draft. It does not send the email for you. Temporary job metadata is removed after handoff; unsent attachment files may remain locally until cleanup or deletion. Redaction is best-effort; review reports before sending. Emailing support sends your message and attachments through email providers. Do not send passwords, cookies, license keys or session files.

Chrome Web Store Limited Use disclosure

LogicaRelay adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements:

• Single purpose limitation: Data usage is restricted exclusively to providing and improving the single user-facing purpose: sharing the authenticated session of websites selected by the user with the local relay for the user's authorized MCP and Playwright workflows.
• Not sold: Data is never sold to third parties under any circumstances.
• No personalized advertising: Data is never used or transferred for personalized advertising, retargeting, profiling, or interest-based ads.
• No credit or lending: Data is never used or transferred for determining creditworthiness or for lending purposes.
• Restricted transfer: Data is not transferred to third parties except as strictly necessary to execute the user's requested workflow (such as destination website requests, user-configured AI model providers, or merchant license verification) or to comply with applicable law.

Chrome Web Store data categories disclosure

In compliance with the Chrome Web Store developer dashboard privacy declarations, LogicaRelay declares the following data categories:

• Authentication Information (credentials, cookies, tokens): Read from user-selected websites after explicit host access is granted. Transferred exclusively over local loopback (127.0.0.1) under Chrome Web Store User Data FAQ #16 transmission exception for local interprocess communication. Encrypted at rest via AES-256-GCM with OS keychain/keystore protection.
• Web History / URLs: Limited strictly to the URLs of tabs matching user-selected websites for session synchronization. General browsing history is never tracked (no history or broad tabs permissions).
• Website Content / Storage: localStorage and sessionStorage items read from user-permitted tabs to enable session automation.
• User Activity: Interaction state in the extension popup, site connection choices, and local relay operational events.
• Personal Identifiers / Purchase metadata: Paid Standard license responses from Lemon Squeezy may include customer name and email address; not retained in session records. There is no location collection, history API tracking, advertising, or hosted session analytics.
• Diagnostics / System Information: Bounded local diagnostic logs and optional browser/environment profile attributes collected only upon explicit per-site user consent.

No "no user data" assumption: Even though session records and cryptographic keys reside locally on your computer, user data is processed by the extension and local companion. We do not claim "no user data" simply because storage is local.

Notice on operational terms: This privacy notice and accompanying product terms describe operational characteristics and developer preview rules; they are not a formal legal compliance certificate or statutory audit certification.

Contact and updates

For privacy questions or a request concerning information you sent to support, email info@logicaflow.dev. This notice will be updated when product data flows change.