Privacy
NOBS is local-first by design. It touches four kinds of data — calendar, contacts, notes, and messages — and each one is treated the same way: read on your device, derived into something useful on your device, and never sent to a server.
On-device data
What NOBS reads
Your events, times, and titles stay on your device. NOBS reads them only to look for openings, deadlines, and conflicts.
What NOBS derives
Free windows, travel buffers, and a realistic estimate of how much each day can hold. Derivation ends at a plan — it is never sent away.
What never leaves your device
On-device data
What NOBS reads
Names and the messaging channels you saved for them. NOBS reads a contact only when you compose a note or message that references it.
What NOBS derives
A short list of who you tend to write to this week, used to surface stale loops and people you might want to follow up with.
What never leaves your device
On-device data
What NOBS reads
Text you paste or type into a note. NOBS treats the note as source material — it is not indexed in the cloud, not synced, not backed up to a server.
What NOBS derives
Action items, dates mentioned in the note, and a shorter recap. Anything derived is stored next to the original note, on your device.
What never leaves your device
On-device data
What NOBS reads
Only the messages you bring into NOBS to draft or analyse. NOBS does not watch your inbox, does not connect to your accounts, and does not subscribe to message feeds.
What NOBS derives
A draft reply, a checklist of asks, and a readiness check against your calendar. The draft lives next to the source message until you send it yourself.
What never leaves your device