DLRBoost Privacy Policy
This Privacy Policy describes how DLRBoost collects, uses, shares, retains, and protects information through its dealership software and related services.
1. Scope
This Privacy Policy describes how DLRBoost LLC (“DLRBoost,” “we,” “us,” or “our”) handles information through its website, application, dealer onboarding, customer offer pages, historical opportunity activation, routine imports, communications, support, and payment workflows. It does not replace a dealership’s own privacy notices or govern its independent operations.
2. Our Roles
For customer information provided by or processed for a dealership (“Dealer Customer Data”), the dealership generally determines the purposes of processing and DLRBoost generally acts as its service provider or processor, subject to applicable law and the Dealer Agreement. DLRBoost independently controls information needed to administer its own business, including dealership subscriptions, billing, support, and security.
3. Categories of Information
We process the categories described below, depending on the features actually used. Not every category is collected from every person.
| Category | Examples | Sources |
|---|---|---|
| Dealership and user details | Dealership name, business contacts, work email, role, login sessions, password hash, branding and account configuration | Dealer representatives and authorized users |
| Customer contact and vehicle records | Customer name, email, phone, VIN, year, make, model, delivery date, product purchase and eligibility data | Dealer reports and authorized users |
| Offer and evidence activity | Product offers, prices, customer selections, status, mileage, odometer photos, approval and contracting workflow | Dealers, customers, and platform workflows |
| Subscription and historical activation | Subscription and onboarding amounts, promotional discounts, selected historical activation package, accepted opportunity counts, invoice and payment status | Dealers, Stripe, and DLRBoost |
| Communications and imports | Email sends, delivery and unsubscribe events, file metadata, record counts, errors and processing status | Dealers, SendGrid, customers, and DLRBoost |
| Payments and technical data | Stripe identifiers, checkout and payment status, connected account status, IP address, cookies, browser, logs and security events | Stripe, devices, infrastructure providers, and DLRBoost |
| Support and administration | Messages, attachments, troubleshooting, billing and support communications | Dealership personnel, customers, and DLRBoost |
4. Sensitive and Payment Information
The platform is not designed for dealers to upload Social Security numbers, driver’s-license numbers, bank credentials, health records, or full payment-card numbers through routine customer imports or offer pages. Dealers should exclude unnecessary sensitive data. Payment-card details entered on Stripe-hosted pages are submitted to Stripe; DLRBoost receives relevant payment identifiers, status, amounts, and metadata rather than full card numbers.
5. How We Use Information
We use information to create and secure accounts; configure dealerships and products; process ongoing new-transaction imports and separately purchased historical opportunity activation; match products and suppress ineligible or previously purchased products; run dealership-authorized follow-up sequences; display offers; receive selections and odometer evidence; route notifications; create payment links; provide reporting, support, troubleshooting, fraud prevention, billing, compliance, and platform maintenance. Dealer Customer Data is processed for the dealership’s instructed services and other purposes permitted by applicable law and agreement.
6. Sources of Information
Information comes from dealerships and their authorized users, CSV/XLSX or scheduled CRM reports, customers interacting with offer pages, payment processors, email providers, hosting and storage vendors, browsers and devices, and communications with DLRBoost.
7. Dealership Customer Data and Instructions
As between DLRBoost and the dealership, the dealership retains its rights in Dealer Customer Data. The dealership is responsible for lawful collection, uploading, historical activation, product eligibility, customer-contact permissions, required notices, accurate data, and applicable opt-outs. DLRBoost processes that information under documented instructions, the Dealer Agreement, and applicable law.
8. Processing Grounds
Depending on the circumstances and applicable law, processing may be based on a contract, documented dealership instructions, consent where required, legitimate interests in security and business operations, compliance with law, and the establishment or defense of legal claims. The dealership determines its own lawful grounds for customer marketing.
9. Disclosures of Information
We disclose relevant information to the applicable dealership and its authorized users; vendors performing services; professional advisers where reasonably needed; authorities when legally required or to protect rights and security; and parties involved in a merger, acquisition, financing, restructuring, or sale subject to appropriate safeguards. We do not disclose Dealer Customer Data to unrelated third parties for their independent marketing.
10. Service Providers and Subprocessors
Depending on the service configuration, providers may include Stripe (billing, checkout and connected accounts), SendGrid (email), Render (application hosting), Supabase (database or private file storage), Google Workspace (business communications), and video, monitoring, security, or support providers. These providers have their own applicable agreements and privacy notices. DLRBoost uses providers as needed to deliver its services and applies appropriate contractual controls to processors of Dealer Customer Data.
11. Subscriptions, Onboarding, and Historical Activation Billing
DLRBoost offers one standard platform subscription at $499 per month, subject to accepted promotional or dealer-specific terms. The standard one-time onboarding fee is $795; qualifying founding-dealer offers may reduce onboarding to $395. Optional historical opportunity activation is separately purchased and billed in addition to onboarding and subscription fees. We may process subscription IDs, billing intervals, amounts, invoice status, promotional eligibility, selected activation tier, record counts, payment status, and related metadata. Commercial terms are governed by the accepted order and applicable agreements, not this Privacy Policy.
12. Stripe and Customer Payment Workflows
Stripe may collect payment-card, billing, business-verification, tax, ownership, banking, fraud-prevention, and payout information. DLRBoost may receive Stripe customer, subscription, invoice, checkout, payment-intent, and connected-account identifiers, transaction amounts, and payment or verification status. Customer payments for dealer products may be routed through a dealership’s connected Stripe account. The dealership is responsible for its product contracts, pricing, refunds, disputes, fulfillment, and customer service.
13. Email and Marketing Communications
DLRBoost sends dealership-authorized promotional follow-ups and operational messages, including the supported 5-, 14-, 28-, 60-, 120-, and 180-day follow-up stages where configured and appropriate. Actual sending depends on eligibility, suppression, configuration, and applicable law. Dealerships are responsible for determining lawful recipients and honoring opt-outs. Promotional emails should provide an appropriate opt-out mechanism; account, security, payment, and requested transactional messages may continue where legally permitted.
14. Historical Opportunity Activation
Dealers may elect no historical activation or purchase a package covering up to 2,500, 5,000, 7,500, 10,000, 15,000, or 25,000 eligible historical opportunities, or a custom package above 25,000. We may process uploaded historical records, validation results, duplicates, exclusions, eligibility flags, accepted opportunity counts, selected packages, and activation status. A record accepted for activation does not guarantee a message, customer response, eligibility, purchase, or revenue. The dealership must have lawful authority to use historical customer records.
15. Ongoing Imports
During an active subscription, routine imports of newly completed dealership transactions may be processed as part of the standard service, subject to technical requirements. Import logs may contain file names, dates, formats, sender information, submitted and accepted counts, duplicates, skipped records, errors, and workflow status.
16. Cookies and Session Technologies
We may use necessary cookies and session identifiers for login, authentication, account security, service functionality, fraud prevention, and performance. The application uses session technology for authorized access. We may also collect IP address, browser and device details, timestamps, and diagnostic logs. Optional analytics or other technologies, if enabled, are subject to applicable notice and choice requirements.
17. Embedded Videos and Third-Party Links
Dealer offer pages may contain embedded product videos or links to outside services. Video providers such as Vimeo or YouTube may receive IP address, browser, device, and interaction information when content loads. External services have their own privacy practices.
18. Sale, Targeted Advertising, and Profiling
DLRBoost does not sell Dealer Customer Data and does not use it for unrelated cross-context behavioral or targeted advertising. DLRBoost does not use Dealer Customer Data to make decisions producing legal or similarly significant effects regarding credit, employment, housing, insurance, education, or essential services. Automated product matching and exclusion assist dealership workflows; the dealership makes final product and contracting decisions. Statements concerning statutory “sale” or “sharing” depend on the practices and definitions applicable to the relevant data.
19. Aggregated and De-Identified Data
We may create aggregated or de-identified information that does not reasonably identify a person or dealership for reliability, security, product improvement, business analytics, and benchmarking, subject to applicable contractual and legal restrictions. We will not attempt to re-identify information maintained as de-identified except as legally permitted or needed to test de-identification safeguards.
20. Data Security
We maintain reasonable administrative, technical, and organizational measures appropriate to the information and risks involved. Depending on implementation, these may include access controls, authentication, encrypted transmission, private file storage, signed file links, upload restrictions, rate limiting, webhook validation, secret management, logging, and incident-response procedures. No system can be guaranteed completely secure.
21. Dealer and User Security Responsibilities
Dealerships and authorized users must protect credentials, restrict access to personnel with a business need, promptly remove departed users, use secure devices and networks, avoid unnecessary sensitive uploads, verify import accuracy, and report suspected account compromise.
22. Security Incidents
If DLRBoost identifies a qualifying security incident affecting Dealer Customer Data, we will notify the affected dealership in accordance with applicable law and the Dealer Agreement and provide reasonably available information to support the dealership’s response. Responsibilities for notifications to individuals or regulators depend on applicable law and the parties’ roles.
23. Retention Principles
We retain information for periods reasonably necessary to provide services, operate active workflows, support dealerships, prevent abuse, maintain security, meet tax and accounting obligations, resolve disputes, and comply with law. Retention varies by data type, contract, dealership instructions, and technical backup cycles.
24. Specific Retention Practices
Account and customer records may remain while a dealership subscription or related workflow is active and for an applicable offboarding period. Odometer evidence may remain while associated workflows require it. Import logs, security records, support records, and payment metadata may be retained for operational, fraud-prevention, legal, or accounting purposes. Expired session records may be removed; residual backup copies may persist until backup rotation or lawful deletion.
25. Export and Deletion
Dealerships may request a reasonable export of available Dealer Customer Data during an active subscription. Following termination, DLRBoost may disable access, allow an agreed export opportunity, delete active Dealer Customer Data under the Dealer Agreement and applicable law, and retain records that must be preserved for legal, security, payment, or dispute purposes. Backup copies may expire through normal cycles. Specific timelines should be established in the applicable contract and supported by actual systems.
26. Privacy Rights
Depending on applicable law, individuals may have rights to access, correct, delete, or obtain copies of personal information; opt out of certain processing; appeal certain decisions; or exercise rights without unlawful discrimination. Rights are subject to identity verification, exceptions, and the law applicable to the relevant information.
27. Requests Involving Dealership Customer Data
For information supplied by a dealership, individuals should ordinarily contact that dealership first. If DLRBoost receives a request concerning Dealer Customer Data, we may direct or forward the request to the dealership and provide reasonable assistance consistent with our obligations. We do not independently determine a dealership’s marketing or retention obligations.
28. Requests Involving DLRBoost Business Data
Dealership representatives and other individuals may contact support@dlrboost.com about information DLRBoost controls. Please describe the request and provide enough information to locate the relevant account without sending unnecessary sensitive documents.
29. Verification, Authorized Agents, and Appeals
We may verify identity, email ownership, dealership affiliation, or an agent’s authority before responding to a request. Verification measures will be proportionate to the request and information involved. Where applicable law provides an appeal right, email support@dlrboost.com with the subject “Privacy Request Appeal.” We will review and respond as required by applicable law.
30. Children
The Services are intended for dealerships, dealership personnel, and adult vehicle customers. They are not directed to children under 13, and we do not knowingly solicit information directly from children under 13. Contact us if you believe a child submitted information.
31. United States Operations and Transfers
DLRBoost operates from the United States. Information may be processed in the United States and other locations used by service providers. The Services are intended for U.S. dealerships and customers unless otherwise agreed in writing.
32. Browser Privacy Signals
Some browsers offer “Do Not Track” settings, which are distinct from legally recognized opt-out preference signals. We do not currently respond to legacy Do Not Track signals. Where an applicable law requires recognition of a valid opt-out preference signal for covered processing, we will address that requirement based on our actual data practices.
33. Changes to This Policy
We may update this Privacy Policy for changes in our services, vendors, law, or practices. We will publish a revised effective date and provide additional notice of material changes where appropriate or required.
34. Contact
For privacy questions or requests, contact DLRBoost LLC at support@dlrboost.com. For a request about a dealership customer record, identify the relevant dealership and enough information to locate the record.