This page summarizes our general approach. A signed Data Processing Addendum per engagement governs the actual handling of any specific buyer's project data.
Buyer project data
Where MenaData processes data on behalf of a buyer (for example, reviewing a buyer-supplied dataset, or collecting new data under a buyer's project scope), we act as a data processor and the buyer's Master Services Agreement and Data Processing Addendum govern that relationship, including instructions for handling, retention, and deletion at the end of an engagement.
Contributor consent
Contributors provide task-specific consent before performing work — covering what they are recording, writing, or reviewing, how it will be used (including that it may be delivered to a buyer as part of a dataset), and what rights they are licensing. Consent is scoped to the project it was given for; it is not a blanket authorization to reuse a contributor's submissions for unrelated future projects without further consent.
Contributor licensing & IP assignment
Contributors grant the rights necessary for a project's data to be used and licensed to the buyer as scoped in that project's terms, and retain any rights not explicitly granted. The specific license terms for each project are set out in that project's task agreement.
PII handling in collected data
Where recordings may contain personal information about third parties (for example, other voices in the background, or people named during a conversation), our collection protocols require consent or redaction appropriate to the project — see Security & Data Rights for how project data is handled.
Sub-processors
We use Amazon Web Services (AWS) to host our application, database, and file storage and to send email, and Cloudflare to deliver and protect this website. If your project requires data to be stored in a specific jurisdiction, tell us during scoping and we'll confirm the arrangement in your project agreement.
Contact
Questions about data processing: [email protected].