Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

gdpr-ecommercegdpr ecommerce 搜索

Agent Skill

gdpr-ecommerce 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

514

周安装

21

GitHub Stars

19

下载量

166
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:gdpr-ecommerce(gdpr ecommerce 搜索)
来源仓库:https://github.com/finsilabs/awesome-ecommerce-skills
仓库路径:skills/gdpr-ecommerce
安装命令:
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill gdpr-ecommerce
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill gdpr-ecommerce

简介

用于查找和筛选与 GDPR 相关的电商合规案例和最佳实践。

  • 适合在电商平台开发中快速定位合规要求。gdpr-ecommerce 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 通过 GitHub 仓库安装,需确认权限范围和操作边界后再使用。
  • 建议结合原始 README 核验具体用法,避免触发不必要的联网或文件读写。
  • 使用前请检查维护状态,确保技能与当前宿主环境兼容。

SKILL.md

GDPR E-commerce

Overview

GDPR (General Data Protection Regulation) requires e-commerce stores serving EU/UK customers to obtain informed consent for data processing, provide data portability (Article 20), support the right to erasure (Article 17), and maintain a lawful basis for every category of personal data processing. Non-compliance carries fines up to €20M or 4% of global annual turnover. All major platforms have GDPR tools built in; the main gaps are cookie consent management and handling Subject Access Requests (SARs).

When to Use This Skill

  • When your store serves customers in the EU, EEA, or UK (UK GDPR)
  • When adding analytics, marketing, or personalization tools that process personal data
  • When a customer submits a Subject Access Request (SAR) or deletion request
  • When reviewing third-party integrations for GDPR compliance
  • When preparing for a data protection audit or DPA (Data Processing Agreement) review

Core Instructions

Step 1: Map your data processing activities

Before configuring any tool, document every category of personal data and its lawful basis. This Register of Processing Activities (RoPA) is required under Article 30 for large processors and recommended for all:

Data CategoryLawful BasisRetention Period
Order data (name, address, items)Contract (Art. 6(1)(b))7 years (tax law)
Account data (email, password hash)ContractUntil account deletion + 30 days
Analytics (page views, session duration)Legitimate interest / Consent13 months
Marketing emailsConsent (Art. 6(1)(a))Until unsubscribe
Fraud prevention (IP, device fingerprint)Legitimate interest90 days

Step 2: Implement cookie consent


Shopify

Shopify includes a built-in cookie consent banner via the Privacy & Compliance app (free):

  1. Go to Apps → Shopify Privacy & Compliance (or search in the App Store)
  2. Configure the banner text, position, and which cookie categories to ask about
  3. The app integrates with Shopify's Consent API so that analytics and marketing pixels respect customer choices
  4. Alternatively, install a dedicated CMP (Consent Management Platform) like CookieYes or Cookiebot — both have Shopify app integrations

Enabling consent-aware analytics:

  • For Google Analytics / GA4: use Shopify's Customer Events (Settings → Customer events) which respects consent automatically
  • For custom Pixel tracking: use the Shopify Customer Privacy API to check consent before loading tracking code

WooCommerce

WooCommerce includes basic GDPR features since version 3.4, but cookie consent requires a dedicated plugin.

Install GDPR Cookie Consent (by WebToffee) — free/premium:

  1. Install from the WordPress plugin directory
  2. Go to Cookie Law Info → Settings:

- Configure the banner text, colors, and button labels - Set up cookie categories: Necessary (always on), Analytics, Marketing - Map your installed plugins/scripts to categories (Google Analytics → Analytics, Facebook Pixel → Marketing)

  1. The plugin blocks third-party scripts until consent is given

WordPress native GDPR tools:

  • Go to Settings → Privacy to configure your privacy policy page
  • Go to Settings → Privacy → Data Erasure Requests — customers can submit erasure requests from My Account; WordPress generates a confirmation email and you process it manually

BigCommerce

Install CookieYes or Cookiebot from the BigCommerce App Marketplace. Both provide:

  • A GDPR-compliant consent banner
  • Script blocking until consent is given
  • Consent logging for audit purposes

BigCommerce also supports custom cookie consent via the Script Manager (Storefront → Script Manager) — you can add a Cookiebot or CookieYes script globally.

Step 3: Handle Subject Access Requests (SARs)

Under GDPR Article 20, customers have the right to receive all their personal data in a machine-readable format within 30 days.


Shopify

  1. When a customer requests their data, go to their Customer profile in Shopify admin
  2. Click Request data — Shopify generates a data export file containing:

- Customer profile data - Order history - Addresses

  1. Shopify emails the download link directly to the customer

Customer privacy settings:

  1. Go to Settings → Customer privacy
  2. Configure data request webhooks — Shopify sends customers/data_request webhooks to all installed apps when a customer requests their data, so apps can also provide their data

WooCommerce

WordPress includes a built-in personal data export tool:

  1. Go to Tools → Export Personal Data
  2. Enter the customer's email address and click Send Request
  3. The customer receives a confirmation email; once they confirm, you see the request in the admin
  4. Click Generate export file — WordPress collects data from WooCommerce and all plugins with data exporters
  5. The customer receives a zip file with their data in a machine-readable format

BigCommerce

BigCommerce does not have a built-in SAR tool. To handle data requests:

  1. Use the BigCommerce Customers API and Orders API to extract all data for a customer
  2. Package the data as a JSON or CSV export
  3. Deliver to the customer within 30 days of the request

Consider building or using a third-party service like Transcend or Mine to automate data request handling.

Step 4: Handle Right to Erasure (Article 17)

The right to erasure must balance deletion with legal retention obligations (tax records must be kept 5–7 years).


Shopify

  1. Open the customer's profile in Shopify admin
  2. Click More actions → Erase personal data
  3. Shopify anonymizes the customer's PII (replaces name, email, phone with anonymized placeholders) while keeping the order records for accounting
  4. Shopify sends customers/redact webhooks to all installed apps

WooCommerce

  1. Go to Tools → Erase Personal Data
  2. Enter the customer's email and send them a verification request
  3. Once they confirm, WordPress and WooCommerce anonymize:

- Customer account (email replaced with anonymized placeholder) - Orders (customer name, billing/shipping details replaced with "Deleted User" / anonymized)

  1. Order financial records are preserved

BigCommerce

Use the Customers API to update the customer record, replacing PII with anonymized placeholders, and delete the customer account. The order records remain (financial data preserved) with the customer references removed.

Step 5: Ensure lawful marketing consent

Only send marketing emails to customers who have explicitly opted in. Pre-ticked boxes are prohibited under GDPR.

On all platforms:

  1. Add a clearly labeled, unchecked checkbox to the registration form and checkout: "Yes, I'd like to receive marketing emails"
  2. Record the consent timestamp, IP address, and form version in your database (or in your email platform)
  3. Include a one-click unsubscribe link in every marketing email
  4. Process unsubscribes immediately — within 10 business days is the standard requirement

Email platforms:

  • Klaviyo: tracks consent separately; use Klaviyo's built-in opt-in forms and consent properties
  • Mailchimp: uses double opt-in by default (recommended for GDPR); configure under audience settings
  • Omnisend: has GDPR mode with consent recording built in

Step 6: Sign Data Processing Agreements (DPAs)

Every third-party tool that processes customer data on your behalf must have a DPA in place:

  1. Stripe: DPA available at stripe.com/legal/dpa
  2. Klaviyo: DPA available in Klaviyo account settings under Account → Privacy
  3. Google Analytics: accept Google's DPA in the GA4 admin
  4. Shopify: Shopify is a data processor for your customer data; their DPA is in their legal agreements
  5. For each vendor, find the DPA in their privacy/legal documentation and complete it

Best Practices

  • Default all consent to denied — under GDPR, consent must be freely given and unambiguous; pre-ticked boxes are explicitly prohibited
  • Keep a consent audit trail — log every consent grant, withdrawal, and change with timestamp and the exact consent text version shown to the user
  • Respond to SARs within 30 days — automate data exports so they're available quickly via a self-service portal; manual exports are slow and error-prone at scale
  • Sign DPAs with all vendors before using their service — Stripe, Klaviyo, Google Analytics — any tool processing customer data must have a DPA
  • Separate consent from account creation — do not bundle marketing consent with T&Cs acceptance; each processing purpose needs a separate, granular consent
  • Test your deletion pipeline regularly — run erasure requests on test accounts quarterly to verify all data is deleted from the database, search indexes, analytics tools, and third-party processors

Common Pitfalls

ProblemSolution
Cookie banner pre-ticking analytics boxesGDPR requires opt-in consent; pre-ticked boxes are explicitly prohibited under Recital 32
Deleting orders when customer requests erasureOrders must be retained for the statutory tax period (5–7 years); anonymize PII within orders rather than deleting the order record
Forgetting to delete from email platform and analyticsShopify's customers/redact webhook notifies apps; ensure your Klaviyo, Mailchimp, and analytics tools also receive the deletion request
Marketing emails sent without consent documentationStore the IP address, timestamp, consent text version, and method (checkbox, sign-up form) for every marketing opt-in
Missing DPA with a key vendorAudit your vendor list annually; Google, Stripe, Klaviyo, and your hosting provider all need DPAs if they process EU customer data

Related Skills

  • @data-retention-policies
  • @account-security
  • @analytics-integration
  • @fraud-detection

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.92%
按下载量换算56

Claude

33.06%
按下载量换算55

Cursor

16.93%
按下载量换算28

Gemini CLI

9.6%
按下载量换算16

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills