NoData + Claude

// Claude writes this:
const res = await fetch("https://www.nodatacapsule.com/api/v1/encrypt", {
  method: "POST",
  headers: {
    "Authorization": "Bearer sk_live_...",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    field: "phone",
    value: customer.phone
  })
});
const { ciphertext } = await res.json();
await db.insert({ phone: ciphertext }); // DB gets ciphertext only

// Claude writes this:
const res = await fetch("https://www.nodatacapsule.com/api/v1/deliver", {
  method: "POST",
  headers: { "Authorization": "Bearer sk_live_..." },
  body: JSON.stringify({
    content: "sk_prod_a8f3e9c2d1b8...",
    ttl: "1h",
    maxViews: 1,
    burn: true
  })
});
const { link } = await res.json();
// link = nodatacapsule.com/v/del-x8Kd — one view, then gone

// Claude runs the scanner on your open code:
// Found 155 PII fields across 75 tables
// Encrypted: 75/155 (48%)
// Routes without auth: 309/309
// Breach impact: 52% readable as plaintext
// SOC 2 readiness: 73%
//
// Recommendation: Add encrypt() to 80 fields

// 1. Claude encrypts FIRST
const { ciphertext } = await nodata.encrypt("phone", value);

// 2. THEN deploys to Netlify/Vercel
// Only ciphertext reaches the server
// Netlify/Vercel never sees plaintext

// ✅ SAFE: server gets aes256gcm:v1:x8Kd...
// ❌ WRONG: deploy plaintext, then encrypt on server