A public audit trail for oto data
Every dataset available through oto is backed by an audit trail of contributor consent, policy acceptance, provenance signals, and compensation status. Verify any asset. Review any dataset and the chain of custody.
Live receipts
Every contribution oto accepts surfaces here within seconds. Click any hash for the full receipt.
| Event | App | Address | Activity | Date |
|---|---|---|---|---|
Legal & Compliance Review
oto's participant consent, Terms of Service, and data licensing documents have been reviewed by U.S. counsel to address AI training, third-party dataset licensing, voice/biometric data considerations, and applicable U.S. state privacy and consent requirements. Formal third-party certifications and technical audits will be listed here once completed.
Reviewed by U.S. counsel for AI training use, third-party dataset licensing, and applicable U.S. state privacy and consent requirements.
Reviewed for conversational audio/video collection, voice/biometric data language, and California and Texas consent considerations.
Reviewed for third-party dataset licensing and downstream AI training use.
Audit controls
- Information checks
Contributor-provided information is checked before participation.
In place - Pre-join screening
Verifies participants meet session requirements before a session begins.
In place - Post-join automated filtering
Detects quality issues and anomalies after sessions.
Automated
Published
Policies & legal
oto's published Terms of Service, Privacy Policy, and Recording Consent & Release, hosted by oto and linked here directly.
What oto collects
File coverage
Every receipt declares the media category, MIME type, and size of the file it stands for.
Average file
235.7 KB
Files measured
3,214,115
Media categories
File formats
Where contributions come from
Contributor geography
Each receipt carries the contributor's region (contributor.geo_region), bucketed here so individual contributors stay anonymous.
Top region
NA
North America
Regions
3
with located receipts
Geographic spread of contributors
North America
NA
41.1%
European Union
EU
29.5%
Southeast Asia
SEA
29.5%
Weighted by receipt volume. Sub-regional resolution available per asset; never finer than country / state.
Consent receipts
Consent and policy versions
The exact terms and privacy policy each contributor agreed to at the moment of contribution, including every version that's ever appeared on a receipt.
Terms of service
Privacy policy
F.A.Q.
If your team has a question we haven't covered, your account manager can answer it, and we'll add it here.
Are oto's Terms of Service and Recording Consent reviewed for U.S. legal requirements?
Yes. oto's Terms of Service, Recording Consent and Release, and related data licensing documents have been reviewed by U.S. counsel. These documents are designed to address applicable U.S. privacy, consent, data licensing, and voice/biometric data considerations for conversational audio and video data used in AI training.
How does oto address California and Texas privacy and consent considerations?
oto's legal documents were reviewed with particular attention to state-specific privacy and consent considerations, including California and Texas. This includes consent for conversational audio/video collection, use of data for AI training, third-party dataset licensing, and restrictions related to voice cloning, impersonation, and misuse of identifiable speakers.
Can contributors withdraw the voice data they provided?
Yes. Contributors can request withdrawal or removal of their contributed data through the oto platform, according to oto's applicable policies. Once removed, the affected assets are no longer made available through active datasets. The audit record may remain as a historical receipt to preserve provenance, consent, and lifecycle history.
How does oto handle personally identifiable information before AI training use?
oto is designed to remove or minimize personally identifiable information before contributed data is used as AI training data, where applicable. The underlying audio, video, text, or media assets are not publicly exposed through this portal. Trace is used to show audit receipts, provenance signals, consent status, and policy references rather than the underlying dataset itself.
Does this portal expose the underlying audio, video, or text data?
No. The portal is intended to expose audit receipts, provenance signals, consent status, lifecycle events, and policy version references. It does not provide public access to the underlying audio, video, text, or media assets.