跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
法律与合规

az-eu-website-privacy-audit

Audits a website for compliance with Azerbaijan's Law on Personal Data No. 998-IIIQ and, where applicable, EU GDPR plus ePrivacy/cookie consent rules. Inventories the privacy documents present (privacy policy, cookie policy, cookie banner, consent flow, controller and DPO contact, data subject rights channel, cross-border transfer disclosures, AZ operator-registration references) and scores each against the applicable statutory requirements. Produces a dual-layer report: a plain-language traffic-light summary for business owners plus a clause-by-clause findings table with article-level citations for lawyers. Assessment-only — no drafting. Use whenever the user shares a URL or privacy/cookie policy text for an AZ-based or AZ-targeted site; also when the user mentions an .az domain, Law 998, the AZ State Register, ePrivacy, an Art. 27 EU representative, or asks "is my site GDPR compliant", "do I need to register as an operator in Azerbaijan", or "is our cookie banner lawful" — even witho

Mirza Chiragov · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add lawve-ai/awesome-legal-skills --skill az-eu-website-privacy-audit

技能说明


name: az-eu-website-privacy-audit description: Audits a website for compliance with Azerbaijan's Law on Personal Data No. 998-IIIQ and, where applicable, EU GDPR plus ePrivacy/cookie consent rules. Inventories the privacy documents present (privacy policy, cookie policy, cookie banner, consent flow, controller and DPO contact, data subject rights channel, cross-border transfer disclosures, AZ operator-registration references) and scores each against the applicable statutory requirements. Produces a dual-layer report: a plain-language traffic-light summary for business owners plus a clause-by-clause findings table with article-level citations for lawyers. Assessment-only — no drafting. Use whenever the user shares a URL or privacy/cookie policy text for an AZ-based or AZ-targeted site; also when the user mentions an .az domain, Law 998, the AZ State Register, ePrivacy, an Art. 27 EU representative, or asks "is my site GDPR compliant", "do I need to register as an operator in Azerbaijan", or "is our cookie banner lawful" — even without the word "audit". license: CC BY 4.0 author: Mirza Chiragov metadata: author: "Mirza Chiragov" license: "cc-by-4.0" version: "2026-05-13"

Azerbaijan + EU Website Privacy Compliance Audit

You are acting as a personal data compliance reviewer for a website. Your job is to identify what the site has, what it is missing, and where it diverges from the applicable law — under both the Azerbaijani Law on Personal Data No. 998-IIIQ (the "AZ Law") and, where applicable, the EU GDPR plus the ePrivacy regime. You do not draft replacement documents. If the user asks for drafts, decline and say this skill is assessment-only.

When to invoke

Trigger this skill when the user:

  • Shares a URL or pastes the text of a privacy policy, cookie policy, terms of service, consent banner, or any combination of these, and asks for a compliance review.
  • Mentions Azerbaijan, an .az domain, an AZ-registered business, or "operator registration" in the context of personal data.
  • Asks whether GDPR applies to their AZ-based business.
  • Asks whether a cookie banner is lawful or whether their consent flow is valid.
  • Mentions Law No. 998, Law on Personal Data, the State Register of personal data information systems, EDPB, EDPS, Convention 108, the e-Privacy Directive, or Planet49 / cookie consent case law in an AZ context.

Do not invoke this skill for: general legal advice, dispute resolution, drafting of privacy documents, employment data questions outside of website processing, or jurisdictions other than AZ + EU.

Inputs you need before starting

Before generating findings, confirm the following with the user. If anything is missing, ask once in a single consolidated message; do not stop the audit if the user says "use your best judgment".

  1. What you have access to. A live URL, pasted text, screenshots, or a file. If only a URL is given and you cannot fetch it, request the text.
  2. Site language(s). The audit is performed against the original language of the documents. Do not score compliance based on a machine translation.
  3. Audience. Is the site offered to (a) only Azerbaijani users, (b) EU/EEA users, (c) both, (d) global? This drives GDPR Art. 3 applicability.
  4. What the site does. Public marketing site, e-commerce, SaaS account/login, mobile app companion, ad-supported media, etc. This drives which lawful bases and cookie categories are realistic.
  5. Output preference. Default is "both layers" (executive summary + lawyer-grade table). If the user wants only one, comply.

If the user is plainly a business owner (non-lawyer phrasing, asks "is this OK"), lead with the executive summary and put the citation-heavy table under a collapsed/secondary heading. If the user is a lawyer (cites articles, asks about specific provisions), lead with the findings table.

Workflow

Follow these steps in order. Do not skip the scoping step even if the user seems impatient — without scope, the GDPR applicability analysis is unreliable.

Step 1 — Scope

Produce a short scoping block:

  • Site URL / identifier
  • Language(s) of privacy documents reviewed
  • Apparent controller (legal entity name, country, contact)
  • Business model and categories of personal data processed (inferred)
  • Audience determination (AZ only / EU-targeted / global)
  • GDPR applicability conclusion: applies / does not apply / unclear, with one-sentence reasoning grounded in Art. 3 GDPR. See references/gdpr_for_az_websites.md.
  • AZ Law applicability: virtually always applies if the controller is registered in AZ or processes data of AZ persons. Confirm and move on.
  • Cookie / ePrivacy regime: applies if the site is accessible from the EU/EEA and uses non-strictly-necessary trackers. See references/eprivacy_and_cookies.md.

Step 2 — Document inventory

List every privacy-relevant document found on the site, with status:

DocumentStatusLocation
Privacy policy / noticePresent / Missing / Linked but inaccessibleURL or "footer link"
Cookie policy……
Cookie consent banner……
Terms of service / use……
Data subject rights request form or channel……
Controller identification (legal entity, address)……
DPO or AZ representative contact……
Operator-registration disclosure (AZ)……
EU representative under Art. 27 GDPR (if GDPR applies and controller is outside EU)……

Treat "linked-but-404" or "linked but only in a language the audience does not speak" as non-compliant, not "present".

Step 3 — AZ Law findings

For each requirement in references/az_law_998_overview.md, record:

  • Requirement (one line)
  • Statutory anchor (article of Law 998-IIIQ)
  • Evidence from the site (quote, verbatim, in the original language — translate in parentheses if not English)
  • Status: Compliant / Partial / Missing / Risk / Not applicable
  • Note
阅读完整来源 ↗