Fast structured PII detection, implemented in Rust and exposed for Rust, Python, Node.js, and browsers.
It detects EMAIL, PHONE, SSN, CREDIT_CARD, IP_ADDRESS, DATE, and ZIP_CODE. Every binding returns the same finding information:
entity type, matched text, byte range, code-point range,
optional confidence, detector name, optional detector version
Structured JSON scanning additionally discovers PERSON from documented name-field
aliases or explicit JSON Pointer mappings. It scans every string value with the
existing detectors and returns field paths plus string-local findings. No model
or dictionary download is needed. See person-field discovery
for scan_structured / scanStructured and structured transformation APIs.
Both ranges use zero-based, end-exclusive offsets. The byte range addresses the
UTF-8 input; the code-point range addresses Unicode scalar values. Rule-based
detectors currently report no confidence score. Node.js and browser WASM also
return an explicitly named UTF-16 code-unit range that can be passed directly
to JavaScript String.prototype.slice.
The transformation strategies are redact, mask, remove, pseudonymize,
and tokenize in Rust, Python, and Node.js.
Redaction uses an unnumbered [ENTITY_TYPE] placeholder, masking supports full
or leading/trailing reveal modes, and removal deletes only the exact finding
span. Pseudonymization uses provider-resolved 256-bit keys and deterministic
HMAC-SHA-256 tokens. Tokenization uses an application-supplied asynchronous
provider to issue opaque DFTOKENv1(...) envelopes and restore them under an
exact request-level scope. Both provider-backed strategies are deliberately
unsupported in browser WASM.
transform requires explicit findings; scan_and_transform (or
scanAndTransform in JavaScript) is the explicit scan-then-transform
convenience. Results include the transformed text and an ordered record for
every applied replacement, including its source metadata and output byte and
code-point ranges. Node.js and browser WASM additionally return source and
output UTF-16 ranges. Transformation records never include the original
matched text.
Transformation calls require an envelope with a default strategy. It can also select entity types, override the strategy per entity, and exempt exact or full-match regex values:
{
default: { strategy: "redact" },
entities: ["EMAIL", "PHONE"],
overrides: {
PHONE: { strategy: "mask", reveal: { direction: "last", count: 4 } },
},
allow: {
exact: { EMAIL: ["support@example.com"] },
regex: { EMAIL: [{ pattern: ".+@example\\.org" }] },
},
}scan_and_transform uses { scan?: { locale?: string }, transform: ... } so
detection settings remain separate from transformation policy.
| Runtime | Distribution | Import | Status |
|---|---|---|---|
| Rust | datafog-core |
datafog_core |
Published |
| Python | datafog-core |
datafog_core |
Published |
| Node.js | @datafog/node |
@datafog/node |
Published |
| Browser/WASM | @datafog/wasm |
@datafog/wasm |
Published |
DataFog Core is a separate distribution and canonical API, not a drop-in
replacement for the established datafog Python package.
| DataFog Python 4.8.x | DataFog Core 0.3.x |
|---|---|
pip install datafog |
pip install datafog-core |
from datafog.engine import ... |
from datafog_core import ... |
scan(...).entities |
scan(...) returns list[Finding] |
scan_and_redact(...) |
scan_and_transform(...) |
result.redacted_text |
result.text |
Entity.type, .text, .start, .end |
Finding.entity_type, .matched_text, .byte_range, .codepoint_range |
Do not mechanically rename legacy token to Core tokenize: Core tokenization
is provider-backed and reversible. For non-reversible output, use redact,
mask, or remove; use keyed pseudonymize when stable linkage is required.
See the dedicated DataFog Python migration guide for the API mapping, strategy differences, entity names, range semantics, and migration checklist.
cargo add datafog-coreuse datafog_core::{
scan, scan_and_transform, ScanAndTransformConfig, TransformationConfig,
TransformationStrategy,
};
let findings = scan("Email jane@example.com");
assert_eq!(findings[0].entity_type, "EMAIL");
assert_eq!(findings[0].matched_text, "jane@example.com");
assert_eq!(findings[0].byte_range.start, 6);
let result = scan_and_transform(
"Email jane@example.com",
&ScanAndTransformConfig::new(TransformationConfig::new(
TransformationStrategy::Redact,
)),
).unwrap();
assert_eq!(result.text, "Email [EMAIL]");python -m pip install datafog-coreimport asyncio
from datafog_core import PrivacyManager, scan, scan_and_transform
findings = scan("Email jane@example.com")
print(findings[0].entity_type) # EMAIL
print(findings[0].matched_text) # jane@example.com
print(findings[0].byte_range.start) # 6
result = scan_and_transform(
"Email jane@example.com",
{"transform": {"default": {"strategy": "redact"}}},
)
assert result.text == "Email [EMAIL]"
masked = scan_and_transform(
"Email jane@example.com",
{
"transform": {
"default": {
"strategy": "mask",
"reveal": {"direction": "last", "count": 4},
}
}
},
)
assert masked.text == "Email ************.com"
class KeyProvider:
async def resolve_key(self, key_ref, key_version):
return {"key": load_32_byte_key(key_ref, key_version), "resolved_version": "7"}
async def pseudonymize():
return await PrivacyManager(KeyProvider()).scan_and_transform(
"Email jane@example.com",
{
"transform": {
"default": {"strategy": "pseudonymize", "key_ref": "customers/email"}
}
},
)
pseudonymized = asyncio.run(pseudonymize())
# A token provider implements tokenize_batch(scope, items) and
# restore_batch(scope, items). It owns storage or reversible cryptography,
# authorization, lifecycle, and audit.
token_manager = PrivacyManager(None, token_provider=TokenProvider())
tokenized = asyncio.run(token_manager.scan_and_transform(
"Email jane@example.com",
{"transform": {"default": {"strategy": "tokenize", "token_ref": "customers/default"}}},
{"scope": "tenant-a"},
))
restored = asyncio.run(token_manager.restore(tokenized.text, {"scope": "tenant-a"}))Install the native Node.js package:
npm install @datafog/nodeimport { PrivacyManager, scan, scanAndTransform } from "@datafog/node";
console.log(scan("Email jane@example.com"));
console.log(
scanAndTransform("Email jane@example.com", {
transform: { default: { strategy: "redact" } },
}).text,
);
const manager = new PrivacyManager({
async resolveKey({ keyRef, keyVersion }) {
return { key: await load32ByteKey(keyRef, keyVersion), resolvedVersion: "7" };
},
});
const pseudonymized = await manager.scanAndTransform("Email jane@example.com", {
transform: {
default: { strategy: "pseudonymize", key_ref: "customers/email" },
},
});
const tokenManager = new PrivacyManager({ tokenProvider });
const tokenized = await tokenManager.scanAndTransform(
"Email jane@example.com",
{ transform: { default: { strategy: "tokenize", token_ref: "customers/default" } } },
{ scope: "tenant-a" },
);
const restored = await tokenManager.restore(tokenized.text, { scope: "tenant-a" });The release includes prebuilt binaries for macOS (Intel and Apple Silicon), Linux (x64 and ARM64), and Windows x64.
Install the browser/WASM package:
npm install @datafog/wasmimport { init, scan, scanAndTransform } from "@datafog/wasm";
await init();
console.log(scan("Email jane@example.com"));
console.log(
scanAndTransform("Email jane@example.com", {
transform: { default: { strategy: "redact" } },
}).text,
);cargo test --workspaceTo exercise an installed binding package locally:
npm ci --prefix bindings/node
npm run test:package --prefix bindings/node
rustup target add wasm32-unknown-unknown
cargo install wasm-bindgen-cli --version 0.2.127 --locked
npm ci --prefix bindings/wasm
npx --prefix bindings/wasm playwright install chromium
npm run test:package --prefix bindings/wasmcrates/core/ Rust scanning library
bindings/python/ Python extension
bindings/node/ Node.js native binding
bindings/wasm/ Browser/WASM binding
fixtures/ Shared conformance fixtures