Trust Center
What we do with your data, how we protect it, and how contributors consent to the work they produce. Each control below carries its actual status — including the ones that are planned rather than in place.
Controls
No controls have been published yet. This page lists a control only once it has been reviewed and approved for release, so an empty section means nothing has been approved — not that nothing is in place. Enterprise buyers can request the full register under NDA.
Contributor consent
Consent is recorded per person, per type, against the version of the document they accepted, with the date. The types are separate on purpose: agreeing that a client may train a model on your voice is not agreeing that strangers may listen to it.
Platform terms
Required of everyoneThe rules for using the platform.
Privacy notice
Required of everyoneHow LAHJA handles the contributor's own personal data.
Contributor agreement
Required of everyoneThe working relationship: how work is offered, reviewed and paid, and who owns the result.
Data processing
Required of everyoneThat work produced on the platform is processed and delivered to clients.
Voice recording
That the contributor's recorded voice may be delivered to a client under contract.
AI training use
That delivered work may be used to train models.
Public sample
Optional and withdrawableThat a specific recording may be published publicly — on the website, in the Lab, in a talk. Separate from any client delivery, and withdrawable.
Project confidentiality
That project material seen while working is confidential.
Project-specific terms
Additional terms a particular client requires.
For any project we can produce a consent evidence report showing, per record, which consents are held and at which document version. Contributors appear as project-scoped pseudonyms: the report proves coverage without identifying anybody.
Certifications
No certification is currently held.
LAHJA AI does not hold ISO 27001, SOC 2 or any equivalent third-party attestation, and does not claim to. Where a certification is being worked towards it is listed below as planned — planned is not achieved, and this page will not say otherwise until a certificate exists and has been attached to the record.
Reference mapping only. A tag indicates which topic a control would speak to in an audit. It is not a certification, an audit result, or a claim of compliance with that framework.
Subprocessors
Providers that process data on our behalf. A provider appears here only once its security review is complete.
No subprocessors are currently published. See the full list and change log →
Documents
Signed agreements — NDA, DPA, MSA, statements of work — are private to the client they belong to and are available in that client’s own compliance room. They are never published here.
Getting in touch
- Security
- contact@lahja-ai.com
- Privacy
- contact@lahja-ai.com
- Legal
- contact@lahja-ai.com
- Vendor onboarding
- contact@lahja-ai.com
Reporting a security issue? See responsible disclosure.
This page describes operational practice. It is not legal advice, and it is not a certification or an audit report. Where a control is planned rather than in place, it says so. An enterprise buyer needing more detail than is published here can request the full control register and evidence under NDA.