Skip to content
How access works

From first call to secure delivery

This is the five-step path from “we’re interested” to data in your bucket.

Samples after NDADownload access logged
Workflow

Five steps, start to finish

Each step ends with a clear deliverable.

01

30-minute call to scope it out

Languages, formats, use case, and buyer constraints are clarified before anything sensitive moves.

02

Sign an NDA, swap paperwork

License, security, buyer requirements, and source evidence are exchanged.

03

Look at sample data

A real slice arrives with a data card, dialect breakdown, license summary, and QA notes.

04

Sign the contract

Scope, price, delivery dates, and commercial limits go into the contract.

05

Data lands in your bucket

The dataset lands in S3, GCS, Azure, or SFTP with manifest, checksums, and source docs.

First reply

2 business days

We confirm the request and first scoping questions.

NDA-to-sample

5 business days

From signed NDA to first sample package.

Pilot timeline

3-4 weeks

From inquiry to signed pilot, depending on scope.

Delivery security

How delivery stays locked down

These controls apply to every handoff.

Who can download what

Named buyer contacts get access. Everyone else gets nothing.

SHA-256 on every file

Every bundle ships with checksums so your team can verify integrity.

Time-boxed download links

URLs expire and are re-issued only after approval.

Audit log of every download

Who accessed what, when, available after delivery.

FAQ

Common questions

Short answers to the things teams usually ask before a pilot starts.

Can I see a sample before signing anything?

Not cold. After a short scoping call and NDA, you get a real slice with the same data card and license paperwork the full release would carry.

How fast does a Bengali pilot move?

Most Bengali-led pilots run two to four weeks from NDA to first data drop.

Can I get just speech, or just text?

Yes. Scope is by modality, so buyers only pay for and review what they need.

Do you ship the license paperwork too?

Yes. Release summaries include source references, license summaries, and contract links for each source group.

Can blocked data be mixed into a release?

No. Blocked sources stay blocked unless the license situation changes.

Start with a short scoping call.

Tell us the languages and format you need. We’ll take it from there.