Free for 30 days on Scale.Start free
Build8 steps1-2 weeks

Write your Terms of Service and Privacy Policy

ToS + Privacy Policy + Cookie Notice + standard DPA published, lawyer-blessed, version-controlled, and matching what your product actually does.

ToS + Privacy Policy + Cookie Notice + standard DPA published

ToS + Privacy Policy + Cookie Notice + standard DPA published, lawyer-blessed, version-controlled, and matching what your product actually does.

Spin up an agent for the heavy lifting

Drafts the ToS + privacy notice from the data inventory + product spec, in plain language so founders can read what they're signing.

8 steps, 14 official links, 4 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

5Surfaces
8Steps
4Agent prompts
14Official links
5Tools mapped
Surfaces
  • tableSteps
  • tableClauses
  • docLegal docs plan
  • tableVersions log
  • docStatus
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/write-terms-of-service-and-privacy-policy and follow the agent prompt.”

FAQ

Common questions on this template.

Can I just use a template generator and skip the lawyer?
For a side project: probably yes; the template generators (Termly, Iubenda) cover the basics. For a real business with revenue or B2B contracts: no. Templates miss product-specific risk: limit-of-liability caps appropriate to your contract sizes, IP carve-outs for AI features, indemnification scope, governing law that's actually enforceable. Budget $300-$800 for a 1-3 hour SaaS lawyer review of your final draft.
How long should the Terms of Service be?
Short and clear beats long and bulletproof. Stripe's Services Agreement is ~3500 words. AWS Customer Agreement is ~12,000 words. The right length is whatever your product spec demands — every clause should map to a real risk. Don't pad.
What's the difference between a ToS and a Privacy Policy?
ToS is the contract: what users agree to when they use your product (rights, obligations, liability, payment, dispute resolution). Privacy Policy is the legally-required disclosure: what personal data you collect, why, with whom you share it, how long you retain it, what rights users have. They're separate documents; sometimes a privacy policy is referenced from inside the ToS.
Do I need a Data Processing Agreement?
If you have B2B customers whose users you process personal data on behalf of: yes, you'll be asked for one in procurement, often by week 2 of any enterprise sale. Common Paper's free standard DPA is the right starting point. If you're consumer-only with no B2B path, you may not need one yet — but many SaaS companies add it the day the first B2B prospect asks.
Can my AI agents help draft these documents?
Yes, for the first draft. Agents are good at: building the product spec from your codebase, drafting the data inventory, drafting initial ToS and privacy text from a template + your spec, scanning new PRs for changes that affect the docs. They are NOT a substitute for lawyer review on liability, IP, and dispute resolution clauses. The template ships agent prompts inline.
How often do I need to update these documents?
Quarterly review at minimum. Material change updates: when you add a sub-processor, change pricing materially, add a new product feature with new data flows, change governing law or limit of liability. Material changes typically require a 30-day user notice (email + in-app banner). Non-material changes can ship silently with a version bump.

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.