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. With your consent, two streams of fully anonymised data may also be uploaded to a backend hosted in Singapore — described in detail below. Both are switched on by default, are shown to you during setup, and 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. It is never sent to us. If you turn on optional cloud backup (section 6), it is saved to your own Google Drive — storage that belongs to you, not to us.

✓ Your parking history (level, timestamp, confirmation status)
✓ My Parking Spot photos and notes
✓ Your full carpark configuration (name, level layout, entrance details)
✓ 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, only with your consent

Two independent anonymous data streams may be uploaded. Each has its own toggle in the app's Settings, and each can be turned off independently without affecting the other or the app's core functionality.

A. Help improve accuracy (default: 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). We also count how often the app's guess matched your confirmation, so accuracy can be measured and improved — these are running totals per carpark, not a record of individual parks. Nothing identifies you or your device.

A2. Detailed readings — covered by the same toggle as A

When you confirm or correct a detected level, the app may upload the sensor readings from that one detection, so level detection can be made more accurate at your carpark. Your confirmation is what makes the readings useful: it says which answer was the right one.

What's sent: the carpark's HDB code, the sensor readings, how far you were from the carpark entrance you configured, when your phone detected walking, and which level was detected versus which one you confirmed.

No map positions and no clock times are included. Distances are a single number in metres from your own configured entrance — never a coordinate, never a route. Times are only how many seconds apart things happened, counted from the start of that one detection, so nothing can be matched to a time of day or to another visit. These readings are used for improving the app and are deleted after 90 days.

B. Share anonymous parking data (default: on)

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.

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 we never receive

Independent of any toggle, the following are never sent to us — not to our backend, and not to anyone through us. (Optional cloud backup, section 6, copies some of this to your own Google Drive; that goes to your storage, never through our servers.)

✗ Your name, email, or any personal identifier
✗ Your device ID, advertising ID, or app-install ID
✗ Your parking history list or any photos
✗ Your home, work, or any location other than the HDB carpark entrance you set up
✗ Crash reports, usage analytics, or behavioural telemetry
✗ Precise timestamps that could trace your routine

5. How we keep it anonymous

The 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 (demand stream) or the date (accuracy stream). The detailed readings carry no clock time at all — only how many seconds apart things happened.
✓ No location data finer than the carpark entrance you configured — never your phone's live location. The detailed readings carry only your distance from that entrance, as a number in metres.
✓ 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. Optional cloud backup — to your storage, not ours

If you turn on cloud backup, the app saves a backup of your carpark setup and parking history to your own cloud storage: a private app folder in your Google Drive (Android; iPhone support planned). Signing in is used for exactly one thing — letting the app reach your own storage. It does not create an account with us.

✓ Your backup never passes through or touches our servers. We cannot see, read, or access it.
✓ No identity reaches us: your name, email, and account details stay between you and Google or Apple.
✓ The anonymous uploads in section 3 are completely unchanged by this — they carry no account information whether backup is on or off.
✓ Turn it off any time in Settings. You can delete the backup yourself from your Google Drive, and signing out stops any further backups.

You can also make a backup without any sign-in at all: Settings → Backup saves the same data as a file you can keep anywhere you choose.

7. 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.

Activity Recognition

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. 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.

8. 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 Supabase backend hosted in Singapore. 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). If you enable optional cloud backup (Section 6), Google Drive acts as your own storage provider under its own terms — that relationship is between you and them, and your backup never reaches us.

9. Children's Privacy

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

10. 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.

11. Contact

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

Privacy you can verify.

Always anonymous

You control the uploads

Records stay yours