Privacy by architecture,
not afterthought.

Last updated March 28, 2026. This page explains what Peer2Park collects, how it is used, and where the boundaries are between on-device analysis and shared parking signals.

Read the policy Ask a question

scroll

Overview

The product is designed to keep the heaviest data closest to the device.

Peer2Park is built around the idea that parking detection should happen on-device whenever possible. In the normal product flow described on the homepage, raw dashcam footage is processed locally and parking availability is represented as structured signals rather than uploaded video.

This policy covers both the public website and any product interactions tied to Peer2Park. If a future release introduces additional data collection, this page should be updated before that collection goes live.

What we collect Your rights Contact us

Website Contact and hosting data

If you use the contact form, the information you submit includes your name, email address, selected topic, and message content. Hosting providers may also collect routine technical request data such as IP address, browser type, and request timestamps.

Product Shared parking signals only

Peer2Park’s stated product model is that computer-vision analysis runs on-device and only the parking signal needed to make the network useful is shared, such as approximate location, timestamp, confidence score, and parking availability state.

Data use

What Peer2Park collects, uses, and tries not to keep.

1. Information collected

Contact-form submissions you choose to send through this website.
Basic technical logs generated by the website’s hosting and delivery infrastructure.
For the product itself, structured parking metadata necessary to surface fresh availability signals.

2. How information is used

To answer messages, evaluate partnerships, and respond to product questions.
To operate, secure, and troubleshoot the website and future Peer2Park services.
To rank and distribute parking availability based on recency and confidence.

3. Sharing and disclosure

Contact-form messages are delivered through FormSubmit to the designated inbox.
Infrastructure providers may process limited technical data while hosting or routing the service.
Peer2Park should not sell personal information or share raw footage as part of its standard parking-detection flow.

4. Retention and security

Messages are retained for as long as needed to manage the conversation and related follow-up.
Structured parking data should be retained only as long as it remains operationally useful.
No system is perfectly secure, but minimizing raw data exposure is part of the product’s security posture.

Your rights

If Peer2Park expands into additional jurisdictions or introduces new categories of personal data, this policy should be updated to reflect the applicable legal rights and operational details before launch.

Policy changes

Material changes should be reflected on this page with a new effective date. Continued use after an update means the newer version governs that interaction.

This page is a working policy for the current Peer2Park website and product description. It should be reviewed whenever data flows, vendors, storage practices, or release scope change.

Need clarification?

Privacy by architecture,not afterthought.