Policies

Legal, security, and the product owner read the same draft.

Argue in threads on a team-only policy update. Agent connect fixes a retention period that does not match the product.

Set it up for your agentHow agent connect works
livepolicies/loyalty-privacy-update.md

Loyalty program privacy update

Owner: Ruth Feldman. Company: Juniperline Travel. Share: team only.

Draft update to the Juniperline Travel privacy policy for the new loyalty program. Team review only. Publishing still happens on the policy site Juniperline already uses. This file is not the public page. Ruth owns the sign-off.

What the program stores

  • The program stores a member id, a trip count, and a passport number when the member adds one.
  • The product does not ask for a passport number. That example should not survive review. Jonah flagged the field, and Sofia agreed it goes. A policy should not describe a field the product never collects.
  • A member id and a trip count are the fields the program actually writes. A trip is a booking the member completed, nothing more. Do not add a document number to make the list look complete.

Retention

Loyalty records are kept for 90 days after an account closes.Loyalty records are kept for 30 days after an account closes.

The product keeps loyalty records for 30 days after the account closes. The draft said 90 because an older program did. Use the product, not the older program. When the public page changes, it should say 30 too. Ruth should not sign that page while it still says 90.

Not in this update

  • Payment cards stay where they are. This draft does not describe them, and it should not link to the card policy.
  • The public page is updated by the policy site after this team signs off. This file is the review copy, not that public page. Publishing still happens on the site Juniperline already uses.

passport number

Jonah Weiss

The program does not collect passport numbers. Delete that example.

Sofia Marin

Delete it. We should not describe a field we do not have.

90 days

Sofia Marin

@agent the retention section says 90 days, the product keeps 30, fix it.

agent

Changed loyalty retention from 90 days to 30 days.

resolved
Start with @agent to ask the agent
ResolveReply
Fictional example: a Juniperline Travel loyalty privacy update, team-only in Gander, with a product thread and a scripted agent connect reply.

How policy drafts get reviewed today

A shared doc is a common place for a policy argument, and it works until the agent rewrites the source and the comments stay behind.

Email threads between legal and product fork by paragraph. The published policy site is where the finished text goes, not where the draft should collect half-applied edits.

Thirty days, not ninety

Ruth Feldman asks her agent to update Juniperline Travel's privacy policy for a new loyalty program. She limits the share to the team, runs gander watch on policies/loyalty-privacy-update.md, and sends it to Sofia Marin and Jonah Weiss.

Jonah highlights the loyalty section and says the program does not collect passport numbers. Sofia replies to delete that example. Human thread, on the team.

Sofia starts a new comment: "@agent the retention section says 90 days, the product keeps 30, fix it." Ruth's agent changes the retention line, replies, and resolves the thread. Jonah sees 30 days on the same link. Publishing still happens on the policy site Juniperline already uses.

Who's in the doc

WriterSecurity or privacy counselProductThe author's agent

Writer Counsel or ops. Team link only.

Security or privacy counsel Checks retention, collection, and what the draft overclaims.

Product Checks the draft against what the product actually stores.

The author's agent Fixes the period when counsel uses agent connect.

Reviewers only need a browser. Talk to each other in normal threads. Use agent connect when you want the draft changed.

Agents that fit policies

Grok BotA policy draft from the current text plus a brief, with agent connect through MCP.
Claude CodeWhen the policy markdown lives in a repo, MCP returns agent connect to the author.

Settle the retention line on the team draft. Publish from the policy site when the argument is done.

See how it works on the homepage