Diaspeak
Download
← Back to home

Diaspeak

Privacy policy

  • Usage statistics are on by default in the app.
  • They measure how Diaspeak is used, including the Premium checkout, for the publisher only.
  • They use a random installation identifier, never linked to an account, email or advertising.
  • You can turn them off at any time in Settings → Privacy & legal; this deletes the identifier.
  • PostHog, in the European Union, keeps them for 12 months (25 is the French maximum).
  • Technical error reports stay off unless a later build is compiled to send them.

Learn as a guest or connect with Google or Apple. Here is what stays on your device, what is saved online and how to export or delete your data.

Updated: November 11, 2026 · v1.30Download the text ↓

Who is responsible?

Diaspeak is operated by Reda Sahraoui, sole trader (EI), SIREN 989252713, 59 route d’Allauch, 13011 Marseille, France. For privacy requests, write to [email protected].

The website

The site has no account, advertising tracker, newsletter form, or audience-measurement tool added by Diaspeak. Fonts and illustrations are served with the site.

Cloudflare hosts and secures the website. Delivering a page can involve your IP address, browser information, requested URL, request time, and security signals. These operations serve our legitimate interests in making the website available and protecting it against abuse. Cloudflare may use strictly necessary security mechanisms. See Cloudflare’s privacy policy.

Cookies and other tracking technologies

The website’s code sets no advertising cookies or language-preference cookie. Diaspeak has added no audience measurement. We therefore do not request consent for advertising trackers that are not present.

Cloudflare may use strictly necessary security and delivery mechanisms, for example during an anti-abuse check. Actual mechanisms depend on the request and configuration. Trackers requiring consent must not be enabled before your choice. This page will be updated if those uses change.

The Android and iOS apps

Account features apply only when your installed version offers Google or Apple sign-in. Versions without those options keep learning progress on the device. Your Diaspeak avatar, exercise answers, reviews, saved words, favourites, lives, quests, bonuses, rewards and preferences stay on your device. Lessons remain available offline.

Android and iOS use RevenueCat with Google Play and the Apple App Store respectively to display offers, validate purchases, restore subscriptions and check Premium access. These operations exchange an app identifier, associated with your Diaspeak account ID when you connect, technical app/device information and, when relevant, purchase tokens or receipts and subscription events. Subscription management supports the requested contract or pre-contractual steps; access verification also serves our legitimate interest in providing a reliable service and preventing abuse. Diaspeak does not send your learning answers, chosen name, avatar or email to RevenueCat, and does not receive your payment card number.

Purchase records are retained as needed to verify access, restore purchases, resolve refunds or disputes and meet legal obligations. Uninstalling does not automatically erase provider records or cancel a subscription. For access or deletion requests, contact [email protected]; a transaction reference may be needed to locate your records. RevenueCat processes subscription data on our behalf and may process it in the United States under its data processing terms. See its privacy information. Audience statistics are described below. Technical error reports are described separately. Builds through version 1.4.1 do not send them.

The iOS app also uses RevenueCat, with the Apple App Store, to display offers, validate purchases, restore subscriptions and check Premium access. It exchanges a random app identifier, technical app/device information and purchase or subscription records for the same purposes and retention criteria described above. Apple handles payment details; Diaspeak does not receive your card number. Learning answers, your chosen name and avatar remain on your device. The app does not request advertising-tracking permission. See Apple’s privacy policy for its store services. TestFlight testing may also provide Apple and the developer with test feedback and technical information under Apple’s TestFlight terms.

In versions with local guests, learning starts without creating a Supabase account: XP, streak and course progress remain on the phone until you choose Google or Apple. Earlier versions, including 1.3.6, created an anonymous account and synced XP, streak and last validated day. The update keeps the existing guest save on the phone and preserves its purchase identity. After this local migration succeeds, the app automatically requests removal of the old anonymous server account. Cleanup uses the former session in secure storage, with limited retries; learning and optional sign-in remain available if cleanup cannot finish.

Google or Apple sign-in is optional and saves your course progress. From version 1.4.4, a username is optional in Settings → Account. The current local save is attached when you activate saving for a new account; an existing cloud save requires confirmation before opening it separately. A migrated guest may receive a new save-account identifier; the existing purchase identity stays on this phone. Supabase receives the provider identifier, email address (possibly an Apple relay address) and basic profile information included by the provider, such as a name or photo. Diaspeak does not request access to your messages, contacts or files. Email and password sign-in is not offered. From version 1.4.3, after you sign out, the username, avatar colour, sign-in provider and its technical identifier stay on the device so you can find the account again. They are not sent anywhere and follow system backups like local progress. “Remove from this device” erases them along with that account’s local save.

For every account, Supabase stores total XP, streak and last validated day, calculated by the app. Linked accounts also store the chosen username, content version and one furthest completed lesson identifier per language. Signing in again recovers these synced values and marks the preceding lessons completed. Exercise answers, review history, saved words and bonuses are not recovered from this checkpoint. The highest XP total and furthest course position are kept; XP earned separately offline on multiple devices are not added together. Since November 11, 2026, the leaderboard and online cosmetic collection have been retired and their stored records removed. The 1.4.4 app has no leaderboard or friends system. A username is optional and stays within account settings; no member list is published.

Accounts and synchronisation provide the requested service under its contract. Abuse prevention relies on our legitimate interest in securing the service. Access controls, session validation, request limits and technical logs protect accounts. Network requests also expose IP addresses and connection information to infrastructure providers. Only the account owner and authorised service operators access these data for these purposes.

Advertising and privacy choices

The free Android and iOS apps use Google AdMob and its User Messaging Platform (UMP). Rewarded ads are optional and show the reward before you choose to watch; interstitial ads can appear between lessons. Premium disables ads. Lessons and time-based life recovery remain available offline. Advertising and purchases depend on local availability and applicable restrictions.

Diaspeak is intended for a general audience aged 13 and over. Ad requests are not tagged as child-directed or as under the age of consent, unless you state your age as below. Versions up to 1.4.2 ask no age or birth date. From version 1.4.3, the app asks your age only when you create an account: it is compared with the limits below on your device, then neither kept nor sent, and no birth date is requested. If you state you are under 13, you cannot create an account but can keep learning without one. This phone then keeps only that indication: ads are requested as child-directed with content rated G, and audience statistics and technical error reports are off. If you state you are 13 to 15, this phone keeps only that indication: ads are requested with teen treatment and as under the age of consent, so they are not personalized on the basis of your consent. Whether an ad is personalized depends on the consent you give or refuse in Google’s User Messaging Platform (UMP) message. Diaspeak does not request any ad before that consent can be collected. You can change this choice later in the app settings. Diaspeak does not request iOS tracking authorization (App Tracking Transparency). Diaspeak does not send your name, avatar or learning answers to AdMob. Advertising services can process network/IP information, technical app/device information, ad interactions and diagnostics; identifiers depend on the SDK settings, the device and your choice. UMP processes privacy choices.

Use Privacy choices in the app settings to change your UMP choice when that option is shown, or contact [email protected] to exercise your rights. Refusing optional uses does not block offline learning or time-based life recovery. Choosing to watch an ad is separate from consent to data uses. Google’s privacy policy describes its processing, retention, transfers and rights. Processing may occur outside the European Economic Area. Internal test builds use demonstration ads and separate test purchase identifiers.

When you contact us

We receive the email address, name, message, and any attachments you choose to send. We use them to answer your request and resolve the issue, based on our legitimate interest in providing assistance; a request about a contract may also be processed to perform that contract or meet a legal obligation.

Mail to [email protected] is routed by Cloudflare Email Routing to a mailbox hosted by Google (Gmail). Only the operator and the service providers needed to handle the request have access for that purpose. We do not sell your information or use support messages for advertising. Please avoid sending passwords, payment details, or unrelated sensitive information.

If a complaint is referred to a mediator or requires legal advice, only information necessary for the case is shared with the relevant parties to handle it or defend a right.

Retention periods

Local data remain until you erase them or the app data, subject to system backups. Linked account data remain until account deletion is requested. Legacy anonymous account data are automatically deleted after successful local migration and authenticated cleanup. If cleanup cannot finish, for example without a valid session, records may remain until the existing purge after 12 months without use. The new version does not automatically recreate these accounts or sync the remaining local progress. Cleanup compares the counters saved on the phone with those on the server and retains any newer server copy. Uninstalling does not delete existing server records. For deletion requested in Settings, a random receipt fingerprint and completion date remain without an account identifier or email, so interrupted deletion can be confirmed.

Ordinary support requests are kept while being handled and for no more than 12 months after closure. Attachments not needed for the response are deleted sooner. A limited part of a record may be kept separately where needed to meet a legal obligation or defend a right, for the period applicable to that record or proceeding. Any accounting records held follow their own statutory retention period; this website takes no payments.

Hosting logs and providers’ technical copies follow the periods applicable to their services. We do not create permanent exports of these logs to measure your browsing. Removing an email from the active mailbox may be followed by a technical delay before the provider’s copies are purged.

Providers and international processing

Cloudflare and Google may process information outside the European Economic Area, including in the United States. Their published terms describe applicable transfer arrangements and safeguards; these may include adequacy decisions and standard contractual clauses, depending on the service. Consult Cloudflare’s data processing terms and Google’s privacy policy. Contact us for details about your request.

Supabase processes account and progress data on our behalf. Our database and authentication service are hosted in Ireland, and synchronization/deletion requests are configured for that region. This does not guarantee that all support, technical logs or service operations stay in the European Economic Area. See the Supabase data processing terms and regional hosting and transfer information. Google and Apple also process sign-in under their own privacy policies.

Your choices and rights

Subject to legal conditions, you may request access, correction, erasure, restriction, portability, or object to certain processing. Consent may be withdrawn for future processing as easily as it was given. Write to [email protected] describing your request; do not send an identity document unless asked.

We normally respond within one month of receipt. If a lawful extension is needed because of complexity or the number of requests, we inform you within that first month and explain why. Additional identity information is requested only where reasonably in doubt and in a proportionate way.

In Settings → Manage account, use Export my data to create a JSON copy of local learning data and available account/cloud data, or Delete my account to erase the account and its synchronized progress. Export before deleting if you want a copy. Linked accounts require confirmation with the same Google or Apple identity; Apple access is revoked during deletion. A completed deletion also erases that profile on the device used. Copies on other devices, operating-system backups and exports you shared must be managed separately. Provider logs and technical backup copies may require their own retention/purge period.

Deleting the Diaspeak account does not cancel a store subscription or automatically erase purchase records held by RevenueCat, Apple or Google. Manage the subscription in the store and contact [email protected] for purchase-record requests. If you cannot access the app, you can also request account deletion at this address; provide the sign-in email or account identifier if available, never a password. We verify ownership proportionately. You may complain to the CNIL or your local authority without contacting us first.

Request deletion of your Diaspeak account and its data, even without the app.

Minors and automated decisions

This website requests no birth date and offers no purchases. Support messages from minors receive the same attention to data minimization; a legal representative may contact us to exercise their rights where applicable.

Reviews are organized locally from your learning progress. Diaspeak makes no automated decisions with legal or similarly significant effects and does not infer your age. Diaspeak is intended for a general audience aged 13 and over, and from version 1.4.3 creating an account requires being 13 or older. A parent can ask for the account to be deleted at [email protected]. Where local law requires it, minors need their legal representative’s authorization to use the service or make purchases.

Audience statistics

From version 1.4.1, Diaspeak sends usage statistics to understand how the app is used and improve it, for the publisher only. They are enabled by default, without a banner. You can turn this off at any time in Settings → Privacy & legal. An earlier refusal stays off. This setting does not affect access to learning, progress saving or Premium.

Version 1.4.0 used anonymous aggregate counters without an installation identifier. Version 1.3.7 builds using the earlier settings require express activation. Versions through 1.3.6 used default-on counters with an option to turn them off. Some earlier builds also counted ad interactions and Premium checkout.

The app sends individual events: app opens, onboarding start, steps and completion, lessons started, completed or left, the first completed lesson, completed reviews, views of the Premium screen, taps on its subscribe button, purchase attempts, trials the store confirms, completed purchases, purchases that do not finish, reminder choices, ad load failures and level test results. Each event carries only predefined categories where applicable: onboarding step, lesson type, exit stage, Premium screen placement, offer period (monthly or annual), a generic purchase outcome (cancelled, unavailable, pending or failed), ad format with a generic failure reason, reminder choice, or the level reached in the level test (A1, A2 or B1) and whether it was finished or stopped, plus the platform, app version, environment and event format. A trial is counted only when the store confirms one for that purchase; its length is not sent. From version 1.4.3, a separate event also carries your answers to the closed onboarding questions (motivations, starting point, where you chose to start and how you heard about Diaspeak). It uses a random one-time identifier that is not your installation identifier, and only the day, so it is not linked to your other events; we only count these answers. From version 1.4.4, only the starting level and choice of starting activity are sent; motivations and discovery source are no longer asked. No exercise answers, free text, username, course, interface language, content version, Premium status, price, currency, product identifier, receipt, store account or email are sent. These events are not linked to RevenueCat, AdMob or your account. Ad performance, campaign attribution and experiment cohorts are not measured.

These events are linked to a random installation identifier generated by the app and stored only on your device. It is distinct from any account: it is never linked to your Diaspeak or Supabase account, email address, name, advertising identifier (IDFA or Google advertising ID), AdMob or RevenueCat, and it is never shared with them. It is excluded from device backups. It is replaced after 13 months at most, without extension when you use the app, and deleted when you turn statistics off. The app uses no PostHog SDK, automatic event capture, session recording, person profiles or location enrichment, and no advertising profile is built. We only read aggregate dashboards.

This audience measurement relies on our legitimate interest in measuring and improving the app, within the French exemption for audience-measurement trackers (Article 82 of the French Data Protection Act) under its conditions: use for the publisher only, anonymous statistics, no tracking across apps or sites and no combining with other processing. You can object at any time with the setting above. Events wait in the app’s temporary memory for a send attempt after about 30 seconds or when the app enters the background; there is no analytics queue saved on your device and no automatic retry.

PostHog processes these events on our behalf in the European Union and only to produce these statistics. They are kept for 12 months, the retention PostHog enforces on its free plan; the French exemption allows a maximum of 25 months. The app replaces the event’s IP field with a fixed placeholder and disables location enrichment, and the PostHog project is set to discard client IP data, so your IP address is not stored with events. Network transport still exposes an IP address to the service infrastructure. European hosting does not exclude every international access or transfer by service providers; see the PostHog data processing terms and privacy information.

We cannot find your events from your name, email or account, because the identifier is not linked to them. Turning statistics off deletes the identifier on your device and stops further sends; it cannot recall events already received. To ask about this processing or exercise your rights, contact [email protected]. This measurement concerns the app only; the website does not send these statistics.

Technical error reports

Starting with version 1.4.1, build 139, signed Android and iOS builds send automatic technical error reports to Sentry, so that Diaspeak can detect and fix malfunctions. Earlier builds, including older 1.4.1 test builds, send none. The reports use the Sentry Flutter SDK, version 10.3.0, and are on only in builds compiled with the public DSN of the Sentry project diaspeak and with SENTRY_ERRORS.

The lawful basis is Diaspeak’s legitimate interest in keeping the app working (Article 6(1)(f) GDPR). The French audience-measurement exemption is not used for these reports. The Audience statistics switch does not control them, and there is no switch for them in Settings. You can object by writing to the address below. Because a report has no user identifier, Diaspeak cannot exclude one device from sending; to stop sending, you can stop using a build that sends reports.

The app’s Dart filter transmits to Sentry only: the technical exception type; from version 1.4.2, build 140, for a failed Apple or Google sign-in, the provider’s fixed error code, and for a frozen screen, a duration band (over 5, 15 or 30 seconds); a fixed stage name for startup, the Flutter framework, a platform error, an isolate, a local progress read or write, a frozen screen, the abnormal end of the previous session, account open, sign-in, cloud sync, purchase or restore, speech, advertising startup, or notification scheduling; stack frames limited to package paths and line numbers, or, for an obfuscated frame, a hexadecimal instruction address; for an obfuscated build, the Dart snapshot debug identifier, its image address, and the code file name libapp.so or App.Framework/App; the installed application id, version and build number; the build environment; a random event identifier and technical trace identifier generated by the SDK; the Dart and Flutter runtime versions; and, when present, device family, brand, manufacturer, model, architecture, simulator flag and orientation, operating-system name and version, light or dark theme and whether the device is rooted, and app name, package identifier, version, build type and whether the app was in the foreground. The raw exception message, lesson answers, progress contents, email, account, audience identifier, breadcrumbs, screenshots, view hierarchy, sessions, performance traces, logs and metrics are not included by this filter.

Native crash reports, Android ANR reports, iOS hang reports and watchdog termination reports are not sent, because they do not pass through the Dart filter. Filtered events can be kept on the device in a cache of at most 30 envelopes and retried.

Sentry (Functional Software, Inc.) acts as a processor under its data processing addendum. The organization’s data storage region is the European Union and events are received at ingest.de.sentry.io. Sentry’s documentation says those events are stored in Frankfurt, while account, organization, project and token metadata can remain in the United States; event hosting in Germany does not mean that all processing stays in the European Union. Transfers to the United States rely on the Data Privacy Framework and, failing that, on standard contractual clauses, as that addendum provides. On the current Sentry plan, Sentry’s documentation gives a 30-day retention for error events.

The event has no IP-address field, but the HTTPS connection exposes an IP address to the receiving infrastructure. The project is set not to store that address and to remove the location Sentry derives from it. The absence of an email address does not make the event anonymous. Sentry’s documentation says the mobile SDK can generate a random per-installation identifier for session statistics; this build turns session tracking off and removes the user from the event. No advertising identifier is requested for this diagnostic.

From version 1.4.3, no report is sent from a phone where the person stated being under 13. To ask about this processing or exercise your rights, contact [email protected]. Because the event has no user identifier, Diaspeak cannot find a report from your name or email.

Reminders and device permissions

Learning reminders are optional. The app asks for notification permission when you choose to enable them. You can refuse or turn them off in the app or device settings and continue learning. Reminders are scheduled on your device; Diaspeak does not send a push-notification token to a server.

The app does not request access to your contacts, camera, microphone, photo library or precise location. Google and Apple sign-in request identity information only. Installed speech voices on the device read the learning text first, and that text stays on the device. Diaspeak does not record your voice and does not keep any audio. If no installed voice can speak the language and the phone is online, the phone’s own speech engine may use a network voice. On Android this can be the Google or Samsung engine. The word or phrase is then sent to that engine’s provider, not to Diaspeak. Offline, only a voice already installed on the device can speak.

Updates

This page will be revised when the services or data processing change. The date above identifies this version. The same notice is available in English, French, and Spanish.