This Website collects some Personal Data from its Users.
Personal Data: Trackers; Usage Data
Personal Data: device information; Trackers; Usage Data
Personal Data: browser information; session statistics; Trackers; Usage Data
Personal Data: Trackers
Personal Data: language
Personal Data: email address; first name; last name; phone number
Personal Data: Trackers; Usage Data
Personal Data: Trackers; Universally unique identifier (UUID); Usage Data
Personal Data: Trackers
Personal Data: Usage Data
Personal Data: email address; Usage Data
Personal Data: Trackers; Usage Data
Personal Data: answers to questions; clicks; keypress events; motion sensor events; mouse movements; scroll position; touch events; Trackers; Usage Data
Personal Data: Trackers
Personal Data: various types of Data as specified in the privacy policy of the service
Personal Data: company name; email address; first name; last name; phone number
In addition to any opt-out feature provided by any of the services listed in this document, Users may learn more on how to generally opt out of interest-based advertising within the dedicated section of the Cookie Policy.
On the ZEP trial registration page, a website visitor ("Interested Party") can register for a free 30-day running ZEP trial.
A ZEP Trial is personal and can be accessed and viewed by the user only with the user's credentials. A ZEP test version is fully equivalent to a productive ZEP instance and differs from it only in the test identification, which expires automatically after 30 days, as well as the possibility that the user can switch modules on or off during the test phase in order to get to know them.
The following information is required to create a ZEP trial:
- Company name. The user must enter a company name, but this name is not validated and can be an imaginary name. It is used to create a unique call name for the user's trial version.
- Email address. The user's email address will be used to send him/her the access data, as well as to contact him/her during the ZEP trial period to offer assistance.
During registration a prospective customer can provide the following optional information:
- Salutation (Mr./Mrs.), surname and first name: in order to be able to address the interested party specifically in mails.
- Phone number: the phone number where the user can be reached, e.g. to arrange the appointment for an online presentation
- Checkbox, whether there is interest in an online presentation of ZEP.
After registration, the data will be used to automatically provide the interested party
- to create the prospective customer with exclusively the above mentioned data for the purpose of contract initiation in the provantis CRM,
- to create a personal ZEP test version for him,
- to send him the access data to his test version by e-mail,
- and to pre-populate the mask for the creation of the first ZEP user with this data as far as possible.
If the customer decides against ZEP or lets his ZEP test version expire without feedback, all data as well as the test version with possible test data already created in it by the interested party will be deleted automatically and irretrievably from all our systems within 30 days after expiration of the test version.
The ZEP-Apps (ZEP2 and ZEP Clock) are used for convenient, mobile recording and changing of time bookings, receipts (ZEP2), etc. on a mobile device (smartphone) and synchronises them with the cloud solutions ZEP or ZEP Clock respectively. To use the apps, an active and valid ZEP or ZEP Clock rental, purchase or trial version is required, as well as a valid ZEP or ZEP Clock access. A user can connect the apps with his ZEP, access data for himself with ZEP and then also create, change or delete his time bookings and receipts (ZEP2) via the apps.
Description of the types of data collected by the apps and access rights
The apps are used to record time bookings and receipts (ZEP2) by the user. When logging in, the access data that the user also provides to log in to the respective cloud solution must be entered. These are stored in the app and are transmitted to ZEP in encrypted form for authentication with each request. The app does not log, collect, store or send any device, contact, movement or personal data.
Access to the Internet (WiFi, wireless network): Used to synchronise the data recorded by the user with the apps with ZEP.
Access to the camera:
• Scanning the QR code with the ZEP access data: this is a comfort feature through which the ZEP access data (call URL and user name) can be read in from the ZEP account via a QR code and thus do not have to be typed in. The QR code is only displayed to a user after logging into the ZEP web frontend.
• Photographing receipts (ZEP2): when entering receipts, a photo of the receipt can be taken via the camera and linked to the receipt data. The picture is transmitted to ZEP together with the receipt data.
Access to the photo archive / photo gallery: When creating a receipt, it can be linked to a photo of the receipt from the photo archive. The image is synchronised with the receipt data to ZEP.
Access to the calendar (ZEP2): If access to the calendar is enabled, appointments from the calendar can be transferred to time bookings in ZEP. In doing so, the start and end time of the appointment as well as its title are transferred to the time booking. The app neither enters appointments in the calendar nor changes appointments, there is only a reading access.
Access to location services:
• ZEP2: If access to the location services is enabled, the app can optionally determine the distance travelled in stopwatch mode. This is used to create a travel booking (for business trips) and to preset it with the distance travelled determined in this way. In addition, an attempt is made via reverse geocoding to determine the name of the starting point and the destination and to transfer these to the travel booking as well. The determined geo-positions are not saved, not used further and not transferred to ZEP.
• ZEP Clock: In the device management, administrators can request that a device transmits its location when the user clocks in and out. The respective user must then consciously agree to this within the app so that the location can be determined and sent to ZEP.
Access to the phone: Is used to call ZEP Support in the support area by tapping the displayed phone number.
Access to "external memory" (ZEP2 Android): Needed on older Android versions to temporarily store images attached to a receipt in the app's memory.
Access to vibration alarm (Android): Is required to signal the successful reading of the QR code with a short vibration.
Storage period
The data collected with the app is synchronised with ZEP and stored there for evaluations via the ZEP frontend, billing to customers, etc. in terms of ZEP use. The collected data is permanently stored in ZEP as long as ZEP is used, i.e. as long as the cloud version is booked or the test version is active.
Transmission to third parties and their purpose
All data collected with the app is synchronised exclusively with the user's ZEP access, stored in ZEP and not passed on to third parties.
ZEP GmbH
Stuttgarter Str. 41
71254 Ditzingen
Germany
Owner contact email: support@zep.de