Privacy Policy

Your information, used for private alerts

ParkBeep uses your email address, account credentials, display name, vehicle details, notification choices, and activity within the service to operate private vehicle alerts. We use the plate and state you voluntarily register to match alerts inside ParkBeep. We do not obtain DMV ownership records, provide a public owner directory, or reveal your contact details to an alert sender.

Vehicle reviews use your claimed authorization, registration details, review explanations, and decision history. Competing claims remain private. You can reply to clarification requests, appeal a decision, request a control review, or end your authorization from Vehicles. A photo of a parked vehicle alone does not establish control. Staff may suspend alerts during review and document any transfer decision.

Account review uses the information you submit about your intended use of ParkBeep. It is a staff review, not government identity verification. Do not submit identity documents or biometric information.

Replies and support conversations

A sender normally receives a generic submission receipt. Marking a beep seen or resolved stays private. For 24 hours, a recipient may deliberately share a limited thanks or resolved reply after confirming that this reveals receipt to the sender. A shared reply does not include the recipient’s identity, vehicle details, or contact information. Shared replies are retained for up to 90 days and removed on account erasure.

Support cases contain the topic, messages you submit, staff replies, and internal review notes. Authorized staff use these records to investigate your request. Customer views and downloads include your conversation with staff. Internal notes stay within staff tools. Closed cases and their messages are removed after 90 days, or when your account is erased. Open cases remain while help is needed.

Photos and approximate locations

Plate scanning reads an image on your device to suggest plate text. A scan image is not uploaded to ParkBeep as evidence. You must confirm the plate and state yourself.

You can separately choose an evidence photo where the alert reason permits it. We remove image metadata, store the processed image privately, and require moderation before the recipient can open it. Authorized staff can inspect evidence to review alerts and reports. Location descriptions are limited to nearby blocks or cross streets. We do not continuously track your device.

Providers and notifications

Supabase stores account, database, and private photo records. Vercel hosts the web applications and account services. Resend processes transactional email. Native mobile notifications use Expo, Apple Push Notification service, and Firebase Cloud Messaging. Expo processes a device notification token, a general notification, and an alert reference to route it to your phone. Browser notifications use your browser notification provider. These providers process information needed to perform their services.

Email and push alerts are optional. You can change preferences in Account and disconnect devices. Account confirmation and password recovery messages support authentication. Push previews contain a general alert and do not show a plate or contact details. We do not sell personal information.

A welcome notification test is optional and sends only to your current device. It records a test reference, your account and connection, and receipt or opening times when the app can report them. Its limited proof travels in the notification and cannot read your account. Provider acceptance does not prove device receipt or audible sound. Test history is removed after seven days or account erasure, and proof content is removed from the queue after delivery finishes or expires. These tests do not contact other drivers or change your normal alert preferences.

Signing out clears the saved account session on that device. If it is offline, a limited disconnection proof may remain on the device until ParkBeep can finish removing its notification connection. That proof cannot read your account or send an alert. Older connections may need the same account to sign in again while online. Some notifications can arrive until the connection is removed; you can also disable ParkBeep notifications in device settings.

Retention and deletion

Evidence is scheduled for removal after 30 days unless staff place it on a documented preservation hold. Matching target data is cleared after routing. Notification content used for retrying delivery is cleared after two days. Detailed location and request security data are reduced on a scheduled basis; active reports may require longer review.

Vehicle review message text is cleared after 90 days unless the review or appeal remains open. Current registration details and decisions remain while needed to operate the account. Approved account erasure removes review message text and identifying review notes. Unanswered clarification requests expire after 30 days and can be reopened. Temporary authorization ends after the selected date in UTC.

Account and vehicle records remain while needed to operate your account. A deletion request immediately pauses alerts. Staff then remove account credentials and identifying profile and vehicle details after reviewing any active report or preservation hold. Limited consent, security, alert, audit, and request records may remain to document service use, prevent abuse, and address legal obligations. Provider backups may persist under their own recovery schedules.

Your choices and requests

Open Account to download your records, correct your display name or vehicle details, submit a data request, report an alert, block a sender, or request deletion. You can also contact parkbeepapp@gmail.com. We verify requests before releasing or changing private information.

We may disclose information when required by valid legal process or needed to protect people and the service, subject to applicable law. Material changes to these practices will be reflected here and communicated as appropriate.