Skip to content

AgriciDaniel/claude-ads / ads

Operate professional paid advertising across Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, Apple, Amazon, Reddit, Pinterest, Snapchat, and X. Use for account intake, source-grounded audits, strategy, budget and measurement planning, creative production, experiments, reporting, monitoring, and explicitly approved campaign changes. Also trigger on PPC, paid social, retail media, attribution, tracking, landing pages, cross-platform conversion totals, negative keywords or search terms, beta-feature scoring, stale platform claims, API-token or credential setup, campaign deletion, and safe Claude Ads installation or uninstall.

FileKindSize
SKILL.mdskill md19.4 KB
agents/openai.yamlconfig205 B
references/additional-platforms.mdmarkdown3.1 KB
references/amazon-audit.mdmarkdown3.8 KB
references/apple-audit.mdmarkdown4.4 KB
references/automation-tier-classifier.mdmarkdown3.4 KB
references/benchmarks.mdmarkdown4.4 KB
references/bidding-strategies.mdmarkdown4.9 KB
references/budget-allocation.mdmarkdown4.2 KB
references/compliance-requirements.mdmarkdown6.2 KB
references/compliance.mdmarkdown5.0 KB
references/conversion-tracking.mdmarkdown6.9 KB
references/copy-frameworks.mdmarkdown4.1 KB
references/creative-source-registry.mdmarkdown2.0 KB
references/gaql-notes.mdmarkdown7.5 KB
references/google-audit.mdmarkdown26.1 KB
references/google-creative-specs.mdmarkdown2.2 KB
references/image-providers.mdmarkdown5.0 KB
references/linkedin-audit.mdmarkdown11.8 KB
references/linkedin-creative-specs.mdmarkdown1.8 KB
references/mcp-integration.mdmarkdown6.5 KB
references/meta-ai-stack.mdmarkdown4.9 KB
references/meta-audit.mdmarkdown17.8 KB
references/meta-creative-specs.mdmarkdown1.9 KB
references/microsoft-audit.mdmarkdown10.4 KB
references/microsoft-creative-specs.mdmarkdown1.8 KB
references/pinterest-audit.mdmarkdown4.2 KB
references/platform-specs.mdmarkdown5.2 KB
references/prompt-patterns.mdmarkdown3.4 KB
references/reddit-audit.mdmarkdown4.7 KB
references/scoring-system.mdmarkdown5.8 KB
references/snapchat-audit.mdmarkdown4.1 KB
references/status-contract.mdmarkdown773 B
references/thinking-framework.mdmarkdown13.7 KB
references/tiktok-audit.mdmarkdown11.4 KB
references/tiktok-creative-specs.mdmarkdown2.0 KB
references/voice-to-style.mdmarkdown4.0 KB
references/x-audit.mdmarkdown3.3 KB
references/youtube-audit.mdmarkdown4.5 KB
references/youtube-creative-specs.mdmarkdown2.0 KB

references/compliance-requirements.md

View on GitHub
# Regulatory Compliance Requirements

**Verified:** 2026-10-12 for the EU AI Act row; other rows follow their ledger entries (2026-10-07)
**Refresh:** event-driven; re-check within 30 days of an applicable effective date, including the AI Act marking transition date (2026-12-02); ledger entries next due 2026-11-06
**Scope:** issue spotting and evidence collection, not legal advice

Do not apply a global checklist before establishing jurisdiction, role, data
flow, audience, product, and creative provenance. Laws and regulator guidance
change; a stale state-count table is not a compliance system.

## Intake

Capture:

- Advertiser, controller/business, processor/service-provider, agency, platform,
  and AI provider/deployer roles.
- Audience and operational geographies, including excluded locations.
- Product category, claims, endorsements, political content, and age exposure.
- Data collected, inferred, uploaded, disclosed, sold/shared, retained, and deleted.
- Consent, opt-out, preference-signal, access/deletion, and vendor-contract flows.
- AI-generated or manipulated text, image, audio, and video provenance.
- Applicable counsel decisions, regulator correspondence, and platform approvals.

Missing jurisdiction or data-flow evidence produces `needs_input`, not a pass.

## Current primary sources

| Area | Source | Retained fact |
| --- | --- | --- |
| EU AI Act | `eu-ai-act-article-50-official`: [European Commission transparency code](https://digital-strategy.ec.europa.eu/en/policies/code-practice-ai-generated-content), `eu-ai-act-article-50-faq-official`: [Commission Article 50 FAQ](https://digital-strategy.ec.europa.eu/en/faqs/transparency-obligations-under-article-50-ai-act), and [Regulation (EU) 2024/1689](https://eur-lex.europa.eu/eli/reg/2024/1689/oj) | Article 50 transparency obligations apply from 2 August 2026; scope differs for providers and deployers; a limited grace period to 2 December 2026 covers only the Article 50(2) marking and detection obligation for systems placed on the market before 2 August 2026 |
| Digital Services Act | `eu-dsa-official`: [European Commission DSA overview](https://digital-strategy.ec.europa.eu/en/policies/digital-services-act) | Ads must be identifiable and include information about who placed them and why they are shown; platform duties differ by service type |
| California privacy | `cppa-regulations-official`: [CPPA laws and regulations](https://cppa.ca.gov/regulations/) | Adopted and proposed packages are distinct; consult the effective text rather than commentary |
| Health information | `hhs-tracking-guidance-official`: [HHS tracking guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/hipaa-online-tracking/index.html) | HIPAA-regulated entities must assess tracking technologies when collected or disclosed information includes PHI; the page records a court-vacated portion of earlier guidance |
| US endorsements | `ftc-endorsement-guides-official`: [FTC Endorsement Guides FAQ](https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking) | Material connections and non-typical result claims require context-appropriate, clear disclosure/substantiation analysis |

The cited Article 50 transparency date is in effect as of the verification date. Do not convert it
into a claim that every AI-assisted advertisement requires the same label. Check
the actor, output type, use, exceptions, final Commission guidance, and platform
implementation. Regulation (EU) 2026/1744 (Digital Omnibus on AI, of 8 July 2026,
Official Journal 24 July 2026, verified on EUR-Lex on 2026-10-12) requires
providers of generative systems placed on the market before 2 August 2026 to
comply with Article 50(2) marking by 2 December 2026. The Commission FAQ
(updated 24 July 2026) describes the same limited grace period (`CLM-0106`).
It does not cover other Article 50 duties or systems placed on the market from
2 August 2026. Any further transition proposal remains a proposal until adopted.

## Data and privacy review

Map each event and audience field from collection to destination. For each step,
record purpose, legal basis or permission relied upon, consent state, sensitive
status, recipient, retention, deletion, security, and user-control mechanism.

Verify the actual applicable law and effective regulation for each jurisdiction.
Do not use a remembered count of US state privacy laws or a generic “GDPR/CCPA
compliant” label as evidence. Test preference signals and opt-outs end to end,
including downstream suppression and proof visible to the operator.

## Sensitive and regulated contexts

Escalate to counsel or the accountable compliance owner when the flow can include
health, financial, precise location, biometric, neural, child/teen, political,
employment, housing, credit, immigration, or other legally sensitive data.

For HIPAA-regulated entities and business associates, inspect HHS's current
tracking guidance and the court-order note on that page. Do not claim that every
visit to a public health-information page is PHI, and do not assume a privacy
notice alone authorizes disclosure.

## Claims, endorsements, and AI media

- Keep substantiation for express and implied objective claims.
- Disclose material connections in a way ordinary viewers can notice and understand.
- Compare testimonial results with generally expected results; a vague disclaimer
  does not repair an otherwise misleading impression.
- Preserve AI provenance and platform labels; assess Article 50 and local rules
  against the exact output and role.
- Review political and public-interest content under current election, platform,
  and jurisdiction rules before launch.

## Finding and escalation contract

Each finding states jurisdiction, actor, data/creative flow, current primary
source, observed evidence, applicability rationale, result, confidence, exposure,
owner, remediation, and re-check date. Keep legal exposure separate from account
health scoring.

Block a mutation when required consent/authorization, counsel decision,
certification, disclosure, data minimization, or jurisdiction evidence is absent.
Use `unknown` for unresolved applicability. Claude Ads may identify and document
the issue; the accountable owner or qualified counsel makes the legal decision.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall