End-to-End Encrypted

Security

Lumber is built so it can't read your logs. Your servers encrypt each one before it's sent, with a key that never reaches Lumber in readable form, and only the people you give access decrypt them, on their own devices.

This page is for teams deciding whether to send Lumber logs that carry personal, health or payment data. Encryption has the algorithms and the details.

What Lumber Can and Can't See

Lumber's servers store your logs and deliver them to your devices, but what they say is encrypted. A few details stay readable so the service can work.

Lumber Can't Read

  • Each log's message, request and trace IDs, context and metadata
  • The notes your team writes about logs
  • Your apps' encryption keys, which it stores only wrapped to each reader's account key

Lumber Can Read

  • Each log's level and time, so it can filter by level and send push alerts
  • Which app each log belongs to, who wrote each note, and which logs are flagged
  • Your account (email, name and plan) and each app's name, color and logo URL
  • A SHA-256 hash of each API key's token, never the token itself

Every field, and why each readable one stays readable: What the Server Sees

Where the Keys Live

Two kinds of key keep your logs closed: each app's encryption key, and each person's account key, which carries app keys between people and devices.

On Your Servers

Each app has its own 256-bit encryption key, made on the device of whoever creates the app. Every API key for the app carries it, and Lumber's client encrypts each log with it before the log leaves your process. The key itself is never sent.

API Keys

On Your Devices

Each person has an account key. Its private half stays in each of their devices' secure storage: the Keychain on iPhone and iPad, a file encrypted with a key the system holds in the desktop app, and the system's credential store for the lumber command.

With Your Team

To give someone access, a device that has the app's key encrypts it to their account key, and Lumber stores that copy without being able to open it. Someone new gets keys only once a person who has them confirms the newcomer's account key with a short code, so Lumber can't slip in a key of its own.

Confirming a Key

On a New Device

A new phone or computer gets your account key from one you already use, once you type the 7-digit code that one shows. Lumber carries the exchange but never sees the code, so it can't send your key anywhere else.

Linking a Device

If Lumber Is Breached

Someone who broke in and copied Lumber's database would find:

  • Logs and notes they have no key to decrypt
  • App keys wrapped to account keys that are kept on your devices
  • Hashes of API key tokens, which can't be used to send logs to your apps
  • Passwords stored as bcrypt hashes

They could read what Lumber can: account details, app names, and each log's level and time.

Read the Code

The code that encrypts your logs on your servers, and the lumber command that decrypts them on your computer, is public on GitHub under the MIT license, so you can check what it does rather than take this page's word for it.

The rest is private: the Lumber app, which also decrypts your logs, its desktop shell, the API, the server behind live streaming and the background worker.

Where Lumber Runs

Lumber's API runs on Vercel, its database on Supabase, and its live streaming and background work on Amazon Web Services. Everything between your servers, your devices and Lumber travels over TLS.

Payments go through Stripe, so Lumber never sees card numbers. Push alerts go through Expo and Apple, and carry an app's name and a log's level and time, never what the log says. The Privacy Policy lists every service Lumber uses and what each one receives.

Keep in Mind

What end-to-end encryption asks of you, and what it doesn't cover.

Lost Keys Can't Be Recovered

If nobody with access to an app still has its key on a device, and no server still has one of its API keys, the app's logs can't be decrypted, by you or by Lumber.

Losing the Key

Keep API Keys on Your Servers

Each API key carries its app's encryption key, so it belongs only in processes you run. Never put one in a phone app, web page or game you ship to people.

Keep the Key on Your Servers

An Agent's Model Sees What It Reads

The lumber command's MCP server decrypts logs on your computer for your AI agent. The service that runs the agent's model then receives the logs it reads, under that service's own terms.

AI Agents

No Key Rotation Yet

An app's encryption key can't be changed yet. Replacing an API key gives it a new token, but the new key carries the same encryption key.

Key Rotation

Report a Vulnerability

If you find a security problem in Lumber, email security@infinitetoken.com with what you found and how to reproduce it, and give us time to fix it before telling anyone else.