Lesson 7.1
NDA-safe workflow.
WHAT YOU'LL LEARN
How to use Worktale on NDA'd work without violating the agreement, and how to share outputs safely.
What Worktale captures
Commit metadata only:
- SHA, author email, timestamp, branch name, tag names
- Commit message (the text you wrote)
- Lines added/removed, files changed count, names of changed files
- AI session cost/tokens/tools — but not the agent's transcript content
What Worktale does not capture
- File contents, diffs, or snippets
- Secrets, env vars, or config values
- The agent's conversation transcript
- Any data from remote git hosts
Safe-to-share outputs
- Digest output — uses commit messages you wrote. Review before sharing; if you wrote secrets into a commit message, they'll be in the digest. You'd have the same problem with a
git logpaste. - Stats (
worktale status) — counts only. Always safe. - AI session stats — models and costs. Always safe (no transcript content).
Riskier
- Notes you wrote yourself — may contain sensitive detail. Review before sharing.
- File name lists — the top-modules view may reveal internal structure (e.g.
src/billing/stripe/enterprise-overrides). Consider repo-slug anonymization if you publish.
Repo slug for anonymization
When publishing to Worktale Cloud, each repo has a public slug. Default = repo name. You can override:
$ worktale repos rename acme-proprietary-thing "Client Work"
The public profile will now show “Client Work” instead of the real repo name.