clerk-data-handling
Tools and patterns for handling user data, exports, and GDPR compliance within Clerk integrations.
Install
mkdir -p .claude/skills/clerk-data-handling && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8359" && unzip -o skill.zip -d .claude/skills/clerk-data-handling && rm skill.zipInstalls to .claude/skills/clerk-data-handling
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Handle user data, privacy, and GDPR compliance with Clerk.Key capabilities
- →Export user profiles and application data
- →Cascade deletion of user records and associated data
- →Manage user consent via publicMetadata
- →Implement audit logging for compliance events
How it works
This skill uses the Clerk Backend API to retrieve user profiles and manage metadata. It provides templates for cascading deletions across application databases and Clerk, ensuring audit trails for compliance.
Inputs & outputs
When to use clerk-data-handling
- →Implement user data export functionality
- →Automate user account deletion for GDPR
- →Manage user consent and data privacy
- →Audit user data storage and handling
About this skill
Clerk Data Handling
Overview
Manage user data, implement privacy features, and ensure GDPR/CCPA compliance using the Clerk Backend API. Covers data export, right to be forgotten, consent management, and audit logging.
Prerequisites
- Clerk integration working
- Understanding of GDPR/CCPA requirements
- Database with user-related data linked by Clerk user IDs
Instructions
Step 1: User Data Export
// app/api/privacy/export/route.ts
import { auth, clerkClient } from '@clerk/nextjs/server'
export async function GET() {
const { userId } = await auth()
if (!userId) return Response.json({ error: 'Unauthorized' }, { status: 401 })
const client = await clerkClient()
const clerkUser = await client.users.getUser(userId)
// Gather data from Clerk
const clerkData = {
id: clerkUser.id,
emails: clerkUser.emailAddresses.map((e) => e.emailAddress),
firstName: clerkUser.firstName,
lastName: clerkUser.lastName,
createdAt: clerkUser.createdAt,
lastSignInAt: clerkUser.lastSignInAt,
publicMetadata: clerkUser.publicMetadata,
}
// Gather data from your database
const appData = await db.user.findUnique({
where: { clerkId: userId },
include: { posts: true, comments: true, preferences: true },
})
return Response.json({
exportDate: new Date().toISOString(),
clerkProfile: clerkData,
applicationData: appData,
})
}
Step 2: User Deletion (Right to be Forgotten)
// app/api/privacy/delete/route.ts
import { auth, clerkClient } from '@clerk/nextjs/server'
export async function DELETE() {
const { userId } = await auth()
if (!userId) return Response.json({ error: 'Unauthorized' }, { status: 401 })
const deletionLog: { step: string; status: string }[] = []
try {
// 1. Delete application data first
await db.comment.deleteMany({ where: { authorId: userId } })
deletionLog.push({ step: 'comments', status: 'deleted' })
await db.post.deleteMany({ where: { authorId: userId } })
deletionLog.push({ step: 'posts', status: 'deleted' })
await db.user.delete({ where: { clerkId: userId } })
deletionLog.push({ step: 'app_user', status: 'deleted' })
// 2. Delete from Clerk (this ends the session)
const client = await clerkClient()
await client.users.deleteUser(userId)
deletionLog.push({ step: 'clerk_user', status: 'deleted' })
// 3. Log deletion for compliance audit trail
await db.auditLog.create({
data: {
action: 'USER_DELETED',
subjectId: userId,
details: JSON.stringify(deletionLog),
timestamp: new Date(),
},
})
return Response.json({ deleted: true, log: deletionLog })
} catch (error) {
return Response.json({ error: 'Partial deletion', log: deletionLog }, { status: 500 })
}
}
Step 3: Consent Management with Metadata
// lib/consent.ts
import { clerkClient } from '@clerk/nextjs/server'
interface ConsentRecord {
marketing: boolean
analytics: boolean
thirdParty: boolean
updatedAt: string
}
export async function updateConsent(userId: string, consent: Partial<ConsentRecord>) {
const client = await clerkClient()
const user = await client.users.getUser(userId)
const existing = (user.publicMetadata.consent as ConsentRecord) || {}
const updated: ConsentRecord = {
...existing,
...consent,
updatedAt: new Date().toISOString(),
}
await client.users.updateUser(userId, {
publicMetadata: { ...user.publicMetadata, consent: updated },
})
return updated
}
export async function getConsent(userId: string): Promise<ConsentRecord | null> {
const client = await clerkClient()
const user = await client.users.getUser(userId)
return (user.publicMetadata.consent as ConsentRecord) || null
}
Step 4: Consent UI Component
'use client'
import { useUser } from '@clerk/nextjs'
import { useState } from 'react'
export function ConsentManager() {
const { user } = useUser()
const consent = (user?.publicMetadata as any)?.consent || {}
const [marketing, setMarketing] = useState(consent.marketing ?? false)
const [analytics, setAnalytics] = useState(consent.analytics ?? true)
const saveConsent = async () => {
await fetch('/api/privacy/consent', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ marketing, analytics }),
})
}
return (
<div>
<h3>Privacy Preferences</h3>
<label>
<input type="checkbox" checked={marketing} onChange={(e) => setMarketing(e.target.checked)} />
Marketing communications
</label>
<label>
<input type="checkbox" checked={analytics} onChange={(e) => setAnalytics(e.target.checked)} />
Analytics tracking
</label>
<button onClick={saveConsent}>Save Preferences</button>
</div>
)
}
Step 5: Audit Logging via Webhooks
// app/api/webhooks/clerk/route.ts (audit section)
async function logAuditEvent(evt: WebhookEvent) {
const auditEntry = {
eventType: evt.type,
userId: 'user_id' in evt.data ? evt.data.user_id : evt.data.id,
timestamp: new Date().toISOString(),
metadata: JSON.stringify(evt.data),
}
await db.auditLog.create({ data: auditEntry })
// Track compliance-relevant events
if (['user.deleted', 'user.updated'].includes(evt.type)) {
console.log(`[COMPLIANCE] ${evt.type} for user ${auditEntry.userId}`)
}
}
Output
- Data export API returning Clerk profile + application data
- User deletion cascade (app data, then Clerk, then audit log)
- Consent management stored in Clerk publicMetadata
- Privacy preferences UI component
- Audit logging for compliance events
Error Handling
| Scenario | Action |
|---|---|
| Partial deletion failure | Log completed steps, retry failed services, alert ops team |
| Export timeout on large data | Queue export job, email user download link when ready |
| Consent sync failure | Retry with exponential backoff, fall back to local storage |
| Clerk API rate limit on bulk delete | Batch deletions with delays between requests |
Examples
Bulk User Data Cleanup Script
// scripts/cleanup-orphaned-users.ts
import { createClerkClient } from '@clerk/backend'
const clerk = createClerkClient({ secretKey: process.env.CLERK_SECRET_KEY! })
async function cleanupOrphanedDbUsers() {
const dbUsers = await db.user.findMany({ select: { clerkId: true } })
for (const dbUser of dbUsers) {
try {
await clerk.users.getUser(dbUser.clerkId)
} catch (err: any) {
if (err.status === 404) {
console.log(`Orphaned user: ${dbUser.clerkId} — removing from DB`)
await db.user.delete({ where: { clerkId: dbUser.clerkId } })
}
}
}
}
Resources
Next Steps
Proceed to clerk-enterprise-rbac for enterprise SSO and RBAC.
Prerequisites
Limitations
- →Partial deletion requires manual retry or logging
- →Bulk deletion may hit Clerk API rate limits
How it compares
It automates the data lifecycle management process by linking Clerk user deletion with application-specific database cleanup.
Compared to similar skills
clerk-data-handling side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| clerk-data-handling (this skill) | 0 | 27d | Review | Advanced |
| auth-patterns | 7 | 7mo | Review | Intermediate |
| middleware-protection | 1 | 6mo | Review | Intermediate |
| reviewing-nextjs-16-patterns | 11 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
auth-patterns
davepoon
This skill should be used when the user asks about "authentication in Next.js", "NextAuth", "Auth.js", "middleware auth", "protected routes", "session management", "JWT", "login flow", or needs guidance on implementing authentication and authorization in Next.js applications.
middleware-protection
dadbodgeoff
Protect routes with Next.js middleware. Check authentication once, protect routes declaratively. Supports public routes, protected routes, and role-based access.
reviewing-nextjs-16-patterns
djankies
Review code for Next.js 16 compliance - security patterns, caching, breaking changes. Use when reviewing Next.js code, preparing for migration, or auditing for violations.
nextjs-supabase-auth
davila7
Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route.
firebase
davila7
Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they're often wrong. Firestore queries are limited, and you learn this after you've designed your data model. This skill covers Firebase Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Firebase Hosting. Key insight: Firebase is optimized for read-heavy, denormalized data. I
better-auth
mrgoonie
Implement authentication and authorization with Better Auth - a framework-agnostic TypeScript authentication framework. Features include email/password authentication with verification, OAuth providers (Google, GitHub, Discord, etc.), two-factor authentication (TOTP, SMS), passkeys/WebAuthn support, session management, role-based access control (RBAC), rate limiting, and database adapters. Use when adding authentication to applications, implementing OAuth flows, setting up 2FA/MFA, managing user sessions, configuring authorization rules, or building secure authentication systems for web applications.