JavaScript is off, so the screen carousel stays on its first slide and the charts in the mockups are simplified. Everything else on this page works without it.

Factory Log
X @tryfactorylog Download
How it works Features Privacy Install guide $FLOG Pricing & skills Follow @tryfactorylog on X Download
Privacy

Everything stays on this Mac.

Factory Log has no accounts, no analytics, no advertising and no hosted service. It doesn't read source code, Git history, diffs or terminal output.

What is stored, and where

Agent-written task events live in the event file, by default ~/Library/Application Support/Factory Log/events.jsonl. The app watches that file and keeps two more beside it: narratives.json for the day recaps, and daily-aggregates.json after a confirmed purge.

Installing the CLI or an agent integration changes only the local files named on the setup screen, and only after you press the button.

The only two times it goes online

  • Update checks. Once a day the app asks whether there is a newer release, sending only the app's name and version. A download happens only when you choose Install and Relaunch, and the update is verified by checksum, bundle ID, version and code signature before it is swapped in.
  • Day recaps. When an Ollama-compatible endpoint answers, finished days' project names, task titles and summaries are sent to it to write one sentence per project. The default endpoint is on your Mac; pointing FACTORYLOG_OLLAMA_HOST at another machine sends that text there, so trust that machine first.

What never leaves

Factory Log doesn't upload logs, event history, crash reports or configuration. There is no telemetry to opt out of, because there is no telemetry.

The instructions it installs for agents forbid source code, diffs, command output and secrets in reports. Reports are whatever your agents write — so if an agent ignores its instructions, treat the log like any other local file you would not paste in public.

The optional importers

The importers run only when you start them. The Git one reads commit subjects, dates and author emails from local repositories; if an AI tool is available and you leave AI titles enabled, it sends those commit subjects to that tool to write task titles. --no-titles keeps everything local.

$FLOG and your work

The token is not connected to your log.

Buying a skill pack with $FLOG asks your wallet to sign one payment. It never asks for a report, a project name or a file. Your work history is never linked to a wallet address, and no skill needs network access to run.

  • No account is created, and no email address is required
  • The licence is your wallet address: nothing to revoke, nothing to unsubscribe
  • Holder tiers are a balance read at checkout — no staking, no lock-up, no approvals
  • Uninstalling the app and deleting the Factory Log folder in Application Support leaves nothing behind
◔

Time is estimated, never tracked

There is no tracker, no keystroke logger and no screen recording. Active time is derived from when reports arrive: within a project, reports at most 45 minutes apart form one session, and each session gets 5 minutes of lead-in. Two agents working in parallel count toward both projects.

Treat the numbers as a map of where the time went, not as billing-grade time tracking.