Privacy policy

Controller

Christian Hermann & Martina Hermann GbR
An Rainen 3
72525 Münsingen
Germany
Represented by Christian Hermann and Martina Hermann
Email: apps@bitbeans.de

Data in the app

Depending on how you use the app, we process sign-in data, particularly email address and sign-in identifier, as well as learning progress, quiz results, settings and started exercises. These are processed locally or linked to the signed-in account. To verify and restore purchases, we process the product identifier, store platform and technical receipt data. If you contact us voluntarily, we process your message and contact details. Necessary connection and security data arise when operating online services.

Optional study help

Only when you ask the optional study help a question (including through the suggestion in the exam results) are that question, relevant learning material and, for questions from a quiz, the answers concerned sent through our backend to a text-generation provider (USA) to generate a response. Account and payment data are not sent for this purpose. Please do not enter personal data in free-text fields. To select matching catalog texts and to check whether the answer from the study help is supported by them, we also send the question, catalog excerpts, for questions asked from a quiz also the quiz question with its options, your chosen answer, the solution and explanation, and the generated answer to a text-assessment provider (USA); a question held back by the word filter may additionally be assessed there together with its quiz context. This service does not generate text; account, sign-in and payment data are not sent.

Voluntary feedback and question suggestions

Voluntary feedback contains your message, an optional contact email address, category, app version, platform and the screen it was sent from; question suggestions contain the suggested text and, where applicable, the topic. If you are signed in, we link both to your account; we forward feedback to our support team by internal email for handling. Both are deleted when you delete your account.

Anonymous purchase, learning and review statistics

So that we can see where a purchase fails, whether a review prompt could be shown and whether the app runs fast and reliably, the app reports a few fixed events to our backend operated by a hosting provider: technical purchase steps such as purchase page shown, price loaded, purchase started, cancelled, failed or restored, and whether a review prompt was possible, requested, suppressed or unavailable, and a failed sign-in or account deletion. Once per installation, the app also reports whether the introduction was started, skipped or completed; we delete these counts after at most 120 days. Also, each at most once a day: where the purchase page was opened from (a fixed category such as start page, settings, introduction or a locked topic), whether Buy was tapped there and whether a purchase was made from it, whether a learning round or mock exam was started and roughly at which point one of them was left, the coarse start time until the app can be used (for example “1 to 2 seconds”) and whether the daily reminder is on, was switched or opened the app. With a purchase, the app also sends which purchase page it came from along with the purchase verification; we store this fixed category with the purchase data so that purchases per page cannot be miscounted, and delete it together with them. On the purchase page, the app also counts, at most once a day per page of origin, whether “Check status” was tapped for a waiting purchase, whether the confirmation was shown after a purchase or restore, and whether a restore ended without a purchase found. Each event contains only the event name, fixed categories, platform, app version and app language; no learning content, no answers, no input and no purchase receipts. The event itself contains no sign-in, account or device identifier. If the app already has a sign-in (including an anonymous one), it sends that session’s credential along for authentication; our backend uses it only for short-term rate limiting and to match a purchase report with a purchase the server verified for the same sign-in. Stored with the event is only whether it was signed in, neither identifier nor session; so that a confirmed purchase counts only once, a hashed reference to that purchase is kept with it for at most 8 days. Current app versions also send with every event the coarse origin of the installation (store, test or developer installation) so that test traffic is counted separately; it is determined on the device, without any device or installation identifier. If an event comes from the networks Google publishes for its automated pre-launch tests, our backend also counts it as test traffic; the IP address is only compared for this and not stored. We delete individual events after seven days. Daily totals of review prompts and of the daily events are deleted after at most 120 days; aggregate daily counters of purchase steps and of purchase and account-deletion errors are kept without a fixed deletion date. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is finding errors and purchase problems and improving the app. Because the events contain no identifier, we cannot link them to a person (Art. 11 GDPR). You can object under Art. 21 GDPR at any time by emailing apps@bitbeans.de. A failed report has no effect on learning or purchases.

Purposes and legal bases

We process data to provide the app, enable sign-in and learning progress, verify purchases, fix technical issues, protect the service and respond to enquiries. Depending on the activity, the legal bases are Article 6(1)(b) or (f) GDPR; where consent is requested, Article 6(1)(a). You may withdraw consent for the future.

Delivery of this website

When you visit this site, our hosting provider (USA and EU) processes technically necessary access data, particularly your IP address, time, requested URL, browser information and HTTP status. This supports secure delivery and abuse prevention under Article 6(1)(f) GDPR. Security logs are kept only as long as needed for operation and protection.

Tools on this website

Calculators, search, quizzes and the recording checker process inputs and file contents in your browser. We do not upload files, store learning progress or send search terms, calculation values, filenames or quiz answers to our audience measurement. A shared calculation link includes the values in its URL fragment; anyone receiving the link can read them. The audience measurement receives neither URL fragments nor query parameters. We only measure tool use with its fixed name. Downloaded results remain on your device until you delete them. If you choose offline storage in the GHS trainer, your browser caches that page and its public learning data locally. Remove this copy using the button in the trainer or your browser’s website settings.

Audience measurement with Umami

This website uses the open-source audience measurement Umami, which we operate ourselves, on a server of a hosting provider in Frankfurt, Germany. It measures pages visited, referrer, country of origin, device type, screen size, browser and operating system, plus clicks on App Store and Google Play buttons. Store-click events transmit only the store and app. It sets no cookies and does not store IP addresses; a daily rotating, non-reversible hash helps count visits. We do not build advertising profiles or share analytics data with third parties. The data is deleted after 14 months. The legal basis is Article 6(1)(f) GDPR. We respect browser Do Not Track settings. You can also object by emailing apps@bitbeans.de.

Recipients and international transfers

We use service providers in these categories: hosting, backend, database, media and security (USA and EU), sign-in (USA), text generation and checking of answers for the optional study help (USA, only when you ask a question), and Apple and Google for store services. Apple and Google generally act as independent controllers for store purchases. For transfers to the USA, the EU-US Data Privacy Framework or EU standard contractual clauses apply; otherwise we rely on appropriate safeguards or applicable legal exceptions. You can obtain a copy of the safeguards on request at apps@bitbeans.de. We name the individual providers on request at apps@bitbeans.de.

Retention and your rights

We generally keep account and learning progress data until deletion. Purchase data may need to be kept longer for legal evidence or retention obligations. Technical logs and enquiries are retained only as long as needed for security, operation or follow-up. Subject to legal conditions, you have rights of access, rectification, erasure, restriction, portability and objection. You may also complain to a data protection authority; the authority for our registered location is the LfDI Baden-Württemberg. See Delete data for removal steps.