Yükleniyor…Yükleniyor…

Privacy Policy – Balagh App

Last updated: November 2, 2026

This privacy policy covers the Balagh mobile app (iOS and Android). It is a courtesy translation – the German version is the legally binding one. The moschee.io platform is covered by our general privacy policy.

1. Privacy at a glance

Balagh is an app that lets you capture a speech – such as a khutbah – with your device's microphone and have it translated into your language in near real time. The speech is transcribed, machine translated and, if you wish, played back as synthesized speech.

The most important points up front:

  • No server-side recording: Audio from live sessions is processed transiently only. We store neither audio recordings nor captures on our servers.
  • Transcripts stay on your device: Your translation history from live sessions is stored locally in the app only (up to 100 sessions) and can be deleted by you at any time. Only the results of a file translation are stored on our server, until you delete them, and a summary you request, until the app has fetched it (section 3).
  • No ad tracking: The app contains no advertising SDKs, uses no advertising ID, sends push notifications only when a summary you asked for is ready and as a Friday reminder you can switch off in Settings, and does not access your contacts or camera. It asks for your location only when you check the 7-day pass yourself in Makkah or Madinah, and does not store it (section 3). Your data is never combined with data from other providers, never used to show you ads and never shared with data brokers. On iPhone and iPad the app only checks, through Apple's own interface, whether it was installed from an ad in the App Store (section 7).
  • Anonymous product analytics, more detail only with your consent: The app counts which screens and features are used (for example whether a session starts or fails) – never the content of the khutbah. Without your consent this is anonymous: no lasting identifier, no profile, and nothing stored on your device for it. Only once you choose "Share usage data" during setup or in Settings does the app use a lasting identifier, linked to your account once you sign in. You can turn this off again at any time; see section 8.
  • European infrastructure where possible: We run our media server and our database ourselves, in Germany.

2. Controller

The controller for data processing in connection with the Balagh app is:

Youcci UG (haftungsbeschränkt)
Metzer Straße 9
66117 Saarbrücken
Germany

Represented by: Youcef Wippert
Email: info@youcci.de
Privacy contact: datenschutz@moschee.io

A data protection officer has not been appointed, as the legal requirements for a mandatory appointment are not met.

3. What data we process

Account data

When you register, we process your name, your email address, an optional profile picture and the sign-in provider used (Apple or Google). The legal basis is Art. 6(1)(b) GDPR (performance of a contract).

Audio data

During an active translation session, your microphone audio is transmitted to our media server and processed transiently by the translation pipeline (see sections 5 and 6). The audio is not stored on our servers.

Transcripts and translations

The transcripts and translations generated in live sessions are stored locally on your device only (history, up to 100 sessions). You can delete the entire history at any time in the settings. These contents only pass through our servers transiently during a live session and when you request a summary (see below).

Translating audio and video files

Where the app offers translation of audio or video files, you can upload a file with an active subscription. It is stored in non-public storage on our servers in Germany and processed by speech recognition and translation providers (see section 6). We delete the uploaded file as soon as processing has finished or failed, and an unfinished upload after 24 hours. The result (transcript and translation with timestamps) is stored on our server until you delete it in the app or delete your account. Legal basis: Art. 6(1)(b) GDPR.

AI summaries

Where the app offers summaries and you request one for a session in your history, the app sends that session's transcript to our server. A large language model summarizes it, connected through a routing service based in the USA that only uses hosts that neither store nor train on inputs (see section 6). We delete the transcript as soon as the summary is done. The summary stays on our server until the app has fetched it, at most 7 days; after that the app keeps it on your device only. When it is ready, we notify you by push notification through a push service provider based in the USA and Apple's or Google's push service. For this we store your device's push token until the notification has been sent; the notification contains no khutbah content. Legal basis: Art. 6(1)(b) GDPR.

Session metadata

For each translation session we store metadata on our servers, without any content: room identifier, source and target languages, whether speech output was enabled, session start and end, and the billed seconds. We need this data to account for your minute quota (Art. 6(1)(b) GDPR).

Friday reminder

If you have allowed notifications and left the Friday reminder on in Settings, the app reminds you of the khutbah by push notification on Fridays, 30 minutes before the start time you set, otherwise at 11:00, and tells you the minutes you have left. We send it only with an active subscription that has minutes left, at most once a week, and not if you have already started a session that day. For this we store your device's push token, its platform and time zone, the start time you set, the app language and when the last reminder was sent. It is delivered through the same push service provider based in the USA and Apple's or Google's push service. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in reminding you of your subscription); you can switch the reminder off at any time in the app's or your device's settings.

Ratings after a session

After a session the app may ask you for a voluntary rating: one to five stars, short tags and, if you like, your own text. We store it with the session, the languages, the duration, app version, platform and app language, and an irreversible pseudonym of your account or device so that a session is rated only once. If the text is not in German, we have it translated into German the same way as the summaries. Only we read the ratings, to improve the translation. We delete texts after twelve months; stars and tags stay without the text for statistics. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in improving the app).

Usage and device data

The app records the screens and features you use, your plan, and technical device details (device model, operating system and version, app version, language, time zone). Without your consent this is anonymous, with an identifier that is created anew on every app start and never stored; the data is not linked to any account. If you have chosen "Share usage data", the app uses a randomly generated identifier stored on your device instead, linked to your account once you sign in. Khutbah content – audio, transcripts or translations – is expressly excluded. See section 8 for details and how to switch it off.

Subscription data

To manage your subscription we store your tier, status, store (App Store / Google Play), period start and end, and the transaction events transmitted by our subscription provider (see section 7). We never receive payment details (such as credit card numbers).

Questions on first launch

On first launch the app asks how you found Balagh and where you will mostly use it. Both questions are optional and can be skipped. Once you sign in, we store your choice (e.g. "Searched the store" or "In Makkah or Madinah") with your customer record at our subscription provider (see section 7), to understand how people find and use Balagh. The legal basis is Art. 6(1)(f) GDPR. The answers are deleted with your account. Whether your phone is set to Saudi time is checked on the device only, to show groups in Makkah and Madinah relevant tips; nothing is transmitted for it.

Location check for the 7-day pass

The 7-day pass is only available in Makkah and Madinah. When your phone is set to Saudi time, the app offers it. Only when you tap "Check my location" does it ask, once, for permission to use your location while you use the app, and it reads it a single time. The position is rounded to about two kilometres on the device and sent to our server, together with your phone's indication of whether it comes from an app that fakes locations, and whether the app is running in Apple's test environment. The server checks whether the position is in Makkah (25 km around the Kaaba) or Madinah (20 km around the Prophet's Mosque) and then discards it. We keep only the result (e.g. "in Makkah" or "outside"), the time, the operating system and whether the phone was set to Saudi time; we never store the coordinates. When you buy a pass, our subscription provider also tells us the country of your store account. The purpose is to offer the pass only to people who are there (Art. 6(1)(b) GDPR). We delete the check results after 90 days, and with your account at the latest. You can withdraw the location permission at any time in your phone's settings.

Support requests

If you contact us by email (e.g. at support@moschee.io), we process the information you provide in order to handle your request (Art. 6(1)(b) or (f) GDPR).

4. Registration and sign-in

Sign-in is handled by our self-operated authentication system running on our own infrastructure. Your session token is stored on your device in protected system storage (iOS Keychain / Android Keystore).

Sign in with Apple

When you sign in with Apple, we receive your name and email address from Apple (optionally an anonymized relay address). The provider is Apple Inc., One Apple Park Way, Cupertino, CA 95014, USA, and Apple Distribution International Ltd., Hollyhill Industrial Estate, Cork, Ireland. The legal basis is Art. 6(1)(b) GDPR.

Google sign-in

When you sign in with Google, we receive your name, email address and optionally your profile picture. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. The legal basis is Art. 6(1)(b) GDPR.

5. Audio processing and live translation

The app's core feature is live translation of spoken language. Your microphone audio is transmitted encrypted (WebRTC/WSS) to our self-operated media server, located in a data center in Germany.

From the media server, the audio is routed transiently through our translation pipeline: speech recognition (speech-to-text) → machine translation → optional speech synthesis (text-to-speech). Specialized AI service providers are used for this (see section 6). No recording and no permanent storage of audio or transcripts takes place on our servers.

The legal basis for this processing is Art. 6(1)(b) GDPR (provision of the translation service you requested).

Third parties' voices

When using the app, you will typically capture the voice of another person (e.g. the speaker or imam). You, as the user, are responsible for the lawfulness of that capture. Please inform the person concerned and obtain their consent where required. Before you start a session with the microphone, the app reminds you that your phone picks up everyone nearby and that the audio goes to our servers and to speech recognition and translation services. See our Terms of Service for details.

6. AI service providers

For speech recognition, translation, speech synthesis and summaries we use specialized service providers as processors. Audio and text data are processed transiently and solely to provide these features; which services are used depends on the current system configuration. The following categories of providers are used:

  • Speech-recognition providers (speech-to-text): providers based in the USA; depending on the provider and configuration, the audio is processed in data centers in the EU or the USA.
  • AI translation providers: providers of large language models based in the USA, connected through a routing service (based in the USA); they also write the summaries. Transcripts are transmitted, not audio.
  • Speech-synthesis providers (text-to-speech): providers based in the USA; only the translated text is transmitted, no audio.

Data processing agreements are in place with all providers; transfers to third countries are based on EU standard contractual clauses, in some cases supplemented by a certification under the EU-U.S. Data Privacy Framework (see section 14). Individual providers may use audio data to improve their models to the extent contractually agreed; we work towards disabling such use. We are happy to provide a current list of the specific sub-processors on request at datenschutz@moschee.io.

The legal basis is Art. 6(1)(b) GDPR. No automated decision-making with legal effect within the meaning of Art. 22 GDPR takes place.

7. Subscriptions and payments

Subscriptions are purchased and billed exclusively through the Apple App Store or Google Play. Your payment counterparty and the recipient of your payment data is the respective store operator (Apple or Google). We never receive payment details.

Subscription management

We use a service provider based in the USA as a processor to manage subscriptions. It processes a pseudonymous user identifier (your account ID), your subscription status and transaction events (e.g. purchase, renewal, cancellation), and forwards these to us via webhooks. The legal basis is Art. 6(1)(b) GDPR.

Apple Ads attribution (iOS only)

To measure whether ads for Balagh in the App Store (Apple Ads) lead to trials and purchases, the app on iPhone and iPad fetches an attribution token through Apple's AdServices interface and passes it to our subscription provider. The provider uses it to ask Apple whether Balagh was installed from an Apple Ads ad and, if so, stores the campaign, ad group and search keyword with your customer record. The token is valid for 24 hours and contains no identifier of you or your device. The advertising ID (IDFA) is not used, the information is not combined with data from other apps or providers, and there is no tracking as defined by Apple's App Tracking Transparency. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in measuring how well our advertising works). The information is deleted with your account. No such attribution takes place on Android.

8. Usage data and error diagnostics

Minute metering

Your plan includes a monthly translation quota. For billing we record the billed seconds per session; the quota resets monthly, anchored to your purchase date. One active session per account is possible at a time.

Product analytics (PostHog)

We use PostHog, operated on EU servers (PostHog EU, Frankfurt), to understand how the service is used. Collection happens in two places:

  • On our servers: aggregated metrics about translation sessions, such as duration, languages used and technical latency figures.
  • In the app, anonymously: without your consent, the app sends which screens and features you use (such as whether a translation session starts, ends or fails, and steps around sign-in and subscription), your plan, device model, operating system and app version, language and time zone. The identifier for this is created anew on every app start and never stored; no profile is created, and the data is not linked to any account.
  • In the app, with your consent: if you choose "Share usage data" during setup or in Settings, the app sends the same details with a randomly generated identifier that is stored on your device and linked to your account once you sign in.

Khutbah content is not transmitted. Neither audio nor transcripts nor translations leave your device for analytics purposes; the app is technically configured so that screen areas containing khutbah content and your account details are excluded from collection. There is no cross-device tracking: the data is not combined with data from other providers, not used for advertising and not shared with data brokers.

The legal basis for the anonymous counting in the app and for the aggregated metrics on our servers is Art. 6(1)(f) GDPR (legitimate interest in operating, debugging and improving the service); you may object to it at any time (Art. 21 GDPR, contact in section 2). The legal basis for collection with a stored identifier linked to your account is your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG). You may withdraw your consent at any time without giving reasons: turn off the switch under Settings → Privacy → "Share usage data" in the app. From that point on, the app only counts anonymously. The app is fully usable with or without consent.

Error diagnostics (Sentry)

To detect software faults and crashes we use Sentry (Functional Software, Inc., USA) with EU data processing (ingest in Germany) – both server-side and in the app. Error reports contain technical identifiers (e.g. room and job IDs), device and app version details and the program state at the time of the fault, but never audio, transcript or translation content.

Transmission of standard personal fields is disabled both server-side and in the app; for example, the app does not send your IP address with error reports. The legal basis is Art. 6(1)(f) GDPR.

9. Email delivery

We use an email delivery provider based in the USA as a processor to send transactional emails (e.g. the confirmation of your account deletion). Your email address and the message content are processed. The legal basis is Art. 6(1)(b) GDPR.

10. Retention periods

  • Account data: until you delete your account.
  • Audio data from live sessions: not stored – transient processing during the session only.
  • Transcripts/translations from live sessions: locally on your device only; deletion is entirely in your hands.
  • File translations: the uploaded file until processing ends, an unfinished upload for 24 hours; the result until you delete it or your account.
  • AI summaries: the transcript until the summary is done, the summary until the app has fetched it, at most 7 days.
  • Ratings: the text for 12 months, stars and tags without the text beyond that.
  • Friday reminder: the device details until you switch the reminder off, sign out or delete your account; if you removed the app, until the next reminder.
  • Session and billing metadata: for the duration of the contract and beyond where statutory retention obligations apply (in particular § 147 AO, § 257 HGB: up to 10 years for billing-relevant records).
  • Subscription transaction events (notifications from our subscription provider): 90 days.
  • 7-day pass location checks: the result only, without coordinates, 90 days.

11. Account deletion

You can delete your account at any time directly in the app (Settings → Delete account). Your user account and all associated server data (sign-in data, session metadata, subscription data, results of file translations) are permanently deleted. We also delete your customer record at our subscription provider and your profile in product analytics (PostHog). You receive a deletion confirmation by email. Data subject to statutory retention obligations is kept in a restricted state until those periods expire.

Important: Deleting your account does not cancel your subscription. Please also cancel your subscription in the App Store or Google Play subscription settings.

12. Your rights as a data subject

You have the following rights:

  • Access to your stored data (Art. 15 GDPR),
  • Rectification of inaccurate data (Art. 16 GDPR),
  • Erasure (Art. 17 GDPR),
  • Restriction of processing (Art. 18 GDPR),
  • Data portability (Art. 20 GDPR),
  • Objection to processing based on Art. 6(1)(f) GDPR (Art. 21 GDPR),
  • Withdrawal of consent with effect for the future (Art. 7(3) GDPR).

You can download a copy of your data yourself at any time in the Balagh app under Settings. The ZIP file holds your data as a JSON file and as a readable overview, plus your history, which is stored only on your device. If you signed in more than an hour ago, you confirm the download with a code we send to your email address, and we let you know by email after each download.

An informal email to datenschutz@moschee.io is sufficient to exercise these rights. You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for us is the Unabhängiges Datenschutzzentrum Saarland, Fritz-Dobisch-Straße 12, 66111 Saarbrücken, Germany.

13. Data security

We take technical and organizational measures to protect your data, in particular: transport encryption of all connections (TLS and encrypted WebRTC), storage of the session token in protected device storage, access controls and logging on our systems, and hosting of central components (media server, database) in Germany.

14. Transfers to third countries

Where service providers outside the EU/EEA are used, transfers are based on EU standard contractual clauses (SCCs) under Art. 46 GDPR or, for certified US providers, on the adequacy decision for the EU-U.S. Data Privacy Framework (DPF).

ServiceLocationSafeguard
Hosting providers (media server, database, storage)GermanyEU processing, DPA
Speech-recognition providers (STT)USA/EUSCCs, partly DPF
AI translation providers (language models, summaries)USASCCs, partly DPF
Speech-synthesis providers (TTS)USASCCs, partly DPF
Subscription managementUSASCCs, DPF
Apple (sign-in, App Store, Apple Ads attribution)USA/IrelandSCCs, DPF
Google (sign-in, Google Play)USA/IrelandSCCs, DPF
Email deliveryUSASCCs, DPF
Push service provider (summaries, Friday reminder)USASCCs, partly DPF
PostHog (statistics)EU (Frankfurt)EU data processing
Sentry (error diagnostics)EU ingest (Germany)EU data processing; SCCs (US provider)

15. Changes to this privacy policy

We update this privacy policy when data processing in the app changes (e.g. new features or service providers). The current version is always available at this address; the date of the last update is shown at the top of the page.

Questions about privacy? Write to us at datenschutz@moschee.io.