Privacy Policy

1. Controller and contact

2. This website

GitHub Pages hosting

This static website is hosted through GitHub Pages. When a GitHub Pages site is visited, GitHub states that the visitor’s IP address is logged and stored for security purposes, whether or not the visitor is signed in. Technical request data may therefore be processed by GitHub to deliver and protect the site.

The legal basis for providing and securing this website is our legitimate interest under Article 6(1)(f) GDPR. GitHub describes its own retention, security, and international-transfer safeguards in its privacy statement.

• GitHub Pages data collection
• GitHub General Privacy Statement

No website tracking

The ParkLoka website code contains no analytics, advertising, tracking pixels, contact form, or marketing cookies. It does not access parking data stored by the Android app.

Email contact

If you email us, we process your email address, message, and any information you choose to include so we can respond. The legal basis is Article 6(1)(b) GDPR for pre-contractual or service-related requests and otherwise Article 6(1)(f) GDPR for answering legitimate enquiries.

3. Location and address lookup in the app

Foreground location

ParkLoka asks Android for approximate or precise foreground location when you choose to save your current parking spot. While the app is open on the parked-car screen, it also receives foreground location updates to calculate the live straight-line distance to the saved car. ParkLoka does not request background-location permission and does not build a location history.

The saved record contains one set of coordinates, measured accuracy, and timestamp. Live positions used for the distance calculation are not added to the parking database. You may deny location permission, but saving a new spot and calculating live distance will then be unavailable.

Best-effort address lookup

After coordinates are saved, ParkLoka asks Android’s built-in Geocoder for a readable address. The geocoder implementation configured on the device—often a Google service—may receive the coordinates and may use a network connection. ParkLoka does not operate this service, and Android does not guarantee availability or accuracy. If lookup fails, the coordinates remain usable.

Android Geocoder documentation

4. Local parking data, photos, and backup

ParkLoka stores only one active parking record in its private local database. Depending on what you add, this can include:

• coordinates, accuracy, save time, and resolved address;
• an optional note and parking type;
• optional level, zone, and space values for a garage or outdoor lot;
• the private file path for one optional parking photo.

A photo is captured through a compatible camera app using a temporary Android file permission, then stored in ParkLoka’s app-private files. ParkLoka does not request access to the device-wide photo library.

Android backup and device transfer

Android backup is currently enabled for ParkLoka. Depending on your Android version, device manufacturer, account, and backup settings, Android may include the app database, preferences, and internal files in an encrypted cloud backup or device-to-device transfer. That processing is controlled by Android and the selected backup provider, not by a ParkLoka server. You can manage backup in your device settings.

Android Auto Backup documentation

Local calculations

Distance, elapsed parking time, and the approximate walking time are calculated locally. Walking time is a rough estimate based on straight-line distance, not a routed journey time.

5. Navigation, sharing, and external apps

ParkLoka sends information to another app only when you choose an external action:

• Navigate: Android receives a geo link containing the saved coordinates and opens a compatible app you select or have configured.
• Share: Android’s share menu receives localized text containing the address when available, coordinates, and a Google Maps HTTPS link. The optional note, photo, type, level, zone, and space are not included.
• Camera: a compatible camera app receives temporary access to write the requested parking photo.

The selected provider processes the transmitted information under its own privacy policy. ParkLoka does not receive a copy of what you send through navigation or sharing. The Google Maps link is generated as text; ParkLoka does not contact Google Maps merely by creating the share message.

6. Google AdMob and consent

The Android app uses Google AdMob for an adaptive banner and restrained interstitial advertising. At each launch, Google’s User Messaging Platform (UMP) refreshes consent information and shows a privacy message if required. ParkLoka requests ads only when UMP reports that ads may be requested; if the consent update fails without a usable status, ads remain disabled for that session.

When advertising is active, Google states that the Mobile Ads SDK automatically collects and shares data such as the IP address (which can estimate general location), app interactions, diagnostic information, Android advertising ID, app set ID, and—where applicable—other device or account identifiers for advertising, analytics, and fraud prevention. ParkLoka does not pass your saved parking coordinates, address, note, parking details, or photo to AdMob.

Depending on your region and choices, Google may serve personalised, non-personalised, limited, or technical ads. Even non-personalised advertising can use identifiers for functions such as frequency capping and aggregated reporting. Where consent is legally required, the basis is Article 6(1)(a) GDPR and applicable device-storage rules. Where permitted without consent, limited technical delivery, fraud prevention, and financing the free app may rely on legitimate interests under Article 6(1)(f) GDPR, subject to the choices and vendor purposes shown by UMP.

When required, you can reopen the consent form from About & Legal → Ad privacy options. You can also reset or delete the Android advertising ID in Android settings. Withdrawing consent does not affect processing that occurred before withdrawal.

• Google Mobile Ads SDK data disclosure
• Google UMP privacy guidance
• How Google uses information from partner apps
• Google Privacy Policy

ParkLoka does not include Google Analytics or Firebase Analytics. Local counters record when an interstitial becomes eligible and the last day one was displayed; they do not contain parking coordinates.

7. Recipients, legal bases, and international processing

Parking content remains under your control unless you deliberately invoke an external app or Android backup. Relevant recipients or independent providers can include:

• the device’s location and geocoding implementation;
• the camera, navigation, messaging, or other app you choose;
• the Android backup or device-transfer provider configured on your device;
• Google and its advertising partners when AdMob/UMP is active;
• GitHub for website hosting and security logs.

Local feature processing is necessary to provide the functionality you request and relies on Article 6(1)(b) GDPR where the GDPR applies. Website security and ordinary support enquiries rely on Article 6(1)(f) GDPR. Advertising bases are described in section 6.

Google, GitHub, and chosen external providers may process information outside the European Economic Area. Their privacy notices describe applicable safeguards such as adequacy decisions, the EU–US Data Privacy Framework, or Standard Contractual Clauses. ParkLoka itself operates no backend and makes no independent transfer of the locally stored parking record.

8. Retention and deletion

• The active parking record remains until you replace it, choose Forget, clear app data, or uninstall the app.
• Replacing or forgetting a spot removes the obsolete ParkLoka photo from app-private storage; removing or replacing a photo removes the prior file.
• Uninstalling removes the on-device app data, but an Android backup may remain according to device/account settings and the backup provider’s retention rules and may restore data later.
• GitHub determines retention for GitHub Pages security logs; Google and advertising partners determine retention for data they process under their policies.
• Email enquiries are retained until the request is resolved and for any additional period required to meet legal obligations or defend claims.

9. Your rights

Subject to the applicable conditions, you may request access, rectification, erasure, restriction, portability, or object to processing. Where processing relies on consent, you may withdraw it at any time for the future. Contact contact@parkloka.app.

For data kept only inside ParkLoka, you can exercise direct control by viewing or changing details, choosing Forget, clearing app storage, uninstalling, and managing Android backup settings. We cannot retrieve a local parking record from your device because ParkLoka has no account or backend.

You also have the right to lodge a complaint with a supervisory authority. The authority responsible for a Berlin-based controller is:

10. Changes to this policy

We will update this policy when ParkLoka’s implementation, providers, or legal requirements materially change. The current date will always appear at the top of the page.