— Contact
Share your use case, task category, environment, and data requirements. dexset can help design the right dataset collection and delivery workflow.
— Compliance & Trust
From first consent form to final delivery, dexset workflows are built to meet data protection, security, and labor standards across the regions where we capture and the regions where our customers operate.
Every participant is briefed and signs a release before capture begins. Consent records attach to each clip, and withdrawal requests are honored across all delivered versions.
Face blurring, anonymization, and exclusion zones are applied wherever required. We minimize personal data by design and never collect more than the task brief demands.
Footage is encrypted in transit and at rest, with role-based access controls, signed delivery URLs, and per-recipient transfer records on every dataset.
Capture and delivery workflows are designed to align with GDPR and UK GDPR, CCPA/CPRA, PIPL, APPI, and LGPD requirements, with regional data-residency options where needed.
Source, consent, capture, environment, and annotation records persist for every dataset, supporting audits that run from raw footage to the exported training file.
Capture operators, demonstrators, and annotators are fairly paid and work under documented, safe conditions — quality data should never come from exploitative labor.
— What Teams Say
★★★★★
“From brief to delivered COCO export in three weeks. Generic annotation vendors quoted us three months for lower quality.”
David Park
Founding Engineer, Independent Robotics Vendor
★★★★★
“dexset captured 400 hours of bin-picking demonstrations across three warehouses. The failure taxonomy alone cut our triage time in half.”
Lena Ortiz
Head of Robot Learning, AI Robotics Company
★★★★★
“Their teleoperation intervention capture turned our deployment into a data source. Every takeover now feeds the next training run.”
Jonas Weber
CTO, Independent Robotics Vendor
— FAQ
A dexset data expert reviews your use case and replies within one business day with clarifying questions or a proposed scoping call. Most projects move from first contact to a written capture plan within a week.
The task your robot needs to learn, the environment it will operate in, rough volume expectations, and your preferred export format. A short failure description — what breaks today — helps us scope the most useful dataset first.
Yes, and most teams do. A pilot of a few hours of captured, annotated data validates capture setup, label quality, and schema fit before you commit to a larger program.
Yes. We routinely work under NDA before any task details are shared, and capture programs inside your facilities run under your confidentiality and security requirements.