Controlled pilot
Privacy notice
Updated September 11, 2026
AvLu™ is a controlled pilot review workflow for vehicle and equipment opportunities. It organizes listing facts, source links, quote assumptions, proof gaps, seller notes, feedback notes, and final human decision notes.
What may be collected
Public intake and feedback forms may collect the information a user chooses to submit, including listing details, contact name and email, optional phone number, company, source addresses, VIN or serial status, asking price, mileage or hours, location, repair concerns, proof status, and feedback.
How pilot data is used
Pilot submissions are used to review the workflow, prepare listing review packages, identify proof gaps, test the product, and follow up when permission is provided. Review state may also be saved in the browser or in the configured pilot storage system.
Walkthrough requests submitted through the public contact form are offered to FormSubmit for delivery to the designated AvLu inbox. The page reports success only after FormSubmit returns a positive JSON receipt; that receipt confirms service acceptance, not inbox reading or a reply. FormSubmit states that it retains form submissions for 30 days. Do not use the contact form for sensitive or confidential records.
Customer research and optional gift-card entries
The homepage research form collects the answers shown, an optional first name and research email, and a separate optional gift-card entry email. Incoming UTM source, campaign, and content values plus the referring site origin and path may be retained with the research response. Referrer query strings and fragments are not retained. Answers are offered to the configured website storage system and FormSubmit for delivery to AVLU. A positive service receipt confirms acceptance, not that AVLU has read a message. Answers may be summarized without names for product development and gBETA or I-Corps customer discovery. Survey responses are not permission to publish a named quote.
Research follow-up permission is optional and separate from entering the drawing. Gift-card entry contact information is used to administer the drawing. Research answers are not saved to browser storage. Initial campaign attribution is retained only for the browser tab session so it can accompany a submitted response. You may request deletion by contacting Contact AVLU. Please do not submit customer records or confidential information.
Minimal funnel measurement
AvLu records a limited first-party funnel event for a landing visit, first meaningful survey interaction, successful survey completion, real-listing link click, or interview-booking link click. Each event contains only the event name, timestamp, page path, and a random non-identifying identifier limited to the browser tab session. It does not include survey answers, contact details, gift-card information, listing details, UTM values, or the referrer.
Private workspace sign-in
The private AvLu workspace is owner-only. If email sign-in is enabled, the browser uses Replit-managed Clerk to request and verify a one-time code. Public input cannot create an account. Password sign-in is disabled. The AvLu server independently verifies the resulting Clerk session and checks its verified primary email against the approved owner. AvLu returns generic responses that do not confirm whether an email is approved.
AvLu does not save the one-time code or the Clerk session token. A successful exchange creates a separate random AvLu session cookie. The server stores only a digest of that AvLu token with the owner role, authentication method, timestamps, and revocation state. Abuse-control keys are derived so raw email and client addresses are not stored in the throttle table.
Decision alerts and browser notifications
The protected Review Desk can calculate an in-app screening alert from the numbers and human decision already visible in that review. The temporary reviewer confirmation is not saved and is cleared whenever a relevant identity, proof, cost, resale, or decision input changes. Illustrative samples cannot produce an actionable alert.
Browser notifications are optional. The signed-in user must click to request browser permission. AvLu does not save a separate notification preference, register a service worker, or send decision alerts through an external provider. A native notification is shown only while the protected tab is visible and focused, and its generic message contains no VIN, seller, vehicle, price, contact, or source details. Browser permission itself is controlled by the browser.
What not to submit
Do not submit unnecessary private information, payment credentials, medical information, government identification, private title documents, lien documents, customer financial records, or other sensitive material through public forms.
Storage and deletion
AvLu uses PostHog Cloud in the United States for product analytics. It records pageviews, interaction counts, named journey milestones, and technical browser, device, and session identifiers. Event properties also include route, journey stage, environment, and app version. This is separate from the minimal first-party funnel measurement described above. Session recording is disabled. The analytics boundary removes form-field values, element text and attributes, query strings, referrers, passwords, authentication tokens, VIN or listing details, contact information, customer financial details, and free-form intake content before an event is sent.
The pilot supports local preview storage and a production-style storage adapter. Authenticated admin controls provide narrow exports, targeted deletion, and minimal deletion-event logging. Exported files should be stored outside the public repository.
On the public Vercel preview, a client review draft is stored only in that browser using local storage; it is not sent to AVLU through the review API. The draft can remain on that device until it is cleared from the review handoff or the browser's site data. The separate contact form still sends the fields shown on that form through FormSubmit.
Source Search packets saved on the public preview also stay only in that browser. JSON and CSV exports download to the user's device. Saving or exporting a candidate packet does not send it to AVLU, verify any source, or promote it into AvLu's completed dealer evidence.
Contact
Questions about pilot data or deletion requests may be directed to AVLU at Contact AVLU.