Metadata is the most sensitive asset in your catalog. Here's exactly how we handle, encrypt, and protect it through every step of the validation process.
All metadata files and database records are encrypted using AES-256. Files uploaded for validation are stored in encrypted object storage and are never accessible via public URLs.
Every API request and response is transmitted over TLS 1.3 with perfect forward secrecy. No plaintext metadata ever traverses the network between your system and our engine.
Validation runs in isolated, ephemeral containers. Your metadata is processed in memory, results are returned, and the container is destroyed — no residual data persists between runs.
Your catalog metadata is never used to train models, build datasets, or improve shared algorithms. Your data is your data — it is used exclusively to serve your validation requests.
From upload to purge — five stages, each with its own security guarantees. No step stores raw metadata unless you explicitly choose to persist it.
You upload a metadata file (CSV, XLSX, or DDEX ERN) via the API or dashboard. The file is encrypted client-side before transmission.
The file is placed in an isolated, ephemeral processing container. No other tenant's data exists in the same execution context.
The validation engine runs the metadata through 2,400+ store-specific rule sets. Processing occurs entirely in encrypted memory.
A structured compliance report is returned via the API. The report contains field-level verdicts — no raw metadata is stored post-validation.
The processing container is destroyed. Uploaded files are retained only if you explicitly enable persistence, and only for your configured retention window.
Every entity record is scoped to the owning account via row-level security. No cross-tenant data access is possible, even at the database layer.
API keys are issued per-environment with granular scope. Read-only validation tokens cannot modify records. Write tokens are rate-limited and auditable.
Every read, write, and validation request is logged with timestamp, source IP, token ID, and affected records. Logs are retained for 90 days and available via the audit API.
Anomalous access patterns — unusual IP ranges, burst requests, credential stuffing attempts — are detected automatically and trigger temporary access blocks.
You control how long validation results and uploaded files are retained. Default retention is 30 days; configurable per-project down to 24 hours.
Submit a deletion request via the API or dashboard. All associated records, files, and logs are purged within 72 hours and a deletion certificate is issued.
Annual third-party audit of security, availability, and confidentiality controls.
Information security management system certified by accredited registrar.
Full compliance with EU data protection regulations, including DPO appointment and data subject rights.
California Consumer Privacy Act compliance with opt-out and deletion rights.
We do not process or store payment card data. Billing is handled by our payment processor.
Enterprise customers can request access to our full security documentation, data processing agreements, and penetration test reports.
Request Documentation