AlpGrid Privacy Policy
1. Who is responsible?
The controller for the processing of your data in AlpGrid is MaDaTo UG, which operates the app:
MaDaTo UG (haftungsbeschränkt)Trienter Str. 25, 86316 Friedberg, Germany
Contact for the app and data protection: info@alpgrid.app
Legal notice: madato.eu/impressum
Your owners' association decides to use AlpGrid for your property and concludes the contract with us for this purpose. It does not transfer any personal data to us and does not receive any data about individual persons or reservations from us. We use your data solely to operate the app for your property – not for advertising and not for analyses of individuals.
We have not appointed a data protection officer because the legal requirements are not met. No representative in Switzerland under Art. 14 of the Swiss Federal Act on Data Protection (FADP) has been designated, as there is no extensive processing involving high risk.
This policy applies under the General Data Protection Regulation (GDPR) and the Swiss Federal Act on Data Protection (FADP).
2. Where we get your data from
From you. Your property management does not transfer any names or email addresses to us. It receives an activation code for each parking space from us and passes it on to the entitled person. Anyone who wishes to participate creates an account in the app and enters a display name and their email address themselves.
If you do not wish to participate, simply do not redeem the activation code. We then learn nothing about you, and your parking space is not available to others.
Invitations: A main user can invite further persons to their parking space (co-users). To do so, they enter the person's email address; we send an invitation code to that address. The email states the name of the inviting person; a reply goes to that person's email address. The invited person then creates their account themselves. Please only invite people who agree to this. The app is intended for adults.
3. What data we process and why
| Data | Purpose |
|---|---|
| Display name, email address, password (stored only as an encrypted hash) | Account, sign-in, password reset, notifications |
| Language setting (German, English or Italian) | Notifications in your language |
| Assigned parking space, role (main user/co-user), property | Core function of the app |
| Reservations and own stays: parking space, period, planned wallbox charging times | Allocation of parking spaces and wallboxes |
| Invitations: email address of the invited person, parking space, validity | Delivery of the invitation code |
| Times of sent invitation emails | Protection against misuse: at most 5 invitation emails per hour and 20 per day |
| Push token and app installation ID | Delivery of push notifications |
| Technical logs: time, internal identifiers (account, property, parking space, reservation), parking space number and period of an operation, shortened email address when sending emails, error messages | Operational security and troubleshooting |
Notifications: If your reservation is rebooked or cancelled, you receive an email with a personal salutation, the parking space and the period and – if you have allowed this on your device – a push notification with the new parking space. No notification states a reason or names other persons. Without push permission, the app continues to work fully.
On your device, the app stores your sign-in and the selected language; the operating system manages the identifier for push notifications. The sign-in is removed when you sign out, everything else when you delete the app. This data is not included in device backups.
Legal bases (GDPR): We process account, parking space, reservations, stays, notifications and push notifications to enable you to use the app, which you start by registering (Art. 6(1)(b)). Invitations to co-users, technical logs, backups, the lock after failed attempts, the limit on invitation emails and the aggregated figures are based on our legitimate interest and that of your association in secure operation and in inviting co-users (Art. 6(1)(f)). Storage on your device is strictly necessary for the use you have requested (Section 25(2) No. 2 TDDDG).
What we do not process: no location data, no payment data, no consumption or charging data of the wallboxes, no access to camera, microphone, contacts or photos. We use no analytics, advertising or tracking services.
Aggregated figures: For the owners' meeting, we count per property and calendar year, for example, how many reservations, stays and charging times there were and how high the occupancy was. These figures contain no persons and no individual parking spaces. So that different parking spaces are only counted once, we internally keep a list of the parking space identifiers of the current year; it is not passed on and is deleted at the end of January of the following year.
4. Where data is processed and who receives it
Your reservations, stays, parking space data and your user profile are stored and processed in a Google data centre in Zurich (Switzerland). The server functions that process reservations, the technical logs and the backups also run there.
We use the following service providers, who process data on our behalf:
| Service provider | Service | Location |
|---|---|---|
| Google (Firebase, Google Cloud; contracting party Google Ireland Limited or Google Cloud EMEA Limited, Dublin, Ireland) | Database, server functions, logs, backups | Zurich, Switzerland |
| Google (Firebase Authentication) | Sign-in and sending of the emails for confirming the email address and resetting the password: email address, password hash, sign-in times; IP address and technical device information to prevent abuse | worldwide, including the USA |
| Google (Firebase Cloud Messaging) and Apple (Apple Push Notification Service) | Delivery of push notifications: push token, app installation ID, notification text and internal reservation identifier; device model, operating system and app version, language, time zone | worldwide, including the USA |
| IONOS SE, Montabaur | Sending of all other emails (invitations, rebookings, cancellations, account notices) | Germany |
Transfer to the USA: For sign-in and push notifications, data is also processed in the USA. Google LLC is certified under the EU-U.S. Data Privacy Framework and the Swiss-U.S. Data Privacy Framework; adequacy decisions of the EU Commission and the Swiss Federal Council exist for both frameworks. In addition, the EU Standard Contractual Clauses in Google's contractual terms apply. For Apple, the EU Standard Contractual Clauses apply.
5. How long we store data
| Data | Retention period |
|---|---|
| Account | until you delete it or your access to the property ends; if the contract with your association ends, we delete all data of the property within 30 days |
| Account without an assigned parking space | 90 days after registration; you receive a reminder by email one week beforehand |
| Sign-in account whose registration was not completed | 90 days after creation, without a reminder |
| Reservations and stays | deleted two days after departure |
| Invitation (email address of the invited person, code), not accepted | deleted after 14 days |
| Invitation, accepted | the invitation record is deleted 30 days after acceptance; the invited person's account remains |
| Failed code entry attempts | deleted one day after the last attempt |
| Times of sent invitation emails | no longer used after 24 hours and deleted after two days at the latest |
| Push token | until you sign out or delete your account; a token that has become invalid, for example after the app has been deleted, is removed at the next delivery attempt, at the latest together with the account |
| Technical logs | 30 days |
| Backups | deleted data may still be contained in them for up to 30 days; they are used only for restoration after an error |
| Internal counting list of parking space identifiers | until the end of January of the following year |
6. What other users see
Other users of your property see which parking spaces are occupied during which period. On their own parking space, an owner sees that and when another person has made a reservation – marked with that person's parking space number, not their name. Names are only visible within your own parking space (main user and co-users); the main user additionally sees the email addresses of their co-users and open invitations.
It is not visible who is using an occupied space – the owner or another person – or why a space is unavailable. Others only see that a space is occupied or unavailable; reservations and stays of other parking spaces cannot be retrieved by them.
Your property management has no access to the app and does not see any reservations. At most, it receives the aggregated figures from section 3.
If several persons use a shared access, they all see the same entries; it is then not possible to attribute an entry to a specific person. Anyone who wants separate attribution can be invited as a co-user with their own access.
7. Deletion and your rights
Delete account: at any time yourself in the app under “My Profile” → “Delete account”. Your account and your reservations are deleted immediately.
For main users: If you delete your account, the accounts of the co-users you invited are deleted as well. The app shows you those affected beforehand; they receive an email.
For co-users: If you delete your account, we inform the main user of your parking space by email, stating your name.
Without access to the app: via madato.eu/alpgrid/loeschanfrage or by email to info@alpgrid.app. To prevent anyone from having other people's accounts deleted, we only process requests that come from the registered email address or are confirmed there.
Your rights: access, rectification, erasure, restriction of processing, data portability and objection to processing based on our legitimate interest. Please contact info@alpgrid.app.
Complaints to a data protection authority, for example:
- Switzerland: Federal Data Protection and Information Commissioner (FDPIC)
- Germany: Bavarian State Office for Data Protection Supervision (BayLDA), responsible for us
- Austria: Austrian Data Protection Authority
- Italy: Garante per la protezione dei dati personali
8. Security
Transmissions are encrypted (TLS). Each user can technically only read data of their own property. Passwords are stored only as hashes. Administrative access is limited to the shareholders of MaDaTo UG via an account secured with two-factor authentication. In technical logs, email addresses and codes are stored only in shortened form.
9. Changes
We adapt this policy when the app or the legal situation changes. The version published here applies. We inform you of material changes by email.
Last updated: 8 November 2026