How to Add Custom Disclosures in SecureWebX

Write the wording your store is required to show, once, and attach it to the applications that need it. Every customer who signs is recorded agreeing to the version they saw.

1. Open the compliance settings

   Open the SecureWebX console from the dock in the CRM and go to your company's compliance settings. This is where your privacy notice, your terms and State-specific disclosures live, and it is the library the apply links draw from. Adding a disclosure here takes a role with access to company settings, so it is usually the finance director or a master administrator.

2. Add the disclosure

   Click Add disclosure and give it a title that names the thing, not the file it came from. The field shows e.g. California Disclosure as the hint, which is exactly the right shape: the state or the subject, in words your finance office will recognize in a list two years from now.

3. Paste the exact wording

   Put in the text your counsel or your state association gave you, word for word. Do not paraphrase a required notice to make it read better, and do not merge two notices into one paragraph because they are both about privacy. Set the state it applies to so it can be pulled onto the right applications later, then click Save disclosure.

4. Put it on the apply links that need it

   Open the apply link in the customizer and go to Disclosures. Use Add from library to pull in the one you just wrote, which keeps a single source for the wording across every link. The customizer is where each link gets its own Add fields, sections and disclosures to this application treatment, so a link for out of state buyers can carry a different set than the one on your website.

5. Write a one off when a link needs it

   Some disclosures belong to one path only, such as a notice tied to a particular promotion or a commercial application. Use Add a disclosure inside the customizer, give it a Disclosure title and type the text there. It lives on that link, which is the point, and it does not clutter the company library.

6. Require the acknowledgment and preview it

   Set whether the customer has to acknowledge the disclosure before they continue. Then open the apply page yourself and read it on a phone, because a disclosure that is technically present and practically unreadable helps nobody. Check the line breaks, check the length, and check it appears on the step where a customer expects it.

7. Keep them current

   Put a standing item on someone's calendar to reread the library. When a state changes a requirement, you edit the disclosure once in the console and every link that uses it shows the new wording from that moment on. Applications already signed keep the version the customer actually agreed to, which is the whole point of versioned terms.

You need the SecureWebX console, which opens from the dock in the CRM with the login you already use, and the wording you intend to show. The console gives you the editor, the library, the acknowledgment and the record of who agreed to what; your counsel owns the words. That division is worth keeping straight, because the part software does well is proving what a customer saw and when, and the part your attorney does well is deciding what that should say.

It also helps to have your apply links sorted out first. Disclosures attach to links, so knowing which links exist, and what each one is for, decides where each notice belongs. How to customize an apply link covers the customizer itself, and compliance disclosures and privacy notices covers the wider picture of per store legal text inside SecureWebX.

In the console, your disclosures listed under State-specific disclosures, each with a title, the state it belongs to and the text you pasted, all editable. In the customizer, a Disclosures area on the apply link showing which ones that link carries and in what order.

On the customer's side, the disclosure appears inside the branded application at the point you placed it, with the acknowledgment if you required one. When the customer signs, the e-signature and consent capture records the exact version of the terms and disclosures they agreed to, together with when they agreed. That record stays with the application in the credit application inbox, where a manager can open it months later and see precisely what the customer was shown.

Archiving is how records leave the active list. Nothing is deleted, which is what you want the day someone asks what a customer saw on a Saturday last spring.

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.

Ask your counsel, then put what they give you in the library. The pattern most stores end up with looks like this: a privacy notice, the consent to obtain credit information, an electronic signature and electronic records consent, a contact consent covering calls and texts, and one or more state specific notices for the states the store sells into. Dealers who sell across state lines usually keep one link per market so the right set travels with the right customer.

Two habits separate the stores that sail through a review from the ones that scramble. The first is writing each notice once and reusing it from the library, instead of pasting slightly different wording onto four links and losing track of which is current. The second is treating the acknowledgment as a feature and not a nuisance: a customer who checked a box next to a notice they could actually read is a customer whose file holds up.

Compliance here is built into the way the system works rather than bolted on. Bot protection sits on the public form, application data is encrypted once submitted, every sign in to the console uses two factor authentication, uploads are virus scanned and a full audit log records who opened, edited, shared and exported each application. Adding your disclosures is the last piece that only your store can supply.

The disclosure is in the console but not on the application. It is in the library and not yet on the link. Open the apply link in the customizer, go to Disclosures and use Add from library.

It shows on one link and not another. That is the design. Each link carries its own set, so add it to every link that needs it, and leave it off the ones that do not.

The formatting looks wrong on a phone. Long notices pasted out of a word processor can arrive with odd spacing. Retype the paragraph breaks in the editor and preview the apply page on a phone before you send it to a customer.

You changed the wording and want to know what older customers saw. Open the application in the inbox. The signed record holds the version of the terms and disclosures in force when that customer signed, not the version you are looking at today.

Your state requires something the editor does not obviously cover. It is available on request, and our team puts it in production for your dealership. Send the wording and the requirement to our team and it gets built.

Adverse action notices are generated from the application record itself and are covered on adverse action notices. Screening runs on every application, described on OFAC screening. The security that surrounds all of it, from encryption at rest to the watermarked document viewer, is on credit application security.

The LeadLocate Help Center has the rest of the SecureWebX guides, including creating and customizing apply links and reviewing applications as they arrive.

Where do custom disclosures live in SecureWebX?

In the company compliance settings in the dealer console, under State-specific disclosures. Apply links then pull from that library, so the wording has one source.

Can different apply links carry different disclosures?

Yes. Disclosures attach to a link, so your website link, your special finance link and an out of state link can each carry the set that belongs to it.

What happens to applications signed under older wording?

They keep it. Consent is captured against versioned terms, so each signed application records the exact disclosures the customer saw and when they agreed.

Can I require the customer to acknowledge a disclosure?

Yes. Set the acknowledgment on the disclosure and the applicant has to accept it before continuing, and the acceptance is stored with the application record.

Per store disclosures, privacy notices, versioned terms and consent capture come with SecureWebX on every LeadLocate plan. See it in the pre-recorded demo.

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