Skip to content
elokeo
Back to home

elokeo information

Privacy policy

How elokeo processes your account, voice, analyses and progress, and how to exercise your rights.

Updated:

1. Who is responsible for your data?

This policy applies to the elokeo app and its presentation website. The publisher is Hugo Monte Limited.

Address: 34, TRIQ WIED GHOMOR, SAN GILJAN, STJ 2043, Malta

Registration: C113491

For a question about your data: hello@elokeo.com.

2. Data used by the app

  • Account: email address, name when provided, verification status and sign-in identifiers. If you choose Google or Apple, elokeo receives the identity information needed for that sign-in.
  • Speaking attempts: audio sent for analysis, transcription, timestamps, recording measurements and exercise feedback. The content of your voice may itself contain personal information.
  • Practice: completed exercises and sessions, preparation and vocabulary answers, selected course, history, practice dates, points, badges and daily streaks.
  • Preferences and reminders: language, time zone, reminder preferences and, if you allow notifications, the technical delivery identifier associated with your device.
  • App updates: a random installation identifier sent to Expo to download updates, even when notifications are disabled.
  • Operation and security: session information, IP address during sign-in, technical records and analysis-service usage data such as duration, model and processing cost.
  • Support: email address and the content of messages you choose to send to the team.
  • Subscription: pseudonymous customer identifier, store used, purchased product, Premium access status, expiry dates and technical transaction information needed to verify your access. elokeo does not receive your payment card details.

Do not include secrets or sensitive information about yourself or others in your exercises. The microphone is used when you start recording, after system permission. elokeo does not transmit a continuous stream while you speak: uploading starts after the recording ends.

3. Why data is processed

Account and practice data provide the service you request: signing in, analysing an attempt, retrieving progress and continuing your course. The legal basis is performance of the service where the GDPR applies.

Microphone and notification permissions are your choice. You can withdraw them in your phone's settings and turn off reminders in your profile. Without microphone access, you cannot record a new attempt.

Technical data protects sign-ins, prevents abuse, resolves incidents and monitors analysis operation. This processing relies on the legitimate interest in maintaining a secure, functional service where that basis applies.

Automated observations support practice. They may be wrong and do not measure your personality, emotions or confidence.

4. Who receives data?

People authorised by the publisher may access the data needed for maintenance, support and service operation.

  • Voice analysis: audio is sent to OpenRouter for transcription and automated feedback. Feedback also uses the transcript, recording measurements and exercise context. The current configuration uses Microsoft and Google models. Analysis providers receive the data needed for their processing.
  • Sign-in: Google or Apple are involved only if you choose their sign-in method.
  • Notifications: Expo and Apple or Google notification services receive the information needed to deliver reminders you allow.
  • App updates: Expo also receives a random installation identifier to deliver app updates.
  • Purchases and subscriptions: Apple or Google process payment in their store. RevenueCat receives the pseudonymous customer identifier linked to your account and purchase information to verify Premium access and provide subscription analytics to the publisher. Data shared with these providers is also subject to their own retention periods and obligations.
  • Usage measurement and errors: PostHog, hosted in the European Union, receives your account identifier, the screens you visit, interactions, exercise and purchase events, technical device information and app and server errors. The app also records sessions as screen captures to understand where you get stuck: input fields and images are masked, and audio is not recorded. This data is used to improve the service, not for advertising.
  • Chat support: Crisp receives technical conversation data, your IP address, approximate location derived from that address for support and statistics, and messages or attachments you send. When you open native chat from your profile, the app also sends your email address and name, or your email if no name is provided. The native SDK may initialise a technical session before chat opens; on the website, chat loads only when opened.
  • Internal alerts: Your email address and sign-in method are sent to the Telegram channel configured by the publisher when you create an account. These messages are not automatically deleted when you delete your elokeo account.
  • Hosting and email: OVHcloud hosts the API and private audio files. Cloudflare hosts the website, manages domains and network traffic, and delivers sign-in emails. These services receive the data needed to operate, including IP addresses and data in the requests or emails they process. Hosting: API: OVHcloud / OVH SAS, 2 rue Kellermann, 59100 Roubaix, France, https://www.ovhcloud.com/fr/contact/. Web / DNS: Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA, +1 650 319 8930, https://www.cloudflare.com/.

Audio files are not published or shared with other learners. The presentation website includes no advertising or advertising tracking tools.

5. Retention and deletion

Account and practice: account information, analyses, transcriptions, sessions, progress and badges are retained while the account is used. Deleting the account removes this data from active application tables, along with sign-in sessions and reminder subscriptions.

Audio file: Finished takes are saved on the device, then in private storage on elokeo servers. You can recover takes for an unfinished exercise in the app. Uploaded audio and its analysis are kept until account deletion; authorized team members can access them to review feedback and handle reports.

Analysis cache: attempt results may also remain in a technical cache for up to one hour after creation, including if the account is deleted during that time.

Processing records: Server logs are replaced as files rotate, with a limit of three 10 MB files. Analysis cost and operational records have no scheduled automatic deletion; they may remain until manually deleted, even after their direct account reference is removed.

Backups: The publisher confirms that no backups, OVH snapshots or manual copies of production data (database and audio files) are retained. Copies held by other providers follow the rules described in this policy.

Providers: Providers do not share one retention period. Retention depends on the service, its logs and the data received. OpenRouter retains request metadata; its analysis providers may apply their own rules. Deleting an elokeo account does not automatically delete copies already shared.

Also read the providers’ privacy notices: OpenRouter, RevenueCat, Crisp, PostHog, OVHcloud, Cloudflare and Telegram.

Deleting your elokeo account does not currently trigger an automatic request to delete your RevenueCat profile, Crisp conversations or Telegram alerts. To request deletion of these copies, use the contact at the start of this page.

Support and deletion requests: Your request and the information needed to verify your identity are used to handle it and document the response. Retention depends on the handling of the request and applicable obligations or disputes. Where GDPR applies, a response is due within one month; any extension must be explained within that period.

Crisp conversations: Crisp retains conversations until the team deletes them. A web session without messages expires after 30 minutes of inactivity; a conversation and its IP address may remain longer. To request deletion of your messages, attachments or support profile, email our privacy contact. Some security logs may be subject to Crisp’s own retention.

6. Security and transfers

Account access is authenticated. Email codes expire; mobile session credentials are kept in the system's secure storage. Administrative access is restricted to authorised people.

Not all services are limited to the European Union: RevenueCat uses servers in the United States; Crisp stores messages in the European Union but also uses relays outside it. AI processing countries depend on the selected provider. The providers’ published safeguards are available through the links below; you can ask us for the information applicable to your data.

Published processing agreements describe the safeguards and transfer mechanisms offered: Cloudflare, RevenueCat, PostHog and Crisp.

7. Your choices and rights

You can turn off reminders, change preferences and delete your account in the app. An account deletion request page is also provided if you no longer have the app.

In the app, open your profile, then My data, Delete my account and Delete permanently. Deletion also revokes Apple sign-in when used. It does not cancel your store subscription.

Where the GDPR applies, you can request access, correction, erasure, restriction or portability of your data and object to certain processing under the regulation's conditions. You can also withdraw consent and contact the competent data protection authority.

Use the contact at the start of this page. Your identity may need to be verified to protect your account.

You can complain to the data protection authority where you live or to Malta’s authority: Information and Data Protection Commissioner (IDPC).

8. The website and updates

This landing page does not create accounts, record your voice or set tracking cookies. Fonts and images are served with the site. Contact forms prepare an email in your mail application and do not store your input on this website.

Crisp chat loads only when you open it. Crisp then uses a session cookie to enable the conversation and recover it on a later visit. Messages are processed by Crisp and the support team. Chat is optional.

Pages and links may change with the service. The date at the top of this policy shows its latest update. Significant changes to data processing will be communicated through an appropriate channel.