Privacy and Consent for Egocentric Data
Operational controls for first-person recording in homes, workplaces, and other real environments.
Read Guide ↗Trust architecture
Trust Is a Chain of Evidence, Not a Badge Row.
Quality, provenance, privacy, licensing, and security must remain connected from collection protocol to the exact files a buyer receives.
01
Protocol
Versioned task, capture, environment, device, instruction, and stop rules.
02
Asset
Integrity, media properties, timestamps, checksums, required fields, and relationships.
03
Decision
Visibility, task completion, annotation, privacy, rights, rejection, and adjudication evidence.
04
Release
Dataset card, schema, version, lineage, license, limitations, and buyer ingest proof.
Quality Control Should Mirror Model Risk
Generic media checks are necessary but insufficient. Acceptance must verify that the target supervision survives capture and transformation.
Media
Integrity
Decode, duration, dimensions, codec, frame rate, audio policy, corruption, and duplicates.
Task
Observability
Required actions, contacts, objects, outcomes, and failures remain visible.
Labels
Consistency
Ontology, boundaries, agreement, confidence, adjudication, and version.
Context
Coverage
Task, environment, object, viewpoint, and edge-case distributions match the brief.
Rights
Eligibility
Consent, privacy review, permitted use, distribution tier, and retention status.
Delivery
Reproducibility
Schema, checksums, splits, transformations, lineage, and loader validation.
Provenance
Every Transformation Needs a Traceable Parent.
Raw assets, normalized media, clips, annotations, redactions, exports, and releases should use stable identifiers and versioned lineage. Corrections must be additive and auditable rather than silently overwriting the record.
Buyer-facing documentation should explain what changed, which tools or reviewer roles performed the change, and which source and policy versions produced the delivered output.
Privacy and Licensing Are Release-Specific
Collection permission, internal model use, controlled buyer access, and indexed public marketing are different distribution decisions.
- 01
Minimize
Exclude unnecessary people, places, screens, documents, audio, and sensitive context before recording.
- 02
Document
Connect consent, rights scope, policy version, compensation, and retention to eligible assets.
- 03
Screen
Review for incidental identity, private information, sensitive activity, and distribution restrictions.
- 04
Control
Apply access tiers, least privilege, revocable credentials, logging, and contractual limits.
- 05
Reapprove
Run the release gate again for new versions, buyers, public pages, or distribution channels.
Due diligence
Put the Acceptance Criteria in the Brief.
Share the privacy, rights, security, QA, documentation, and delivery controls your program requires.
Start Technical Review