Juicebox Data Handling

Overview

Juicebox AI processes people datasets for talent intelligence and analysis workflows. Data types include people search results, enriched profile records (employment history, skills, social links), analysis exports, and outreach logs. Profile data often contains personal information governed by GDPR, CCPA, and recruitment privacy regulations. All enrichment results must be handled with consent tracking, purpose limitation, and right-to-deletion support. Contact data requires field-level encryption and strict access controls to prevent unauthorized disclosure.

Data Classification

Data Import

interface JuiceboxProfile {
  id: string; name: string; email?: string; phone?: string;
  company: string; title: string; skills: string[];
  source: string; enrichedAt: string;
}

async function importPeopleDataset(query: string, maxResults = 100): Promise<JuiceboxProfile[]> {
  const profiles: JuiceboxProfile[] = [];
  let offset = 0;
  do {
    const res = await fetch(`https://api.juicebox.ai/v1/search`, {
      method: 'POST',
      headers: { Authorization: `Bearer ${process.env.JUICEBOX_API_KEY}`, 'Content-Type': 'application/json' },
      body: JSON.stringify({ query, limit: 50, offset }),
    });
    const data = await res.json();
    if (!data.results?.length) break;
    for (const p of data.results) {
      if (!p.id || !p.name) throw new Error(`Invalid profile: missing required fields`);
      profiles.push(p);
    }
    offset += 50;
  } while (profiles.length < maxResults);
  return profiles;
}

Data Export

async function exportAnalysisResults(profiles: JuiceboxProfile[], format: 'csv' | 'json') {
  // Strip direct contact info from exports unless explicitly authorized
  const sanitized = profiles.map(({ email, phone, ...rest }) => ({
    ...rest,
    email: email ? '[CONSENT_REQUIRED]' : undefined,
    phone: phone ? '[CONSENT_REQUIRED]' : undefined,
  }));
  if (format === 'csv') {
    const header = Object.keys(sanitized[0]).join(',');
    const rows = sanitized.map(r => Object.values(r).join(','));
    return [header, ...rows].join('\n');
  }
  return JSON.stringify(sanitized, null, 2);
}

Data Validation

function validateProfile(p: JuiceboxProfile): string[] {
  const errors: string[] = [];
  if (!p.id) errors.push('Missing profile ID');
  if (!p.name || p.name.length > 200) errors.push('Invalid or missing name');
  if (p.email && !/^[\w.+-]+@[\w-]+\.[\w.]+$/.test(p.email)) errors.push('Invalid email format');
  if (p.phone && !/^\+?[\d\s()-]{7,20}$/.test(p.phone)) errors.push('Invalid phone format');
  if (!p.source) errors.push('Missing data source attribution');
  if (p.enrichedAt && isNaN(Date.parse(p.enrichedAt))) errors.push('Invalid enrichment timestamp');
  return errors;
}

Compliance

• GDPR consent tracked per profile: lawful basis recorded (consent, legitimate interest)
• Right-to-deletion: purge profile, enrichment data, and outreach logs within 30 days of request
• GDPR data subject access: export all stored data for a candidate on request
• CCPA opt-out: honor Do Not Sell signals for California residents
• Purpose limitation: enrichment data used only for stated recruitment/analysis purpose
• Contact data encrypted at field level with per-tenant keys
• Audit log for all profile access, export, and deletion events
• Data minimization: auto-purge enriched profiles older than retention window

Error Handling

Prerequisites

• A documented source authority and lawful-use basis, data owner, classification/retention policy, suppression list, approved destination, and synthetic fixture.

Instructions

1. Inventory fields, source terms, and intended destination before ingestion; quarantine unknown authority, classification, or suppression state.
2. Run schema, minimization, and suppression validation on bounded synthetic batches, logging only opaque IDs and aggregate counts.
3. Compare intended source/destination scope with policy before any enrichment or export, defaulting uncertainty to deny.
4. Submit idempotent staged work only to approved destinations, retain a redacted manifest, and verify deletion at the stated retention boundary.
5. Stop and escalate rather than weakening suppression, authority, or data-minimization rules.

Output

Return a handling receipt with source authority, classification, destination, policy revision, input/accepted/quarantined counts, suppression result, retention/deletion state, and rollback reference. Exclude identities, contact fields, and enrichment values.

Examples

source=synthetic-prospects; authority=approved; class=internal-test; accepted=96; quarantined=4; suppression=pass; contacts_exported=0; retention=24h; cleanup=verified is a compliant processing result.

Resources

• Juicebox Privacy Policy
• GDPR Data Subject Rights

Next Steps

See juicebox-security-basics.