Data Collection

Multi-modal training data for regulated AI

A contributor standing alone on a marked capture floor beneath a circular multi-camera sensor rig

Audio, image, video, LiDAR, text, TTS, transcription, and parallel corpus, collected through a managed contributor network and delivered with documentation scoped to your review.

150+ LANGUAGES NORWEGIAN LEGAL ENTITY ARTICLE 10 DOCUMENTATION SUPPORT SCOPED PILOTS
Scope a collection project Inspect the documentation

Norwegian legal entity (Brønnøysund reg. 933 915 778).

Input Channels

Eight modalities, one engagement

Most vendors split data collection across separate service lines. YPAI runs every channel below in one engagement, one consent design, one documentation posture.

CH-1 Audio 150+ languages · native-speaker capture · wake-word, in-cabin assistant, multilingual ASR, dialect coverage WAV/FLAC 48kHz/24-bit + JSON Automotive (in-cabin voice) · Healthcare (clinical voice) · Financial (KYC voice + MiFID II)
CH-2 Image Segmentation-ready · demographic metadata · face imagery only under explicit consent 12-bit RAW + COCO/YOLO/Pascal Automotive perception · Retail computer vision · Healthcare imaging
CH-3 Video Multi-camera synchronised capture · automated ingestion and QC MP4/MOV + per-frame metadata Automotive ADAS · Sports analytics · Security
CH-4 LiDAR Sensor-fusion grade, per project · time-aligned LiDAR, radar and camera PCD/LAS + fusion sidecar Automotive perception · Robotics · Surveying
CH-5 Text Domain-specialised corpora · legal, medical, financial lexicons JSONL + provenance manifest LLM fine-tuning · Domain RAG · Regulated NLP
CH-6 TTS Studio-grade voice · designed for Article 9 explicit consent in voice-cloning use WAV + speaker metadata Voice assistants · Localised TTS · Accessibility
CH-7 Transcription 150+ languages · phoneme-level option · diarisation, timing alignment, in-house QA TextGrid/JSON + alignment ASR training · Closed-captioning · Forensic linguistics
CH-8 Parallel corpus Post-edited machine translation for regulated domains · domain-tagged TMX/XLIFF + dual-source provenance MT training · Multilingual model alignment

Consent Chain

Per-contributor consent, audit-defensible by design

Marketplace consent is platform Terms of Service: bundled, aggregate, and not GDPR Article 7 valid for biometric voice or facial data. YPAI consent is recorded per contributor, per project, with Article 9 special-category handling separated and a 30-day erasure SLA.

  1. Foundational

    01 Recruitment and ID verification

    Contributor identity verified at intake. No anonymous crowd workers.

  2. GDPR Art. 7

    02 Per-project consent

    Specific purpose, informed, freely given. Captured per project, not bundled into a platform agreement.

  3. GDPR Art. 9

    03 Special-category consent

    Separated evidence pack for biometric voice, facial, health, or other special-category data.

  4. Per-record manifest

    04 Tamper-evident provenance

    Per-recording manifest with tamper-evident signing on the consent and metadata bundle.

  5. GDPR Art. 17

    05 30-day erasure SLA

    Individual-level erasure with audit-log proof. SLA measured against per-record completion.

Regulatory Alignment

EU AI Act Article 10, mapped to deliverables

Article 10 sets data-governance obligations for high-risk AI systems. YPAI ships the documentation that supports your conformity assessment. We do not certify your AI system; we provide the evidence pack your assessment needs.

Article 10(2)(b)

data governance and management practices

Per-project data governance manifest

Sub-processor list, sampling methodology, and QA audit log shipped per project.

Article 10(3)

relevant statistical properties

Demographic and dialect metadata

Per-recording demographic, dialect, and locale metadata. Aggregate distribution report per project.

Article 10(4)

examination in view of possible biases

Bias-audit log

Sampling methodology, demographic coverage report, and known-gap declarations included in the deliverable bundle.

Article 10(5)

processing of special categories of personal data

Article 9 separated evidence pack

Special-category consent records, erasure-receipt log, and purpose-limited retention attestations.

Contributor Network

40,000 verified contributors across 150+ languages

Identity-verified network with documented EEA residency, demographic metadata per contributor, and self-hosted EU annotation infrastructure. Not a marketplace crowd: a vetted network with individual-level provenance.

Verified contributors

210,000+

Identity-verified at intake

Languages and locales

150+

Documented per-language coverage

Countries reached

50+

EEA-based teams available where required

Jurisdiction

EEA

Norwegian legal entity; transfer controls per project

Norwegian Swedish Danish Finnish Icelandic German Dutch French Spanish Italian Portuguese Polish Czech Slovak Greek Romanian Bulgarian Hungarian Estonian Latvian Lithuanian Slovenian Croatian Maltese Irish Welsh Basque Catalan Galician and 120+ more
MTPE Coverage · 300+ language pairs Post-edited machine translation across regulated-vertical lexicons Show coverage detail

Coverage is organised in four language families plus a regulated-vertical lexicon overlay. The exact pair list and per-pair throughput are confirmed at project scoping; below are the groups in scope.

  • EU-24 EN paired with FR, DE, ES, IT, NL, PT, PL, CS, HU, EL, BG, RO, HR, SK, SL, ET, LT, LV, FI, SV, DA, MT, GA
  • Nordic + EFTA NO, IS, plus EU-Nordic cross-pairs (SV-NO, DA-NO, FI-SV)
  • Asian + Cyrillic EN paired with JA, ZH, KO, AR, RU, UK, TR
  • Vertical lexicons Legal (case-law citation, EU Regulation), Medical (ICD-11, pharmaceutical), Financial (MiFID II, KYC, accounting)

Pair-level throughput, post-edit quality grade, and reviewer credentials confirmed at project scoping. DPA and Article 28 clauses are included by default, not on request.

Deliverable Evidence Pack

Every project ships an audit-ready evidence pack

On delivery you receive the data plus a structured evidence bundle your DPO, legal counsel, and procurement team can review without follow-up. Master DPA included by default, not on request.

bundle.tree YPAI-DC / per project 
project-deliverable/
 consent-records/                  [per-contributor]
 consent-{id}.json               [signed]
 article-9-special-category/     [separated pack]
 provenance/                       [per-recording]
 recording-{id}.json             [tamper-evident]
 device-locale-dialect-metadata/
 qa-logs/                          [immutable versioning]
 demographic-metadata.csv          [aggregate + per-record]
 sampling-methodology.pdf          [bias-audit input]
 bias-audit-log.pdf                [Article 10(4)]
 sub-processor-list.pdf            [transparency]
 erasure-receipts.log              [30-day SLA]
 DPA.pdf                           [signed, project-scoped]

  • consent-records/

    One JSON per contributor with the Article 7 capture, separated Article 9 evidence if applicable, and the documented revocation pathway.

  • provenance/

    Per-recording manifest with device, locale, dialect, and tamper-evident signing on the consent and metadata bundle.

  • qa-logs/ and bias-audit-log.pdf

    Documentation supporting your EU AI Act Article 10(4) bias examination. Sampling methodology, demographic coverage, and known-gap declarations included.

  • DPA.pdf and erasure-receipts.log

    Master DPA signed and project-scoped, included with every engagement. Erasure-receipt log tracks the 30-day SLA at the per-record level.

Master DPA template and audit-artefact specifications

Next Step

Scope your multi-modal collection

Tell us the modality, the regulatory context, and the volume. We map a delivery plan with the consent chain, evidence pack, and master DPA included by default.

EU AI Act Article 10 applies from 2026-08-02. Cumulative GDPR fines have passed EUR 7.1B. The cost of getting data provenance wrong is procurement-blocking; the cost of getting it right is a conversation.

Scope a collection project

Master DPA included with every YPAI engagement, not on request. Norwegian legal entity. Reply within one business day.

DATA COLLECTION INTAKE

Scope a collection project.

Bring modality, environment, volume estimate, and any regulatory constraints. A named project lead replies within one EU business day with a feasibility read.

  • GDPR Article 7 consent records on every asset
  • EEA-only operations, Norwegian Aksjeselskap
  • Zero web scraping, identity-verified contributors only
  • 30-day erasure SLA on withdrawal
Modalities (optional)

GDPR Article 7 · GDPR Article 9 · EU AI Act Article 10

What happens next

From brief to a scoped pilot plan

Three states this serves: you have submitted and want to know the timing, you are about to submit and have a procurement objection, or you are not ready to submit and want a route deeper into the work.

After you submit

  1. Within one business day

    Project lead reads your brief

    A named EU-resident project lead replies within one business day with feasibility, scope clarifications, and a first read on Article 10 risk classification.

  2. During scoping

    Sample evidence pack returned

    Anonymised sample evidence pack ( data_provenance.pdf, bias_assessment.pdf, consent_audit.csv, residency_attestation.pdf ). Availability and scope are confirmed during scoping.

  3. After scoping

    Scoped pilot delivered

    The pilot uses the actual modality, markets, participant profile, capture specifications, output schema, and acceptance criteria agreed for the programme. Scope, timing, and commercial terms are project-specific.

  4. By agreement

    Master DPA signed, production scope locked

    The DPA, processing locations, sub-processors, delivery plan, and production acceptance gates are agreed before scale-up.

Procurement FAQ

Is there a minimum project size?

Project size and pilot scope are set from the modality, markets, participant profile, collection protocol, QA design, and acceptance criteria. We confirm the viable starting scope during scoping.

Can I see a sample evidence pack before signing?

We confirm which representative evidence artefacts can be shared during scoping and which project-specific artefacts will be produced under the engagement.

Does the DPA require negotiation?

No. Article 28 clauses are pre-cleared and included with every contract. Customer-specific addendums on residency or sub-processor scope are accepted, but the standard DPA ships by default. Not on request.

What about US-based sub-processors?

None by default. EEA-only operations with a named sub-processor list confirmed at scoping. Any US-domiciled sub-processor requires explicit customer sign-off via DPA addendum.

What is the withdrawal and erasure SLA?

30-day erasure SLA on any speaker or contributor withdrawal under GDPR Article 7. Recordings and derived datasets are wiped within 30 days; the audit log is retained for compliance traceability.

Or explore deeper

All routes preserve the same compliance posture: Norwegian Aksjeselskap, EEA-resident processing, GDPR Article 7 consent, EU AI Act Article 10 evidence at delivery.