Organisation isolation
Every asset, job, dataset and review belongs to one organisation. A request for another organisation’s data is answered as not found.
Updates from skilled work & robotics.
Sign upEach point below states what the Curatrix application does today. The terms for your project are set out in writing before collection.
Every asset, job, dataset and review belongs to one organisation. A request for another organisation’s data is answered as not found.
Members prepare footage, reviews and datasets. Only admins sign off privacy reviews, release datasets and download original footage.
An organisation can sign in through its own OpenID Connect provider. Only existing members get in; no accounts are created automatically.
An API key belongs to one organisation and reaches only its data. We store only a hash of each key, and an admin can revoke it at any time.
Role changes, privacy sign-offs, releases, original downloads and deletion requests are written to an append-only log per organisation. Entries cannot be changed or deleted.
The application servers and footage storage are hosted in the EU. Every connection runs over TLS, and browsers are told to use HTTPS only.
Admins record the evidence of permission for each site and approve or revoke it. An expired or revoked permission blocks the release.
A detector finds faces, a person corrects them and an admin signs off. Faces are pixelated in the delivered video, and a release is refused until every video is cleared. Location tags stored inside the file (GPS), which are not visible in the picture, are removed from every copy the platform makes, and processing stops if any remain.
A release pins the reviewed annotations and pixelated videos it contains. A rebuild produces the same bytes and the same checksum for the main archive; the LeRobot export is not signed and can differ between builds.
Each release ships a manifest with a SHA-256 checksum for every file. The manifest is signed with Ed25519, and the public key is published so you can verify the archive.
A download link is issued only after the licence check and is valid for five minutes. Video goes straight from storage; the API never passes it through.
When an admin deletes a recording, access ends at once. A worker then purges every stored version and the affected delivery archives. A backup copy can remain for up to 30 more days.
Curatrix is preparing for ISO 27001 certification and a SOC 2 Type II examination. Both are in progress, and no certificate or report is available yet. For procurement reviews we share the planned scope, the current status and the expected timing on request. A report is shared only once the audit is complete.
Your project brief defines data acceptance: task coverage, usable duration, annotation requirements and review evidence. Agree the quality evidence for your release before collection begins.
Plain answers to the questions that come up in every review. The written agreement for your project sets out the details.
The contributor agrees to the recording terms in the application before a recording can be submitted, and the people recorded are told beforehand who is responsible and for what purpose, as our privacy notice sets out. The contributor or an admin can withdraw consent at any time: the recording then leaves every future release, and new downloads that contain it stop. Copies already delivered are not recalled.
The person responsible for the site gives written permission before anyone records there; for a customer’s premises we provide the form, as our terms state. An admin records that permission and can revoke it. A recording must be covered by a permission valid on its recording date, and an expired or revoked permission blocks the release.
A detector finds faces, a person corrects them and an admin signs off; faces are pixelated in every delivered video, and a release is refused until every video is cleared. Location tags stored inside the file (GPS) are removed from every copy the platform makes. Only faces are pixelated, so recordings that show readable customer records, addresses or name badges are not accepted.
The application servers and footage storage are hosted in the EU, and every connection runs over TLS. The sub-processors involved in storage and processing are named in the data processing agreement, which is available on request.
The retention period for raw recordings is set per project in the written agreement, and the platform deletes recordings once it has passed unless a released version still ships them. When an admin deletes a recording, access ends at once, and every stored version and the affected delivery archives are purged. A backup copy can remain for up to 30 more days.
Contributors are paid for accepted recordings at the rate for their trade, which they see before they record; a recording that is not accepted is not paid, and the reason is stated. Payment runs once a month on a fixed day by bank transfer, and pay earned for an accepted recording stays with the contributor even after a consent withdrawal. The terms set this out.
No. Footage you upload into a project commissioned by you stays attributed to your organisation: the platform refuses to mix it with other footage, list it, use it as a sample or license it to any other customer. It passes the same face review before release.
We answer security questionnaires for your proposed project. Our data processing agreement and our technical and organisational measures are available on request.