Ela Logs · Speech collection

Privacy Notice

What Ela Logs collects from contributors, why we collect it, who receives it, how long we keep it and how you can withdraw at any time.

Effective and last updated 13 August 2026 · Project MSPO-2450 · Consent version v1.0

1Overview

Ela Logs runs a voice-data collection project. This notice explains, in plain language, what we collect from contributors, why we collect it, who receives it and what control you keep over it.

Nothing is recorded or stored until you have read the consent statement and ticked every affirmation. Recording begins only after consent is given. If you do not consent, you cannot take part and no recordings are kept.

2What we collect and why

  • Google account information used for sign-in — your name and email address from the Google account you sign in with. Used to create your account, to make sure one person has one account, and to contact you about your participation.
  • Profile and demographic information — age, gender, country, state of residence, state you record in, accent/locale and recording setup. Used to confirm your eligibility and to balance the dataset across speaker groups.
  • Voice recordings — the audio you record or upload in response to project prompts. This is the core purpose of the project.
  • Technical and quality-check information — automatic measurements of each recording such as length, speech-versus-silence ratio, background noise level, loudness and file format. Used to accept or reject recordings against the project's quality requirements.
  • Device and session information — device type, browser user agent and timestamps. Used for quality review, to detect duplicate or substituted recordings, and to keep the platform secure.
  • Consent records — which affirmations you ticked, the consent version, a fingerprint of the consent text you saw and the time you agreed. Used as evidence that your participation was consented.

3Voice recordings may be biometric data

Your voice recordings may be treated as voice data or biometric data under applicable laws. We ask you to acknowledge this explicitly as part of consent, and we do not accept contributions from states where we cannot lawfully run this collection.

4Who receives your data

Approved recordings and the associated project metadata (such as speaker ID, prompt ID, accent, age group, gender and device type) may be provided to the project client and its authorised service providers for the purposes described in the consent statement.

Your name, email address and account identity are kept internal to Ela Logs project administration and are not included in the dataset delivered to the client. Client deliveries identify you only by a pseudonymous Speaker ID.

5How your data is stored

Recordings are stored in encrypted cloud object storage, in an area reserved exclusively for project MSPO-2450 and separated from any other project. Access is limited to a small number of explicitly approved Ela Logs staff members, sensitive actions such as playing back audio or viewing contributor identity are recorded in an audit log, and access to the platform requires signing in.

6How long we keep it

Rejected recordings are scheduled for removal after 30 days. Unfinished uploads are scheduled for removal after 24 hours. Accepted recordings are retained for the duration of the project and its delivery to the client.

Automated deletion from cloud storage is not enabled for this release. Removal of stored audio is carried out by an administrator as a reviewed manual step. We confirm your erasure only after the object has been verified as removed from storage, and we keep an audit record that the deletion took place. This means deletion is not instantaneous; we complete requests within 30 days.

Consent records and audit entries are retained after deletion of audio, because they are the evidence that your participation and your erasure were handled correctly.

7Your choices and requests

You can ask for a copy of your data, correct your details, request deletion, or withdraw your consent at any time from the “Your data and choices” page once you are signed in. Withdrawing consent stops any further participation.

If recordings have already been delivered to the project client, we can delete our copies and stop any further use, but we cannot guarantee removal from a dataset that has already left our systems. For that reason, requests made before delivery can always be honoured in full.

8Contact and support

The quickest route for any privacy request is the “Your data and choices” page — requests raised there are tracked, assigned to an administrator and answered within 30 days.

If you cannot sign in, reply to the invitation message you received from the Ela Logs project team and we will handle your request through the same process.