Legal
Chief of Staff privacy
Last updated August 12, 2026
Chief of Staff is a read-mostly coworker for a SKOOR workspace: it can read chats, calls, bookings, callbacks, skills, score, and finance views, draft follow-ups, and take a short list of bounded writes. It cannot run a shell, edit a repository, move money, connect a bank, or publish a phone line. Sending a message needs an explicit confirm.
This notice covers how that coworker handles data. It sits alongside the Privacy Policy, the subprocessor exhibit, and Security.
Who can use it
Internal SKOOR dogfood (@skoor.ai / @shulam.io) may use Chief of Staff today. External workspaces stay off until a data-processing agreement covering the cloud runtime is in place for that workspace. Publishing this notice does not by itself turn the feature on for customers.
Cloud runtime
v1 uses Cursor cloud, operated by Anysphere, Inc. Prompts and tool results are processed on Anysphere’s backend. That remains true if SKOOR later runs self-hosted workers — Anysphere still assembles the final prompt. Anysphere is a subprocessor. See Exhibit A.
What we send — and what we do not
Default: no customer secrets in Chief of Staff prompts. API keys, access tokens, passwords, bank connection credentials, card numbers, and government ID numbers are stripped before a prompt or tool result is sent to the cloud runtime. Connection credentials stay in SKOOR’s vault; the coworker sees the work (invoices, callbacks, score), not the keys used to fetch it.
Do not paste secrets into the Chief of Staff composer. If a secret is pasted, our redaction layer is designed to drop it, but the durable rule is: keep secrets out of the conversation.
Retention and training
- SKOOR does not use Chief of Staff prompts or tool results to train SKOOR models.
- The Cursor account used for Chief of Staff is operated with Privacy Mode on. Under Anysphere’s published data-use policy, customer data is not used to train Cursor or its model providers, and Anysphere maintains zero-data-retention (ZDR) agreements with those providers for Privacy Mode traffic. cursor.com/data-use
- SKOOR does not enable non-ZDR models on that account. Abuse / terms classifiers may retain flagged prompts per Anysphere’s policy; that is an Anysphere control, not a SKOOR training use.
- SKOOR keeps session receipts (actions attempted and denied, token and tool counts, a trust score) to operate and meter the feature. Receipts are not a training corpus.
Security controls that stay on
Allow/deny is enforced even when the model asks. Shell, repository edits, payments, Stripe, bank connect, money movement, and phone-line publish are denied. Daily caps apply. Action receipts are the work proof. Details: Security at SKOOR.