vercel-data-handling

Implement Vercel PII handling, data retention, and GDPR/CCPA compliance patterns.Use when handling sensitive data, implementing data redaction, configuring retention policies,or ensuring compliance with privacy regulations for Vercel integrations.Trigger with phrases like "vercel data", "vercel PII","vercel GDPR", "vercel data retention", "vercel privacy", "vercel CCPA".

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026

When & Why to Use This Skill

The Vercel Data Handling skill is a specialized toolkit designed to automate PII (Personally Identifiable Information) detection, data redaction, and regulatory compliance within Vercel environments. It provides developers with standardized patterns for GDPR and CCPA compliance, enabling secure data retention policies and robust protection of sensitive information like emails, credit card numbers, and API tokens during Vercel integrations.

Use Cases

  • 1. GDPR/CCPA Compliance Automation: Streamline the implementation of privacy-by-design patterns to ensure Vercel-hosted applications meet international data protection standards.
  • 2. Automated PII Redaction: Identify and mask sensitive user data (emails, phone numbers, SSNs) in real-time before it reaches logs or third-party storage to prevent data leaks.
  • 3. Data Retention Management: Configure and enforce automated data cleanup schedules and retention policies to minimize legal liability and storage costs.
  • 4. Secure Integration Auditing: Establish encrypted audit logging and data classification workflows for Vercel integrations, ensuring sensitive credentials and business metrics are handled according to security best practices.
namevercel-data-handling
description|
allowed-toolsRead, Write, Edit
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Vercel Data Handling

Overview

Handle sensitive data correctly when integrating with Vercel.

Prerequisites

  • Understanding of GDPR/CCPA requirements
  • Vercel SDK with data export capabilities
  • Database for audit logging
  • Scheduled job infrastructure for cleanup

Data Classification

Category Examples Handling
PII Email, name, phone Encrypt, minimize
Sensitive API keys, tokens Never log, rotate
Business Usage metrics Aggregate when possible
Public Product names Standard handling

PII Detection

const PII_PATTERNS = [
  { type: 'email', regex: /[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}/g },
  { type: 'phone', regex: /\b\d{3}[-.]?\d{3}[-.]?\d{4}\b/g },
  { type: 'ssn', regex: /\b\d{3}-\d{2}-\d{4}\b/g },
  { type: 'credit_card', regex: /\b\d{4}[- ]?\d{4}[- ]?\d{4}[- ]?\d{4}\b/g },
];

function detectPII(text: string): { type: string; match: string }[] {
  const findings: { type: string; match: string }[] = [];

  for (const pattern of PII_PATTERNS) {
    const matches = text.matchAll(pattern.regex);
    for (const match of matches) {

## Detailed Reference

See `{baseDir}/references/implementation.md` for complete data handling guide.