Skip to content

Use cases

Legal

Map the personal data a feature stores, check customer paper against your playbook and catch new subprocessors.

Merlin recipes for legal teams. Map what personal data a feature stores from its code, check a customer's paper against your playbook and catch new subprocessors in merged code before your public list falls behind.

Privacy reviews and contract work depend on facts that live with other teams: what the code stores, which services it sends data to and which positions the company has agreed to. The recipes below ask for those facts from the legal channel or a Linear issue. Merlin reads the code and your playbook, then replies there with references a lawyer can check. Counsel makes every decision.

What you need

RequirementWhy it matters here
An eligible runtime with the repositoryData maps and subprocessor checks are read from the actual code.
Merlin in the legal channelsRequests and results stay in channels whose members may see them.
A playbook skillContract review compares each clause with your preferred, fallback and walk-away positions.
GitHub App installedThe weekly subprocessor check links each finding to its pull request.

A private channel needs /invite @Merlin. It reads public memory plus its own private store, so positions saved there stay in that channel.

Prompts to paste

Map what personal data a feature stores

Ask in the legal channel or mention Merlin on the feature's Linear issue.

@Merlin map the personal data the referrals feature stores: fields, tables, logs, retention and third-party services, with file references. Pin it to the current commit and list what the code can't show, such as backups and manual exports.

Pinning to a commit makes the map auditable, and the list of blind spots tells you what to ask engineering. See it step by step.

Check customer paper against your playbook

Attach the customer's draft to a message in the private deal channel.

@Merlin compare this agreement with the contract-playbook skill. List each clause that differs from our preferred position, propose only playbook language and send back a tracked-changes copy marked draft for counsel.

Merlin proposes language from your playbook only, and counsel decides what goes back to the customer. See it step by step.

Catch new subprocessors before customers do

Schedule the check to the private legal channel.

@Merlin every Monday at 9am, check last week's merged code for new third-party SDKs, API hosts and environment variables that receive customer data. Compare them with our public subprocessor page and post what's new, unlisted or removed, with pull request links.

Engineers rarely tell legal when they add a service. A weekly check keeps the advance notice your agreements promise. See it step by step.

Limits

Merlin's output is a draft for counsel, never legal advice. It does not send, sign or accept anything.

A data map covers what the code shows. Data handled by people, vendors' own systems or backups outside the repository has to be confirmed separately.