Minimal data for a machine-first service.

Website analytics

FilmRightsProof uses Google Analytics on public HTML pages to understand aggregate website usage. This browser analytics is separate from FilmRightsProof's machine-operation telemetry and is not added to JSON, OpenAPI, MCP, or research API responses.

Application telemetry

Aggregate machine telemetry keeps low-cardinality operational facts such as discovery/search/trace activity, status, protocol, duration, synthetic-test exclusion, payment status/rail, trace status, safe ambiguity, current-evidence category, partial lookup, historical fallback, cache reuse and normalization failure.

It is designed not to retain searched titles, creator or party names, request bodies, IP addresses, user-agent strings, payment credentials, wallet addresses, raw authorization payloads or private buyer identity. Because buyer identity is not stored, unique repeat-buyer rate cannot be calculated directly.

Current-source requests

When current verification is enabled, FilmRightsProof sends the requested work title to the U.S. Copyright Office Copyright Public Records System to retrieve bounded public-record search results. FilmRightsProof does not intentionally attach caller identity or its internal adoption telemetry to that source request.

Infrastructure

Infrastructure providers and the public source system may process ordinary technical request information as part of operating and securing their services. FilmRightsProof does not treat those infrastructure records as a product-level user profile.

Payments

The $2 specialist trace uses the established machine-payment system. FilmRightsProof retains only the minimum provider/replay/idempotency state needed for safe settlement and does not store raw Shared Payment Tokens, stablecoin credentials, wallet secrets or payment authorization payloads in adoption analytics.

Questions: hello@davisvillelabs.com.