Compliance Disclosures and Privacy Notices per Store

Your disclosures, your privacy notice, your terms, in your words, for your states, shown on every application and kept by version. One editor, no vendor ticket.

Every credit application a dealership takes carries language the store is responsible for: the credit authorization, the state specific disclosures the store's counsel requires, the privacy notice that tells the applicant what the store does with their information, and the terms under which the application is submitted. In most stores that language lives in a folder of PDFs, a website footer and the memory of whoever set up the last vendor. In SecureWebX it lives in the console, under the store's own control, and it appears on every application the store's apply links produce.

Four things make up the feature. State specific disclosures are added, edited and deleted per state, and shown on credit applications. A privacy notice and terms editor lets each company keep its own notice and its own terms current, with formatting. Disclosures can also be added to an individual apply link, with acknowledgment required before the applicant continues. And every user of the console is required to accept the terms before they work, so the store's own people are on the record too. Underneath all of it, the applicant's consent is captured against versioned terms, so the exact language each customer agreed to is kept with their application.

This page is the product side. The dealership compliance document management page covers the wider problem of where a store's documents and consent records go wrong and how a secure intake layer fixes the trail.

The store's compliance counsel sends an updated paragraph for the disclosure the store shows applicants in one of the two states it sells into. The office manager opens the SecureWebX console, goes to Compliance Settings, finds that state's entry under State-specific disclosures, pastes the new language into the editor, tidies it with a heading and a bulleted list, and saves. From that moment the application shows the new language to applicants in that state. The old language is not gone: every applicant who signed under it has their consent recorded against that version.

The same afternoon the special finance manager asks for an extra disclosure on the special finance apply link only, a short acknowledgment about the documents the store may request. The office manager opens that link's customizer, adds the disclosure, sets it to require acknowledgment, and saves. The website link is untouched. The following week a new finance manager joins; on first sign in to the console she is asked to read and accept the terms before she can open an application, and her acceptance is recorded with the date.

None of that involved a support ticket, a vendor, or a wait. That is the difference between a compliance record a store owns and one it rents.

Leave your number and a lead specialist calls you back to answer your questions about pricing, coverage, and setup. Mon - Sat, 9:00 AM - 6:00 PM Pacific.

Prefer to talk right now? Call or text 844-376-2274.

Dealerships that sell across a state line, or that draw from a neighboring state's buyers, deal with disclosure requirements that differ by state. Under State-specific disclosures the store adds a disclosure, selects the state, gives it an optional title such as a state name followed by the word disclosure, writes the language in the editor and chooses whether to show it on credit applications. A disclosure is edited when counsel changes it and deleted when it no longer applies. The editor supports bold, italic, underline, headings, bulleted and numbered lists and links, so the language reads the way counsel wrote it rather than as a wall of text.

Disclosures shown on credit applications are presented to the applicant on the review step, alongside the standard credit authorization and the e-signature. What the applicant sees and agrees to is recorded against the version in force at that moment. The online credit application form page walks the five steps the applicant works through, including where the disclosures appear.

The store's privacy notice and terms are edited in the same console, per company. A dealer group with several rooftops keeps each store's notice separate; a single store keeps one. The editor is the same one used for disclosures, and the notice and terms it produces are what applicants and console users see. The store's own privacy policy and terms of service URLs can be recorded on the company as well, so the notice in the application and the policy on the website point to the same thing.

The point of doing this in the console, rather than in a vendor's template, is ownership. A store's counsel decides what the privacy notice says. The console makes it possible to change the language the day counsel sends it, and to know exactly which version every applicant saw. Software supports a compliance program, it does not write one, and this editor is where the store's own program gets put in front of the customer.

Some disclosures belong to a path rather than a state. A special finance link might carry an acknowledgment about documentation; an event link might carry the terms of the event. Each apply link is customized separately, and a disclosure added to a link appears only on that link's application. The customizer draws from a compliance library, so a disclosure written once is added to another link from the library rather than retyped. The drawn signatures and the credit authorization are always included on every link, whatever else the store adds.

A disclosure on a link can be set to require acknowledgment. The applicant does not continue past it without acknowledging, and the acknowledgment is captured with the consent. The customizer also states the store's compliance responsibility plainly, because the language on a link is the store's language. The apply links page covers everything else a link can carry, from extra sections to document uploads.

Two mechanisms hold the record together. The first is forced terms acceptance: every user of the console, from the dealer principal to a newly invited salesperson, is required to read and accept the terms before working in it. The acceptance is recorded, so the store's own people are on the record for the conditions under which they handle applicant data. When terms change, acceptance is required again.

The second is versioned consent on the applicant side. Every application ends with an e-signature and consent capture against the terms and disclosures in force at that moment. When the store changes a disclosure, SecureWebX keeps the exact prior version each earlier applicant agreed to, and when. A question about what a specific applicant consented to, asked months or years later, has a specific answer. Combined with the archive, never delete rule, the full audit log and a watermarked PDF viewer with print and download gated, this is the record keeping layer a compliance program relies on.

Everything on this page lives in the SecureWebX console, which opens from the SecureWebX button in the LeadLocate CRM dock with one login. State disclosures, the privacy notice and the terms are under Compliance Settings. Per link disclosures are in each link's Customize application screen. Terms acceptance meets each user at sign in. Users are invited with roles, so a store decides who may edit compliance language.

It replaces the folder of disclosure PDFs with three versions of the same document, the paper application with a disclosure block that was last updated when the forms were printed, the website privacy page that says one thing while the application says another, and the vendor ticket to change a sentence. It also replaces a purchase: compliance vendors sell disclosure and consent management to dealerships as a separate module with its own invoice. Here it is part of SecureWebX, which is part of every LeadLocate plan, month to month, on the pricing page.

There is nothing to install. The console is created with your LeadLocate account, the standard credit authorization and signature are already on every apply link, and the store adds its state disclosures, privacy notice and terms from Compliance Settings whenever counsel is ready. If your store needs a disclosure behaviour the console does not already offer, it is available on request, and our team puts it in production for your dealership. Because SecureWebX runs as its own system, applications keep showing the store's disclosures and keep capturing consent even if the CRM is unavailable.

Pair the disclosures with adverse action notices, so the language a declined applicant receives is the language counsel approved. Pair the privacy notice with the store's consent records on every application, which the online credit application software page puts in the wider context of what an application system should do. The all features page lists everything else in the platform.

Can I add a disclosure for one state only?

Yes. Under Compliance Settings, add a disclosure, select the state, write the language in the editor and choose to show it on credit applications. Edit it when counsel changes it and delete it when it no longer applies.

Who writes the disclosure and privacy language?

Your store, on the advice of its compliance counsel. SecureWebX provides the editor, shows the language on every application, captures consent against it and keeps every version. It does not decide what the language must say.

What happens to consent records when I change a disclosure?

Nothing is lost. Applicant consent is captured against versioned terms, so every earlier applicant's consent stays tied to the exact version they agreed to, with the date. New applicants see the new version.

Can a disclosure apply to one apply link and not another?

Yes. Each apply link is customized separately, and a disclosure added to a link appears only on that link's application. It can require acknowledgment before the applicant continues, and it can be reused from the compliance library.

What is forced terms acceptance?

Every console user is required to read and accept the terms before working in SecureWebX, and the acceptance is recorded. When the terms change, acceptance is required again, so the store's own people are on the record.

Is this an extra module?

No. Disclosures, the privacy notice and terms editor, per link disclosures and terms acceptance are part of SecureWebX, which is part of every LeadLocate plan, month to month. Plans are listed on the pricing page.

Disclosures, privacy notices and versioned consent are part of SecureWebX and every LeadLocate plan, month to month. See a state disclosure added in the console and shown on the next application.

Prefer to talk right now? Call or text 844-376-2274.