Privacy policy velowire app
velowire hereby informs you that the velowire app collects data for the following purposes:
In the future, the app will also allow to add comments in order to react to publications, photos and cycling races in the UCI cycling calendar. Your personal information will be collected for that and this privacy policy will be updated accordingly at that time.
App usage analytics
Usage analytics of the velowire app are captured using Google Analytics. On iOS, usage and diagnostics information of the Firebase SDK are also logged by Firebase. Therefore, Google is processing these usage data. This use complies with the EU-U.S. and Swiss-U.S. Data Privacy Frameworks (DPF) and the UK Extension to the EU-U.S. DPF as set forth by the US Department of Commerce regarding the collection, use and retention of personal information from the EEA, Switzerland and the UK, respectively. Google LLC (and its wholly-owned US subsidiaries unless explicitly excluded) has certified that it adheres to the DPF Principles. The way Google uses these data is described here.
Crash data
The velowire app is using Crashlytics in order to determine any crashes of the app and their reasons. This data is used in order to improve the app and make sure we'll be able to remove any bugs and other problems in the app.
Data collected by Crashlytics include (non-exhaustive list):
- An RFC-4122 UUID which permits us to deduplicate crashes (UUID means Unique User Identifier, an identifier which can uniquely identify a user of the app, but without a relation to his personal data)
- The Crashlytics Installation UUID
- The Firebase installations ID (FID)
- The Firebase session ID, which is a random UUID generated to tag events with a session
- The timestamp of when the crash occurred
- The app's bundle identifier and full version number
- The device's operating system name and version number
- A boolean indicating whether the device was jailbroken/rooted
- The device's model name, CPU architecture, amount of RAM and disk space
- The uint64 instruction pointer of every frame of every currently running thread
- If available in the runtime, the plain-text method or function name containing each instruction pointer
- If an exception was thrown, the plain-text class name and message value of the exception
- If a fatal signal was raised, its name and integer code
- For each binary image loaded into the application, its name, UUID, byte size, and the uint64 base address at which it was loaded into RAM
- A boolean indicating whether or not the app was in the background at the time it crashed
- An integer value indicating the rotation of the screen at the time of crash
- A boolean indicating whether the device's proximity sensor was triggered
Velowire is using these data anonymously, only for the purposes of debugging and correcting any bugs or other crash situations.
The way Google uses these data is described here.
Advertising
The velowire app is using Google's Admob for advertising. It therefore collects information for personalised advertising. A detailed and dedicated privacy message will be added to the app before it's official release. This message will allow the user to consent to data collection or not.