Last updated: November 2026
1. Controller
The controller responsible for data processing is:
Frank Egger Software Entwicklung
Auf der Pief 5
52134 Herzogenrath
Germany
Email: frank.egger@gmail.com
2. Overview of Data Processing
We take the protection of your personal data seriously. The app Calendar Event Reminder (CER) is designed to operate primarily locally on your device. We do not collect or store personal data on our servers in connection with your use of the app, except where explicitly stated below.
The free version shows ads (see 3.9).
3. Data Processed by the App
3.1 Calendar Data (Local Processing Only)
The app accesses calendar data (e.g., event titles, descriptions, times) exclusively to provide reminder functionality.
- Processing takes place only on your device
- No transmission to the provider
Exception: if you enable Time to leave, the location of upcoming events is sent to the routing provider you chose (see 3.8).
Legal basis: Art. 6(1)(b) GDPR
3.2 Google Tasks Data (Local Processing Only)
If the user enables Google Tasks integration and grants the required permissions through Google OAuth, the app may access task information stored in the user’s Google account.
This information may include:
- Task titles
- Task descriptions or notes
- Due dates and times
- Completion status
- Reminder information
- Task list names
The purpose of this processing is to synchronize tasks to the device and provide reminder and notification functionality. Task data is processed locally on the user’s device and is not transmitted to the provider’s servers. The provider does not use task data for profiling, advertising, analytics, or any other purpose unrelated to the functionality of the app.
Legal basis: Art. 6(1)(a) GDPR (consent) and Art. 6(1)(b) GDPR (performance of a contract).
3.3 Google Account Authorization
To access Google Tasks, users authenticate through Google’s OAuth authorization process. The app receives authorization tokens from Google that permit access to the user’s selected Google account and authorized Google Tasks data. The provider does not receive the user’s Google password. Authorization tokens are stored only on the user’s device and are used solely to access the user’s Google Tasks data.
Legal basis: Art. 6(1)(a) GDPR (consent).
3.4 Usage Access (Foreground Apps)
If you grant permission, the app may access information about which apps are currently in use to enable features such as suppressing notifications.
- Processed only locally
- Not transmitted to us
Legal basis: Art. 6(1)(a) – consent
3.5 Crash Reports (Firebase Crashlytics)
We use Firebase Crashlytics to analyze app crashes.
Data processed may include:
- Device type
- Operating system
- App version
- Crash logs
This data is:
- Pseudonymized (not directly identifying individuals)
- Used solely to improve stability
Legal basis: Art. 6(1)(f) GDPR (legitimate interest)
3.6 Google Play Services
Integration of Google Play Services may result in independent data processing by Google. Please refer to Google’s privacy policy.
If you enable the optional weather feature (section 3.7), Google Play services is also used to determine your approximate location and, if device location or location accuracy is switched off, to show you Google’s dialog asking whether to turn it on. This processing is carried out by Google on your device and under Google’s own privacy policy. Time to leave (section 3.8) also uses Google Play services to determine your position.
3.7 Approximate Location and Weather (Optional)
The weather display below the alarm window is off by default. It works only if you switch it on in the presentation settings and grant the optional approximate-location permission (ACCESS_COARSE_LOCATION).
When an alarm is shown, or when you enable the option, the app determines your approximate location, using Google Play services where available. Your coordinates, rounded to about 100 m, are then sent directly from your device to the Norwegian Meteorological Institute (MET Norway, api.met.no) to retrieve the forecast. MET Norway also receives your IP address and the app’s name and version with the request. This data does not pass through our servers, and we do not receive or store it.
To show the name of your town, the coordinates are passed to your device’s Android geocoding service, which on most devices is provided by Google.
The app does not track you in the background and does not keep a location history. The last location, place name and forecast are cached on your device for a few hours so they need not be fetched again. They are deleted when you switch the option off or uninstall the app.
Legal basis: your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time by switching off the option or revoking the permission in Android’s system settings.
3.8 Time to leave (optional, CER+)
“Time to leave” is off by default. It works only if you switch it on, enter your own API key for a routing provider (TomTom or Google Maps) and grant the location permissions, including access to your location in the background (ACCESS_FINE_LOCATION, ACCESS_BACKGROUND_LOCATION). Before asking for these, the app explains what it uses them for.
To calculate travel times, the app sends the following directly from your device to the routing provider you chose:
- your current position, or the default starting point you set, as the start of the route
- the location of upcoming events, as text and as coordinates
- your last known position, as a hint for finding the right place when the app looks up an event’s address
- the travel mode and the planned arrival time
- your device language
- your API key; the provider also receives your IP address
TomTom or Google processes this data as an independent controller, under your own account with them and under their privacy policies. The data does not pass through our servers, and we do not receive or store it. To determine your position, the app uses Google Play services where available. When you search for a default starting point, your search text is sent only to your device’s Android geocoding service, not to the routing provider. If the routing provider finds no place for an event’s address, the app also asks the Android geocoding service. On most devices this service is provided by Google.
On your device the app stores the planned trips for upcoming events, your last determined position, the coordinates found for event addresses, and the default starting point you set. Coordinates from Google are kept for up to 29 days, those from TomTom only as long as TomTom’s response allows (currently not at all), and those from the Android geocoding service for up to 7 days. The app does not keep a location history.
Legal basis: your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time by switching off Time to leave or revoking the location permission in Android’s system settings.
3.9 Advertising (free version only, Google AdMob)
The free version of the app shows ads provided by Google AdMob (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). CER+ contains no ads. Ads are never shown over the lock screen.
To deliver ads, measure them and prevent fraud, the Google Mobile Ads SDK processes data directly on your device and sends it to Google and its advertising partners: the advertising ID of your device, your IP address (from which an approximate location is derived), device and app information (device model, operating system, app version, language), and interactions with ads (views, clicks). Information may be stored on and read from your device. This data does not pass through our servers, and we do not receive it.
Consent: When you first start the app in the EEA, the UK or Switzerland, Google’s consent form (IAB Transparency and Consent Framework) asks whether you agree to personalised advertising and to storing information on your device. If you do not consent, Google shows only limited, non-personalised ads. You can change or withdraw your decision at any time in the app via the menu entry “Ad privacy settings”. You can also reset or delete your advertising ID in Android’s settings (Settings → Privacy → Ads).
Legal basis: your consent (Art. 6(1)(a) GDPR; § 25(1) TDDDG for storing and reading information on your device). For limited ads without consent, Google relies on its legitimate interest in showing and measuring ads and preventing fraud (Art. 6(1)(f) GDPR).
Google’s privacy policy: https://policies.google.com/privacy
How Google uses data from apps that use its services: https://policies.google.com/technologies/partner-sites
The list of advertising partners is shown in the consent form (“Manage options”).
4. Website & Account System
If you create an account (e.g., for feature requests), the following data is processed:
- Email address
- First name
- Last name
- Username
- Password (securely hashed)
Purpose:
- Account management
- Communication
- Feature request handling
Legal basis: Art. 6(1)(b) GDPR
5. Data Sharing
We do not sell personal data.
Users in certain US states can opt out of the sharing of personal data for targeted advertising via ‘Ad privacy settings’ in the app.
Data may be shared with:
- Service providers (e.g., Firebase)
- Authorities if legally required
If you enable the weather display, MET Norway (your IP address and approximate coordinates) and Google (coordinates for the place name, via Android’s geocoding service) receive this data directly from your device, not through our servers. It is not sold and not used for advertising.
If you enable Time to leave, TomTom or Google (whichever you chose) receives your position and the location of upcoming events directly from your device, not through our servers.
If you use the free version, Google and its advertising partners receive the data described in 3.9 directly from your device.
6. Google Services
The app may integrate with Google services, including Google Tasks APIs and Google OAuth authentication. When users choose to connect a Google account, Google may independently process personal data in accordance with Google’s Privacy Policy and Terms of Service. The provider has no control over Google’s data processing activities.
For information regarding Google’s processing of personal data, please refer to:
7. Other third party services
MET Norway (weather data)
The Norwegian Meteorological Institute acts as an independent controller for the requests it receives. According to its terms of service, it stores users’ IP addresses and the coordinates used in requests in its server logs, located in Norway. We have no access to these logs and no influence over how long they are kept. See MET Norway’s privacy information at https://www.met.no/en/About-us/privacy. Weather data: MET Norway, licensed under CC BY 4.0 and NLOD 2.0.
Android geocoding
To display the name of your location, the app uses the geocoding service of your device. On most devices this service is provided by Google, which then processes the coordinates under Google’s privacy policy (https://policies.google.com/privacy).
Routing providers (Time to leave)
TomTom (TomTom International B.V., Netherlands): https://www.tomtom.com/en_gb/privacy/, https://www.tomtom.com/en_gb/thirdpartyproductterms/
Google Maps Platform (Google): https://policies.google.com/privacy
8. International Data Transfers
Processing by Google/Firebase may occur outside the EU.
Norway is a member of the European Economic Area, so no transfer to a third country takes place when weather data is requested from MET Norway.
Transfers are based on:
- EU Standard Contractual Clauses (Art. 46 GDPR)
TomTom processes data in the EU. Requests to Google Maps Platform may be processed outside the EU.
Google may process advertising data in the USA. Google LLC is certified under the EU-US Data Privacy Framework; transfers are also covered by EU Standard Contractual Clauses.
9. Data Retention
- Account data: until deletion request
- Crash data: according to Firebase retention policies
- App data: stored locally on device
- Location data used for the weather feature (last coordinates, town name and last forecast) is stored only on your device. It is deleted when you turn off “Show weather” or uninstall the app. The app does not create a location history.
- Time-to-leave data (planned trips, your last determined position and coordinates of event addresses) is stored only on your device. Coordinates of event addresses are kept for at most 29 days (Google), as long as TomTom’s response allows (TomTom), or 7 days (Android geocoding). Everything is deleted when you switch off Time to leave or uninstall the app. The default starting point stays in the settings until you change or remove it.
- Advertising data: according to Google’s retention policies; your consent decision is stored on your device until you change it or uninstall the app.
10. Your Rights (GDPR)
You have the right to:
- Access your data (Art. 15 GDPR)
- Rectification (Art. 16)
- Deletion (Art. 17)
- Restriction (Art. 18)
- Data portability (Art. 20)
- Object (Art. 21)
To exercise your rights: frank.egger@gmail.com
11. Security
We implement appropriate technical and organizational measures, including:
- Secure password storage (hashing)
- Access restrictions
12. Children
Users under the age of 16 should only use the app with parental consent (Art. 8 GDPR).
We do not knowingly collect sensitive personal data from children.
The app is not directed at children. Ads are not intended for children under 13.
13. Changes to this Policy
We may update this Privacy Policy. Changes will be published on this page.