Contact
The public contact setup is intentionally lightweight. The current route is GitHub issues so product feedback, corrections, and listing-removal requests can be triaged without adding a heavier support system before the site actually needs one.
Use the public issue route for broken links, suspicious range values, duplicate listings, UI bugs, or general product feedback. The more specific the report, the easier it is to fix.
Helpful details: listing URL, make and model, the page or filter state you were using, and what looked wrong.
If a listing should not appear in the index, use the same public issue route and state that it is a takedown or removal request. Include the source URL and any identifying source listing ID if available.
What happens next: the listing can be suppressed from the published index and older runtime payloads age out on a short retention window rather than staying available indefinitely.
If you want to discuss a contextual partner fit, include the offer, the intended buyer problem it solves, the landing page, and why it belongs in a product-first EV buying journey rather than as generic display inventory.
A direct private inbox is not published yet. If the site grows into a more data-heavy or commercially complex service, this page and the privacy notice should be updated with a stronger contact route.