Privacy Policy
Applies to the Android apps ENL NF (com.enlnf) and NF (com.nf), version 3.0 and newer, and to this website. Last updated: 16 October 2026.
- There is no account, no login and no advertising.
- Your attacks, filters and messages are stored on your phone and are not sent to the developer.
- Crash reports (Firebase Crashlytics) and anonymous usage statistics (Firebase Analytics) are sent to Google. The statistics can be switched off in the settings.
- The Google Drive backup is optional and uses your own Drive.
1. Who is responsible
Oliwer Christ, who goes by 1110101
Kleegartenstraße 16, 69207 Sandhausen, Germany
Contact: help@enlnf.link. See also the Impressum.
2. What the app processes on your device
The app needs notification access, so Android can hand it the notifications of other apps. It only evaluates notifications of the Ingress app (com.nianticproject.ingress) and its own test notifications, and ignores all others. From an Ingress notification it reads the type, the text, portal name and address, the player name and the time. It can also dismiss an Ingress notification after it has processed it.
The result is stored in a local database in the app: the attacks, messages and achievements, plus your filters and filter groups with their settings. This data stays on your phone. It is deleted when you clear the app data or uninstall the app. You can delete single entries in the app.
Permissions
| Permission | Why |
|---|---|
| Notification access | Read Ingress notifications, see above |
| Post notifications, vibrate, wake lock, full-screen intent | Show filtered alerts and, for groups where you turned it on, wake the phone and open Ingress |
| Ignore battery optimizations | Optional request, so Android does not stop the background service |
| Receive boot completed | Restart the background tasks after a reboot |
| Internet, network state | Google Drive backup, crash reports, usage statistics, donations |
| Billing | Optional donations through Google Play |
The app does not use the advertising ID, location, contacts, the camera, the microphone or the phone's storage.
3. What leaves your device
Crash reports (Firebase Crashlytics, Google)
If the app crashes or an error is logged, Crashlytics receives the error trace, the app version, the device model, the Android version, the state of the device and a random installation ID. This is how I find and fix bugs. It is switched off in debug builds. There is no switch for it in the app. If you want to prevent it, uninstall the app or contact me.
Anonymous usage statistics (Firebase Analytics, Google)
The app records which screens are used and a few actions, for example creating a filter, together with a random app instance ID, device and Android information and the approximate region taken from the IP address (the IP address itself is not stored). The advertising ID is not collected. I use this to decide which features are worth working on. You can switch it off under Settings, Anonymous usage reporting.
Google Play services and Firebase
The Firebase libraries create an installation ID and can receive push messages from Firebase Cloud Messaging. I use this at most to inform users of the app about important changes, for example a new version. Messages like this carry no personal data.
Google Drive backup (optional)
If you tap sign in in the backup screen, the app asks Google for access to Google Drive. It uses the narrow permissions to files the app created itself and to its own app data folder, not to your other files. The backup contains your filters, filter groups and the stored attacks and messages and is uploaded to your Drive. The app reads the email address of the account only to show it on the screen. You can sign out and delete the backups in the app, and at any time in your Google account settings.
Donations (optional)
Donations are handled by Google Play. I only get the information Google Play shows me for a purchase. I receive no payment data.
4. Legal bases (GDPR)
- Notification access, local storage: Art. 6 (1) b, to provide the function you installed the app for.
- Crash reports: Art. 6 (1) f, my legitimate interest in a stable app.
- Usage statistics: Art. 6 (1) f, my interest in improving the app. You can object at any time by switching it off in the settings.
- Google Drive backup: Art. 6 (1) a, your consent when you sign in. You can withdraw it by signing out.
5. Recipients and transfers
Google is the recipient for Crashlytics, Analytics, Cloud Messaging, Google Drive and Google Play. Google can process data in the USA and other countries and relies on the EU-US Data Privacy Framework and standard contractual clauses. More information: policies.google.com/privacy and firebase.google.com/support/privacy. I pass data to nobody else and do not sell it.
6. How long data is stored
Data on your phone stays until you delete it. Crashlytics and Analytics data is deleted automatically by Google after the retention period configured in Firebase. Drive backups stay in your Drive until you delete them.
7. Your rights
You have the right to access, rectification, erasure, restriction of processing, data portability and objection. Write to help@enlnf.link. Because the app uses random IDs and no account, I can only find your Crashlytics or Analytics data if you tell me your installation ID. The IDs can be reset by clearing the app data. You can also complain to a data protection authority, for example the Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg (baden-wuerttemberg.datenschutz.de).
8. Website enlnf.link
This website sets no cookies and uses no trackers. All pages load nothing from third parties. The web server of the hosting provider logs the IP address, the time and the requested file when you visit a page or download the APK. These logs are kept according to the provider's own rules and are used to run the server and to defend against abuse.
9. Children
The apps are not directed at children under 16.
10. Changes
I update this policy when the apps change. The date at the top shows the current version.