LFOS Console — Security & Privacy

This is the local app members install on their own computer. It is not a browser extension, not a kernel extension, and it does not request Full Disk Access, Accessibility, or Screen Recording. Read this before you run the install command — especially if the machine holds client files, banking, or Stripe access.

Last updated 30 August 2026.

1. Review the installer first

The command in your welcome email downloads this script from our servers and runs it. Nothing is installed until you pipe it to a shell. To read it without running it:

Mac / Linux

curl -fsSL https://app.lifestylefounder.com/install

Windows (PowerShell)

irm https://app.lifestylefounder.com/install.ps1

The installer does not ask for administrator (sudo) rights. It only writes under your user account.

2. What it installs

Everything lives in one folder: ~/.lfos on Mac/Linux, or %USERPROFILE%\.lfos on Windows.

What	Where
Console app (compiled bundle)	~/.lfos/console/
The `lfos` command	~/.lfos/bin/
Private Node.js runtime	~/.lfos/runtime/
Chats, Business Vault, uploaded docs	~/.lfos/data/
License / workspace token	~/.lfos/config.json
Logs (kept 7 days)	~/.lfos/logs/

It also:

Adds a PATH line (marked # LFOS bin PATH) to your shell profiles so lfos works in Terminal.
Installs login auto-start: a LaunchAgent at ~/Library/LaunchAgents/com.lfg.lfos-console.plist on Mac, or a per-user Scheduled Task / Startup folder entry on Windows. That starts Console when you log in and restarts it if it crashes. It does not run while the machine is asleep or you are logged out.

The installer does not scan Documents, Downloads, email, browsers, or password managers. Claude Code (Anthropic’s CLI) is a separate product. On Mac the LFOS installer checks for it and tells you if it is missing; it does not silently install it. Claude’s own sign-in lives in macOS Keychain, not in our files.

3. Does it run all the time?

Yes, by default — as a user-level process on 127.0.0.1:5367 (this computer only). It is not reachable from other devices on your Wi-Fi.

lfos stop
lfos autostart disable
lfos status

Auto-start is convenience, not a requirement. You can start and stop Console yourself with lfos start / lfos stop.

4. What it can access

The app itself is locked to this computer: it binds 127.0.0.1 only, rejects requests from other websites, and uses a session cookie that other sites cannot send.

There is no Full Disk Access grant and no “give agents the whole drive” switch. What agents can do still depends on the kind of agent:

Agent kind	Read your files?	Write your files?
Advisory (King Consultant and the other talk-to-me agents)	No	No
Action (Executive Assistant, Video Editor, Media Buyer, Tech Officer, Social)	They can read any file your user account can already open. Working directory starts in `~/.lfos`, but there is no path jail on Read.	Write, Edit, and shell commands show an Approve / Deny card (unless you turn on auto-approve or unrestricted). Catastrophic commands like `rm -rf /` are blocked.

Connecting Gmail, Calendar, Stripe, Meta, and similar tools is optional and off until you connect them in Settings. The app does not get a blanket key to Finder, 1Password, your Stripe dashboard, or banking sites.

5. What is transmitted, and to whom

Three channels. None of them scrape your laptop in the background.

5.1 LFOS cloud (app.lifestylefounder.com)

Your setup / license code, so the install belongs to your workspace
Fetching agent instructions (those stay on our servers; they are not in the download)
Tracker and client records that live in the cloud dashboard
Optional crash reports: app version, OS, error code, redacted stack. No chat, no vault, no prompts, no file paths from your home folder. Opt out with LFOS_ERROR_REPORTING=0

There is no Sentry, PostHog, or other third-party analytics SDK in the local app.

5.2 Anthropic (Claude)

Chat, plus any Business Vault context the agent needs for that session, goes to Anthropic on your Claude Pro or Max account. We do not proxy that through our servers and we cannot read those chats. That is the trade of “runs on your Max plan.” Subject to Anthropic’s privacy policy.

5.3 Integrations you connect

Gmail / Calendar / Drive / Notion / Stripe (via Composio): OAuth tokens sit with Composio on an LFOS-owned account, per workspace — not as files on your disk. Disconnect in Settings.
Native connections (Meta Ads, GoHighLevel, YouTube, KIE, and similar): stored locally in ~/.lfos/integrations.json (file permissions 0600) and used only when that tool is on.

If you never connect Stripe or email, LFOS never sees them.

6. How credentials are stored

Credential	Where	Who holds it
LFOS license token	~/.lfos/config.json	Your machine (permissions 0600)
Claude login	macOS Keychain, or Windows Claude credentials file	Anthropic’s CLI
Gmail / Calendar / similar	Composio (cloud broker)	Only after you click Connect
Meta / GHL / API keys	~/.lfos/integrations.json	Your machine (permissions 0600)
Chats + Business Vault	~/.lfos/data/console.db	Your machine — we cannot open it

7. How to fully uninstall

There is not a separate Uninstaller app. In Terminal (Mac) or PowerShell (Windows), run:

lfos uninstall

You will get three choices: stop Console and keep your data (no background CPU; a little storage stays so you can come back with lfos start), completely uninstall and delete everything, or cancel.

A full delete asks you to type yes, shows an irreversible warning, then asks you to type I agree to delete. That wipes chats, vault, the app, and the lfos command. Coming back means starting from scratch — reinstall and go through the interview again to re-enter your business information in the Business Vault.

Scripts can skip the menu with lfos uninstall --keep (stop, keep data) or lfos uninstall --yes (full wipe). Add --claude on a wipe to also clear Claude Code sign-in on this machine.

Then, optional cleanup:

Claude Code is Anthropic’s CLI. Leave it if you use it elsewhere, or uninstall Claude Code separately.
Your LFOS cloud login stays until you cancel with us. Uninstalling the local app does not delete the cloud account.

8. Minimum-trust setup

If you want to try Console with the smallest footprint:

Read the installer URLs above, then run the install command.
Complete setup with the license key; skip Integrations entirely.
Run lfos autostart disable and use start / stop yourself.
Do not connect Stripe, Gmail, or banking-adjacent tools until you are comfortable.
Set LFOS_ERROR_REPORTING=0 if you do not want crash reports sent to us.

Questions about this page: message Dan or Kevin in the LFOS community, or use Report a bug / feedback in Console after install.