skills / legal & compliance

compliance-check

what it does

Run a compliance check on a proposed action, product feature, or business initiative, surfacing applicable regulations, required approvals, and risk areas. Use when launching a feature that touches personal data, when marketing or product proposes something with regulatory implications, or when you need to know which approvals and jurisdictional requirements apply before proceeding.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“We scanned about 40,000 badges at a trade show in Amsterdam. Marketing wants to add everyone to our monthly newsletter next week. Lots of them are from Germany and France. Any compliance issues?”

Source material given with the request

Company: Tidewell Software, based in Austin, Texas, with an EU office in Dublin. The badge scans give name, company, job title and work email. The organizer's attendee terms say exhibitors may contact attendees "about the products shown at the booth". Nothing in them mentions newsletters. Plan: import all 40,000 into the newsletter list, no confirmation email, unsubscribe link in footer.
with the skill
## Compliance Check: Trade-show contacts → newsletter ### Summary **Do not proceed with the blanket import and newsletter send as proposed.** An unsubscribe link does not cure missing permission to send marketing emails. The organizer’s wording—contact “about the products shown at the booth”—does **not, on its own, establish valid consent to Tidewell’s recurring newsletter**. Scanning a badge also does not automatically establish consent. Any specific permission given at the booth needs to be evaluated separately. EU privacy and national electronic-marketing rules both matter. **A GDPR legitimate-interest assessment alone cannot override a national requirement for prior email-marketing consent.** ### Applicable Regulations and Policies | Regulation / policy | Relevance | Key requirements | |---|---|---| | **GDPR** | The Dublin office’s involvement and the context of the processing determine territorial applicability; US headquarters does not avoid EU obligations. Names and named work emails are personal data. | Lawful basis, transparency, purpose limitation, data minimization, and an unconditional right to object to direct marketing. | | **National electronic-marketing laws implementing the ePrivacy Directive** | Newsletter permission depends on the applicable national rules—not simply where the trade show occurred. | Assess recipient jurisdictions and any narrowly available exceptions before sending. | | **Germany: UWG §7** | Germany generally requires prior express consent for advertising emails, **including B2B**. | A badge scan is not enough by itself. The existing-customer exception is narrow and generally requires an actual sale plus other conditions; a booth interaction does not ordinarily qualify. | | **France: electronic-marketing rules and CNIL guidance** | Professional B2B prospecting may be permitted without opt-in where the solicitation relates to the recipient’s professional role. | Proper notice and an easy, free objection mechanism are still
Show the rest (43 more lines)
necessary. This is not blanket permission to send a general newsletter to every French attendee. | | **Netherlands / Ireland and other relevant national rules** | Dutch event location, Irish operations, and other recipient locations may affect the analysis. | Legal should determine applicable rules and exceptions; do not assume one EU-wide B2B standard. | ### Requirements | # | Requirement | Status | Action needed | |---|---|---|---| | 1 | Evidence of newsletter permission or a valid national exception | **Not established** | Review booth scripts, scan-screen notices, checkboxes, and recorded choices. | | 2 | Permission consistent with the stated collection purpose | **Not established** | Do not stretch “products shown at the booth” into automatic recurring-newsletter enrollment. | | 3 | GDPR lawful basis and transparency | **Unknown** | Document the basis and review what attendees were told about Tidewell’s processing. | | 4 | Country- and purpose-specific segmentation | **Not met in proposed plan** | Separate eligible contacts from those without sufficient permission. | | 5 | Effective opt-out and suppression controls | **Partially planned** | Make unsubscribing easy, honor objections, and screen against existing suppression lists. | **Privacy-notice timing:** If Tidewell obtained the data indirectly from the organizer, GDPR Article 14 generally requires information within one month, or at the first communication if earlier, unless an exception applies. If collected directly from attendees, Article 13 generally requires notice at collection. **A notice obligation does not itself authorize a marketing email.** ### Risk Areas | Risk | Severity | Mitigation | |---|---|---| | Unsolicited marketing, particularly to German contacts | **High** | Exclude contacts without provable consent or a verified exception. | | Repurposing a limited booth contact into an ongoing subscription | **High** | Assess the precise notice and permission; keep any permitted follow-up within scope. | | Complaints, enforcement, German competitor claims, and email-platform restrictions | **High** | Pause the bulk upload/send pending review. | | EU data being processed in US systems | **Conditional** | Review vendor agreements, security, and any required international-transfer safeguards. | ### Recommended Actions 1. **Pause next week’s bulk enrollment.** Keep the records out of active newsletter audiences while reviewing permission. 2. **Audit the actual collection process.** Obtain the organizer’s complete terms, privacy notices, exhibitor agreement, and evidence of any booth-level consent. 3. **Create an eligible-only list.** German recipients generally need documented opt-in; French professional contacts require a separate role-relevance and notice assessment. 4. **Do not email all 40,000 asking them to consent.** A “permission request” email can itself be regulated advertising. Nor does a confirmation email retroactively fix an unauthorized collection or send. For future signups, use a clear, separate newsletter choice and retain evidence; double opt-in is a useful evidentiary safeguard. 5. **Document retention and processing arrangements.** Retain only what is justified, apply suppression controls, and review the newsletter provider and US access. ### Approvals Needed | Approver | Why | Status | |---|---|---| | EU privacy/legal lead, with DPO input if appointed | Lawful basis, notices, purpose, and transfers | Pending | | Counsel familiar with relevant national marketing laws | German, French, and other country-specific sending rules | Pending | | Marketing operations | Consent evidence, segmentation, and suppression testing | Pending | **Bottom line:** A narrowly scoped booth follow-up and a recurring newsletter are not interchangeable. On the facts provided, **there is no adequate basis to enroll all 40,000 people**. *This is compliance guidance, not legal advice. Qualified counsel should verify current national requirements before launch; current authoritative sources have not been checked here.*
without
**Yes—pause the bulk import and newsletter send.** On these facts, Tidewell should not treat the 40,000 badge scans as newsletter subscribers. An unsubscribe link alone does not fix the lack of permission where prior consent is required. Two separate legal layers matter: **GDPR governs use of the contact data; national electronic-marketing laws govern whether you may email them.** A GDPR “legitimate interests” argument does not override an email-consent requirement. ### Main issues | Issue | What it means for this plan | |---|---| | **Badge scan ≠ newsletter consent** | Scanning a badge may support an expected, relevant booth follow-up, depending on what attendees were told. It does not automatically authorize an ongoing newsletter. The organizer’s wording—contact “about the products shown at the booth”—is not clear, specific consent to a monthly subscription. | | **Germany: generally prior express consent, including B2B** | German rules generally require prior express consent for marketing emails to work addresses too. The narrow existing-customer exception typically requires an actual sale, marketing of your own similar offerings, and specified opt-out notices. **A trade-show lead alone is not an existing customer.** | | **France: a qualified B2B exception** | French rules can permit professional prospecting without prior opt-in when it relates to the recipient’s professional role, the person is properly informed, and they have a simple, free way to object. This is **not blanket permission for every attendee or a general newsletter**. You need to assess recipients, content, and the information provided at collection. | | **Other countries** | EU electronic-marketing rules vary by country. One EU-wide “B2B email is allowed” rule will not work. The show’s Amsterdam location does not make Dutch rules the only relevant ones. | ### GDPR issues to address too - **Lawful basis and purpose:** Document a lawful basis for each use. Legitimate interests may support
Show the rest (14 more lines)
some targeted B2B outreach, but it requires a necessity and balancing assessment—not just a label. A recurring newsletter may exceed attendees’ reasonable expectations. - **Transparency:** Check the actual booth signage, scan screens, organizer notices, and any recorded choices. If Tidewell obtained data indirectly, GDPR Article 14 generally requires its privacy information within one month, or by the first communication if earlier, unless an exception applies. Direct collection has its own notice requirements. - **Objections:** People have an absolute right to object to processing for direct marketing. Stop marketing after an objection and retain an appropriate suppression record. - **US access/transfers:** If EU data goes to Austin or a US mailing provider, assess the applicable international-transfer mechanism, such as eligible EU–US Data Privacy Framework coverage or appropriate contractual safeguards. The Dublin office does not automatically resolve this. ### What to do before next week 1. **Keep the scans out of the active newsletter audience.** Store them separately with restricted access while reviewing. 2. **Audit the evidence:** what each attendee saw, what they agreed to, when, and whether a booth conversation created a specific follow-up request. 3. **Segment by applicable country rules, permission evidence, and professional relevance.** Do not infer someone’s country solely from an email domain. 4. **Send only outreach that your review supports.** A requested product response is different from enrollment in recurring marketing—but unsolicited “product follow-up” can itself be regulated advertising. 5. **Build a documented opt-in process going forward.** Double opt-in is useful evidence, especially for Germany. **Do not send all 40,000 a “please confirm your subscription” email**: an unsolicited consent-request email can itself be marketing. **Bottom line:** Cancel the blanket newsletter enrollment. Have EU privacy/marketing counsel review a segmented approach—particularly Germany and France—before any campaign. Compliance with US CAN-SPAM alone would not make this plan lawful.

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 3 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 3 Nov 2026

The tasks

written by Carte Blanche
deletion-request-during-dispute

“A customer in California emailed asking us to delete all their data. They're also in a billing dispute with us that might go to small claims. What do we do?”

face-login-illinois

“We're adding face recognition login to our personal budgeting app. Users are all over the US, including a lot in Illinois. We'd store the face templates on our servers indefinitely. What do we need to check?”

kids-chat-feature

“Our reading app for kids aged 8 to 12 is adding chat between students in the same class. Product also wants to share chat transcripts with an ad partner to improve targeting. Can we launch next month?”

trade-show-badge-list

“We scanned about 40,000 badges at a trade show in Amsterdam. Marketing wants to add everyone to our monthly newsletter next week. Lots of them are from Germany and France. Any compliance issues?”

vendor-dpa-review

“Our new analytics vendor sent their data processing addendum. We're the controller and send them EU customer data. Can you check it before procurement signs?”

Install

Download the .zip and unzip it. Put its files, in a folder named compliance-check, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.