Used Lot Signal · Privacy
What happens when you submit a lot.
This page describes the information flows currently visible in Used Lot Signal for U.S. used-car dealers: the public URL you submit, the observations made from readable pages, the resulting audit, and the optional ways to contact you.
At a glance
Four kinds of information stay distinct.
Submitted information
A public dealership or inventory URL, and—when signed in—dealer context such as a name, city, state, or holding-cost rate.
Page observations
Information readable on the bounded public pages, such as listing details, source excerpts, and capture metadata.
Derived outputs
Audit scores, evidence, reports, rewrites, action plans, and recommendations created by the workflow.
Optional inputs
Feedback, a next action, or an email address entered to receive a completed result link.
01 · Public intake
Start with one public URL.
The public Lot Audit form accepts one public HTTP or HTTPS dealership or inventory URL. It does not require sign-in. When you submit it, Used Lot Signal creates a request token, saves the URL with a queued or pending status, and opens a tokenized public result path. The public intake does not collect an email address when the request is created.
A signed-in audit can additionally include a dealer name, city, state, and holding-cost rate. Those fields are part of the authenticated audit workflow rather than the public URL-only intake.
02 · Review data
The audit stays close to readable pages.
The workflow reads bounded public pages on the submitted host through its configured page-reading service. It can store the source title and markdown, source URLs and excerpts, provenance, capture metadata, retrieval status, timestamps, and truncation details.
It can also store listing fields and observations such as stock, year, make, model, trim, price, mileage, and photos. The configured AI workflow can produce structured vehicle facts, scoring, listing rewrites, action plans, and recommendation drafts. Reports, evidence, snapshots, feedback, and realized outcomes are stored when those parts of the workflow are used.
The result reflects what the configured public-page review can read and process. It does not turn unavailable page information into an observation.
03 · Results
A token connects you to the result.
Public result endpoints use the request token to find the audit. When a result is complete, the result flow can expose the report as a web result, JSON, or PDF. It can also accept feedback and a next action for a unit.
The result flow can accept an email address to send a link to the completed result. That address is an optional result-delivery input and is separate from the URL-only public intake.
04 · Accounts
Signed-in work stays tied to the account.
Used Lot Signal accounts use email and password sign-in. Account records include a name, email address, and email-verification state. Account credentials are represented in the authentication account record. Session records include an expiration and token, with optional IP address and user-agent fields.
Authenticated audit handlers scope audit data to the signed-in user. Depending on the workflow, authenticated records can include inventory snapshots, dealer notes, unit counts, review fields, feedback, and later outcomes.
05 · Contact
Contact requests have their own path.
The public contact form accepts a name, email address, optional inventory size, and message. It stores a contact message, first attempts to record the submission in the founder dashboard, and falls back to the configured company inbox when the dashboard does not record it. The app separately attempts an acknowledgment email to the visitor.
For general contact about Used Lot Signal, use the existing contact destination: lot-signal@polsia.app.
06 · Browser behavior
A few settings live in your browser.
When deploy analytics is configured, the visitor beacon creates or reuses a polsia_vidvalue in browser localStorage and sends it with the configured app slug to the analytics endpoint on page load.
The theme provider may store the selected theme locally. Signed-in authentication uses cookies for its session.
07 · Scope
A description of the current app behavior.
The current app does not establish retention or deletion periods, sharing or sale practices, security guarantees, legal rights or compliance status, or provider-specific handling terms. Those details are not stated here.