Can it certify our banner is compliant?

No. It supports factual tracking analysis, consent architecture and issue spotting. Applicability, exemptions and jurisdiction-specific legal conclusions require qualified privacy/legal review.

What evidence is useful?

Provide authorized HAR traces, cookie/storage exports, tag-manager and CMP exports, source code or SDK lists, vendor inventories and test observations with timestamps and versions.

Does withdrawal testing cover every data use?

No. Browser observations need to be supplemented for backend, server-side, conditional and regional behavior. It proposes tests and records missing evidence instead of claiming comprehensive coverage.

Cookie Compliance Planner — Map Consent & Tracking

Example session with this skill installed

Illustrative scenario: Plan consent QA from these supplied observations for our website. Tracker A is an analytics tag observed firing before any choice and using local storage; purpose is audience measurement, but fields, recipient and duration are unknown. Tracker B is a session cookie supplied by engineering as maintaining login, with no measured trace provided. The preference panel has accept and reject options; withdrawal behavior is untested. We have users in Sweden and other countries but no confirmed regional configuration. Make an inventory, implementation plan and test cases. Do not browse, certify compliance or change production.

Read your context and instructions
Compiled the cookie compliance planner

Tracking and consent planning brief

Evidence consists of supplied observations and an engineering description. No independent scan, legal applicability determination or production test was performed. Regional requirements and legal classifications require qualified review.

Technology	Evidence	Purpose	Activation / storage	Missing information
A: analytics tag	User-supplied observation	Audience measurement, supplied	Fires before choice; local storage observed	Data fields, recipient, duration, consent dependency and backend uses
B: login session cookie	Engineering-supplied description	Maintain login, described	Actual trigger and expiry not measured	Trace, cookie attributes, recipient, lifecycle and necessity assessment

Issues and proposed implementation

A: pre-choice firing is a factual discrepancy to investigate, not proof of a specific legal violation. Inventory the tag and downstream requests; obtain vendor configuration and data-flow evidence; map its execution to reviewed consent logic. B: validate the login purpose and lifecycle before categorizing it. Do not treat every cookie from this vendor as necessary.

Document accepted, rejected, withdrawn and unknown consent states. Define category-level gates after legal/privacy review. Preserve the current CMP and tag versions, record proposed changes and prepare rollback. Synchronize notices and preferences with verified data, recipients and retention; do not invent notice text for unknown practices.

QA plan — proposed, not run

T1 Fresh visitor: clear test-state only in an authorized test environment; record pre-choice network/storage activity and consent defaults. T2 Reject: verify reviewed category gates, downstream requests and stored identifiers. T3 Accept: verify intended activation and consent evidence. T4 Withdraw: verify future execution stops where required and document existing identifier handling. T5 Return visit: verify stored preferences and version changes. T6 Regional/audience variants: test documented configurations, including authenticated and delayed behavior.

For each test retain timestamp, property/environment, CMP/tag versions, region setup, consent state, observed requests/storage and deviations. Server-side uses need separate evidence.

Owners and open decisions

Engineering validates triggers and storage; marketing supplies tag/vendor purposes; privacy/legal reviews applicability, categories and disclosures; product approves preference behavior. These are proposed responsibilities, not confirmed assigned owners. Exact data, recipients, retention, mobile scope, regional rules and withdrawal behavior remain unresolved. No live settings or notices were changed.

Connects securely to your tools. The creator never sees your data.

About this skill

Cookie Compliance Planner supports privacy, engineering, product and marketing teams in organizing verified website and app tracking behavior into an auditable implementation plan. It covers cookies, pixels, tags, SDKs, local storage, identifiers, session replay and server-side tracking where evidence exists.

The workflow records purpose, data, recipients, duration, triggers and consent states; separates observed behavior from legal classification; identifies regional review questions; and plans preference logic, notices, QA, evidence and change governance. Supplied HAR files, cookie exports, tag-manager or CMP exports, source code, SDK inventories and screenshots can support the analysis when the host can read them.

Outputs can include tracker inventories, discrepancies, pre-consent and post-withdrawal test plans, implementation tasks and review gaps. It does not classify a tracker as necessary from its name alone or certify legal compliance. Actual production changes and public notices require explicit authorization and review; a browser scan cannot reveal every backend use.

How to use

Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

Reviews

No reviews yet

Be one of the first to try it. Every listed skill passes our trust checks below.

Security scanned

Passed our 8-point scan before listing

Fresh listing

Recently published to Agensi

Money-back guarantee

Doesn't do what its page promises? You get your money back.

Cookie Compliance Planner — Map Consent & Tracking