Privacy Policy — Parkmarkr

1. Overview

Parkmarkr ("the app") is a mobile application that helps you remember where you parked. Most of what the app knows about you stays on your device. Two streams of fully anonymised data may also be uploaded to a secure backend — described in detail below. The first (accuracy sharing) is part of how the app works and is always on; the second (parking-demand sharing) can be turned off at any time in the app's Settings screen.

2. What stays only on your device

The following information is stored locally on your device and is never uploaded as such. Only the anonymous pieces described in Section 3 — a carpark code, a level, a date, sensor readings without positions or clock times — are derived from it. The only full copy that can exist elsewhere is the optional backup you make to your own Google Drive (Section 7).

✓ Your parking history (level, timestamp, confirmation status) — only the anonymous per-park summary in Section 3A is derived from it
✓ My Parking Spot photos and notes
✓ Your carpark setup — only the anonymous calibration part described in Section 3A is shared
✓ App preferences and settings

You can delete any of this from within the app. Uninstalling removes everything stored locally.

3. What may be uploaded — anonymously

Two independent anonymous data streams may be uploaded. Accuracy sharing (A) is always on: every user benefits from the carpark setups and confirmed levels of everyone else at the same carpark, and the app's first park at a new carpark depends on it. Parking-demand sharing (B) has its own switch in Settings and can be turned off without affecting the app.

A. Accuracy sharing (always on)

When you set up an HDB multi-storey carpark and confirm parks at it, the app may upload anonymous calibration information for that specific carpark, so other users of the same carpark benefit from a better starting setup.

What's sent: the carpark's HDB code, the coordinates of the carpark entrance (not your home, work, or any other location), the carpark's level layout, the confirmed level you parked at, and the date (no time). After you confirm or correct a detection, an anonymous accuracy tally is also sent: whether the detected level was right and by how many levels it was off, per carpark and month. Nothing identifies you or your device.

When you confirm or correct a detected level, the app also sends the sensor readings from that detection so the carpark can be understood better: how the readings changed over the visit, how far you were from the carpark entrance, and how many seconds and metres apart things happened. No map positions and no clock times are included — only relative distances and durations, which cannot be placed on a map or on a calendar.

B. Share anonymous parking statistics (switch in Settings, on by default)

When you park at and leave an HDB multi-storey carpark, the app may upload an anonymous record of that visit so aggregate insights about parking demand can be produced.

What's sent: the carpark's HDB code, the hour-of-day you arrived, the hour-of-day you left, the day of the week, the month (no exact date), an approximate dwell-duration band, and the level. No coordinates, no precise timestamps, nothing that could be tied back to you. Each record is held on your phone and sent hours later at a random moment, so even the time of the upload says nothing about when you parked.

These aggregated insights may be shared with town councils, carpark operators, urban-planning agencies, or other parties interested in parking-demand patterns. Any insight surfaced to such a party shows only cells with at least five independent events — no single park is ever exposed.

4. What is never uploaded

Whatever the settings, the following are never sent off your device:

✗ Your name, email, or any personal identifier
✗ Your device ID, advertising ID, or app-install ID
✗ Your parking history list or any photos (your own optional Google Drive backup aside — Section 7)
✗ Your home, work, or any location other than the HDB carpark entrance you set up
✗ Crash reports, advertising identifiers, or behavioural telemetry
✗ Precise timestamps that could trace your routine

5. How we keep it anonymous

The two upload streams above are designed so that uploaded events cannot be linked together or back to you:

✓ No account, no device ID, no install ID — nothing identifies the source phone.
✓ No timestamp finer than the hour (parking statistics) or the date (accuracy sharing); sensor readings carry only durations relative to the visit.
✓ No location data finer than the carpark entrance you configured — never your phone's live location.
✓ Aggregate-only access on the demand stream: any cell exposed to a third party must contain at least five independent events.
✓ Events from the same phone cannot be chained — there is no shared identifier across uploads.

6. Permissions explained

The app requests the following device permissions. The data accessed via these permissions is processed on your device; only the limited, anonymised information described in Section 3 ever leaves it.

Location (Always)

Used to recognise when you arrive at your configured carpark, even when the app is not open. Your live location is processed on the device and is never uploaded.

Physical activity (Android) / Motion & Fitness (iPhone)

Used to detect when you have finished parking and started walking. This signal is used purely for on-device processing.

Notifications

Used to send a local notification after each parking session. On Android, a quiet persistent "Parkmarkr is on" notification also keeps the app running in the background. Notifications are generated on-device.

Camera & Photo Library

Used only when you choose to add a photo in My Parking Spot. Photos are saved locally on your device and are never uploaded.

Google account (optional)

Asked for only if you turn on Google Drive backup in Settings. It is used solely to place the backup file in your own Google Drive and to read it back. Parkmarkr has no account of its own and never receives your Google identity.

7. Third-Party Services

Parkmarkr does not use any analytics, advertising, or crash-reporting SDKs.

The anonymous uploads described in Section 3 are stored on a secure backend. Apart from this hosting relationship, no data is shared with any third party except as described in Section 3B (aggregate-only, with at least five independent events per cell).

Google Drive backup (optional). If you turn on "Back up to Google Drive" in Settings, a copy of your carpark setup and your most recent parking records is saved in a hidden app-only area of your own Google Drive, under your own Google account. We never see it, and Parkmarkr cannot see any other file in your Drive. Google's privacy policy applies to that storage. You can turn the backup off, or delete the file from your Drive, at any time.

8. Children's Privacy

Parkmarkr is not directed at children and does not knowingly collect any information from anyone under 13.

9. Changes to This Policy

If this Privacy Policy is updated, the new version will be posted on this page with an updated date. We encourage you to review this page periodically.

10. Contact

If you have any questions about this Privacy Policy, please contact us.

Privacy you can verify.

Always anonymous

Clear about the uploads

Records stay yours