Privacy

Earshot is run by Yurii Trofymov, a private individual based in Ukraine. For anything on this page, write to privacy@meetearshot.com.

If you have an account (you build studies and read results), we decide how your account data is used, and we are responsible for it. In the language of data-protection law we are the controller.

If you were invited to an interview, the team that invited you decides what is asked and what is done with your answers. They are the controller of that data; we hold and process it for them, on their instructions, as their processor. Questions about your interview are best put to them first; you can also write to us and we will pass it on.

• Your account. Your email address. If you sign in with Google, also the name and profile picture Google shares. If you sign in with a code, the one-time code we emailed you, kept only as a hash and only for ten minutes.
• Your workspace. The studies, guides and settings your team writes, who its members are, the invitations it sends, what you ask the built-in assistant and what it answers, and how much interview time the workspace has used.
• Interviews. A participant's name and email address, if the team asks for them; the audio recording of the conversation; its transcript; and what is made from it: summaries, answers sorted by question, and analysis across interviews.
• What a server sees. Your IP address and the time of each request, in short-lived logs kept by our hosting provider and used to keep the service running and to stop abuse.
• One cookie. A session cookie that keeps you signed in for up to thirty days. It is essential and there are no others: no advertising, no analytics, no tracking across sites. Your light or dark theme and keyboard preference are kept in your own browser.

A participant does not need an account and gets no cookie from us.

• To provide the service you or your team signed up for: holding interviews and showing their results.
• To sign you in, send the emails you ask for (a sign-in code, an invitation) and keep accounts secure.
• To count the interview time a workspace uses.
• To fix faults and prevent abuse.

Nothing is sold, nothing is used for advertising, and we do not use interviews to train models of our own. For account holders the legal basis is our agreement with you, and our legitimate interest in keeping the service secure. For participants the basis is the one the inviting team relies on, usually your consent, which the interview page asks for before the conversation starts.

We use other companies to run parts of the service. Each receives only what its part needs and handles it under its own data-processing terms:

• A voice and speech provider carries the spoken conversation, makes the recording and the transcript, and keeps the recording.
• A file storage provider keeps a copy of each recording. It is the copy the research team plays back.
• An AI model provider reads transcripts to write the analysis, and powers the built-in assistant.
• Hosting and database providers run the application and store what it holds.
• An email delivery provider sends sign-in codes and invitations.
• Google, if you choose to sign in with it, confirms who you are.

Within a workspace, its members see its studies and interviews. Nobody outside it does, except us when that is needed to run or repair the service, or when the law requires it.

Our own database and servers are in the European Union. Some of the providers above process data in other countries, including the United States. Where the law asks for it, those transfers rest on appropriate safeguards such as standard contractual clauses.

• Your account, for as long as you have it. Ask and it is deleted.
• A workspace's studies and interviews, until the team deletes them or asks us to. Deleting a study or an interview in the app removes its transcript and analysis from our database at once.
• A recording is kept by the voice provider, and a copy of it in our file storage. Deleting an interview or a study in the app removes that copy and asks the voice provider to remove its recording and transcript at the same moment. If you want to be sure one is gone, write to us and we will check.
• Sign-in codes, ten minutes. Sessions, thirty days. Invitations, fourteen days.

Under the EU's General Data Protection Regulation and Ukraine's Law “On Personal Data Protection” you can ask to see the data held about you, to have it corrected or deleted, to have its use limited, to object to its use, to receive it in a portable form, and to withdraw a consent you gave. Write to privacy@meetearshot.com; we answer within thirty days. If you took part in an interview, the team that invited you can do the same for you, and we will help them.

If you think your data has been mishandled, you can complain to a supervisory authority: in Ukraine, the Ukrainian Parliament Commissioner for Human Rights; in the EU, the data-protection authority of the country you live in.

Earshot is a tool for work. It isn't meant for anyone under sixteen, and interviews aren't to be held with them.

When this page changes, the date at the top does. If a change affects what is done with data already collected, account holders are told by email before it takes effect.