DE

Legal

Privacy policy.

This English version is provided for convenience. The German version is authoritative. It explains which data the website and apps process and which rights you have.

Controller

Blogbox UG (haftungsbeschränkt), Stadlbergstr. 7, 83714 Miesbach, Germany. Email: mail@bernhardhering.de

Website

The hosting provider automatically records technical access data such as IP address, time, requested file, transferred volume and browser or system information. These logs are used for stability, security and technical administration.

  • The website uses no first-party advertising or analytics tracking cookies.
  • Technically necessary cookies may be used when required for secure operation.
  • External services such as app stores and social platforms apply their own privacy policies after you follow a link.

Apps and stores

Apple App Store and Google Play process their own download, account, payment and usage data. Please consult the store privacy information.

  • Health and fitness data is generally processed locally or in operating-system cloud services you enable. RunWatch's explicitly authorized AI coach is the exception described below.
  • Location history in the relevant apps is stored inside the app and not transferred to our own servers.
  • System permissions can be revoked at any time.

RunWatch AI coach

If you explicitly authorize the feature in RunWatch, the app sends coach messages and selected training and Health data over an encrypted connection to a proxy operated by us. This may include workouts, training load, recovery, sleep, heart rate, and goals, preferences or limitations stored in the coach. The proxy forwards the request to the OpenAI API to generate the coach response.

This data is used only for the requested coach feature, not for advertising or tracking. RunWatch does not send a reporting identifier, email address or account data with these requests. By default, OpenAI does not use content submitted through its API to train its models. OpenAI provides more information about business data processing at https://openai.com/business-data/.

Without authorization, AI coaching stays paused and no coach messages or training data are sent to our proxy or OpenAI. You can withdraw authorization for future requests at any time in RunWatch settings. RunWatch stores the coach history locally on the device.

Zero Effort Diary

Zero Effort Diary creates an editable daily recap on your device. Apple Health, Photos, Places & Routes, Calendar, and Reminders are separate optional sources and are disabled by default. The app also works when you enable only some or none of them.

When you enable Health, the app reads the data you permit for steps, walking and running distance, active energy, heart rate, resting heart rate, heart-rate variability, sleep, workouts and state of mind. It processes this information only on your device for your journal entry, never sends it to our own servers and never uses it for advertising.

When you enable Photos, the app reads the capture date, a local photo reference and—only if Places & Routes is also enabled—available location metadata of permitted photos. Originals stay in Apple Photos. If iCloud Photos is enabled, Apple may download a required image from your iCloud account. Zero Effort Diary does not upload photos to our own servers.

When you enable Places & Routes, the app reads location history stored locally and shared with the related location apps. To turn coordinates into readable place names, the app may submit coordinates to Apple Maps and geocoding services under Apple’s privacy terms. Coordinates and location histories are never sent to our own servers.

Calendar and Reminders are read through Apple’s EventKit only after separate permission for each source. The app imports titles, time or all-day status, and completion status, but not notes, attendees, URLs, attachments, calendar names, or list names. It never changes, deletes, or completes events and tasks.

On compatible devices, selected shortened event and task titles may be phrased by Apple Foundation Models entirely on the device. No titles, prompts, or generated text are sent to us, HipsterReport, or an external AI service. Widgets and notifications contain no private event or task titles.

Journal text, personal notes and derived daily data are stored locally. There is no user account and no AI or text server operated by us or an external provider. “Delete all journal data” removes local journal entries and derived caches; it does not alter originals in Apple Health, Apple Photos, Calendar, Reminders, the related location apps or an existing iCloud backup.

Optional iCloud backup

Backing up location history to an app-specific container in your personal iCloud account is a separate option and is disabled by default. Turning it off stops future backups. A backup file that already exists may remain in iCloud until you remove the relevant app data there. Apple processes this data under its own iCloud terms; it is not sent to our own servers.

Usage analytics and app reporting

Some apps record a small set of usage events, such as opened features, paywall views, selected products, purchase or restore attempts, app version, build, platform, device family, language and system version. We use our own reporting endpoints and, in some apps, TelemetryDeck. An app-specific installation identifier is stored on our servers only as a hash.

Wrist Temperature uses HipsterReport in App Store builds for events covering onboarding, navigation, permission prompts, completed data requests, notification settings, paywalls, purchases and restores, and selecting other apps. A completed data request is reported regardless of whether HealthKit returns any temperature values.

GPX Workout Repair uses HipsterReport for events covering opened workflows, GPX import, preview, repair, splitting and export, as well as loading, inspecting and writing workouts. It also reports when the HealthKit permission prompt, rating prompt or feedback path is requested. It does not submit GPX files, file names, workout IDs, activity names or types, routes, coordinates, HealthKit values, rating values, error messages or free text.

In Zero Effort Diary, our reporting is called HipsterReport. It is a separate option and is disabled by default. If you enable it, the app submits a random app-specific installation identifier, event identifier and timestamp, plus events for onboarding, source or permission choices, journal review, opening the app from a widget or notification, and selecting a related app. App version, build, platform, device family, operating system, language and SDK version are included as technical context.

  • No names, email addresses, journal text, personal notes, Health data, fitness data, photos, places, coordinates or location histories are sent to our own reporting servers.
  • The information is not used for advertising, data brokers or tracking across other companies’ apps and websites.
  • Optional crash and usage statistics from Apple or Google depend on the system settings you choose.

Contact and newsletter

When you contact us by email, we store the message and contact details to answer and handle follow-up questions. Newsletter registration stores the email address plus technical registration and confirmation data. Subscription uses double opt-in and can be cancelled through the unsubscribe link or by email.

Legal bases, retention and deletion

Processing is based, as applicable, on Article 6(1)(f) GDPR for secure operation and improving our products, Article 6(1)(b) GDPR for contracts or pre-contractual requests, and Article 6(1)(a) GDPR for consent, including the newsletter, optional app reporting, data sources and cloud features. You may withdraw consent for future processing at any time.

We retain personal data only as long as needed for its stated purpose or legal obligations. Technical reporting events are retained only as long as needed for product analysis, troubleshooting and security, and are then deleted or aggregated. Local journal data remains on your device until you delete it in Zero Effort Diary or remove the app and its local data. You can disable permissions and future reporting in the app or system settings. You manage deletion of an optional iCloud backup through the iCloud app data in your Apple account.

For access or deletion requests concerning data on our systems, email mail@bernhardhering.de. Because reporting data is pseudonymous and there is no user account, additional technical details may be required to locate it.

Your rights

Subject to the legal requirements, you may request access, correction, deletion, restriction, portability or object to processing. You may withdraw consent for the future and lodge a complaint with a data-protection authority.

Version

Last updated: 11 August 2026. If this convenience translation and the German policy differ, the German text controls.