ideogram-data-handling

Implement Ideogram 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 Ideogram integrations.Trigger with phrases like "ideogram data", "ideogram PII","ideogram GDPR", "ideogram data retention", "ideogram privacy", "ideogram CCPA".

⭐920stars🔀111forks📁View on GitHub🕐Updated Jan 9, 2026

When & Why to Use This Skill

This Claude skill provides a robust framework for implementing PII handling, data retention policies, and GDPR/CCPA compliance patterns specifically for Ideogram integrations. It helps developers secure sensitive information through automated redaction, data classification, and standardized privacy workflows to ensure enterprise-grade data safety.

Use Cases

  • Detecting and redacting sensitive information like emails, phone numbers, and credit card details from Ideogram integration logs to prevent data leaks.
  • Automating data cleanup and retention schedules to ensure technical compliance with global privacy regulations like GDPR and CCPA.
  • Streamlining Data Subject Access Requests (DSAR) by providing structured workflows for user data export and permanent deletion.
  • Implementing data minimization strategies to ensure only the strictly necessary user fields are requested and stored during Ideogram API interactions.
nameideogram-data-handling
description|
allowed-toolsRead, Write, Edit
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Ideogram Data Handling

Overview

Handle sensitive data correctly when integrating with Ideogram.

Prerequisites

  • Understanding of GDPR/CCPA requirements
  • Ideogram 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) {
      findings.push({ type: pattern.type, match: match[0] });
    }
  }

  return findings;
}

Data Redaction

function redactPII(data: Record<string, any>): Record<string, any> {
  const sensitiveFields = ['email', 'phone', 'ssn', 'password', 'apiKey'];
  const redacted = { ...data };

  for (const field of sensitiveFields) {
    if (redacted[field]) {
      redacted[field] = '[REDACTED]';
    }
  }

  return redacted;
}

// Use in logging
console.log('Ideogram request:', redactPII(requestData));

Data Retention Policy

Retention Periods

Data Type Retention Reason
API logs 30 days Debugging
Error logs 90 days Root cause analysis
Audit logs 7 years Compliance
PII Until deletion request GDPR/CCPA

Automatic Cleanup

async function cleanupIdeogramData(retentionDays: number): Promise<void> {
  const cutoff = new Date();
  cutoff.setDate(cutoff.getDate() - retentionDays);

  await db.ideogramLogs.deleteMany({
    createdAt: { $lt: cutoff },
    type: { $nin: ['audit', 'compliance'] },
  });
}

// Schedule daily cleanup
cron.schedule('0 3 * * *', () => cleanupIdeogramData(30));

GDPR/CCPA Compliance

Data Subject Access Request (DSAR)

async function exportUserData(userId: string): Promise<DataExport> {
  const ideogramData = await ideogramClient.getUserData(userId);

  return {
    source: 'Ideogram',
    exportedAt: new Date().toISOString(),
    data: {
      profile: ideogramData.profile,
      activities: ideogramData.activities,
      // Include all user-related data
    },
  };
}

Right to Deletion

async function deleteUserData(userId: string): Promise<DeletionResult> {
  // 1. Delete from Ideogram
  await ideogramClient.deleteUser(userId);

  // 2. Delete local copies
  await db.ideogramUserCache.deleteMany({ userId });

  // 3. Audit log (required to keep)
  await auditLog.record({
    action: 'GDPR_DELETION',
    userId,
    service: 'ideogram',
    timestamp: new Date(),
  });

  return { success: true, deletedAt: new Date() };
}

Data Minimization

// Only request needed fields
const user = await ideogramClient.getUser(userId, {
  fields: ['id', 'name'], // Not email, phone, address
});

// Don't store unnecessary data
const cacheData = {
  id: user.id,
  name: user.name,
  // Omit sensitive fields
};

Instructions

Step 1: Classify Data

Categorize all Ideogram data by sensitivity level.

Step 2: Implement PII Detection

Add regex patterns to detect sensitive data in logs.

Step 3: Configure Redaction

Apply redaction to sensitive fields before logging.

Step 4: Set Up Retention

Configure automatic cleanup with appropriate retention periods.

Output

  • Data classification documented
  • PII detection implemented
  • Redaction in logging active
  • Retention policy enforced

Error Handling

Issue Cause Solution
PII in logs Missing redaction Wrap logging with redact
Deletion failed Data locked Check dependencies
Export incomplete Timeout Increase batch size
Audit gap Missing entries Review log pipeline

Examples

Quick PII Scan

const findings = detectPII(JSON.stringify(userData));
if (findings.length > 0) {
  console.warn(`PII detected: ${findings.map(f => f.type).join(', ')}`);
}

Redact Before Logging

const safeData = redactPII(apiResponse);
logger.info('Ideogram response:', safeData);

GDPR Data Export

const userExport = await exportUserData('user-123');
await sendToUser(userExport);

Resources

Next Steps

For enterprise access control, see ideogram-enterprise-rbac.