apollo-data-handling
'Apollo.io data management and compliance.
Install / Use
npx skills add jeremylongshore/tons-of-skills-marketplace --skill apollo-data-handlingInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
LegalSupported Platforms
Our assessment of apollo-data-handling
apollo-data-handling scores 86/100 on our quality scale, 97th of 208 Legal skills we index (top 47%).
Its SKILL.md is 9.0 KB long, well organised into 14 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.
With 2,785 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so apollo-data-handling is actively maintained.
- Our last check on 2026-10-12 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
apollo-data-handling compared with similar skills
All 4 of these similar skills score higher than apollo-data-handling; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| apollo-data-handling (this skill)by jeremylongshore | 86 | 2.8k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install apollo-data-handling?
- Run
npx skills add jeremylongshore/tons-of-skills-marketplace --skill apollo-data-handling. The install tabs above show the steps for each supported agent. - Which AI agents does apollo-data-handling work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is apollo-data-handling safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is apollo-data-handling still maintained?
- The repository was last updated about 2 months ago, so apollo-data-handling is actively maintained.
Skill content
View source on GitHubname: apollo-data-handling description: 'Apollo.io data management and compliance.
Use when handling contact data, implementing GDPR compliance,
or managing data exports and retention.
Trigger with phrases like "apollo data", "apollo gdpr", "apollo compliance",
"apollo data export", "apollo data retention", "apollo pii".
' allowed-tools: Read, Write, Edit, Bash(kubectl:), Bash(curl:) version: 1.13.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags:
- saas
- apollo
- compliance compatibility: Designed for Claude Code
Apollo Data Handling
Overview
Data management, compliance, and governance for Apollo.io contact data. Apollo's database contains 275M+ contacts with PII (emails, phones, LinkedIn profiles). This covers GDPR subject access/erasure, data retention, field-level encryption, and audit logging — using the real Apollo Contacts API endpoints.
Prerequisites
- Apollo master API key (contacts/delete requires master key)
- Node.js 18+
Instructions
Step 1: GDPR Subject Access Request (SAR)
Find all data Apollo has on a person and export it.
// src/data/gdpr.ts
import axios from 'axios';
const client = axios.create({
baseURL: 'https://api.apollo.io/api/v1',
headers: { 'Content-Type': 'application/json', 'x-api-key': process.env.APOLLO_API_KEY! },
});
interface SubjectAccessReport {
email: string;
dataFound: boolean;
crmContact?: Record<string, any>;
apolloDatabaseMatch?: Record<string, any>;
activeSequences: string[];
exportedAt: string;
}
export async function handleSAR(email: string): Promise<SubjectAccessReport> {
const report: SubjectAccessReport = {
email, dataFound: false, activeSequences: [],
exportedAt: new Date().toISOString(),
};
// 1. Search your CRM contacts (contacts you've saved)
const { data: crmData } = await client.post('/contacts/search', {
q_keywords: email,
per_page: 1,
});
if (crmData.contacts?.length > 0) {
const c = crmData.contacts[0];
report.dataFound = true;
report.crmContact = {
id: c.id, name: c.name, email: c.email, title: c.title,
phone: c.phone_numbers, organization: c.organization_name,
city: c.city, state: c.state, country: c.country,
createdAt: c.created_at, updatedAt: c.updated_at,
contactStage: c.contact_stage_id,
labels: c.label_ids,
};
report.activeSequences = c.emailer_campaign_ids ?? [];
}
// 2. Check Apollo's database (enrichment data)
try {
const { data: enrichData } = await client.post('/people/match', { email });
if (enrichData.person) {
report.dataFound = true;
report.apolloDatabaseMatch = {
name: enrichData.person.name,
title: enrichData.person.title,
seniority: enrichData.person.seniority,
city: enrichData.person.city,
linkedinUrl: enrichData.person.linkedin_url,
organization: enrichData.person.organization?.name,
};
}
} catch { /* person not found in Apollo DB */ }
return report;
}
Step 2: Right to Erasure (Delete)
export async function handleErasure(email: string): Promise<{
email: string; erased: boolean; sequencesRemoved: number;
}> {
// 1. Find the CRM contact
const { data } = await client.post('/contacts/search', {
q_keywords: email, per_page: 1,
});
const contact = data.contacts?.[0];
if (!contact) return { email, erased: false, sequencesRemoved: 0 };
// 2. Remove from all sequences first
let sequencesRemoved = 0;
const sequenceRemovalFailures: string[] = [];
for (const seqId of contact.emailer_campaign_ids ?? []) {
try {
await client.post('/emailer_campaigns/remove_or_stop_contact_ids', {
emailer_campaign_id: seqId,
contact_ids: [contact.id],
});
sequencesRemoved++;
} catch (err: any) {
// Do not delete while the contact may still receive outreach.
sequenceRemovalFailures.push(seqId);
}
}
if (sequenceRemovalFailures.length > 0) {
throw new Error(`Erasure paused: removal failed for ${sequenceRemovalFailures.length} sequence(s)`);
}
// 3. Delete the contact from your CRM (requires master key)
await client.delete(`/contacts/${contact.id}`);
return { email, erased: true, sequencesRemoved };
}
Step 3: Data Retention Policy
// src/data/retention.ts
interface RetentionPolicy {
maxAgeDays: number;
inactiveThresholdDays: number;
protectedLabels: string[]; // label IDs to never auto-delete
}
export async function enforceRetention(policy: RetentionPolicy) {
const cutoff = new Date();
cutoff.setDate(cutoff.getDate() - policy.maxAgeDays);
// Search for old contacts
const { data } = await client.post('/contacts/search', {
sort_by_field: 'contact_created_at',
sort_ascending: true,
per_page: 100,
});
const candidates = data.contacts.filter((c: any) => {
if (new Date(c.created_at) > cutoff) return false;
// Skip contacts with protected labels
const labels = c.label_ids ?? [];
return !policy.protectedLabels.some((l) => labels.includes(l));
});
console.log(`Found ${candidates.length} contacts past ${policy.maxAgeDays}-day retention`);
let deleted = 0;
for (const contact of candidates) {
try {
await client.delete(`/contacts/${contact.id}`);
deleted++;
} catch (err: any) {
console.error(`Failed to delete ${contact.name}: ${err.message}`);
}
}
return { evaluated: data.contacts.length, deleted };
}
Step 4: Field-Level Encryption for Local Storage
// src/data/encryption.ts
import crypto from 'crypto';
const KEY = Buffer.from(process.env.APOLLO_ENCRYPTION_KEY!, 'hex'); // 32 bytes
const ALGO = 'aes-256-gcm';
export function encrypt(plaintext: string): string {
const iv = crypto.randomBytes(16);
const cipher = crypto.createCipheriv(ALGO, KEY, iv);
let enc = cipher.update(plaintext, 'utf8', 'hex');
enc += cipher.final('hex');
return `${iv.toString('hex')}:${cipher.getAuthTag().toString('hex')}:${enc}`;
}
export function decrypt(ciphertext: string): string {
const [ivHex, tagHex, enc] = ciphertext.split(':');
const decipher = crypto.createDecipheriv(ALGO, KEY, Buffer.from(ivHex, 'hex'));
decipher.setAuthTag(Buffer.from(tagHex, 'hex'));
let dec = decipher.update(enc, 'hex', 'utf8');
dec += decipher.final('utf8');
return dec;
}
// Encrypt PII before storing Apollo data locally
export function encryptContactPII(contact: any) {
return {
...contact,
email: contact.email ? encrypt(contact.email) : null,
phone: contact.phone ? encrypt(contact.phone) : null,
linkedin_url: contact.linkedin_url ? encrypt(contact.linkedin_url) : null,
name: contact.name, // keep searchable
};
}
Step 5: Audit Logging
// src/data/audit-log.ts
interface AuditEntry {
timestamp: string;
action: 'search' | 'enrich' | 'export' | 'delete' | 'sar' | 'erasure';
userId: string;
contactId?: string;
email?: string;
detail: string;
}
export function logAudit(entry: Omit<AuditEntry, 'timestamp'>) {
const full: AuditEntry = { ...entry, timestamp: new Date().toISOString() };
// In production: write to database or cloud logging
console.log(`[AUDIT] ${full.action} by ${full.userId}: ${full.detail}`);
}
// Usage:
// logAudit({ action: 'erasure', userId: 'privacy@co.com', email: 'user@ex.com',
// detail: 'GDPR erasure: contact deleted, removed from 2 sequences' });
Output
- GDPR Subject Access Request handler searching CRM contacts + Apollo database
- Right to Erasure handler: remove from sequences then delete contact
- Retention policy enforcer with age-based cleanup and label protection
- AES-256-GCM field-level encryption for locally stored PII
- Audit log capturing every data operation with user attribution
Examples
For a verified subject-access and erasure request, authenticate the requester through the organization’s privacy process, create a case ID, and run the SAR against only the authorized contact record. Store the export in the approved restricted location and log its retention deadline without copying raw PII to CI or chat. For erasure, first remove the record from every active sequence; if any removal fails, leave the CRM record intact, record the failed sequence IDs in the case system, and escalate for manual completion. Delete only after all sequence removals succeed, then retain the minimal audit receipt required by the organization’s policy.
Error Handling
| Issue | Resolution | |-------|------------| | 403 on delete | Contact deletion requires master API key | | Contact in active sequence | Remove from sequence before deleting | | Encryption key lost | Use a KMS (GCP KMS, AWS KMS) with key versioning | | Audit log gaps | Write to durable store before processing, not after |
Resources
Next Steps
Proceed to apollo-enterprise-rbac for access control.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
