Privacy Policy — Parking & Drive Away Reminders
Last updated: 3 October 2026 (version 15) · Operator and data controller: Doron Harpaz, Israel · Contact: parkingreminderalerts@gmail.com
Go to the Parking & Drive Away Reminders home page
The principle
The app reminds you to end or renew a parking, and detects driving away from the parking spot. It has no user account, and we keep no list of identified users. What we hold is linked to the installation identifier only.
Everything that reaches us carries one number only — the installation identifier. That number identifies the installation of the app on the phone, not you. We do not ask for and do not collect a name, a phone number, an email address, a Google account or a location, and we have no way of knowing who you are.
Note two exceptions: if you write to us from your own mailbox or on WhatsApp — tools outside the app — your email address or phone number reaches us; and if a name you set yourself contains personal details (the name of a Bluetooth audio device connected to the phone), it reaches us too.
Even without an account, three things are sent to us, and all of them are detailed below: a report you send, a technical report the app sends on its own, and a short request the app makes to check whether a message is waiting for you. There is also a fourth, technical request, which carries no information about you; it is described at the end of the section on the care channel.
The app itself has no ads and no third-party tracking or analytics (for the website, see below), and we do not sell data. We rely on technical service providers, and they are listed below.
What the app uses, and why
Location — to remember the parking spot and detect driving away from it. Distances, speeds and drive detection are computed on the phone. No coordinates, addresses or place names reach us. The parking spot stays on the phone after the watch ends too, so you can navigate back to the car, and is deleted when you start a new parking or when the watch closes by itself after a drive was detected. One exception: the phone passes a point to Android’s address service (usually Google’s) to get the street name — the parking point, for the personal message about the parking, for the parking-spot photo and for sharing, and on the emergency screen your current location, for the emergency message. This is the only request in which the coordinates leave the phone; the address comes back to it and stays on it, and it does not reach us. Optional: location “all the time”. If you allow it and Android stops the watch in the middle of a parking (an app update, a phone restart or low memory), the watch comes back by itself, in the background, without you having to open the app. Without it, the app asks you to open it. In the background, location is used only while a parking is being watched, and the rules above apply to it as always: it is kept on the phone and is not sent to us. You can withdraw it at any time in Android’s settings.
Notifications and exact-time reminders — so that the reminders you asked for arrive exactly on time, even when the phone is asleep. The same mechanism also schedules the technical report the app sends on its own.
The parking apps installed on your phone — to show a matching button for each, and to open the parking app you chose when you start the watch on a new parking. When the drive-away notification appears, the app does not open on its own — it only reminds you; if you tap the notification itself, the parking app opens, because that is what is needed to close the parking. The app checks which parking apps from a known list are installed on your phone, and in addition an app you yourself chose as your parking app. Apart from these, it asks the phone only about what it needs in order to work: navigation apps, the speech engine, the camera, WhatsApp, the browser and Google Play. The other apps on the phone are neither checked nor recorded. The name of a parking app detected on your phone is written to the event log, and so it reaches us together with the report. The report also includes the parking app you chose and the navigation app you used.
Usage access (optional) — if you grant it, the app uses it for three things, all on the phone. First, while the screen is on and no parking is being watched, it checks about every ten seconds whether a known parking app has come to the screen, so it can offer to start the watch on the parking right away. Second, when the car drives away from the parking, it checks when the parking app you chose was last on the screen; if it was closed more than ten minutes before the drive, the app tells you that the parking is probably still open. Third, as long as a watch on a parking started with a parking app continues, it checks about every 20 seconds whether that same parking app has come back to the screen, so it can ask you whether you have finished the parking. In addition, when the screen comes on during a watch, the app uses it to bring the floating sign back to the screen if Android took it away.
For this, Android hands the app a list of the apps that came to the screen — in the check after a drive, in the 12 hours before it. The app filters the list immediately on the phone and discards everything that is not a parking app. The names of other apps are not kept on the phone, are not written to the log and are not sent anywhere. Without this permission the app works as usual, from its own screen.
Display over other apps (optional) — to show a small card on top of the parking app: when you open it ("Watch your parking with Pango?"), and during an active watch, if you reopen the parking app you started the parking with ("Did you end the parking?"). In addition, while a parking is being watched and you are in another app, the floating sign is shown over the screen — a small app icon you can drag, which opens three buttons when tapped. These are the only uses of the permission, and the cards and the sign collect nothing.
The watch service during parking — as long as a watch continues, the app runs a service with a fixed notification, which reads the location to detect a drive. It stops when the watch ends.
A quiet background service ("Ready for parking") — so that the app starts working automatically when you open the parking app, it runs a small service with a fixed silent notification. The service uses no location and makes no network requests, and stops checking when the screen is off. You can switch it off by revoking the "Usage access" permission: the checks stop immediately, and the service itself shuts down the next time it starts.
Technical actions on the phone — vibrating with notifications, keeping the phone awake for the moment an announcement is played, routing audio to the car’s speakers, checking whether there is a network connection (to know why a send failed), and restarting the watch after the phone is switched on. The app also asks you to exempt it from battery restrictions, so that notifications arrive on time. None of these actions collects information about you.
Reading notifications — the app contains a component that can read notifications of parking apps, to detect when a parking started and ended. In this version it is not active: the app does not ask for the permission and does not direct you to it. The component is registered with the system, so it appears in the "Notification access" list in the phone’s settings; if you enable it there manually, it will start working. Even then, Android hands it the notifications of all apps and it filters them immediately on the phone, and from a parking app’s notification it sees only which app it came from, the notification ID, the channel, technical flags and the time it was posted — no title, no text and no content of any kind.
Bluetooth audio — when a Bluetooth audio device is connected to the phone, the app tries to play the announcement through it. For that purpose the name of the connected device — the car’s audio system, headphones or a watch — is read, and the name is recorded in the log, so it reaches us with the report. A device name may contain personal information. When the device is identified as a hearing aid, its name is not recorded — only the fact that it is a hearing aid (from version 10.82).
Contacts — the app does not ask for and does not receive permission to access your contacts. The emergency helpers are chosen from the phone’s contact list, and the app receives only the name and number of the contact you chose. They are kept on the phone and do not reach us.
The event log and the installation identifier
The phone keeps a technical event log of up to the last nine parkings, and sometimes fewer, when the log reaches its size limit. Older ones are deleted by themselves.
What it contains: watch start and end times · distances and speeds measured on the phone relative to the parking spot · the status of permissions and battery settings · the phone’s sound state (volume, ring mode, "Do Not Disturb") · the notification channels you chose · the phone model, Android version and app version · the interface language and the country code of the SIM card (letters that stand for a country, not a location) · the parking app you chose and the navigation app you used · known parking apps detected on the phone · the name of the Bluetooth audio device that was connected (except a hearing aid) · settings made in the app, including the night-time quiet hours · actions taken in the app, including use of the emergency screen (without the helpers’ names and numbers) · the purchase status or trial period · and the installation identifier.
What it does not contain: where you parked — no coordinates, no addresses and no place names. It holds only distance and speed relative to the parking spot, without knowing where that spot is.
The installation identifier is, in most cases, an exact record of the moment you first opened the app — to the millisecond. (When the phone’s clock is wrong, a number close to it.) It is not derived from your Google account and is not an identifier of the phone, and its role is to link reports and messages of the same installation.
▸ Planned change: the installation identifier will be replaced by a long random number generated on the phone.
Uninstalling the app erases the identifier from the phone. The app is configured so that Android does not back it up to the cloud, so the identifier is not restored on reinstallation or when moving to another phone.
A report you send
When you choose to write to us on the "Write to us" screen, the app shows you the full text that will go out — the header line with the phone details, the counters and the event log — and you read it before sending. When you tap, the app itself sends everything to Google Forms. No browser opens, no email app opens, and nothing leaves before the tap.
The installation identifier is not shown in the text on the screen — "install id (hidden)" is written in its place; it is sent with the report.
The app does not send us recordings, photos or emails. Whoever chooses to send us an email from their own mailbox, or a WhatsApp message, does so by their own choice and at their own responsibility, and their email address or phone number and the content of the message reach us.
The report the app sends by itself
So that we learn about faults nobody wrote to us about, the app sends the event log on its own — only the parkings accumulated since the last report that reached us, not the whole log each time. The first report is sent about an hour after installation, then once a day, and after the app is purchased — once a week.
The report is also sent about an hour after every update of the app, shortly after the permission status on the phone changes (within an hour at most), and immediately after a parking that looked faulty or after a crash of the app.
The report is sent first to our own server, run for us by Cloudflare, and only if it does not answer — to Google Forms, as before. The server keeps only the text of the report and the time it arrived — no IP address and no connection details — and deletes it once it has been copied to our computer: within three weeks, and after 30 days at the latest. A report you send on the "Write to us" screen still goes to Google Forms.
Sometimes the report is sent once an hour, for a limited period: when we are handling a fault of a particular installation, or when the app itself detects that it is missing an essential permission — then for up to a week, or until the permission is granted. And when we are investigating a widespread fault, we can ask all installations to send one report immediately.
What it includes: the event log · the counters (how many notifications succeeded, how many faults were counted) · the phone model, Android version and app version · the interface language and country code · the installation identifier · the purchase status or trial period · and the kind of fault detected. It does not include a location, a photo or a recording.
In the first month after installation the report is always sent. After the month, users who paid can switch it off on the "Write to us" screen; whoever switches it off reduces our ability to handle faults on their phone, and that is their responsibility. When it is off, the request for a single report is not answered either. Anyone whose trial period has ended and who has not purchased the app sends one last full report and, from then on, instead of the event log, only a shortened report once a week: the phone details (model, Android version, language), the installation identifier, the trial period status, the app version, on how many days the purchase screen was shown, purchase attempts and up to 20 lines of the log concerning the purchase, and how many times a parking app was opened or the card was shown over it. A crash report and a report we have asked for are still sent in that case. After 4 weeks without opening the app, even this shortened report stops.
The care channel
Sometimes we send you a personal message. The message is placed on our server under the installation identifier. Each time you open the app or return to it, and also about once an hour, the app asks the server whether a message is waiting for you — even when automatic sending is off. After the trial period has ended and the app has not been purchased, this request is sent only once a day. The request carries only the installation identifier, and nothing else about you or the phone.
If a message is waiting, a pink bar appears — on the app’s main screen, and also on the card that pops up over the parking app — and tapping it shows the message. When you have read it, the app tells the server it was read — that is how we know the message reached you. Several messages can be waiting for you; they are shown one after the other, and a message that was not read keeps waiting until it is read. Messages that were read are deleted from the server; the read receipt is deleted within 90 days. The server is run for us by Cloudflare.
On the same channel we can also place a general message for all users, and a flag that asks the installation to send reports more frequently for a limited period. These, too, reach you and collect nothing. In addition, some messages are written by the app itself on the phone, without any communication, and are shown in the same pink bar. Such messages do not pass through our server, and reading them sends no read receipt; the event log records them like everything else.
In addition, usually once a day — when you open the app, when a parking starts, and in the background when automatic sending is on — the app asks a Google service two questions: where to send reports today, and what the minimum required version is. The answer can also redirect the reports to another form and carry the request for one report. If you are shown a message that the version on the phone is too old, the question is asked on every opening, so that a mistaken block is corrected immediately. This request carries no information about you or the phone.
What stays on the phone and is not sent to us from the app
The parking spot · a photograph of the parking spot, if you take one — it is kept inside the app, not in the gallery, and is deleted when a new parking starts or when the watch closes by itself after a drive was detected · the emergency helpers and their phone numbers · and your own live location. If you send us a photo from your own mailbox — that one does reach us.
What you share with a friend or with yourself — a parking spot, your location or a photo — leaves your phone through the app you chose for sharing, straight to the recipient, and does not pass through us. That app’s own policy applies to it.
Service providers and payment
Our service providers: Google (Forms, Sheets, Apps Script, Android’s address service, Gmail for the emails users send us from their own mailbox, and Google Play) and Cloudflare (the website, personal messages, and receiving the automatic reports). They process the data for us, each for its own role.
The one-time payment is made through Google Play. The payment method details are handled by Google only and do not reach us. The app receives from Google Play the purchase status and the purchase identifiers, in order to know that the app has been paid for and to confirm the purchase with Google. The purchase identifiers themselves are not written to the log; the log — and therefore the reports too — records the purchase status, whether it was paid for with money or granted with a promo code, and the status of the trial period.
Connection logs
We do not keep IP addresses or connection logs. Our service providers (Google and Cloudflare) process the IP address at the time of the connection, under their own privacy policies.
Legal basis
| What is collected or sent | Legal basis | Reason |
|---|---|---|
| Running the app: watching the parking, reminders, drive detection | Performance of a contract | To give you the service you asked for |
| Purchase: payment confirmation from Google | Performance of a contract | To confirm the purchase and unlock the app for use |
| Automatic reports: the event log, the phone model, the installation identifier | Legitimate interest | Finding faults in every version of the app so they can be fixed, and checking that the app works properly for users |
| Counting visits to the website | Legitimate interest | To know which pages are read and where visitors come from, in order to improve the website |
| "Write to us": a written message, the event log | Consent | You choose to contact us, so that we can handle your request |
| Permissions you choose to grant: Usage access, Display over other apps | Consent | So that the app can carry out its tasks and functions as well as possible |
"Performance of a contract" means: to give you what you asked for. "Legitimate interest" means: a reasonable need of ours that does not harm you.
EU representative: TBD (to be defined).
Retention and deletion
On the phone: when the watch on the parking ends, the app deletes the watch data. The watch usually ends when you tap the "Stop watching this parking" button, and sometimes automatically, for technical reasons. The parking spot and the photo stay until a new parking starts, or until the watch closes by itself after a drive was detected. The event log keeps only the last nine parkings. Uninstalling the app erases everything from the phone.
With us: the reports you sent and the reports the app sent on its own. Their retention period: TBD (to be defined). Emails you sent us from your own mailbox — retention period: TBD (to be defined). A personal message is deleted from the server after you have read it, and the read receipt is deleted within 90 days. Uninstalling the app does not delete copies that have already reached us.
Your rights
We do not know who you are. A request to access your data or to delete it can be sent on the "Write to us" screen in the app. The request reaches us together with the report from your installation, and we will answer it with a message inside the app. Data sent from an installation that has been uninstalled cannot be located.
If the processing is based on your consent, you may withdraw it. The withdrawal applies from then on; what was done before it remains lawful. If you live in the European Union, you have further rights under the GDPR — including restriction of processing, objection to processing, receiving your data in a file and lodging a complaint with a supervisory authority.
If you wrote to us by email or on WhatsApp, you can ask in the same way that we delete the message and your email address or phone number.
Data security
All communication between the app and Google and Cloudflare is encrypted (HTTPS). Access to the reports and to the computer on which the data is kept is the operator’s alone. The app does not back up its data to the cloud.
Children
The app is intended for drivers and is not directed at children under 18.
The website parkingreminder.app
The website uses Cloudflare Web Analytics to count visits, without cookies and without personal identification. What is measured: the page, the country, the site you came from, the device type, the browser and operating system, and the loading speed.
Terms of use and changes
The terms of use are shown inside the app, under Settings → "About & terms of use".
If this policy is updated, the current text will be published on this page with its update date. Version 15 describes exactly what the app does today, includes the legal basis, the service providers, retention, rights and security, and marks the planned change next to the text that will change. Version 15 adds location “all the time” (optional) and our own server for receiving the automatic reports.
Back to the main page