Privacy Policy – Balagh App
Last updated: August 11, 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 is processed transiently only. We store neither audio recordings nor captures on our servers.
- Transcripts stay on your device: Your translation history is stored locally in the app only (up to 100 sessions) and can be deleted by you at any time.
- No ad tracking: The app contains no advertising SDKs and no push notifications, and does not access your location, contacts or camera. Your data is never combined with data from other providers, never used for advertising and never shared with data brokers.
- Product analytics, switchable off: The app records pseudonymous usage statistics (for example which screens you open, whether a session starts or fails) – never the content of the khutbah. You can turn this off at any time with the "Share usage data" switch in Settings; see section 8.
- European infrastructure where possible: Our media server (LiveKit) and our database are self-hosted 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 that are generated 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.
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).
Usage and device data
Unless you have switched product analytics off, we process pseudonymous usage data from the app: a randomly generated device identifier, the screens you open, interactions with controls, and technical device details (operating system and version, device model, app version, language, time zone). Once you sign in, this data is associated with your user ID. 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).
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 (Better Auth) 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-hosted media server (LiveKit), located in a data center in Germany (hosting: TubeHosting).
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. See our Terms of Service for details.
6. AI service providers
For speech recognition, translation and speech synthesis we use specialized service providers as processors. Audio and text data are processed transiently and solely to provide the translation; 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). 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.
RevenueCat
We use RevenueCat, Inc. (USA) as a processor to manage subscriptions. RevenueCat 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.
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: pseudonymous usage events – which screens you open, which controls you tap, whether a translation session starts, ends or fails, and steps around sign-in and subscription. This transmits a randomly generated device identifier, technical device details and, once you have signed in, your user ID.
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 is Art. 6(1)(f) GDPR (legitimate interest in operating, debugging and improving the service). You may object to this collection at any time and without giving reasons (Art. 21 GDPR): turn off the switch under Settings → Privacy → "Share usage data" in the app. From that point on, no further usage events are recorded or sent. The app remains fully usable.
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.
For server-side errors, transmission of standard personal fields is disabled. Error reports from the app, by contrast, include your IP address and – if you are signed in – your user ID, so that a crash can be tied to a specific operation and fixed. The legal basis is Art. 6(1)(f) GDPR.
9. Email delivery
We use Resend (Plus Five Five, Inc., 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: not stored – transient processing during the session only.
- Transcripts/translations: locally on your device only; deletion is entirely in your hands.
- 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: for the duration of the statutory retention obligations, to keep billing auditable.
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) are permanently deleted; 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).
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 5, 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).
| Service | Location | Safeguard |
|---|---|---|
| LiveKit media server | Germany | Self-hosted, no third-country transfer |
| PostgreSQL database | Germany | Self-hosted, no third-country transfer |
| Vercel (backend hosting) | USA/EU | SCCs, DPF |
| Speech-recognition providers (STT) | USA/EU | SCCs, partly DPF |
| AI translation providers (language models) | USA | SCCs, partly DPF |
| Speech-synthesis providers (TTS) | USA | SCCs, partly DPF |
| RevenueCat (subscriptions) | USA | SCCs, DPF |
| Apple (sign-in, App Store) | USA/Ireland | SCCs, DPF |
| Google (sign-in, Google Play) | USA/Ireland | SCCs, DPF |
| Resend (email delivery) | USA | SCCs, 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.