Swavia app Usage, Privacy and Data Protection terms and conditions
Protecting our user’s personal data and privacy is very important to us and is described below. We follow the rule of using as minimal amount of data as possible.
1. Definitions
1.1 Swavia: the provider of Swavia app and Service:
Worldwide: Swavia Tech OÜ, Lai 6, Tartu 51005, Estonia.
Austria, Germany: Swavia Mobility GmbH, Schleifereigasse 7/2, с/o Swarovski Werk 2, 6112 Wattens, Austria.
1.2 Service: Payments for parking, based on User input on smartphone, smartwatch, or car interface or based on electronic triggers from smartphone, car, or license plate recognition. Swavia is responsible only for payments, parking service and pricing are managed by Parking Operator.
1.3 User: Private customer who uses the Service and has entered into the corresponding contract with Swavia, including the user of a company car or the self-driving car.
1.4 Device: A way in which the User uses and communicates with the Service. It can be a smartphone, smartwatch, tablet, car display, voice commands, or other technical means.
1.5 Parking Operator: Owner or the operator of parking areas, for example, city or other municipality, private land owner, including a company or private person or a company who manages parking on property owned by others.
1.6 Payment Processor: A relaying party through which the User pays for Swavia services, for example, debit or credit card company, issuing bank, payment gateway, or telecom operator.
2. Registration and account data
2.1 To use Swavia Services, the User must register as a User of Swavia. Registration can be done via Swavia app.
2.2 Personal information required on registration is:
2.2.1 User’s mobile phone number, which is used as a unique account identifier. The user’s mobile phone number will be verified with a code transferred via SMS, both on first registration and on every app activation on a new Device.
2.2.2 User’s car(s) license plate number(s).
2.2.3 If the User uses a debit or a credit bank card as a payment method, then User also inserts a name, card number, validity date, and CVC code, which are decrypted and saved as a personal token. This means that the User name and card number are not stored in Swavia system and all payments are made based on the token. Collecting, saving and processing are done by the Payment Processor.
2.2.4 Swavia can request the User’s name from the Payment processor upon request from the User, Payment Processor, or Parking Operator, if there is a case that requires further investigation. These events can be, but are not limited to:
2.2.4.1 User, Parking Operator, or Payment Processor turns to Swavia and asks for further explanations about payments made.
2.2.4.2 Legal requests for information from authorities, IE law enforcement in the event of an accident, etc.
2.2.4.3 If payments are not made on time and Swavia must initiate a debt collection procedure.
2.3 It is the User’s responsibility to ensure that account information is correct. If there is a change, the User must promptly update it through his User Account. Until change User is responsible for every payment made.
2.4 User can register several vehicles. In this case, Swavia tries to select the right vehicle automatically, but when this is not possible, the user must select the right license plate number manually.
2.5 It is the User’s responsibility to protect from unauthorized access and misuse of the access data to his account and Device and not to distribute his personal registry SMS code to the third parties.
3. Parking on street and in other open areas
3.1 On-street and open parking areas are parking places that are accessible without boom, gate, or any other physical barrier, like city streets and other open private parking areas and where session is not activatd automatically via cameras.
3.2 Swavia has three usage methods that User can select from and which work in the following ways:
3.2.1 Manually. In manual mode there is no automation and the User must start and end the payment manually.
3.2.2 Clever notifications. In clever notifications mode, Swavia gives recommendations, but the User must confirm the start or end of the payment manually.
3.2.3 Automatic. In automatic mode the parking payment is activated for the User by Swavia, using electronic signals from Swavia app or car device. In this case, User is responsible for the GPS provided by his Device. If the selected zone and payment is not correct, User is responsible for correcting or canceling it, which can be made in the first 1 (one) minute. Payment also ends automatically, but the User can end it manually at any time.
3.2.4 User can change the usage mode and other preferences by opening Swavia app settings and selecting a new method. Session start and session stop can have different usage methods.
3.3 Clever notifications and automatic mode require that User has granted Swavia a permission to track his phones location and Bluetooth. This information is analyzed to detect parking event start, stop, and location. Data is stored for 4 months in case something needs to be analyzed later. Analysis can be initiated by Swavia employees if there is an anomaly from the expected result or if the User or Parking Operator asks for it. In manual mode, location is used only for zone selection, when starting parking.
3.4 Use of the Service requires a stable (mobile) Internet connection. Only after receiving confirmation as a push notification or information in the Device screen can the User assume that his parking transaction has been initiated or terminated. Swavia is not responsible for possible fines or other actions concerning an instance of parking for the time between parking or leaving and initiating or terminating the transaction, respectively.
3.5 If parking is time-limited, then Swavia has the right to end the payment when maximum time is reached, notifying the user in advance. Swavia is not responsible for possible fines or other actions, when User parks longer, than allowed maximum parking time.
3.6 If Swavia Service is unavailable (IE you do not receive the push notification about payment start in the right zone or Swavia app does not show the parking in the right zone), for instance, due to disruptions at Swavia or network operators, the User must pay the required parking fee in another manner, for instance by purchasing a ticket from the parking machine.
3.7 Failure to adhere to the procedure for settling parking transactions may result in parking fees not being properly paid. If parking fees are not paid, this may be prosecuted by Parking Operators as an infringement of contractual duties, or by municipalities as an administrative offense.
3.8 To identify participating Swavia Users some Parking Operators require a vignette on the inside of the windshield. A list of localities requiring such vignettes is available at the Swavia website www.swavia.com. The vignette can be downloaded or ordered from Swavia.
4. Parking in gated parking areas
4.1 Off-street and gated parking areas are parking places that upon access require opening a boom, gate, or any other physical barrier.
4.2 Swavia has two usage methods that User can select from and which work in the following ways:
4.2.1 Automatic. In automatic mode the parking payment is activated for the User by Swavia, using electronic license plate recognition. In case the User wants not to use it, automation can be turned off from Swavia settings. Already initiated payment can be canceled, leaving the garage within the first 1 (one) minute.
4.2.2 Manually. The User can start and stop parking manually, including selecting a suitable gate (if there are multiple gates). Using manually can be used when the automation is switched off, if the license plate recognition is unable to identify the plate or if there is no recognition in place.
4.3 For automation, Swavia analyzes and stores camera photos on entrance and exit gates. Data is stored for 4 months in case something needs to be analyzed later. Analysis can be initiated by Swavia employees if there is an anomaly from the expected result or if User or Parking Operator asks for it.
4.4 Use of the Service in garages in automatic mode does not require a (mobile) Internet connection and works even if the phone battery is empty, if the phone is not present or even if Swavia app is deleted.
4.5 If there is no Swavia usage for 3 months, then automatic parking in parking houses will be deactivated to protect the User in case the car is sold, etc. User can re-enable it in app settings. Usage is one of the following: new registration, starting or ending parking payment, any other app usage.
4.6 If Swavia Service is unavailable (IE gate does not open), for instance, due to disruptions at Swavia or network operators, the User must pay the required parking fee in another manner, for instance by purchasing a ticket from the parking machine.
4.7 Failure to adhere to the procedure for settling parking transactions intended by these General Terms and Conditions may result in parking fees not being properly paid. If parking fees are not paid, this may be prosecuted by Parking Operators as an infringement of contractual duties, or by municipalities as an administrative offense.
5.1 Freeflow is a parking method where cameras detect the vehicle entrance and exit and the payment is made according to the time spent. It is used mostly in parking garages but can be also outdoors.
5.2 The user is billed after the session automatically, according to parking time, which is calculated from zone entry and zone exit time. Entries and exits are recognized via automatic licence plate recognition from the cameras.
5.3 If parking is time-limited, then Swavia has the right to end the payment when maximum time is reached, notifying the user in advance. Swavia is not responsible for possible fines or other actions, when User parks longer, than allowed maximum parking time.
5.4 If Swavia Service is unavailable (IE you do not receive the push notification about payment start in the right zone or Swavia app does not show the parking in the right zone), for instance, due to disruptions at Swavia or network operators, the User must pay the required parking fee in another manner, for instance paying for the parking in the vending machine.
5.5 Failure to adhere to the procedure for settling parking transactions may result in parking fees not being properly paid. If parking fees are not paid, this may be prosecuted by Parking Operators as an infringement of contractual duties, or by municipalities as an administrative offense.
6. Payments
6.1 Parking price and pricing rules are decided by Parking Operator. Swavia collects those fees and forwards them to Parking Operator.
6.2 Parking fees may be directly changed by the Parking Operator. This is solely their decision and Swavia is not responsible for the pricing of parking areas. Corresponding changes in the fee are passed directly on to the User.
6.3 Swavia asks for service fees for every payment. Swavia service fee is described on Swavia website www.swavia.com and in the app.
6.4 Available payment means are described on Swavia website www.swavia.com.
6.5 User is responsible for initializing payment start and stop and for having a sufficient amount of money in his account when billed through Payment Processor. When a payment fails, User is responsible for enforcement.
6.6 For protection against forgetting, Swavia notifies User at least once a day about ongoing parking payment. The frequency can be modified in the app settings.
6.7 The User can retrieve the parking duration for each parking transaction and an invoice for the amount of the parking fee incurred on the Swavia app. Data is available for the current month and for the previous 12 months.
6.8 User is responsible for entering a valid payment method and renewing it if something changes. In case the payment is unsuccessful, Swavia can ban further usage and initiate unsuccessful payment again any time during the next 36 months from the end of the applicable parking event.
7. Privacy and Data gathered
7.1 To offer the Swavia service, we use the following data:
7.1.1 Usage mode on street. | Manual | Clever notifications or automatic | Data storage duration |
7.1.2 Phone number. | Used as a unique account identifier and verified with a code transferred via SMS. | Phone number until the account is active, SMS code 24 hours or until it is used. | |
7.1.3 Phone type, operating system, and version. | Used for quality and performance monitoring. | Until the account is active. | |
7.1.4 Car license plate(s) and photos in off-street (garages). | Basis of the payments. | License plate until the account is active, pictures from garages 4 months. | |
7.1.5 Phone location and movement, which can be based on GPS, Wifi, Bluetooth beacons or mobile network cell triangulation. | Location is used one time on opening the app, needed for zone selection. Movement data is not monitored or stored. | Monitored during driving and stored with movement up to 1 minute prior to Bluetooth lost. Needed for quick and accurate parking zone selection, including detecting, when parking indoors. | GPS coordinates and movement 4 months, parking zone name 8 years. |
7.1.6 Phone Bluetooth name. | Not used. | Used for detecting parking start and end events. | Until the account is active. |
7.1.7 Phone language. | Used to display preferred language. | Until the account is active. | |
7.1.8 Phone IP | May be used for fraud monitoring. | 4 months. | |
7.1.9 Payment method and bank data. | User payment method, like a bank card or company invoicing. If the method is debit or debit bank card, we process payments based on card token, card number last 4 digits, and validity date. All other card data (described in 2.2.4) are stored only by the Payment Processor. Card token is an anonymous unique identifier for a valid card given us by the Payment Processor. | Until the account is active. Bank data by Payment Processor 8 years. | |
7.1.10 Parking sessions. | All paid parking sessions, defined by start and end time, location, zone name, parking price, and service fee. | All parking sessions, defined by start and end time, location and zone name (including free zone), parking price, and service fee. | All parking sessions 4 months, paid parking sessions 8 years. |
7.1.11 Zones and areas, where payments are disabled | Not applicable. | User can disable payments in any parking zone or in any area defined by GPS central point and radius. | Until the account is active. |
7.2 All data is stored and handled in EU and according to EU privacy laws. Servers are hosted according to Swavia and Digital Ocean contract in Germany (more general info at https://www.digitalocean.com/security/gdpr). Card payments are processed according to Swavia and TeleCash / First Data GmbH contract, whose servers are hosted in Germany (more info at https://www.telecash.de/datenschutz).
8. Data transfer
8.1 Data transfer between Swavia app and server is done over secure and encrypted https protocol.
8.2 Swavia is allowed to transfer parking events to the applicable Parking Operator. This data will contain: User phone, car license plate number, parking zone name, parking start time, parking start trigger (IE manually, Bluetooth, license plate recognition), parking end time, parking end trigger (IE manually, Bluetooth, license plate recognition), transaction cost, used discount (if applicable), full price (if applicable).
8.3 Payments are transferred to Payment Processor. This data can contain:
8.3.1 If payment method is debit or credit bank card (the Payment Processor is TeleCash): User card token, parking id reference, transaction cost.
8.3.2 If payment method is telco (User mobile phone service provider): telephone number, car license plate, parking zone name, parking start time, parking end time, transaction cost.
8.4 Swavia is allowed to use and transfer to third parties any collected data in anonymous and aggregated form. This data can be usage statistics, pricing, heatmaps etc for general performance monitoring, statistics, and marketing. Third parties can be Parking Operators, Payment Processors, Media, Traffic authorities, etc.
8.5 Swavia does not sell customer data, does not forward it to third parties, does not do any advertising, and does not send any push notifications not related to Swavia Service.
9. Third-party tools
9.1 Swavia app uses third-party tools to provide, maintain, protect and improve the Service, develop new services, and protect Swavia and our Users.
9.2 Google Analytics is a tool for analysis, provided by Google Inc. (Google). All data is stored in anonymous form, IE anonymize IP functionality is enabled. Google has servers in many countries and some of the data might be sent outside of EU. See more information at https://policies.google.com/privacy?hl=en&gl=en.
9.3 Firebase is a tool for detecting app reliability, provided by Google Inc. (Google). All data is stored in an anonymous form, IE without a link to customer data stored by Swavia. Google has servers in many countries and some of the data might be sent outside of EU. See more information at https://firebase.google.com/support/privacy.
9.4 Google Maps is a tool to provide maps, provided by Google Inc. (Google). Swavia loads the base map from Google, based on the current or selected location, IE without a link to customer data stored by Swavia. Google has servers in many countries and some of the data might be sent outside of EU. See more information at https://policies.google.com/privacy?hl=en&gl=en.
9.5 Swavia apps work on Google Android or Apple iPhone mobile phones, which are regulated through direct usage agreement between phone provider and the User.
10. Data protection measures
10.1 Swavia app encrypts all data which is transferred from Swavia app to Swavia server. For encryption, we use the Secure Socket Layer protocol (SSL).
10.2 The access to Swavia systems is protected by firewall and access control systems in such a way that no one can access them without correct authorization.
10.3 In addition to these preventive safeguards, all access, and access attempts are logged.
11. User rights
11.1 User can stop using Swavia app anytime. Upon selling the car, the User has to delete it in the app. Until deletion User is responsible for every payment made.
11.2 User can stop using automatic parking by opening the app and disabling automatic parking both on-street and in parking houses. Until this User is responsible for every payment made. NB! Deleting the app does not disable automatic parking inside parking garages and freeflow.
11.3 Swavia complies with legal requirements. User can request data extradition, correction, or deletion by sending us an email at help@swavia.com. General parking transactions which are required by law and by contracts made with Parking Operators and Payment Processors will remain stored as long as legally required.
11.4 User can delete the account. See more information at https://swavia.com/account-deletion. After deletion User can start using Swavia again, starting with a new registration.
12. Liability
12.1 User can submit appeals until 3 months after the parking event. Later appeals are not be accepted, as some data is deleted.
12.2 The User is aware that the ability to use the Swavia Services (such as initiating and terminating parking transactions), use of the Internet and the ability to receive SMS, push notification, and to receive a GPS location depend on the functioning of the mobile telephone, the (mobile) networks, and other third-party services. Swavia may not be held responsible for damages resulting from inadequate function or complete loss of the mobile telephone or networks or third-party services, for instance, failure to receive (in a timely manner) an SMS, push notification, etc. This also includes cases of Force Majeure as provided for in chapter 13.
12.3 When using Swavia service, User is responsible for obeying Parking Operator signage and general traffic laws. Using mobile phone and other Devices when driving is regulated in traffic laws and User is responsible for obeying them.
13. Force Majeure
13.1 Failure to comply with the obligations shall not be deemed to be a breach of Swavia service if it was caused by circumstances that were not foreseeable (Force Majeure). The Force Majeure can be a strike, cyberattack, failure in mobile network service, massive disturbances in the administrative territory of the Parties, uprising, war, fire, new Government law which significantly impedes the performance of the service or any other event, which is independent of the will of Swavia or Parking Operator and is accepted as Force Majeure.
14. Final provisions
14.1 These terms and conditions are governed by and shall be construed in accordance with the laws of the country of the applicable Parking Operator.
14.2 Swavia services, including the Swavia app, maps and website, are protected as intellectual property. Swavia hereby grants to the User a nonexclusive and nontransferable right to use the Services for the duration of the usage.
14.3 Swavia Service is developed constantly further. Swavia reserves the right to discontinue or change certain Services in the future after giving advance notice.
14.4 Should individual provisions of these Terms be or become invalid, the validity of the remaining provisions of these General Terms and Conditions shall not be affected thereby.
14.5 Swavia reserves the right to change these General Terms and Conditions. Changes will be announced on the Swavia website and will enter force 1 (one) month after the announcement. If Users do not agree with such changes, they have the right to terminate the usage without stating a reason (special termination right).
If you have further questions or comments, feel free to contact us at any time at:
Company name: Swavia Tech OÜ
Mailing address: Lai 6, Tartu 51005, Estonia
Phone: +372 5646 6001
E-mail: help@swavia.com
SwaVia Mobility GmbH
Schleifereigasse 7/2
с/o Swarovski Werk 2
6112 Wattens / Austria
