Skip to content
FYRAVUE
HomeSupportLegal noticeDE
FYRAVUE app & website

Privacy Policy

Information about personal-data processing in FYRAVUE and on fyravue.de.

Last updated: 7 September 2026

1. Data controller

Manuel Knakowski
Privacy email: privacy@fyravue.de
General contact: info@fyravue.de

2. General principle

FYRAVUE works without its own user account. Saved places, radii, favourites, filters, map settings and local event states are generally stored on the device. The developer cannot access this local data. The app displays Google AdMob banner advertising in selected views; the map remains ad-free. Section 7 explains the associated processing and consent management.

3. Location and saved places

If you allow location access, FYRAVUE can show your current location on the map and evaluate events within the selected radius. The app requests only the iOS location access intended for its features. Location use is optional; places may be searched and saved instead.

Saved places, watch radii, the latest known device location and local state used to avoid repeated notifications remain on the device. You can delete saved places in the app and change location permission in iOS Settings at any time.

FYRAVUE uses Apple MapKit to resolve places entered in search and to display a satellite view of a fire event when requested. The search request or requested map area is transmitted to Apple for that purpose. Saved watch radii, user-assigned place names and a dedicated FYRAVUE device identifier are not included. Apple's privacy information also applies.

4. External data sources and connection data

FYRAVUE retrieves public map, fire, air-quality and smoke data. When a resource is requested, the relevant provider may process technically necessary connection data such as IP address, time, device/app information and the requested resource.

  • NASA LANCE FIRMS: download of worldwide active-fire data. Saved watched places are not sent to NASA.
  • Copernicus Atmosphere Monitoring Service (CAMS) / ECMWF: FYRAVUE currently requests the public CAMS map services directly. Map-image requests contain the requested map area; a coordinate or derived query position is transmitted for a selected map point or watched place. User-assigned place names, watch radii, account data and a dedicated FYRAVUE device identifier are not included. CAMS/ECMWF may log technically necessary connection data, including the IP address, and use it under its own terms. The CAMS data protection and privacy statement and the ECMWF terms of use apply.
  • OpenFreeMap/OpenStreetMap: delivery of the map style and map tiles; the provider receives the technically necessary request including IP address.

Processing is necessary to provide the app functions requested by the user. Depending on the provider, processing outside the European Economic Area cannot be excluded; the safeguards and privacy terms of the relevant provider then apply.

5. Notifications and background refresh

With your permission, FYRAVUE can display local notifications about confirmed changes in watched areas. The calculation and necessary state are stored on the device. iOS controls permissions, background refresh and delivery time. Notifications can be disabled in iOS Settings at any time.

6. Widgets and App Group

The app and widget extension share only the data needed to display selected places and status values in a protected Apple App Group on your device. This shared storage is used solely for widget functionality and is not transmitted to the developer.

7. Google AdMob advertising and consent management

FYRAVUE uses Google AdMob and the Google User Messaging Platform (UMP). For users in the European Economic Area, the provider is generally Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Depending on the service and processing, Google LLC and advertising partners named by Google or in the consent form may also be involved.

Before the first ad request, UMP updates the consent status and, where required for the user's region and the configured messages, presents a consent form. Depending on region and choice, personalised, non-personalised or limited ads may be served. Personalised ads may be based on previous activity, inferred interests, approximate location, device and app information, and other signals described in the consent form.

According to Google, the following data in particular may be processed:

  • IP address and an approximate region derived from it, device, operating-system and app information, and app- or device-related identifiers,
  • advertising data such as ads delivered or clicked and interactions with the app or advertisement,
  • crash, performance and other diagnostic data.

The processing is used for ad selection, personalisation, technical delivery and frequency controls, fraud and abuse prevention, measurement and billing. Where consent is required, processing is based on Article 6(1)(a) GDPR and applicable rules governing access to terminal equipment. Technically necessary processing and security measures may be based on Article 6(1)(f) GDPR.

After the required UMP flow, and while no decision has yet been made, FYRAVUE also requests authorisation through Apple's AppTrackingTransparency framework (ATT). Only when permission is granted can AdMob access the IDFA advertising identifier and link activity from FYRAVUE with data from other companies' apps, websites or offline properties for personalised advertising or advertising measurement. The Google Mobile Ads SDK publisher first-party ID is enabled and may be used to deliver more relevant advertising based on data from FYRAVUE. If ATT permission is denied, no IDFA is provided; ads may still be served without the IDFA within the scope of the user's other choices.

Where UMP requires it for the user's region, choices made there can be changed or withdrawn at any time in “About FYRAVUE” under “Privacy and cookie settings”. ATT permission can be changed separately in iOS Settings under “Privacy & Security” → “Tracking”. Withdrawal applies to future processing and does not affect earlier processing. After a refusal, the app may display non-personalised or limited ads where legally and technically permitted.

Google may process data outside the European Economic Area. Google's Privacy Policy and information on how Google uses information from sites or apps that use its services explain recipients, transfer safeguards, retention and data-subject rights. Through AdMob, the developer generally receives aggregated reports about ad performance and revenue, but cannot access places stored locally in FYRAVUE or the device's precise location.

8. App Store and TestFlight

When downloading, purchasing or beta testing the app, Apple processes data under its own terms, such as Apple ID/purchase data, device information, installations, sessions, crashes and voluntary feedback. Depending on the invitation method, a TestFlight tester's name and email may be visible in App Store Connect. Apple's TestFlight terms and privacy information apply.

9. Delivery of this website

When fyravue.de is requested, the web server processes technically necessary connection data, particularly IP address, date and time, requested resource, browser/device information and transmission status. This is required to deliver and secure the website and is based on the legitimate interest in a secure, functional web service (Article 6(1)(f) GDPR).

Hosting provider: STRATO GmbH, Otto-Ostrowski-Straße 7, 10249 Berlin, Germany. According to the provider, host names or IP addresses are anonymised in access logs available to customers; log availability is limited depending on type. See the STRATO privacy policy.

This website currently integrates no analytics, tracking, advertising or social-media services, loads no third-party fonts and sets no non-essential cookies.

To remember your privacy selection, an entry named fyravue-consent-v1 is stored in local browser storage. It contains the selected categories, consent version, save time and expiry time. The setting is retained for no more than 180 days and is strictly necessary so that your choice is respected on later visits. You can change it at any time through “Cookie settings” in the footer.

The optional “Analytics” and “External media” categories are disabled by default. No service is currently integrated in either category. If optional services are added later, they will only be loaded after your consent.

10. Retention and deletion

Local places, radii, favourites and app settings can be deleted or reset in FYRAVUE. Deleting the app removes its local app data; data in iCloud/device backups is governed by Apple settings. Website server logs are retained only as long as required for operation, security and applicable legal obligations.

11. Data subject rights

Where legal requirements are met, data subjects may have rights of access, rectification, erasure, restriction, portability and objection. Consent may be withdrawn for the future. A complaint may also be lodged with a competent data protection authority.

Please send requests to privacy@fyravue.de.

12. Changes

This policy will be updated when features, services or legal requirements change. The current version remains available at this address.

FYRAVUEPrivacy-friendly and without user accounts.
HomeSupportLegal noticeSources & licences
© 2026 Manuel Knakowski