Capture Provenance
Rules for lawful capture, privacy, operator context, and what counts as evidence inside Blueprint.
Choose the right support pathWhere to go when you need a package, hosted review, capture access, or human reply.StartPackage access vs hosted evaluationWhen to use each buyer path.PackagesHow to read package provenanceWhat the evidence labels mean.PackagesReport a hosted runtime issueWhat to send if the hosted view behaves incorrectly.HostedWhat to send supportThe minimum packet that gets a useful reply.Fixes
3 min readCapture rules overviewThe baseline rules for capture submissions.3 min readPublic-facing location captureHow Blueprint treats everyday public-facing sites.4 min readRights, privacy, and consentHow support thinks about capture permissions.3 min readCapture quality reviewWhat Blueprint checks before a capture supports a package.3 min readWhen site-operator permission mattersHow operator involvement fits into Blueprint.2 min readCapturer submission statusWhat happens after a capturer submits.
Still need help?
Route the blocker with evidence.
Support works fastest when the request includes the exact page, package, session, or request id plus the outcome you expected.