The use of the application Vehicles Cloud® (the app) on the running iOS® device (the device) takes place thanks to the iCloud® account of the authenticated user at launch time (the user). The owner of the device takes on all the responsibilities for the information uploaded, collected and processed by the user. The owner of the device undertakes to prevent acts of negligence or bad faith in order to protect the data contained in the database.
This document describes the functionality of the app, the data storage, the permissions required by the app, the in-app purchases offered and the data processing.
The purpose of the app is to register and schedule events on a calendar created for each vehicle. The user can share his/her vehicles with other people (the participants) in order to allow them to collaborate and can receive shared vehicles from other people too (the owners). The user can add his/her vehicles in the garage, attach images to the vehicles and create events in the calendar containing lists, notes and images as attachments. Each event can be shown or hidden to the participants. The user can access the vehicles he/she is collaborating on and get the information about the details, the public events in the calendar and see the pictures and, according to the permission, he/she could create new events too.
The user can search the service points by location and distance and receive certified services by professional users.
In the free version, the user can keep only one vehicle in his/her garage.
The app has been designed for CloudKit® to keep the data updated on the user’s iOS devices and to allow users to share their vehicles. According to Apple® documentation, CloudKit apps store data in iCloud®:
“CloudKit provides a way to store data as records in a database. It is a service for moving data to and from iCloud and sharing data between users of the app. Data is segregated and encapsulated in partitions called containers.”
The app stores data in the public database when the user register as Service Point while other data related to the user’s vehicles and events is stored in the private database. Only the user can edit content on the private database.
“Each container has links to a public and private database for storing data. The contents of the public database are accessible to all the users of the app, whereas the contents of the private database are by default visible only to the current user. […] There’s a private database for each user of the app, but the app only has access to the private database of the current user. […] The private database is available only if the device has an active iCloud account. Access to the database is limited to the user of that iCloud account by default. The current user owns all content in the private database and is allowed to read and write that content. Data in the private database is not visible in the developer portal or to any other user. […]”
Data that resides in the public database is attributed to the app quota on iCloud. Data that resides in the private database is attributed to the user's personal storage quota on iCloud.
“The data in a public database counts against the iCloud storage quota of the app. Data in the private database counts against the user’s iCloud storage quota.”
There is also a shared database, that is available only if the device has an active iCloud account. When the user shares vehicles with other people, participants are added with the default permission Read-Write. A participant can access the shared database to read the content of each shared vehicle and to create new events, if they can. Only the owner of the vehicle can change the permission (from Read-Write to Read-Only and vice versa) or add and remove the participants.
“The shared database is available only if the device has an active iCloud account. Permissions on the database are limited to the user based on the permissions of the record that has been shared. The current user does not own the content in the shared database and is allowed to read that content only if the permission has been granted […]. Data in the shared database is not visible in the developer portal or to any user who has not been granted access. Data stored in the shared database does not count against the storage quota of the current user’s iCloud account.”
This app will request access to:
iCloud Photos to attach pictures to the vehicles and to the events
Notifications to add to the app’s icon the badge with the number of new events created by the participants
The user can purchase Garage Unlock to get enabled to add multiple vehicles in his/her garage.
The professional user can purchase Service Point to get enabled to certify the services he/she registers in his/her name on behalf of the owners and to create a public profile visible by all the users of the app.
To proceed with the purchase, the user can buy the IAP from the app or directly from the App Store.
The in-app purchase has no expiring date, however it must be restored when the users installs the app on a device or launches the app when is logged in to iCloud from another device. Restore is a free operation that will get the IAP working on that device.
By using the app, the user accepts all the conditions above mentioned and becomes the only person responsible of the stored and shared data. There is no other data processing but the one provided by the app. There is no commercial or advertising purposes, the user's personal data are not disclosed, no registration or subscription is asked for newsletters or other service for marketing, research o analysis, therefore no authorization is required on the use of personal information. Any misuse or abuse of the user's personal data by other users or other persons, companies, organisations outside the context and functionality described in this document cannot be directly or indirectly attributed to the developer of the app, nor to the producer of the device or to the owner of the operating system copyrights.