Mask PII locally before it reaches any LLM

# Private beta: @trustnode/core is not on the public npm registry yet.
# After waitlist access we share a tarball / private registry invite, or you
# link the package from the TrustNode monorepo:
#
#   npm install ../path/to/packages/trustnode-core-sdk
#   # or in package.json: "@trustnode/core": "file:../trustnode-core-sdk"

import { maskPii, unmaskPii } from '@trustnode/core';

// Run in YOUR process (backend, BFF, or edge) — not as a remote "mask this text" API call.
const vault = new Map();

async function handleUserMessage(userText) {
  const { output: masked, matches } = maskPii(userText, {
    vault,
    kinds: ['email', 'creditCard', 'phone', 'iban', 'tr-tckn', 'nationalId'],
  });

  // Only the masked prompt ever reaches the external LLM.
  const llmReply = await callYourLlm(masked);

  // Restore originals before showing the user (optional).
  return { reply: unmaskPii(llmReply, vault), entitiesMasked: matches.length };
}

// Recommended for mobile + web apps:
// Mobile/Web client → your backend → maskPii(@trustnode/core) → OpenAI / Claude / Gemini
//
// Auth: use the same publishable key (tn_pub_…) as Browser Shield for config + telemetry.
// tn_secret_… is optional on paid plans for server-only clients — never ship it to browsers/mobile.
//
// 1) Fetch workspace policy (cache briefly; respect quotaExceeded)
const config = await fetch('https://api.trustnodehq.com/v1/config', {
  headers: { Authorization: `Bearer ${process.env.TRUSTNODE_PUBLISHABLE_KEY}` },
}).then((r) => r.json());

// 2) Mask locally with the same engine the Chrome extension uses
const { output, matches } = maskPii(req.body.prompt, {
  kinds: Object.entries(config.default_rules ?? {})
    .filter(([, enabled]) => enabled)
    .map(([kind]) => kind),
  brandGuard: { customTerms: config.brand_guard_terms ?? [] },
});

// 3) Call the LLM with masked text only
// 4) Report usage so dashboard Home / Billing quota stays accurate
await fetch('https://api.trustnodehq.com/v1/telemetry', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.TRUSTNODE_PUBLISHABLE_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    masked_count: matches.length,
    events: [{ at: Date.now(), platform: 'my-app', masked_count: matches.length }],
  }),
});

curl -s https://api.trustnodehq.com/v1/config \
  -H "Authorization: Bearer tn_pub_YOUR_KEY"

curl -s -X POST https://api.trustnodehq.com/v1/telemetry \
  -H "Authorization: Bearer tn_pub_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"masked_count": 3}'

# Private beta: @trustnode/cli is not on the public npm registry yet.
# From the TrustNode monorepo (after npm install in packages/trustnode-core-sdk):
cd apps/trustnode-cli
npm install
export TRUSTNODE_API_URL=https://api.trustnodehq.com
export TRUSTNODE_DASHBOARD_URL=https://app.trustnodehq.com
npm run scan -- .

import { maskPii } from '@trustnode/core';

// Dashboard Policies → Brand Guard terms sync via GET /v1/config as brand_guard_terms.
// Pass them as customTerms (flat deny-list). Advanced competitor splits are SDK-only for now.
const { output } = maskPii("Share the Project Nightingale deck with finance.", {
  brandGuard: {
    customTerms: ['Project Nightingale'], // e.g. config.brand_guard_terms
  },
});
// Matched terms are redacted locally — never vaulted.

import { maskPii, unmaskPii } from '@trustnode/core';

const vault = new Map();
const userInput = "Contact jane@example.com about the new project.";
const masked = maskPii(userInput, { vault });
// masked.output -> "Contact [EMAIL_1] about the new project."

const llmResponse = `I drafted a note for ${masked.output}`;
const finalOutput = unmaskPii(llmResponse, vault);
// Restores [EMAIL_1] → jane@example.com for the end user only.