← SAM

SAM Privacy

Short version: SAM stores everything on your machine and phones home to nobody. No account, no tracking, no analytics. The one thing that does leave — a request you send to a cloud model you configured — is spelled out plainly below rather than buried. This document is exact.

What SAM stores, and where

All of it, locally, always:

What leaves, when you ask a cloud model

Be clear-eyed about this one, because it is the only routine exception and a vague promise here would be worse than none.

Choose a cloud brain, and your request goes to that provider under their terms — the same as using their API directly. That request is not only what you typed. To answer you, SAM may first read a file, a web page, an email or your clipboard, and the result becomes part of the conversation sent to the model. So a file you asked SAM about does leave the device, to that provider, for that request.

What never rides along, even then: your stored memory and vault, the life index, learned preferences, and usage stats. Only the conversation in play is sent.

Offline mode sends nothing at all. Point SAM at a local Ollama model and there is no exception left — no request, no content, nothing on the wire. That is the mode to use for anything you would not hand to a third party, and it is the mode this claim is measured against.

The one optional thing: anonymous telemetry (OFF by default)

To know whether people actually use and keep SAM, there's an opt-in anonymous ping. It is:

Exactly what IS sent (only if you opt in)

FieldExampleWhy
schemasam-telemetry/1version of the format
anonIdrandom 32-hexcount distinct installs (nothing else)
version3.1.1which release is in use
osdarwinplatform mix
dautruewere you active today (retention curve)
retentionBucketd7how long you've kept SAM (d1/d7/d30/d30+)
activatedtruedid you complete a first successful task
crashFreetruestability
features{tasks: 12, toolUses: 34, workflowRuns: 2, cacheHits: 4}which capabilities get used — counts only

Exactly what is NEVER sent — even if you opt in

Prompts · messages · file names or paths · tool inputs · workflow contents · learned preferences · your name/email · location · IP-derived identity · any free text you or the model produced. The telemetry payload is built from a whitelist of aggregate numbers; content cannot appear in it. There is a test (telemetry.test.ts) that feeds a poisoned stats object full of fake secrets and asserts none of it reaches the wire, and a isSendable() tripwire that refuses any payload with a non-whitelisted key.

Where telemetry goes

If enabled, the anonymous payload posts to SAM's own aggregate endpoint (the same anonymous-device-id gateway pattern used for the optional free brain — no third-party analytics SDK, no ad networks).

Your controls

If a feature can't be built without transmitting your content, SAM doesn't build it. That's the rule.