1. Information you submit
- Name, email address, topic, and message content you send through the contact form.
- Any information you choose to include in an email sent directly to Peer2Park.
SIG · PRIVACY
Effective April 20, 2026
Privacy policy.
This policy covers the public website at peer2park.net, the contact form on this site, and the Peer2Park product flow described here.
scroll
Overview
Built to keep the heaviest data closest to the device.
Peer2Park is designed so that camera imagery is processed on device and the service shares only the structured parking-signal data needed to make the product work. The public website itself is a static site with a contact form.
As of April 20, 2026, the public website does not use advertising cookies, analytics pixels, or behavioral profiling. If that changes, this policy should change first.
The website loads Google Fonts, routes contact-form submissions through FormSubmit, and relies on standard hosting, DNS, and delivery infrastructure that may log routine request metadata.
If you use the Peer2Park app or beta features, the service may process camera input locally and may transmit signal metadata such as time, location, confidence, freshness, and parking state. Raw video is not uploaded in the ordinary product flow described on this site.
Collection and use
What we collect, how we use it, and who may see it.
2. Website technical data
- IP address, browser or device type, referring page, and request timestamps typically generated when a browser loads a website.
- Requests made to third-party assets used on the site, including Google Fonts.
3. App permissions and signal data
- If you use the app or beta, camera input may be processed locally on your device.
- The service may use precise or approximate location, timestamps, confidence scores, freshness state, and related parking-signal metadata to operate the product.
- Raw camera footage is not uploaded in the ordinary detection flow described on this site.
4. How we use information
- To respond to messages, evaluate pilots or partnerships, and support product questions.
- To operate, secure, debug, and improve the website and Peer2Park services.
- To rank, deduplicate, and surface parking signals based on freshness and confidence.
5. Sharing and third parties
- Contact-form submissions are processed by FormSubmit and sent to the Peer2Park inbox.
- Website hosting, DNS, and delivery providers may process routine request metadata.
- Google receives request information when the site loads Google Fonts.
- If the product hands off navigation to Apple Maps or another map provider, that provider may process the request under its own terms.
- Peer2Park does not sell personal information and, as of April 20, 2026, does not use ad-tech trackers on the public website.
6. Retention and security
- Contact messages are retained only as long as reasonably needed to manage the conversation and any follow-up.
- Parking-signal metadata should be retained only as long as operationally useful for freshness, abuse prevention, debugging, or legal compliance.
- No system is perfectly secure, but minimizing raw data exposure is part of Peer2Park's design approach.
Your choices
You choose whether to submit the contact form. If you use the app, you can manage camera and location permissions through your device settings. You can also request access, correction, or deletion by emailing ryken15@icloud.com.
Peer2Park may keep limited information when needed to comply with law, resolve disputes, prevent abuse, or enforce the service terms.
No sale or ad tracking
Peer2Park does not sell personal information. The public website is not using third-party advertising pixels or behavioral profiling as of April 20, 2026.
Children's privacy
Peer2Park is not directed to children under 13, and we do not knowingly collect personal information from children under 13 through the public website.
Changes and contact
Material updates to this policy should appear here with a new effective date before the underlying data practice changes. Questions can be sent to ryken15@icloud.com.
This policy is written to match the current site and the product flow described here. If vendors, permissions, storage practices, or product scope change, the policy should be updated before rollout.