BahnDeutsch

Clear information. Informed choices.

BahnDeutsch privacy policy

Understand what information we process, why it is needed and how to make a request about your personal data.

Request about my data

Account and learning

Information needed to sign in, provide courses and track your progress.

Optional features

Text, audio or other content you submit to educational tools.

Your requests

Ask support for access, correction or deletion of your personal data.

No account required to read

1. Responsibility and scope

The BahnDeutsch German language academy and its support team handle information and privacy requests relating to BahnDeutsch services. Contact [email protected] or use our contact page.

This policy covers bahndeutsch.com, bahndeutsch.ir, the Android app and BahnDeutsch web apps. Both domains connect to the same educational system. Login sessions and local browser data may be stored separately for each domain.

External services you open, such as payment gateways or social networks, have their own privacy policies.

2. Information we process

The information depends on the features you use. You can read public pages without an account. Account-based features request information when you register or use the relevant feature.

  • Account and authentication: name, email, mobile number, profile details, preferences, sign-in history, verification information and session identifiers. Your password is processed for authentication; do not send it to support.
  • Learning: courses and subscriptions, exercise and exam answers, results and progress, flashcards and vocabulary reviews, class reservations, points and educational activities.
  • Communication and interactive tools: support messages, chats, submitted text or files, and audio you send for exercises, speech recognition or voice conversations.
  • Purchases: order identifiers and items, amounts, payment status, transaction references, discounts and details needed to handle purchases and subscriptions.
  • Technical information: IP address, device and browser type, request time and path, session information, feature-use events and error reports for security, reliability and performance.

3. Why information is used

To create and protect accounts, send verification codes, deliver content and course access, synchronize progress, run exercises and classes, handle purchases and support, and prevent fraud or abuse.

Usage events and technical reports help identify faults and improve service performance. AI features require processing the input submitted to the relevant feature.

Where applicable law requires separate consent, it must be obtained before that processing. Reading this page is not blanket consent to every kind of processing or personalized advertising.

4. Cookies and on-device storage

Cookies, browser storage and app storage support login sessions, language and display preferences, web-app installation status, content caching and some learning or offline features. Local data is not the same as information stored in your account.

You can clear or restrict site cookies and data in browser settings and change device permissions. This may sign you out, reset preferences or limit offline features. Clearing browser data does not necessarily delete server records.

The advertising section below explains advertising tools and Google-related choices.

5. Advertising, measurement and Google services

The current homepage does not activate Google Analytics, Google Ads conversion or Google remarketing tags. Cloudflare performance and visit measurement, BahnDeutsch educational events and operational reports are processed to measure performance, operate and improve the service.

Arriving from an advertisement may add campaign parameters or click identifiers to the page address, which may appear in web-server request logs. Do not put sign-in details, verification codes or banking information in URLs or advertising parameters.

If conversion or remarketing tools are enabled in the future, this policy and the relevant consent controls will be updated. Remarketing allows third-party providers, including Google, to use cookies or device identifiers to show ads based on previous visits. This explanation does not mean those tools are currently active.

Use the official links below to learn how Google processes information and to manage personalized advertising.

6. AI, audio and permissions

When you use an assistant, correction or intelligent exercise, submitted text, content and necessary context may be sent through AvalAI to model providers. Live voice conversations use xAI and require sending audio and conversation context to generate responses.

This processing takes place when you use the feature. Inputs, responses and related records may be saved to show history, continue exercises or manage quotas and costs. Provider policies and terms also apply to their processing; we do not independently guarantee their processing locations or data-use practices.

Microphone, camera or screen-sharing features require the relevant browser or device permission. You can revoke it, which may prevent the feature from working. Content shared in chats or shared spaces is visible to the audience of that space.

Do not submit passwords, sign-in codes, banking details, identity documents or sensitive information about other people to AI tools or chat.

7. Payments and banking information

Rial payments redirect to ZarinPal. BahnDeutsch receives transaction results and references to manage orders and subscriptions. The gateway also processes payment data under its own policy.

Enter full card details, card security codes and banking passwords only on the legitimate payment gateway. Educational and support forms are not a place to send them. If another payment method is offered, its provider and processing practices will be explained in the payment flow and this policy.

8. Recipients and international processing

To provide services, necessary information is processed with infrastructure providers, Cloudflare for networking, security and performance measurement, Melipayamak SMS services, ZarinPal, AI providers and Sentry for error reporting. Data depends on the service; not every provider receives all your account information. The Enamad trustseal image and some external content also load from their provider, which can receive the browser IP address and technical request information.

Support staff, teachers or course administrators may access information needed for their relevant duties. Necessary disclosure may also occur in response to a valid legal requirement, a dispute, or to protect users’ rights and security.

Some providers may process information outside your country of residence. Social-network links and other external services are governed by their own policies.

9. Retention and deletion

Account and learning records are retained while needed to provide the account, access and service. Retention differs between categories; purchase, dispute, security and fraud-prevention records may need to be kept longer.

Retention of technical logs and backups depends on operational and security needs; copies may remain until deleted or replaced. Deleting an account does not immediately erase every transaction record, related database entry or backup.

Deletion requests are assessed for scope, removable data and necessary limitations. Uninstalling the app or clearing browser data alone does not delete the account or server records.

10. Protecting information

Public site connections use HTTPS. Access controls, authentication, restrictions on educational content and security measures help reduce unauthorized access and abuse.

No system is absolutely secure. Use a suitable password, keep sign-in codes private and sign out on shared devices. Contact support if you suspect misuse of your account or information.

11. Your requests and choices

You can request access, correction of inaccurate information, a copy, or deletion of your account and related personal data. Requests to restrict or object to processing are also considered where applicable law provides those rights.

Send your request from the account’s registered email to [email protected] and explain its purpose and scope. Appropriate identity verification may be needed to prevent unauthorized access or deletion. Do not send extra information or sensitive documents without a specific support request.

Handling may depend on the account, purchases, other people’s rights or retention duties. Support will explain the outcome and necessary limitations. Manage microphone and other permissions in your device or browser settings.

12. Users below legal age

Where a user below legal age needs a parent or legal guardian’s consent to use a service or process data, that consent must be obtained before the relevant feature is used. A guardian can contact support about the child’s account and information.

This policy does not replace enrollment terms or course-specific rules. Do not put sensitive information about a child in public chat or AI tools.

13. Changes to this policy

We update this page and its date when services, processing tools or data-use practices change. If fresh consent is required, publishing a revised policy alone does not replace it.

The latest version is available at this address on both domains. Contact us about changes or the version relevant to the time you used the service.

Support and privacy email

Talk to us about your information

Use the subject “Privacy request” and identify the email or phone number registered to your account. Do not send your password, one-time code or full bank card details.

Other contact options