Pocket ChiefHelpprivacy & cost
How automatic recording handles the screen
- The app captures the screen on the device.
- Screen text is read locally.
- Local cleaning and redaction remove text that should not continue.
- The durable local record stores derived text and metadata.
- If record organization is enabled, only the necessary redacted context is sent to the chosen AI source.
The original screenshot, image bytes, and local file path do not enter model context. Screen Recording is required to complete move-in and keep automatic recording running. Revoking it stops new records and leaves Current Work, Footprints, and Summary with missing or stale input.
Screenshot retention
Screenshots are not uploaded and are not saved by default. If you choose temporary or device-local saving, files remain on this computer and expire according to the retention setting. Deleting a segment removes its related local screenshot/text artifacts.
Three AI paths
| Source | Request path | Cost owner | Important boundary |
|---|---|---|---|
Cloud |
App → Pocket Chief Cloud → model provider | Cookies | Cloud keeps identity, task, usage, wallet, order, and support records |
Your API key |
App → selected provider | Your provider account | API key stays in the app’s local secret storage |
Local |
App → configured compatible service | Your local resources | It is local only when the configured URL is local |
There is no automatic fallback between sources.
What stays on this computer
The local workspace can contain Current Work and history, automatic-record metadata and redacted screen text, Footprints and summaries, chat, preferences, integration allow/ignore choices, and optional screenshot artifacts.
An API key stays in local secret storage. Outbound webhooks can send activity and reviews to an endpoint you configure; that endpoint becomes another data recipient.
What Cloud processes
Cloud may process account identity, session/security state, selected prompt context, task and model metadata, token usage, Cookies, wallet and ledger records, purchases/refunds, support ID, and service diagnostics. Raw screenshots are not sent as model input.
Direct and Steam accounts are separate. Their identities, Cookies, purchases, refunds, and entitlements do not merge or transfer. The same operating-system user may open the same local workspace; that is not cloud sync.
Cookies
| Task | Current guide |
|---|---|
| Chat | about 3 Cookies |
| Record organization | about 5 Cookies |
| Record recap | about 5 Cookies |
The final charge follows the actual task. A 15-minute cadence calls the model more often than 30 minutes. BYOK and Local do not use Cookies, but their provider or computer bears the cost.
Each Direct or Steam account can receive 3,000 Starter Cookies once after it completes move-in. The current Direct packs are USD 3 / 3,000, USD 10 / 10,500, and USD 50 / 55,000 Cookies. Direct purchases open Lemon Squeezy from an eligible signed-in app. The website has no universal checkout. Steam purchases use Steam identity and wallet when that channel is public.
Hide, delete, and clear
- Hide activity: removes one activity from normal Review views.
- Delete segment: removes the local batch and related screenshot/text artifacts.
- Clear chat: removes local chat history without deleting automatic records or Current Work.
- Sign out: clears the local Cloud session without deleting the local workspace.
These local actions do not remove provider request logs, Cloud billing records, or payment records already required for service operation.
Product health and diagnostics
Release health reporting can send minimal usage counts, version/platform/channel metadata, and anonymous error diagnostics. Raw screenshots, screen text, chat content, API keys, agent summaries, and full paths should not be included.
Keep one question in mind: which device or service receives this specific action? “Local app” does not mean every optional AI source or webhook is local.