Privacy Policy

5 November 2026

Privacy Policy

Last updated: 5 November 2026

This Privacy Policy explains how MTech & IT (“we”, “us”, or “our”) collects, uses, and protects personal data when you use Workword — the mobile apps, the web app at https://app.workword.eu and the website at https://workword.eu (together, the “Service”). It also explains how we process business contact details of organisations we approach about Workword (Section 3.8c).

We process personal data in accordance with the EU General Data Protection Regulation (GDPR) and applicable Dutch privacy law.


1. Who we are (data controller)

Controller MTech & IT
Address Wismar 34, 8052 CD Hattem, The Netherlands
Chamber of Commerce (KvK) 42050195
VAT (btw-id) NL005456429B14
Email contact@workword.eu
Websites https://workword.eu · https://mtech-it.nl

For privacy requests (access, deletion, objection, questions), contact us at contact@workword.eu.


2. What Workword is

Workword is a language-learning product for foreign and migrant workers. It teaches job-specific Dutch, English, German, French, Italian, Spanish, and Portuguese through workplace vocabulary, phrases, listening practice, and safety-related language for sectors such as welding, hospitality, butchery, and related tracks.

The Service may be used by individual learners and, where an employer has an account, in connection with an employer invite or company link.


3. Personal data we process

Depending on how you use the Service, we may process the following categories of data.

3.1 Account and profile

  • Email address
  • Whether your email address is verified (email_verified on your profile), mirrored from Firebase Authentication after you confirm the link we send (or when your sign-in provider already marks the address as verified)
  • Name (name) — your full name for regular accounts, or the company name for company accounts (also mirrored to display_name for compatibility)
  • Username (username) — a unique public handle without spaces (lowercase letters, numbers, underscore), chosen at email/password sign-up or derived from the email local-part for Google/Apple sign-in
  • Timestamps of the last name and username change (name_changed_at, username_changed_at) so we can enforce a maximum of one change per week for each field after the first set
  • Profile photo (if you upload one)
  • Authentication identifiers (for example Firebase Auth user ID)
  • Sign-in method metadata when you use email/password, Google Sign-In (available in the mobile apps and on the website, including mobile browsers via Google OAuth redirect), or Sign in with Apple (iOS app)
  • A one-time age eligibility confirmation (16+) stored as a timestamp (age_confirmed_at) on your user profile — we do not collect your date of birth
  • Account type (user_type: regular or company) and, when you request a switch in Settings, a pending confirmation flag and a 48-hour provisional window (account_type_provisional_until, account_type_previous) so you can revert in the app. We email you signed confirmation links (Yes/No) to your account email via our email provider (Section 5) before the switch takes effect
  • When you finish onboarding, we may send a one-time welcome email to your account email (via our email provider (Section 5)), chosen for your account type — individual learner, learner linked to an employer, or company/employer — and delivered in your My language setting where available

3.2 Learning and preferences

  • Selected target and source languages
  • Selected sector / learning path
  • Optional default job under that sector (default_job_id) when you choose a role or an employer invite assigns one; company / multi-sector accounts may also store per-sector jobs (default_job_ids)
  • Optional Start with the alphabet preference (script_bridge_enabled) when your My Language does not use the Latin alphabet — alphabet, first words, and starter grammar alongside sector Basics
  • Lesson and module progress, completion status, streaks, experience points (XP), gamification level, and related learning history
  • Review Mistakes — when you answer incorrectly in a learning-path lesson or exit quiz, we may store a per-item miss count and last-missed time (word_mistakes / phrase_mistakes) on your device and in your sector learning snapshot under user_learning_history, together with spaced-repetition (SRS) card state, so you can rehearse weak items from the Practice tab. Successful practice reviews can clear those mistake entries
  • Listening practice audio — when you tap listen on a lesson word or phrase while online and signed in, the spoken prompt text is sent to our Cloud Functions and processed by ElevenLabs (default cloud voice) or, if you choose Online voice (Cartesia) under Settings → Lesson audio voice, by Cartesia, to synthesize speech; a short audio clip may be cached on your device. We log the number of characters synthesized with your user ID to track provider costs. You can instead choose on-device voices (the system text-to-speech engine, or on-device neural voices where offered); these do not send prompt text to us or to a speech provider. If cloud synthesis is unavailable (for example offline), the app falls back to on-device text-to-speech
  • Hands-free listening exercises — on the Exercises tab, Listening: words & phrases and Listen & answer play learned vocabulary with on-device or cloud text-to-speech. On mobile, an ongoing media-style notification lets you play, pause, or stop while the screen is off. Listen & answer also uses your device’s or browser’s speech-recognition service (microphone) to grade your spoken translation. Depending on your device and settings, that service (for example Google on Android and in Chrome, or Apple on iOS) may process the audio on its own servers under its own terms. Workword receives only the recognised text on your device, uses it to grade your answer, and does not send or store your voice recordings.
  • Official exam prep practice progress — A1 Official Exam Prep (for example Basisexamen inburgering or Cambridge A2 Key–style modules) and A2 Exam Prep practice packs after you complete A2 on a sector path — including module completion and mock exam attempt scores stored on your device and optionally synced to your account so you can continue across devices
  • Sector completion certificates stored on your account under user_certificates (sector, optional job role badge, certificate kind, display name, issue time) when you earn a downloadable completion certificate — including full sector-track certificates, words & phrases milestone certificates after passing the sector words and phrases exam, and Workword A2 certificates after finishing the A2 learning path (A2.0–A2+) and A2 Exam Prep practice when that prep is offered for your target language
  • Learning progress may also record whether you passed the sector words and phrases exam (words_phrases_exam_passed) and related certificate timestamps (legacy / sync support)
  • Sector completion certificate issue timestamps on learning progress (legacy / sync support)
  • Onboarding and placement-related choices
  • Lesson reminder and language settings stored on your device and/or synced to your account
  • Sounds — the on/off choice for answer and lesson-complete sound effects, stored on your device under your user id and, once you set it, on your profile as sounds_enabled so it follows your account. Until you choose, company-linked learners have these sounds off and other accounts have them on. Linked employers cannot see this field
  • Challenge results — when you complete, decline, or cancel solo challenges (shown in the app as Goals & Challenges), we store a history entry under user_challenges_history (challenge id, mode, outcome, XP earned, optional target-date metadata, and your default sector when known). After you set a personal target date, solo challenges may auto-complete from your learning progress (for example words learned, phrases completed, lessons finished, streak days, safety-critical vocabulary, or simulated conversations) measured against that challenge’s threshold in your default sector (and, for safety challenges, the safety-critical overlay for that sector). Optional solo target goals under user_solo_challenge_goals may store a numeric baseline snapshot of those counts when you start the challenge (not a full list of word or phrase IDs) so only progress after you set the target counts, and may include an optional recurrence setting (interval unit of day, week, or month and an amount) so a completed goal can start the next period with a new deadline and baseline instead of being cleared.
  • Workplace exercise sessions — when you invite colleagues to or join a sector exercise with colleagues (async same-set drills such as vocab battle, safety call-out, phrase check, toolbox talk, handover race, listen challenge, picture call-out, or type-off), we store an exercise_sessions document with company link, host, invited/participant uids, sector, exercise kind, start conditions (start_mode, optional scheduled_start_at, min_accept_count), play duration (duration_ms, default eight hours), activation and play-window timestamps (started_at, play_ends_at), invite deadline (expires_at; for accept-count starts this is ten hours after creation), invite-reminder scheduling fields (invite_reminder_at, invite_reminder_sent), pre-generated question prompts/options, your submitted scores and elapsed time, and ranked results among participants. Correct-answer keys are stored in a server-only secrets subcollection. Sessions stay pending until start conditions are met, then become active for the play window. Outstanding invites that hit the deadline without enough accepts are marked expired. Personal drills on the Exercises tab are scored on your device; completing them may award XP via the same XP pipeline as other learning actions. Colleague exercise scores and answers are not shared with the employer company account.
  • Streak Buddy pairs — when you send or accept a Streak Buddy request from the Employer screen, we store a streak_buddies document with company link, member uids, requester/recipient, status (pending, active, declined, ended, or expired), shared streak counters (shared_streak, highest_shared_streak), last mutual practice date, per-member last practice dates in each member’s timezone, and timestamps (including pending invite expiry). Shared streak counters advance only when both buddies complete qualifying practice on their own local calendar day. Personal streak counters on your profile remain separate. Streak Buddy pair data is visible to the two members only; the employer company account cannot read pair documents or shared streak numbers.
  • Custom flashcards — when you create decks and cards in Flashcards (Custom) on the Exercises tab, we store deck names, prompt/answer text, sector id, deck id, and timestamps under user_custom_flashcards (also cached on-device). These decks and cards are only for your account and are not shared with employers or colleagues.
  • Flashcard exercise history — when you complete Flashcards or Flashcards (Custom) personal drills, we store your session score, timing, sector, languages, optional deck id, and per-card self-grades (prompt, answer, knew/didn't know) under user_flashcard_exercise_history. This history is private to your account and is not shared with employers or colleagues.

Mock exam results are practice scores only. They are kept private to your account by default and are not shared with employers unless we clearly ask for a separate opt-in in the future.

3.3 Device and notifications

  • Push notification tokens (for example FCM device tokens) when notifications are enabled (for example lesson reminders, flashcard review reminders, workplace exercise invites, invite expiry reminders (about three hours before an unanswered invite closes), workplace exercise started alerts from linked colleagues, Streak Buddy requests, Streak Buddy accept/decline/end notices, Streak Buddy practice nudges, company announcements from your linked employer, and for company accounts notices such as colleague reports and employee seat opened when a linked learner reaches A1). Tokens are stored under your user document’s private push settings (users/{uid}/private/push) so linked employers cannot read them from your profile document.
  • Local preferences stored on your device (for example via SharedPreferences) to support offline use and settings, including appearance choices such as light/dark mode and color theme, notification toggles (lesson reminders and optional flashcard review reminders), flashcard reviewing options (learning steps and intervals), and optional solo challenge target dates (plus baseline progress counts for auto-complete and optional recurrence interval unit/amount) you set on the home screen
  • An optional encrypted offline lesson pack you download from the learning path screen: illustration files for your sector track (Basics and A1 levels, plus any overlay paths you selected) and, when you are linked to an employer, a local snapshot of that employer’s basic-words override and custom words. Media is stored encrypted in the app’s private storage; the encryption key is kept in the platform secure store. You can remove the pack from the same screen
  • Optional offline flashcard packs you download from Flashcards or Flashcards (Custom): card text, spaced-repetition state for those cards, and any images or audio attached to your custom notes. Packs are stored in the app’s private storage on the device; you can remove them from the same download screen
  • Images or audio you attach to custom flashcards (for example image occlusion or audio-to-text notes), stored in Firebase Storage under your account
  • Completion certificate PDFs you generate and share from your device (you control where you send them)
  • An encrypted local screen cache on mobile devices (iOS/Android): snapshots of data shown on Home (including challenges and achievements), Profile, Employees, Employer, Employee Results, Learning Paths Overview (admin engagement metrics), User management in the Admin Panel (first page of the user list for operators), and Achievements. Payloads are sealed with AES-GCM; the encryption key is kept in the platform secure store. Screens paint from this cache immediately, then refresh from our servers in the background while you use the app (not while the app is closed). The cache is cleared when you sign out
  • An encrypted in-app Notifications inbox stored in Firestore collection user_notifications (default database): achievement unlock notices, company announcement notices, workplace exercise invite notices, and Streak Buddy request notices. Each notification body is sealed with AES-GCM on your device before sync; the encryption key is kept in the platform secure store. Operators and other accounts cannot read the plaintext. On mobile, a local warm cache of the same inbox may also be kept for faster display and is cleared when you sign out
  • For company accounts, that same Notifications screen may also show a server-authored row when a linked employee changes their workplace sector and job. Cloud Functions write that row. We also email the company account (in the recipient’s My language where available) using the Employee Job & sector change template
  • For operator (admin) accounts, the same Notifications screen may also show server-authored operational alerts (plaintext rows under user_notifications): new in-lesson content reports (reports), new contact form submissions (contact_messages), new support report submissions (support_reports), new user sign-ups, successful blog post generation awaiting approval, blog generation failures, and successful blog social shares after an approved post is set visible. These alerts are written by Cloud Functions to each eligible admin’s inbox and are gated by the same Admin Notifications preference toggles used for push
  • Employer or company association when you redeem an invite code or open an invite link (for example https://app.workword.eu/invite/...)
  • An employer may enter an employee email address in the app so Workword can send that person an invite email (via our email provider (Section 5)) containing a one-time invite code and invite link. We may store that email on the invite record (invite_codes) for delivery and audit; it is not used to restrict who may redeem the code
  • Company REST API (invites): entitled company accounts may create API keys in Employees → Company settings. We store key metadata and a one-way hash of each secret in Firestore (company_api_keys) — not the raw key after creation — plus labels, creation/revocation timestamps, and last-used time. Using a key to call POST /api/v1/invites creates the same one-time invite_codes records (and optional invite email) as the in-app invite flow. API usage is rate-limited per company account
  • When you link to a company (for example by redeeming an invite), we may email a confirmation to your account email and to the company account email. When either party ends the company link, we may email both sides a unlink confirmation. These transactional notices use your My language setting where available
  • Either party may end the company link without deleting the learner account: a linked employee may unlink from Settings, and an employer may unlink an employee from the Employees screen. Unlinking clears the company association and employer-assigned learning goals; learning progress stays on the learner’s account
  • Sector or content assignment linked to that employer relationship. A linked employee may change their own workplace sector and job, but only among the sectors and jobs that company offers. The employer may also assign or later change that sector and job. Changing sector clears any employer-assigned learning goal for the previous sector; changing only the job keeps the current learning goal. The company account receives an in-app notification and an email when the employee makes this change
  • Employer-assigned learning goals (a target learning level for your current sector), including a default goal that an employer may configure so newly linked employees receive it automatically on invite redeem
  • Workplace vocabulary that an employer account adds or customizes for the basic words learning level of a sector (for example Dutch and English lemmas), which is then shown to linked employees in that company’s learning path
  • Progress information made available to an employer in a privacy-bounded way (see Section 6)
  • Employer display name, profile photo, and company account email shown to linked employees on Home and the Employer screen (see Section 6)
  • Display name and default sector id shared with linked coworkers via the in-app colleague directory when you are linked to the same employer (peer email is not shared through that directory — see Section 6)
  • Company announcements — when your linked employer posts an announcement in the Employees screen, we store the title, message, audience (all linked employees or selected employees), recipient list, and timestamps in company_announcements. Linked employees who are recipients may receive a push notification and can open the announcement in the app; employers can create, edit, and delete announcements for their company
  • Company onboarding cards (welcome pack) — a company account may store cards for its linked employees in company_onboarding_cards/{companyUid}/onboarding_cards. Each card can include a title, message, display order, tagged vocabulary term ids, an optional video link, and an optional image. Images are stored in Firebase Storage at company-onboarding/{companyUid}/ (JPEG, PNG, or WebP, maximum 5 MB). Only that company account can upload or replace those images. The company and its linked employees can read cards that have not been deleted. Creating or changing cards is limited to company or admin accounts with a paid or trial subscription
  • A pending invite code may be stored locally on your device (for example via SharedPreferences) until you sign in or sign up and the invite is applied during onboarding

3.5 Legacy messaging data (product removed)

In-app Messaging (direct chats, learning groups, company employee-group chats, Study Buddy, group challenges, and chat voice) is no longer offered in Workword. We no longer process new chat content for that product.

If you used Messaging before it was removed, residual encrypted chat metadata or message ciphertext may still exist in our systems (user_chats, user_chat_messages, and related Storage paths) until operators purge it. On account deletion, we remove you from legacy user_chats membership and delete your chat_public_key. Historical ciphertext may remain until purged and is not usable without the corresponding keys.

3.6 Technical and security data

  • Data necessary to operate authentication, sync progress, and store files securely through our infrastructure providers
  • API usage counters used to enforce per-account rate limits (for example requests per minute, day, week, and month)
  • Firebase App Check attestation signals (Play Integrity on Android, App Attest / DeviceCheck on iOS, reCAPTCHA on the web) so our servers only accept requests from genuine copies of the app. These checks use device or browser integrity signals, not your learning data
  • Security monitoring signals when automated abuse checks trigger (for example repeated failed invite redemptions, rate-limit breaches, or repeated denied privileged actions). Operators with an admin Workword account may receive a push notification and/or email that includes the affected account’s name (display name), username (when set), account email (when available), Firebase Auth user ID, the signal type, time, and limited technical context so we can investigate abuse. These alerts are sent only to admin operators, not to employers or other learners.
  • New Support contact form submissions. Operators with an admin Workword account may receive a device push notification, and an email is sent to contact@workword.eu with the submission details (sender email, user ID when signed in, subject, message, and related metadata) so we can respond. These Support operational notices are not sent to employers or other learners.
  • New support report submissions. Operators with an admin Workword account who have enabled Support report alerts may receive a device push notification and/or an email to their admin account email address with the report details (sender email, user ID when signed in, category, message, and related metadata). A copy is also sent to contact@workword.eu for triage when the global Support report email toggle is on. These notices are not sent to employers or other learners.
  • New user / colleague reports about other accounts (from the colleague directory / Employer screen). When a colleague report is sent to the company, the linked company account may receive a push notification and an email to that company’s account email address with report details (reporter and reported identifiers, reason, message, and related metadata) so the employer can follow up. Workword operators may also review these reports where needed for safety.

3.7 Crash reports, diagnostics and product analytics

When you use the Workword mobile apps (Android or iOS), we may process diagnostic data to detect and fix crashes and stability issues, including:

  • Crash and non-fatal error reports (for example stack traces and error messages)
  • Device and app context (for example device model, OS version, app version, and build)
  • Limited breadcrumb / usage context leading up to a crash (via Google Analytics integrated with Crashlytics), such as screen or event names
  • Product / acquisition events via Firebase Analytics (for example sign_up when a new account is created, company_sign_up when a company account finishes employer onboarding, onboarding and lesson progress, and screen views). Selected events are imported into Google Ads for conversion reporting

Analytics choice. Firebase Analytics in the mobile apps and in the web app at https://app.workword.eu runs only after you agree in the app’s privacy choice, which we show when you first open the app. You can change this at any time in Settings → Privacy → Analytics. If you decline, we do not collect Firebase Analytics events from your device or set Analytics cookies in the web app. Crash reporting (Crashlytics) is not affected by this choice.

Advertising identifiers. On Android, Firebase Analytics is configured not to collect the Android Advertising ID (google_analytics_adid_collection_enabled=false). On iOS, the advertising identifier (IDFA) is only available to Google’s SDKs if you allow tracking in Apple’s tracking prompt (see Section 3.7a). Separately, unpaid regular accounts in the iOS and Android apps see Google AdMob ads, which may use advertising identifiers for personalized ads only after the consent described in Section 3.7a. Subscribers, employer-covered learners, admin, and company accounts do not see these ads.

Crashlytics applies to the mobile apps. In the web app at https://app.workword.eu, unexpected errors may be stored in Firestore collection client_error_reports (error message, optional stack snippet, signed-in user ID, and platform) so we can fix web stability issues. These web reports are create-only for the signed-in user and are not readable by other clients.

3.7a In-app advertising (free regular accounts)

When you use Workword without an active personal or employer-covered subscription as a regular learner, we show ads to support free access, including:

  • Banner ads on Home (above Profile) and a sticky banner on the Learning path screen
  • Interstitial / lesson-finish ads when finishing a lesson (progress is saved after the ad)
  • Rewarded / lesson-start ads before starting additional lessons after the first free start each local calendar day (mobile rewarded unit; web timed AdSense modal)

Who sees ads. Ads apply only to unpaid regular accounts (including linked employees when the employer does not provide paid coverage). Subscribers, employer-covered linked learners, company accounts, and admin operators do not see these ads. You can remove ads by starting a personal subscription (or receiving employer-covered access).

Mobile (iOS / Android). Ad serving uses Google AdMob via the Google Mobile Ads SDK. Where required (including the EEA and UK), we request advertising consent through Google’s User Messaging Platform (UMP) before personalized ads. The consent form is configured and published in AdMob → Privacy & messaging (GDPR) for our Android and iOS apps; the app loads that form when Google indicates it is required for your region. On iOS, Apple’s App Tracking Transparency prompt is shown as part of Google’s consent flow (UMP / Google Mobile Ads SDK) when Google needs the advertising identifier (IDFA); Workword declares the purpose text Apple requires for that prompt and does not call Apple’s ATT API itself. Google can use the IDFA only if you tap Allow. If you decline personalized ads or tracking, we still show non-personalized ads, which use only limited data (for example for frequency capping, fraud prevention and aggregated reporting).

Data Google may process for AdMob (subject to your choices and Google’s terms) can include: device advertising identifiers (for example Android Advertising ID / IDFA), IP address and approximate location derived from it, device and app technical data, ad request and interaction events (impressions, clicks, rewarded completions), and consent / privacy-signal status. Workword does not sell your account email to advertisers for these in-app ads. AdMob display ads are separate from marketing-site Google Ads measurement on https://workword.eu (Section 11) and from Firebase Analytics product events.

Rewarded ad server-side verification (SSV). For rewarded ads (extra lesson starts) in the mobile apps, Google may send a signed HTTPS callback to Workword’s servers when a rewarded view completes. When you load a rewarded ad while signed in, the app passes your Workword account ID (Firebase user ID) to Google so it can be returned in that callback, together with ad unit and reward metadata and a transaction id. We verify the signature and store a verified reward receipt in Firestore (collection admob_rewarded_ssv) for fraud prevention and integrity checks, and delete it after 90 days (Section 7). Unlocking the next lesson still happens on your device from the standard client reward callback; SSV does not delay that unlock. The web app does not use AdMob SSV.

Web app (app.workword.eu). Free regular accounts may see Google AdSense ads after a first-party in-app consent dialog (separate from the marketing-site cookie banner on workword.eu, which does not cover the Flutter web app). After you accept, the web app may load AdSense for:

  • Display banners on Home (above Profile) and a sticky banner on the Learning path screen
  • A timed AdSense display unit in a modal at lesson start (extra lesson starts) and lesson finish — Continue unlocks after the ad is ready and a short dwell; Cancel blocks the action. If the ad script or fill fails within a short timeout, the lesson continues (fail-open), matching mobile interstitial behaviour

AdSense is registered for the root site workword.eu and may serve on the app.workword.eu subdomain. Declining the web ads dialog means we do not load AdSense slots for that choice. Workword does not pass your account email to AdSense for these ads.

Roles. We decide when ads are shown in Workword (for free regular access). Google provides the ad technology (AdMob on mobile, AdSense on the web app) and may act as controller and/or processor for advertising under Google’s ads terms — see Google’s controller terms, processor terms, and advertising information. You can also manage Google ad preferences in My Ad Center where available; that does not replace Workword’s UMP / in-app choices.

Changing or withdrawing consent. On mobile, you can change or withdraw advertising consent in Settings → Privacy → Ad choices, which reopens Google’s consent form. On iOS you can also turn off tracking for Workword in iOS Settings → Privacy & Security → Tracking. On the web app, decline the ads consent dialog when it appears, or clear the site’s stored ads choice / contact contact@workword.eu to ask us how to reset it. Withdrawal does not affect the lawfulness of processing before withdrawal. Subscribing removes in-app ads going forward.

3.8 In-app Support (contact and reports)

When you use the in-app Support screens to contact us or submit a report, we process:

  • The subject and message you enter on the Contact form (stored in Firestore collection contact_messages)
  • The category and message you enter on the Report form (stored in Firestore collection support_reports), such as bug, content problem, account/privacy, or other
  • Your Firebase Auth user ID and account email address (when available) so we can identify and reply to you
  • Optional device/app context on reports (for example app version and platform) to help triage technical issues

Operators with access to the Workword Firebase project may read these submissions to respond to support requests and improve the product.

We do not require you to provide special-category data (for example health data) to use Workword. Please do not submit sensitive personal information in free-text fields unless we expressly ask for it for a defined purpose.

3.8a User / colleague reports

You may report a colleague to your linked employer from the Employer screen. When you do, we process:

  • Your Firebase Auth user ID and account email (reporter)
  • The reported user’s Firebase Auth user ID
  • Report source (for example colleague), reason, optional free-text details, optional shared company_uid, platform, and app version
  • Records stored in Firestore collection user_reports

Colleague reports are directed to the linked company account (push and email as described in Section 3.6). Workword operators may also review reports where needed for safety.

3.8b Employer lead form (earlier app versions)

Earlier versions of the app invited learners on free access to share employer details in exchange for unlocking additional free sector basic-words lessons. Since free regular accounts now have the full curriculum with ads (Section 3.7a), the current app no longer shows this form. Records submitted through it remain in company_leads and are handled as described in Section 3.8c. If you submitted that form, we processed:

  • Company name, city, and contact email you enter
  • The primary official language of the country for the city you select (city_language, ISO 639-1 such as nl or de), derived from that selection — not from free-typed text
  • Your Firebase Auth user ID and a submission timestamp
  • A profile flag that you unlocked the freemium bonus (employer_lead_bonus_unlocked)

To help you pick a real city, the app sent your city search text from your device to Photon (komoot; OpenStreetMap data) and showed matching suggestions. Only the city you selected (plus the derived language code) was stored with the lead; search queries were not stored in Firestore.

These details are stored in Firestore collection company_leads for follow-up about workplace / company subscriptions (Section 3.8c). Submitting the form does not create an employer account link, send an invite to that company, or share your learning progress with the organisation you named. Access is limited to Workword operators (Admin SDK / console); company accounts cannot read company_leads.

3.8c Business and public-sector prospects (outreach emails)

We approach companies and public-sector organisations (for example municipalities and integration or job-coaching organisations) that may benefit from Workword. For this we process business contact details that MTech & IT collects itself through online research of public sources, such as organisation websites:

  • Organisation name, city, country and the official language of that city
  • A work contact email address (often a general or departmental address, sometimes a named contact)
  • Website, a short note on why Workword may fit the organisation, and internal status notes
  • Outreach status: which emails were sent and when, and whether outreach was stopped

These records are stored in Firestore collections company_leads and government_organizations_leads, and are accessible only to Workword operators.

When we approve an organisation for outreach, we send up to four emails over about 14 days (on days 0, 3, 7 and 14) in the organisation’s local language. Each email contains an Unsubscribe link and a link to this Privacy Policy. When you unsubscribe, we store your email address in marketing_email_suppressions so we never email you again, and we stop any active sequence for that address. This marketing opt-out is separate from in-app operational email preferences for signed-in users.

Legal basis: our legitimate interest in offering Workword to organisations (Art. 6(1)(f) GDPR). You can object at any time to this use of your data for direct marketing, without giving a reason, by using the Unsubscribe link or emailing contact@workword.eu; we will then stop (Art. 21(2)–(3) GDPR).

Retention: 12 months after our last contact, unless the organisation becomes a customer; unsubscribed addresses stay on the suppression list so we can honour the opt-out.

3.9 In-lesson content flags and job requests

During progressive sector lessons, you may tap a flag control to report a specific word or phrase. When you do, we process:

  • Identifiers for the flagged item (content_type of word or phrase, content_id, and a short snapshot of the displayed target-language text as content_text)
  • Lesson context (sector, lesson_id, level_id) so we can find and fix the item
  • An optional free-text reason you enter
  • Your Firebase Auth user ID and account email address (when available)
  • Optional device/app context (for example app version and platform)

From the sector details popup (onboarding and settings), you may also request a missing job. When you do, we process:

  • The job name you enter (content_type job_request, stored as job_name / content_text)
  • An optional job description
  • An optional sector you select from the current tracks, or an optional suggested sector name if you choose “Suggest sector”
  • Your Firebase Auth user ID and account email address (when available)
  • Optional device/app context (for example app version and platform)

These in-lesson flags and job requests are stored in the Firestore collection reports (separate from Support form submissions in support_reports). Operators with access to the Workword Firebase project may read them to correct content, improve lessons, and consider new job roles. Please do not include special-category or highly sensitive personal data in free-text fields.

3.10 Subscriptions and billing

When you or your employer subscribe:

  • Individual plans: App Store / Play purchase identifiers and verification data needed to confirm the purchase, plus subscription status and trial/expiry timestamps we store on your profile to gate access
  • Company plans: Stripe customer and subscription identifiers, selected plan / seat limit, and subscription status on the company profile
  • Linked employees do not carry personal billing fields for the employer plan; access follows the company’s entitlement
  • Subscription emails: when a personal or company subscription starts or ends, we may send a transactional confirmation to the account email (and, when a company entitlement starts or ends, to linked employees about employer-covered access). Copy is delivered in the recipient’s My language where available
  • Targeted discounts and offers: operators may create allow-list-only offers (no public promo codes). We store offer metadata and redemption records (discount_offers) so we can grant complimentary access days to listed regular users or apply a Stripe coupon at company Checkout. Only listed account identifiers are associated with an offer

3.11 Website contact and brochure form (workword.eu)

When you use the contact, demo or brochure form on https://workword.eu, we process your name, email address, optional company, role, category, your message, the request type and your language. We send this to contact@workword.eu by email so we can reply; brochure requests receive an automatic email with the brochure. To prevent abuse, we keep your IP address in a short-lived rate-limit record (Firestore collection rate_limit_windows) that is deleted after the limit window expires.

The website and its contact form run on Replit (Replit Autoscale deployment).


Purpose Examples Legal basis (GDPR)
Provide the Service Create account, sync progress, deliver lessons, listening practice (cloud or on-device TTS), offline cache (including optional encrypted offline lesson packs and the encrypted local screen cache on mobile), issue completion certificates Performance of a contract (Art. 6(1)(b))
Subscriptions and billing Process individual App Store / Play purchases and company Stripe subscriptions; store entitlement status and seat limits to gate access; track whether a linked employee currently occupies a company seat (employer_seat_occupied) and when that seat became occupied (employer_seat_occupied_at) so seats can reopen after the words & phrases exam while the link remains; apply operator-targeted discount offers (complimentary access or Stripe Checkout coupons) to allow-listed accounts Performance of a contract (Art. 6(1)(b)); legitimate interests to run promotions (Art. 6(1)(f)); legal obligation for invoicing where applicable (Art. 6(1)(c))
Employer-linked features Apply invite code or invite link; optionally email an invite code/link to an address the employer enters (SMTP); show limited progress to an employer account; store employer-authored workplace vocabulary for linked learners Contract and/or legitimate interests (Art. 6(1)(b)/(f)), balanced against learner rights
Push notifications Lesson reminders and similar product alerts where enabled Consent where required (Art. 6(1)(a)); you can disable notifications in Settings → Notifications and/or device system settings
In-app support Process contact and report submissions so we can reply and fix issues Performance of a contract (Art. 6(1)(b)); legitimate interests to improve the product (Art. 6(1)(f))
User / colleague reports Process colleague reports (user_reports); notify, where applicable, the linked company and operators Performance of a contract (Art. 6(1)(b)); legitimate interests to keep the Service safe and usable (Art. 6(1)(f))
In-lesson content flags and job requests Process flagged words/phrases and missing-job requests (reports) so we can correct lesson content and consider new job roles Performance of a contract (Art. 6(1)(b)); legitimate interests to improve the product (Art. 6(1)(f))
Security and abuse prevention Authenticate users; protect accounts and infrastructure; rate-limit API calls; alert admin operators about suspicious automated activity Legitimate interests (Art. 6(1)(f))
Improve and maintain the product Fix bugs; ensure reliability of learning sync; crash and stability diagnostics via Crashlytics; web error reports (client_error_reports) Legitimate interests (Art. 6(1)(f))
Product and acquisition analytics (apps and web app) Firebase Analytics / GA4 events such as sign_up, company_sign_up, onboarding and lesson progress; selected events imported into Google Ads for conversion reporting Consent (Art. 6(1)(a)); withdraw in Settings → Privacy → Analytics
Transactional emails in your language Send account, invite, link, subscription and welcome emails; machine-translate them into your My language (Section 5) Performance of a contract (Art. 6(1)(b))
Business and public-sector outreach Research public sources, store business contact details, and send up to four outreach emails (Section 3.8c) Legitimate interests (Art. 6(1)(f)); you can object at any time (Art. 21(2))
Website contact and brochure form Reply to your request, send the brochure, prevent abuse with IP rate limits (Section 3.11) Steps at your request before a contract / legitimate interests in replying to enquiries (Art. 6(1)(b)/(f))
Website advertising and measurement (marketing site) Separate analytics and advertising consent choices; Google Analytics and Google Ads measurement (see Section 11) Consent (Art. 6(1)(a)); you can withdraw via the website’s cookie notice
In-app advertising (free regular accounts) Show AdMob ads (iOS/Android) and AdSense ads (web app) to unpaid regular learners — banners, lesson-finish, and lesson-start/rewarded gates; request consent through Google’s UMP (EEA/UK) on mobile, including Apple’s tracking prompt on iOS via UMP, and a first-party ads consent dialog on the web app (see Section 3.7a) Consent for personalized ads / tracking where required (Art. 6(1)(a)); legitimate interests to fund free access with non-personalized ads where permitted (Art. 6(1)(f)); contract performance for the free ads-supported service tier (Art. 6(1)(b)). You can withdraw consent or subscribe to remove ads
Legal compliance Respond to lawful requests; keep required records Legal obligation (Art. 6(1)(c))

Where we rely on legitimate interests, we balance those interests against your rights and expectations as a learner and, where relevant, as an employee.

Do you have to provide your data? You need to provide an email address (or Google / Apple sign-in) and your learning choices to create an account and use the Service; without them we cannot provide it. Everything else (profile photo, support messages, reports, notifications, analytics and advertising consent) is optional. There is no legal obligation to provide data to us.

Automated decisions. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. Automatic features such as challenge auto-completion, exam scoring and rate limits only affect your use of the app and can be reviewed on request.


5. Processors and subprocessors

We use trusted service providers to host and operate parts of the Service. In particular, we use Google Firebase / Google Cloud for:

  • Firebase Authentication — account sign-in (email/password, Google Sign-In, and Sign in with Apple on iOS)
  • Cloud Firestore — profiles, learning history (including sector learning-path lesson progress under the user_learning_history collection on the default database), employer-authored company vocabulary overrides, company announcements (company_announcements), company onboarding cards (company_onboarding_cards), company activity feed (company_activity) for linked coworkers, challenge catalogs (challenges), solo challenge target dates (user_solo_challenge_goals), learner-authored custom flashcards (user_custom_flashcards), flashcard review settings and exercise SRS state (user_flashcard_review_settings, user_exercise_flashcard_srs), flashcard exercise history (user_flashcard_exercise_history), challenge results history (user_challenges_history), workplace exercise sessions (exercise_sessions, including server-only answer secrets), Streak Buddy pairs (streak_buddies), encrypted in-app Notifications inbox (user_notifications, including server-authored admin operational alerts and a company notice when a linked employee changes sector and job), in-app Support contact and report submissions (contact_messages, support_reports), freemium employer leads (company_leads), marketing email opt-outs (marketing_email_suppressions), user/colleague safety reports (user_reports), in-lesson content flags (reports), public product release notes and upcoming updates (release_notes, app_upcoming), the public FAQ catalog (faqs), operator Automations social generate/publish audit records (automations_in_output), targeted discount offers and redemptions (discount_offers), and related app data. Residual legacy chat collections (user_chats, user_chat_messages) may still exist until operators purge them (see Section 3.5)
  • Firebase Storage — profile photos, company onboarding images under company-onboarding/{companyUid}/ (JPEG, PNG, or WebP, up to 5 MB; readable by that company and its linked employees), vocabulary illustration images used in lessons and quizzes (royalty-free stock hosted by us; not user uploads), blog preview images for the in-app blog, and social-post images generated by operators for LinkedIn / Facebook / Instagram publishing (operator-generated; not user uploads). Residual legacy chat voice files under chat-scoped paths may still exist until operators purge them
  • Firebase Cloud Messaging — push notifications
  • Cloud Functions — server-side app logic (including XP awards, account deletion, the lesson listening speech synthesis proxy, email sending and outreach sequences). See “Where your data is processed” below for regions
  • Firebase Hosting — hosts the web app at https://app.workword.eu
  • Firebase App Check — protects our servers from abuse (Play Integrity, App Attest / DeviceCheck, reCAPTCHA)
  • Firebase Crashlytics — crash and non-fatal error reporting for the mobile apps
  • Google Analytics for Firebase — app analytics for product and acquisition measurement (for example the standard sign_up event after a new account is created, and company_sign_up after company onboarding completes), only after your analytics consent (Section 3.7). Crashlytics may also use Analytics breadcrumbs for diagnostics. On Android, Firebase Analytics does not collect the Android Advertising ID. When our Firebase / GA4 property is linked to Google Ads, selected Analytics events (such as sign_up and company_sign_up) may be imported as conversion actions for campaign reporting
  • Google AdMob / Google Mobile Ads — advertising in the iOS and Android apps for unpaid regular accounts (banners, interstitial, rewarded), including Google’s User Messaging Platform (UMP) for GDPR consent messages published in AdMob Privacy & messaging for our apps, and Apple’s App Tracking Transparency prompt on iOS (shown by Google’s consent / ads flow; Workword does not call ATT directly). Paid, employer-covered, company, and admin users do not receive these ads (see Section 3.7a)
  • Google AdSense — advertising in the Flutter web app at https://app.workword.eu for unpaid regular accounts (home and learning-path banners, and a timed display modal for lesson start/finish), only after a first-party in-app ads consent dialog. AdSense is registered for workword.eu and may serve on the app subdomain. The marketing-site cookie banner does not cover these web-app ads (see Section 3.7a)

Marketing measurement (website and app-store ads)

When we run paid acquisition (for example Google Ads Search campaigns to https://workword.eu), we may use:

  • Google Ads — ad delivery, click measurement, and conversion reporting for campaigns we operate
  • Google Play (linked to Google Ads) — install and related app conversion signals for the Android app (com.mtechit.workword) when our Ads account is linked in Play Console. Install attribution linking is separate from AdMob display ads shown to free regular accounts (Section 3.7a)
  • Firebase Analytics / GA4 (app + linked property, including the web app at https://app.workword.eu) — product measurement events such as sign_up, company_sign_up, onboarding and lesson progress, and related screen views, which may be imported into Google Ads when the Firebase/GA4 property is linked, only after your analytics consent. The web app does not load Google Tag Manager; measurement uses the Firebase Analytics SDK only
  • Google tag / Google Analytics 4 on marketing pages (for example /app, /for-employers, /contact) when enabled — page views, campaign parameters (such as UTM / click identifiers), and optional secondary events such as store-button clicks, subject to consent where required (see Section 11)
  • Google Tag Manager (container GTM-PSDRN2HF) on the marketing website at https://workword.eu only after both analytics and advertising consent are accepted — loads tags configured in that container. See Section 11

We also use ElevenLabs and Cartesia as processors for text-to-speech when cloud listening audio is generated for lesson words and phrases (prompt text only; not your microphone recordings or account details). On-device voices do not send that text to either provider.

We use STRATO AG (Berlin, Germany) to send and receive our emails from contact@workword.eu (SMTP/IMAP). STRATO stores our mailbox, including copies of emails we send in the Sent folder.

We use OpenRouter to machine-translate transactional and operational emails into the recipient’s My language. Before translation, links, email addresses, invite codes and the personal values we insert into our email templates (for example names and company names) are replaced with placeholders, so only the template text is sent for translation. Free-text emails typed by operators in the Admin Panel Mailing tool are not automatically masked the same way and may include personal details the operator enters. OpenRouter routes requests to an underlying AI model provider under OpenRouter’s terms; we do not control that provider’s prompt retention. We also use OpenRouter to generate operator marketing copy (Section 6.1) and to translate this Privacy Policy.

We use Replit (Replit, Inc.) to host the marketing website at https://workword.eu and its contact form (Section 3.11). The web app at https://app.workword.eu is hosted on Firebase Hosting.

For the employer lead city field in earlier app versions, the app sent city search queries from your device to Photon (operated by komoot; powered by OpenStreetMap data) so you could select a real city. Photon received the search text you typed; we did not send your account email or user ID to Photon.

We use Activepieces to publish operator-authored marketing posts from the Admin Panel Automations screen to LinkedIn, Facebook Pages, and Instagram (Meta). The webhook payload contains only the generated post text, selected platform names, an optional public image URL, and a Workword website link — not learner profiles, emails, or learning history. LinkedIn and Meta process that content as the destination social networks for those operator posts. Operator generate/publish attempts from that screen are also stored in Firestore collection automations_in_output (prompt/platforms, generated text and optional image URL, Activepieces response or error, and the operator account id) for operational audit — not for learner profiling.

Payment processors

Depending on how you subscribe, we use:

  • Apple (App Store / StoreKit) — individual subscription purchases and renewals on iOS
  • Google (Google Play Billing) — individual subscription purchases and renewals on Android
  • Stripe — company (employer) subscription Checkout, invoices, and the Customer Portal

We receive purchase and entitlement metadata needed to unlock the Service (for example product or price identifiers, subscription status, trial and expiry timestamps, seat limits for company plans, and Stripe customer/subscription identifiers for company accounts). Card numbers are processed by Apple, Google, or Stripe — not stored by Workword.

Where these providers act as processors, they process data on our instructions under a data processing agreement. For Google’s advertising and measurement services (Google Ads, AdMob), Google acts as an independent controller for some purposes under its controller terms and as a processor for others under its processor terms. Apple, Google Play and Stripe act as independent controllers for payment processing.

Marketing website Google Ads / Analytics

On the marketing website at https://workword.eu, advertising measurement sends data to our Google Ads account (AW-17181401897) only with your separate advertising permission. Our Google Analytics property is workword-c1032 (measurement ID G-42N0ETYX3P). The contracting entity for Google Ads and Google Analytics is Google Ireland Limited.

Where your data is processed (international transfers)

Provider What Location Safeguard for transfers outside the EEA
Google (Firebase / Google Cloud) Firestore database EU multi-region (eur3) Not applicable (EU)
Google (Firebase Hosting) Web app delivery Google’s global network EU-U.S. Data Privacy Framework; Standard Contractual Clauses where required
Google (Cloud Functions) Server-side processing EU (europe-west1) Not applicable (EU)
Google (Analytics, Crashlytics, Ads, AdMob, AdSense, Play) Measurement, diagnostics, advertising EU and USA EU-U.S. Data Privacy Framework (see Google’s data transfer frameworks); Standard Contractual Clauses where required
STRATO Email (SMTP/IMAP, mailbox) Germany (EU) Not applicable (EU)
ElevenLabs Cloud text-to-speech USA / EU (provider infrastructure) EU-U.S. Data Privacy Framework and/or Standard Contractual Clauses under ElevenLabs’ data processing terms
Cartesia Cloud text-to-speech USA Standard Contractual Clauses / Cartesia data processing terms
OpenRouter (and model host) Email and policy translation, marketing copy USA (and model-host region) Standard Contractual Clauses under OpenRouter’s terms; model host under OpenRouter’s routing
Replit (Replit, Inc.) Marketing website and contact form hosting USA Standard Contractual Clauses in Replit’s Data Processing Agreement
Activepieces Social-post publishing (no learner data) USA / EU (provider infrastructure) Standard Contractual Clauses / Activepieces data processing terms where personal data is processed
Photon (komoot) City search (earlier app versions) Germany (EU) Not applicable (EU)
Stripe Company subscriptions EU / USA EU-U.S. Data Privacy Framework and Standard Contractual Clauses (Stripe as independent payment controller for card data)
Apple iOS purchases, Sign in with Apple USA / EU (Apple infrastructure) Apple’s own terms (independent controller)

Server regions. Our database and server-side processing (Cloud Functions, including account deletion, speech synthesis and email sending) run in Google Cloud regions in the EU (eur3 and europe-west1). Other Google services in the table above (for example Analytics, Crashlytics, Ads, AdMob, AdSense, Play, and Firebase Hosting’s global edge network) may still process data in the USA under the safeguards listed for those rows. You can ask us for more information about these safeguards at contact@workword.eu.

We may update our list of processors as the Service evolves. Material changes will be reflected in this policy and the “Last updated” date.


6. Employer visibility

If you link your account to an employer (for example via an invite code):

  • Your employer may see information needed to support workplace language training — typically completion and progress status, including whether you passed a sector words and phrases exam, and safety-related module completion where relevant.
  • Your employer may also see company-level aggregate usage and learning trends (for example on their home dashboard and on Employees → Analysis & results), including weekly active learner counts and words/phrases completed. Those charts do not identify individual employees; named progress remains available only in the employer’s employee-results views (including the results section on that same Employees tab).
  • Your employer may add or edit company-specific words used in the basic words learning level for sectors they assign; those words are shown to linked employees as part of the learning path.
  • Your employer may store a welcome pack of onboarding cards (title, message, optional image, optional video link, and tagged vocabulary terms) that you can read while your account is linked to that company. Those cards do not include your learning scores.
  • Linked coworkers at the same employer may see a colleague directory limited to display name (name) and default sector id (and your own entry may appear in that list). Peer email addresses are not shared through this directory. Other profile fields such as username handles, push tokens, and detailed learning history are not shared through this directory.
  • Linked employees may see their employer’s display name, profile photo, and company account email on Home (Profile → Employer) and on the Employer screen, so they can recognise and contact the workplace account they are linked to.
  • Linked coworkers may also see an Employer & colleague updates feed on Home (company_activity) with short summaries such as company announcements, colleagues joining, workplace exercise invites/completions, and lesson or level milestones. Items show display name and an event summary only (not exercise scores, quiz failure detail, or full learning history). Your own activities are hidden from your view of that feed. The employer company account can review the same short activity summaries on Employees → Activity feed (filterable by event type and sort order). Items still exclude exercise scores, quiz failure detail, and full learning history.
  • Linked coworkers may invite you to workplace exercise sessions. Participants can see shared question prompts and each other’s scores/results for that session. The employer company account cannot read those session payloads or scores.
  • Linked coworkers may send or accept Streak Buddy requests from the Employer screen. Streak Buddies can see each other’s shared streak counters and whether each person has practiced on their local calendar day for that pair. Your personal streak remains on your profile. The employer company account cannot read Streak Buddy pair documents or shared streak numbers.
  • When a linked employee reports a colleague, your company account may receive a push notification and an email with the report details (reporter and reported identifiers, reason, message, and related metadata) so you can follow up. These notices are separate from Workword Support and security alerts.
  • When a linked employee passes the words & phrases exam and unlocks the A1 learning path, their company seat opens again. Your company account may receive a push notification and an email so you can invite another learner. The employee stays linked and keeps employer-covered access.
  • When a learner links to or unlinks from your company, your company account may receive a transactional email confirming the join or leave (display name of the employee). The employee may receive a matching confirmation to their account email.
  • We design employer-facing visibility to be privacy-bounded. We avoid exposing detailed performance in ways that could reasonably be used punitively (for example raw quiz failure detail), consistent with our product principles.
  • Exact fields shown to employers and coworkers may change as workplace features develop; we will update this policy when visibility expands.

Your employer is separately responsible for how they use any information they receive through their workplace account, under their own policies and employment obligations.

6.1 Operator / admin access

A small number of operator (admin) accounts, provisioned by MTech & IT, may access user profile fields needed for support and operations — for example account type, company link identifiers, email, name, username, display name, onboarding status, and account activity timestamps — through an in-app Admin Panel. Operators may also view, edit, soft-delete, and record replies on Support contact form and report submissions (contact_messages, support_reports), including status and internal notes. Operators may also view and update user/colleague safety reports (user_reports), including status and internal notes. When a new contact form or colleague report is created, authorised admin devices may receive a push notification, and contact@workword.eu receives an email (via our email provider (Section 5)) with the submission content for triage. When a new support report is created, opted-in admin operators may also receive a push notification and/or an email to their admin account address, and contact@workword.eu may receive a triage copy when the global Support report email toggle is enabled. Operators with Firebase project access may also read in-lesson content flags stored in the reports collection (word/phrase identifiers, lesson context, optional reason, and submitter identifiers) to correct learning content. Operators may generate a password-reset link to share with a user and may reset onboarding completion so a user can complete setup again (without wiping learning sectors or account type). Operators may also view and update subscription entitlement fields on a user profile (subscription_status, subscription_provider, product and price identifiers, expiry and trial timestamps, and company seat_limit) for support — for example complimentary access. Those Admin Panel changes update Workword access records only; they do not cancel or refund App Store, Google Play, or Stripe billing. Through the Admin Panel Mailing tools, authorised operators may also create and manage reusable email templates (mail_templates) and send operational emails to selected groups of users (for example by account type, company link, or individually selected accounts) using the account email addresses on file, via our email provider (Section 5). Outbound admin mailings use a branded General HTML layout with header/footer links (website, web app, terms, privacy) and a per-user Unsubscribe link to https://app.workword.eu/email-preferences/... so you can opt out of or restore operational emails (admin_mailing_enabled on your profile; default on). Each send is logged in mailings for audit. Through Blog Management, authorised operators may also create, edit, publish, and soft-delete public editorial posts stored in blogposts (localized titles, excerpts, and bodies). These posts are product content shown in the in-app Blog and do not contain user personal data. Through Automations, authorised operators may generate marketing copy and optional images (via OpenRouter) and publish that operator-authored content to LinkedIn, Facebook, and/or Instagram through Activepieces. The share payload is post text, selected platforms, and an optional public image URL only — learner accounts are not included. Admin access is limited to authorised operators and is used to operate and secure the Service, not for third-party marketing of learner data. Replies recorded in the Admin Panel are stored on the submission for operators; they are not automatically emailed to the user unless a later notification channel is enabled.


7. Retention

We keep personal data only as long as needed for the purposes described above.

  • Account and learning data — while your account is active. When you delete your account, it is deleted as described below
  • Device tokens — while notifications are enabled or until the token is replaced or invalid; deleted on account deletion
  • Support messages and reports (contact_messages, support_reports, user_reports, reports) and website form emails — 24 months after the request is closed, then deleted
  • Web error reports (client_error_reports) and crash data (Crashlytics) — 90 days
  • Google Analytics (property workword-c1032) — event data 2 months, user data 14 months (reset on new activity)
  • Rewarded-ad receipts (admob_rewarded_ssv) — 90 days. Google keeps its own ad-serving logs under its advertising retention practices
  • Rate-limit records (including website-form IP addresses in rate_limit_windows) — until the rate-limit window expires
  • Business and public-sector prospects (company_leads, government_organizations_leads) — 12 months after our last contact, unless the organisation becomes a customer. Unsubscribed addresses (marketing_email_suppressions) are kept for as long as we send outreach, so we can honour your opt-out
  • Admin mailing logs (mailings) — 24 months
  • Speech-synthesis cost logs (characters and user ID) — 24 months
  • Billing records (invoices and payment records for company subscriptions, and the purchase records we need for our accounts) — 7 years, as required by Dutch tax law (Art. 52 Algemene wet inzake rijksbelastingen; see the Belastingdienst)
  • Legacy messaging data — on account deletion we remove you from legacy user_chats membership and delete chat_public_key. Residual encrypted messages are not usable without the keys and will be purged by operators as part of legacy chat cleanup
  • Local device data — until you sign out, clear app data or uninstall the app (includes the encrypted local screen cache and offline packs)

When you delete your account (in the app under Profile → Delete account, or by emailing us — see also https://workword.eu/delete-account), we delete your sign-in account, learning history, flashcards and their files, challenges, notifications, workplace exercise data, push tokens, profile photo and username, and we clear your profile fields (name, email, photo, subscription identifiers). We keep a minimal deleted-account record (account ID and a deletion flag, no contact details) for up to 12 months to prevent abuse and duplicate sign-ups, then delete it. Support messages and reports you sent are kept for the periods above, and billing records for 7 years. Apple, Google and Stripe keep their own billing records.

Partial deletion. You can also ask us (or, where the app offers it, use Settings) to delete only your learning history or your profile extras while keeping your account.


8. Security

We take appropriate technical and organisational measures to protect personal data, including:

  • Authentication and access controls
  • Encrypted transport (HTTPS/TLS) for network communication
  • Restricted access to production systems and data
  • Use of established cloud platforms with security controls

No method of transmission or storage is completely secure. Please use a strong password and keep your login credentials confidential.


9. Your rights (GDPR)

Under the GDPR you have the right to:

  • Access your personal data
  • Rectify inaccurate data
  • Erase data (“right to be forgotten”), subject to legal exceptions
  • Restrict processing in certain cases
  • Data portability for data you provided, where applicable
  • Object to processing based on legitimate interests, and object at any time to direct marketing (including our outreach emails, Section 3.8c), in which case we stop
  • Withdraw consent where processing is based on consent (without affecting prior lawful processing), including analytics consent (Section 3.7) and advertising consent (Section 3.7a), in Settings → Privacy
  • Lodge a complaint with a supervisory authority

In the Netherlands, the supervisory authority is the Autoriteit Persoonsgegevens (https://www.autoriteitpersoonsgegevens.nl).

To exercise your rights, email contact@workword.eu. We respond within one month. We may need to verify your identity before fulfilling a request.


10. Children

Workword is designed for adult workplace learners. It is not directed at children under 16. We do not knowingly collect personal data from children under 16. If you believe a child has provided personal data, contact us and we will take appropriate steps to delete it.


11. Cookies and the website

Marketing website (workword.eu)

The website at https://workword.eu uses storage that is strictly necessary for the site to work (for example security, load balancing and remembering your cookie choices). These do not need consent.

Analytics (Google Analytics 4) and advertising measurement (Google Ads) are optional and have separate choices in the cookie banner. Google Tag Manager (GTM-PSDRN2HF) loads only after you accept both. Until you accept, Google tags run in Consent Mode with storage denied and set no analytics or advertising cookies.

With your advertising permission, the website sends measurement data to our Google Ads account (AW-17181401897). This can involve ad-click identifiers and first-party cookies such as _gcl_au and _gcl_aw (Google lists 90 days for these), and Google receives your IP address and browser information. The website sends page URLs without query strings, and a fixed page title.

The website’s Google tag disables advertising personalisation, Google signals and enhanced conversions (allow_enhanced_conversions: false). We do not send names, email addresses or other form data to Google Ads from the website tag, and we do not upload customer lists from the site. Our Google Ads account is configured not to use enhanced conversions or conversion-based customer lists for Workword; if those account features are re-enabled later, we will update this policy.

Your choices are stored in your browser’s local storage. You can change them at any time through the website’s cookie notice (analytics and advertising checkboxes, then Save choices, or Only essential). When you withdraw advertising permission, we remove the first-party advertising cookies we can access and reload the page. This does not delete data already sent to Google; see Google’s advertising information, Google’s advertising-cookie information and My Ad Center.

Web app (app.workword.eu)

The web app at https://app.workword.eu uses storage that is strictly necessary for sign-in, offline use and your settings. Firebase Analytics (G-42N0ETYX3P), which sets Google Analytics cookies, runs only after you agree in the app’s analytics choice (Section 3.7). Free regular accounts may see Google AdSense ads after a separate first-party ads consent dialog (Section 3.7a); the marketing-site cookie notice does not cover those ads. The web app does not load Google Tag Manager.

Mobile apps

The mobile apps do not use cookies. Firebase Analytics and personalized AdMob ads use device identifiers only after the consent described in Sections 3.7 and 3.7a. App-install conversion reporting for our Google Ads campaigns uses the link between Google Play and Google Ads.


12. Changes to this policy

We may update this Privacy Policy from time to time. The “Last updated” date at the top will change when we do. For material changes, we may provide additional notice via the Service or email where appropriate.

Where a change requires your consent, we will ask for it.


13. Contact

MTech & IT Wismar 34, 8052 CD Hattem, The Netherlands KvK 42050195 · btw-id NL005456429B14 Email: contact@workword.eu Web: https://workword.eu · https://mtech-it.nl

Delete your Workword account

Terms of Service