Privacy policy - App "BetonTage"

Status: Version 1.0.0
App: BetonTage (iOS: de.digital.betontage, Android: de.betontage.betontage)
Languages: German / English

1. responsible person

The operator of the “BetonTage” app is responsible for data processing within the meaning of the GDPR.

Contact/imprint: (https://betontage.de/impressum-bildnachweise/)
FBF Betondienst GmbH
Gerhard-Koch-Str. 2+4
73760 Ostfildern
P.O. Box 11 62
73747 Ostfildern

Phone: +49 711 32732-300
Fax: +49 711 32732-350
E-mail: betontage@betonservice.de

represented by the Managing Director Dr. Ulrich Lotz

Entered in the commercial register at Stuttgart Registry Court
HRB 214566
VAT ID no. DE147858660

2. principle

The “BetonTage” app is a content app for displaying event and information content. The app does not process any user accounts and does not collect any personal user data such as name, email, telephone number, location or advertising IDs for tracking purposes.

3. what data is processed?

3.1 Processing content from the CMS (server requests)

The app loads content from WordPress systems and displays it. This includes in particular:
● Program content (incl. location information as text)
● Exhibitor and event content
● Hall plan/content pages
● Team and contact information (as editorial CMS content)
● Legal texts (e.g. imprint, disclaimer, data protection) Purpose: Provision and display of content in the app.

3.2 Local app data (on the device)

The following are stored locally for the function of the app:
● Favorites: Content markers.
Purpose: Favorites function and filtering
● Settings: e.g. language setting.
Purpose: User convenience
● Cache: Intermediate storage of loaded content incl. timestamps/sources/content IDs
Purpose: Performance, offline/restart capability, deduplication

This local data is not transmitted to third parties and is not merged on the server side as a usage profile.

4th data transfer

The app establishes connections to the following hosts:
● betontage.de – retrieval of CMS content.
● betonservice.de – retrieval of news/posts.
● Dynamic image/link hosts from CMS content – images/logos/maps are loaded via the URLs stored in the CMS content (host may vary)

Technically transmitted data during retrieval: Data such as IP address, time, user agent (if applicable) and request header (e.g. language/accept-language) are generated by the system for each connection.

Note: Server-side log storage, storage duration, server locations and order processing are currently not conclusively verified for the aforementioned systems (UNSURE) and depend on the respective hosting/server configuration.

5. tracking / advertising

The app does not use any tracking, advertising or attribution SDKs. There is no tracking as defined by Apple; no IDFA is used and no App Tracking Transparency (ATT) query is performed.

6. storage period and deletion

● Cache: content is cached locally. A validity check can last 24 hours, for example; however, outdated cache data can remain until overwritten or manually deleted.
● Favorites/settings: remain saved until they are removed or app data is deleted.
● Deletion by the user:
Favorites can be removed in the app.
Cache/all local data can be removed using the corresponding functions (“Delete all”) or by deleting the app.

7. safety

● Transmission: Communication takes place via HTTPS (encrypted transmission).
Local storage: Local app data is stored in encrypted form.

8. rights of data subjects

Insofar as personal data is affected, there are rights to information, correction, deletion, restriction of processing, data portability and objection in accordance with the GDPR.
As the app does not maintain a user account and primarily stores user data locally, users can delete a lot of data by removing favorites, emptying the cache or uninstalling.