Your information.
Clearly explained.
Privacy notice for the datai website and marketplace
Version: 3 November 2026 · marketplace-v1
Your account
We store the name and email address you provide, your account role, country, profile description, occupations and activity categories. When you create a contributor account or enable contributions, we record the time you accept contributor permissions and the applicable license version. Passwords are stored as salted scrypt hashes. Session tokens and password recovery codes are stored as hashes. Your recovery code is shown once; there is no email-based password reset service.
Your profile information is self-declared. An email address is an account identifier and is not represented as verified ownership. Your public offers can display your contributor name, activity and collection description. Email addresses and private account information are not displayed in the catalogue.
Recordings and annotations
Uploaded videos are private objects in Cloudflare R2. We store their associated metadata, contributor declarations, action annotations, upload-part checksums and review history in Cloudflare D1. A location hint of Western Europe was requested for the video bucket; this is not a guarantee that every technical network operation takes place in that region.
Authorized contributors can access their own recordings. Platform reviewers can access submissions for quality and rights checks. Buyers can access the recordings included in their paid orders, subject to the license and order status. Public catalogue pages display approved inventory summaries, not unrestricted video downloads.
Automatic video analysis
When a production NVIDIA service is connected, an authenticated media worker reads private originals, measures their technical properties and generates silent video segments for Nemotron 3.5 Super VL. The model produces descriptions, approximate timed actions, visible objects/tools and quality/privacy flags. This is sampled visual analysis, not audio or frame-by-frame review. Original files, model outputs, source hashes and versioned processing provenance are kept private alongside the recording and its licensed snapshots. Permission statements remain contributor declarations. Results with uncertainties or relevant flags are kept off sale rather than automatically published.
The production inference deployment may process recording content on its configured infrastructure. Recordings are not sent to an unconfigured trial service. Do not submit sensitive or unauthorized recordings; the model is not a guarantee that private information will be detected.
Measured file fingerprints help prevent identical uploads from becoming duplicate marketplace supply. Processing decisions and fingerprints remain traceable even when unused analysis artifacts are removed. Private analysis artifacts from withdrawn, unreferenced recordings or stale terminal attempts become eligible for cleanup after a 30-day grace, with existing order snapshots protected. This cleanup does not itself delete source video files or cancel existing licenses.
Private review drafts
Authorized independent reviewers can explicitly save unfinished action labels, raw annotation JSON and review notes as a private draft for a recording. Each draft belongs to one reviewer account, keeps its original source-version references and expires 30 days after its latest save. Regular cleanup removes expired drafts and drafts that are no longer reviewable or authorized. Saving a draft does not approve a recording or change its published annotations.
Reviewers can download their own draft backups and import a compatible file for the same account and source version. Verification checkboxes are never restored as completed. A recording link does not share a private draft or bypass access controls.
Orders, allocations and payouts
Orders preserve a snapshot of the licensed recordings and annotations. The platform records prices, payment provider references, contributor allocations, transfer states and refund adjustments. Payment and payout onboarding are handled by Stripe when configured. Card and bank account details are collected by the payment provider, rather than stored directly by datai.
Payment configuration is separate from account creation and upload access. An unconfigured checkout does not take money or grant paid download access.
Contact requests
The contact form collects your name, email, request type and message. Organization and country are optional. Research requests may include an optional dataset brief with activities, task goals, requested volume, capture preferences, annotation layers, delivery formats, timing and constraints. A request key and payload hash prevent duplicate submissions; they do not provide public access to the request. Authorized administrators can record internal follow-up notes and request statuses, with a history of who made each update. These requests and their activity history are kept for up to 180 days after the original submission and then removed automatically. Recording review access does not grant access to contact requests. Contact form submission does not subscribe you to marketing emails.
Storage and retention
Account records are retained while the account is in use. Uploaded footage and review records are kept to operate the marketplace and honor valid licenses. Order, payment and rights records may need to be retained to administer transactions, resolve disputes or meet applicable obligations. Contact us to request access, correction or deletion; an existing license or transaction can affect which records must be kept.
Sessions expire after seven days. Abandoned multipart uploads are cleaned after six days. Authentication rate-limit records and the contact form’s daily network identifiers are short-lived. We do not store raw IP addresses in these application rate-limit tables. Cloudflare and Stripe may process technical information under their own service and security practices.
Cookies and tracking
The marketplace uses an essential, HttpOnly session cookie for sign-in. It does not add advertising trackers, marketing cookies or third-party audience measurement. Website fonts and images are served with the site. Minimal resumable-upload metadata and an opaque contact-submission key with a payload hash may be stored in your browser; passwords and recovery codes are not kept there by the application.
Your choices and requests
Do not upload recordings containing people without permission, sensitive personal information, confidential work or unauthorized material. The contributor declarations and review process do not replace the permissions you need to capture and license a recording.
To request access, correction or deletion, contact contact@modelmentor.fr using the email associated with your account or request. You can also contact the relevant data protection authority in your jurisdiction. The account recovery code is for password recovery; never send it in a support message.