DataLicenser

Security / trust model

Access should fail closed.
Control should stay yours.

DataLicenser minimizes edge permissions, signs local policy and access state, and verifies licensed labs beyond a claim in the user-agent header.

01

Signed local policy

A versioned disk cache is verified before protected crawler decisions. Invalid or expired policy fails closed for known crawlers.

02

Short-lived access state

HMAC-SHA256 tokens bind licensed access to a publisher, lab, agreement, request class, timestamp, and nonce.

03

Anti-spoofing checks

Where supported, source IP ranges or reverse DNS are checked alongside signed credentials. A matching user-agent alone does not establish trust.

04

No request-time SaaS dependency

Human traffic does not wait on a DataLicenser API call. Rules and telemetry move through background jobs.

05

Publisher deal control

Each lab can be enabled, scoped, or revoked separately. Exclusivity applies only when the publisher has approved it.

06

Minimal telemetry

No page bodies, visitor cookies, or unrelated human traffic are collected by the standard decision event model.

Pre-launch disclosure

Crawler verification is limited by the identity data each provider publishes. Formal certifications, penetration-test reports, production subprocessors, retention schedules, and incident-response SLAs are not claimed until completed.

Evaluate the model against your stack.

Read the cache, token, telemetry, and deal-control reference before connecting infrastructure.

Read technical docs