Privacy Policy

Please read these Terms and Conditions ("Terms", "Terms and Conditions") carefully before using the AOD App (the "Service") operated by PrXenon ("us", "we", or "our").

Your access to and use of the Service is conditioned on your acceptance of and compliance with these Terms. These Terms apply to all visitors, users and others who access or use the Service.

By accessing or using the Service you agree to be bound by these Terms. If you disagree with any part of the terms then you may not access the Services.

We use your data to provide and improve the Service. By using the Service, you agree to the collection and use of information in accordance with this policy. Unless otherwise defined in this Privacy Policy, terms used in this Privacy Policy have the same meanings as in our Terms and Conditions.


When you create an account with us, you must provide us information that is accurate, complete, and current at all times. Failure to do so constitutes a breach of the Terms, which may result in immediate termination of your account on our Service. You can create an account only with Google! After you confirm the Google login consent we will pull personal data from Google+ API. We fetch the following fields for persistent storage in your account:

Information Collection And Use


We may collect personal identification information from Users in a variety of ways, including, but not limited to, when Users using the app, register, and in connection with other activities, services, features or resources we make available. Users may be asked for, as appropriate, name, email address, mailing address, social security number. We will collect personal identification information from Users only if they voluntarily submit such information to us.

  • Installation UUID
  • Google-ID
  • Connected e-mail address
  • Full name
  • Profile picture


We may ask for your Ingress agentname (ingame name) and your Ingress Faction. You agree that we may use this data in our service without restriction. While using our service, you must provide Ingress profile screenshots. We evaluate this screenshot and save the values belonging to the task. Your screenshot will default not be saved on our servers and will not be uploaded.

  • Agentname
  • Faction
  • differnet badge values


We may collect non-personal identification information about Users whenever they interact with our Service. Non-personal identification information may include the browser name, the type of device and technical information about Users means of connection to our Service, such as the operating system and the Internet service providers utilized and other similar information.

  • IP adress
  • Cookies
  • Device data

Usage Data


Our Service may collect and use Users personal information for the following purposes:

  • To run and operate our Service
  • We may need your information display content correctly.
  • To improve customer service
  • Information you provide helps us respond to your customer service requests and support needs more efficiently.
  • To personalize user experience
  • We may use information in the aggregate to understand how our Users as a group use the services and resources.
  • To improve our Service
  • We may use feedback you provide to improve our products and services.
  • We may use your informations for sending push notifications
  • We may use the email address to send User information and updates. It may also be used to respond to their inquiries, questions, and/or other requests.
  • We may use your agent name or/and email to identify you on third party sites, services or apps connected with us. You can find a full list of all connected sites, services and apps. We always will aks before we connect with third party sites, services or apps.


We adopt appropriate data collection, storage and processing practices and security measures to protect against unauthorized access, alteration, disclosure or destruction of your personal information, username transaction information and data stored in our Service.

For more informations visit


We do NOT sell, trade, or rent Users personal identification information to others! We NOT share generic aggregated demographic information not linked to any personal identification information regarding visitors and users with other Ingress related apps or services, trusted affiliates and advertisers for the purposes outlined above. You can connect to affiliate applications. We show you which information is passed on to integrate partner applications into our service. You can revoke these connections at any time.



We are using Fabric (Firebase) Crashlytics. Crashes may be sent automatically. Crashes contain device-specific information to improve our service. Personal data:

  • Installation UUID
  • Crash traces (Crash traces and their associated identifiers are kept for 90 days.)

#FIREBASE Authentication (Google only)

Personal data:

  • User agent
  • IP addresses
  • Email address

Firebase Authentication keeps logged IP addresses for a few weeks. It retains other authentication information until the Firebase customer initiates deletion of the associated user, after which data is removed from live and backup systems within 180 days.

#FIREBASE Cloud Messaging

Personal data:

  • Instance IDs (After the call, data is removed from live and backup systems within 180 days)

#FIREBASE Realtime Database

Personal data:

  • User agent
  • IP addresses

Realtime Database keeps IP addresses and user agent information for a few days, unless a customer chooses to save it for longer.

#FIREBASE Performance Monitoring

Personal data:

  • Instance IDs
  • IP addresses

Performance Monitoring keeps instance and IP-associated events for 30 days and de-identified performance data for 180 days. Firebase retains Instance IDs until the Firebase customer makes an API call to delete the ID. After the call, data is removed from live and backup systems within 180 days.

#FIREBASE Remote Config

Personal data:

  • Instance IDs

Firebase retains Instance IDs until the Firebase customer makes an API call to delete the ID. After the call, data is removed from live and backup systems within 180 days.


no Personal data used (offline usage no cloud based APIs used)

#Data Processing and Security Terms

When customers use Firebase, Google is generally a data processor and processes personal data on their behalf. Firebase terms include Data Processing and Security Terms for all Firebase services, effective May 25, 2018.

#ISO and SOC compliance

Firebase is certified under major privacy and security standards.

  • Firebase Realtime Database: ISO 27001, SOC 1, SOC 2, SOC 3.
  • Firebase Remote Config: ISO 27001, SOC 1, SOC 2, SOC 3.
  • Cloud Storage for Firebase: ISO 27001, ISO 27017, ISO 27018, SOC 1, SOC 2, SOC 3.
  • Firebase Authentication: ISO 27001, ISO 27017, ISO 27018, SOC 1, SOC 2, SOC 3.


We may modify these Terms at any time. If we do so, we’ll let you know either by posting the modified Terms on the App or through other communications. It’s important that you review the Terms whenever we modify them because if you continue to use the Services after we have posted modified Terms on the Site or App, or otherwise communicate them to you, you are indicating to us that you agree to be bound by the modified Terms. If you don’t agree to be bound by the modified Terms, then you may not use the Services anymore. Because our Services evolve over time we may change or discontinue all or any part of the Services, at any time and without notice.


Our Service accepts the Niantic "Ingress Terms of Service" (Last Modified: October 1, 2018) and the "Ingress-Community-Guidelines".
Ingress Logo and Ingress Mission Day Logo are trademarks of Niantic.
This service is not affiliated with Niantic!

This terms are only valid for content created and provided by the service owner. It does not apply for any other linked website, apps, services or assets.

If you have any questions about this Privacy Policy, the practices of this Service, or your dealings with this Service, please contact us (Jonas Eisenmann). Contact by e-mail [email protected] or Telegram: @PrXenon

This document was last updated on January 30, 2019