Privacy Policy

LEVRG Corp.
Effective date: June 13, 2026

This Privacy Policy describes how LEVRG Corp. (“LEVRG,” “we,” “us,” or “our”) collects, uses, and shares information in connection with the LEVRG platform and related websites and services (the “Service”). It applies to visitors to our sites and to users of the Service (for example, dealership managers and sales professionals) when acting on behalf of a business customer.

LEVRG processes information primarily on behalf of business customers and their authorized users.

If you do not agree with this policy, please do not use the Service.

1. Who we are

LEVRG Corp., a Delaware corporation, is the business responsible for this Service.
Mailing address: 3101 W Drexel Ave Unit 217, Franklin, WI 53132, United States
Contact: support@levrg.ai

2. Information we collect

We may collect:

• Account and profile data: name, email address, username, role, organization and store identifiers, and similar account details.
• Service and deal-related data: information entered or generated in the course of using the Service, such as deal context, objections, negotiation notes, coaching inputs and outputs, post-deal feedback (workflow-gated as implemented in the Service, except as the Service may permit limited deferral), deal outcomes, rep-submitted feedback, and performance-related metrics tied to authorized use of the Service, used as described in How we use information below.
• Usage and device data: log data, approximate location derived from IP, browser or app type, timestamps, pages or features used, diagnostics, and similar technical information.
• Marketing attribution: when you arrive via a tagged campaign link (for example, a printed QR code), we store first-touch campaign labels in your browser (cookies) for up to 90 days. When enabled by LEVRG, we may also store a coarse, hashed device bucket (derived from a truncated IP prefix and platform class—not your full IP or browser fingerprint) so the same campaign label can be restored in another browser on the same device and network. Shared networks may cause rare mis-attribution; we do not use this for advertising profiles.
• Analytics data: product analytics events that help us understand feature usage and reliability (collected through our analytics tools).
• Payment-related data: billing contact details and payment status; payment card data is typically collected directly by our payment processor (for example, a third-party payment processor), not stored on LEVRG servers.
• Communications: messages you send us (for example, support requests) and related correspondence.
• In-app suggestions and feedback: if you submit a suggestion, product feedback, or support request through the in-app Suggestions feature, we collect the text you provide and any screenshots or attachments you choose to upload. LEVRG operations staff review this content to operate and improve the Service.
• Information from integrations: if Customer connects third-party systems (for example, a CRM), we may receive information those systems make available according to Customer’s configuration and the third party’s terms.
• Pilot and sales inquiry data: if you submit a pilot request through our public form (for example, /request-pilot) or otherwise contact us about a pilot, demo, or evaluation, we collect business contact information (for example, full name, work email, role, dealership name) and the optional context fields you choose to provide (for example, phone, dealership website, current CRM/DMS, rooftop count range, monthly unit volume, preferred contact method and time, biggest sales challenge, and free-text notes). LEVRG sales personnel use this information to follow up with you about a pilot.
• Public Demo data: if you start a public Demo session, we issue a short-lived anonymous demo access token and may log the inputs you enter against synthetic, seeded demo deals (real dealership data is not exposed in Demo Mode). Demo session data is retained as described in Retention below.
• Anti-abuse signals: for public forms (for example, the pilot request form), we use a bot-mitigation service that may receive your IP address and a challenge token to verify human use. We do not use those signals to build advertising profiles.
• Website visitor identification (public marketing pages): when you visit our public marketing site (for example, the homepage, pilot request page, or public demo entry), we and our vendors may use cookies, session storage, and similar technologies to recognize your browser, log pages viewed, referrer and campaign parameters (for example, UTM tags), and approximate location derived from IP. We use Apollo.io to help identify the company you may represent. When enabled in our Apollo configuration, U.S. visitors may also be matched at a contact level using identity-resolution partners such as LiveIntent, which may receive browser signals and hashed email identifiers. We may also use Microsoft Clarity to record how you interact with public marketing pages (for example, clicks, scrolls, and session replays) so we can improve site experience. These technologies do not run on authenticated dealership workspace pages (for example, /rep or /manager).
• Optional username storage (sign-in only): if you choose Remember my username on the sign-in or manager onboarding screens, we store your username in your browser’s local storage for convenience on return visits. This is separate from marketing analytics and requires your explicit opt-in on those screens.

Cookies and analytics

This summary describes how LEVRG uses cookies, local storage, and similar browser technologies on our public website and sign-in flows:

Marketing analytics and attribution technologies load automatically on public marketing pages. The only optional browser storage we offer is Remember my username, which you control on sign-in screens. For questions or opt-out requests, contact support@levrg.ai.

3. How we collect information

We collect information: (a) directly from you or Customer’s administrators, including through public forms such as the pilot request form; (b) automatically when you use the Service or interact with our public pages; (c) from third-party integrations Customer enables; (d) from our bot-mitigation provider when you submit public forms; and (e) from website visitor-identification and analytics vendors on public marketing pages, as described above.

4. How we use information

We use information to:

• Provide, operate, maintain, and secure the Service;
• Authenticate users and manage accounts, seats, and permissions;
• Generate AI-assisted outputs and analytics for authorized users;
• Use post-deal feedback and deal outcome information submitted through the Service in connection with coaching outputs, talk tracks, tactic surfacing, analytics, and related product functionality (without guaranteeing any particular result);
• Operate our own sales and prospect outreach in response to inquiries you submit (for example, contacting you about a pilot or demo, scheduling a walkthrough, and tracking your inquiry through our internal pilot pipeline);
• Operate the public Demo Mode, including provisioning anonymous demo sessions and reviewing usage to maintain demo quality and integrity;
• Verify that public-form submissions come from humans rather than automated bots;
• Troubleshoot, debug, and improve performance and user experience;
• Review in-app suggestions and attached content to operate and improve the Service;
• Analyze usage trends at an aggregate level;
• Communicate about the Service, including service-related notices;
• Comply with law, enforce our terms, and protect rights and safety;
• Send marketing communications where permitted and with appropriate consent or opt-out, when applicable;
• Understand which businesses visit our public marketing pages and support B2B sales follow-up (for example, after a pilot inquiry), using visitor-identification tools on those pages.

5. AI processing

To provide certain features, we may send portions of your inputs to third-party AI providers (for example, large language model providers). Those providers process inputs to return outputs to the Service. LEVRG does not provide information or content submitted through the Service to third-party AI providers for the purpose of training general-purpose models for third parties. That limitation does not restrict our processing of information—including by LEVRG—to operate, support, personalize, or improve the Service for our customers. LEVRG does not sell your personal information to AI providers. We implement reasonable safeguards designed to protect information processed through the Service, consistent with the nature of cloud-based AI services.

6. Aggregated and de-identified data

We may derive aggregated or de-identified data that does not reasonably identify Customer or any individual. We may use such data for analytics, product development, research, and commercial offerings (including regional or industry-level insights), in accordance with applicable law.

7. How we share information

We may share information with:

• Service providers and processors who perform services on our behalf, such as:
  • Website and application hosting (for example, edge and serverless hosting providers);
  • Cloud application hosting (for example, container or application platforms);
  • Database, authentication, and backend infrastructure providers;
  • Email and communications delivery providers, used both for transactional mail (for example, password resets, weekly reports) and for routing pilot-inquiry notifications to a LEVRG sales address (for example, sales@levrg.ai);
  • CDN, DNS, and traffic proxy (for example, Cloudflare), which processes IP addresses and request metadata for all traffic to levrg.ai;
  • Bot mitigation and anti-abuse providers (for example, Cloudflare Turnstile), which may receive the visitor IP address and a challenge token from public forms to verify human use;
  • Product analytics providers;
  • Error monitoring and logging providers;
  • Payment processing providers;
  • AI inference providers;
  • Website visitor identification and B2B prospecting providers (for example, Apollo.io and LiveIntent), which may receive page-view signals, IP address, browser or device identifiers, referrer and campaign parameters, and (for U.S. person-level identification when enabled) hashed email signals; and other vendors we engage to operate the business. We may change or add vendors over time.
• Professional advisors (lawyers, accountants) under confidentiality obligations.
• Authorities when required by law or to protect rights, safety, and integrity.
• Corporate transactions such as a merger, acquisition, or financing, subject to appropriate protections.

We do not sell your personal information for money. We do not share personal or dealer-identifying information with competitors for their independent commercial use. We may share data with processors as described above to operate the Service.

8. Retention

We retain information for as long as necessary to provide the Service, comply with legal obligations, resolve disputes, and enforce agreements. Operations may shorten any retention period for a specific tenant or jurisdiction when contract or law requires it; the defaults below describe baseline product policy.

This anonymization commitment does not apply where retention of identifiable data is required by law.

9. Security

We use reasonable administrative, technical, and organizational measures designed to protect information appropriate to the sensitivity of the Service. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

Data is encrypted in transit using TLS and encrypted at rest on managed infrastructure. User passwords are stored using one-way cryptographic hashing and are never recoverable in plain text. Selected sensitive fields (for example, optional time-based one-time-password (TOTP) secrets used for two-factor authentication, and certain financing-related deal fields) are additionally encrypted at the application layer. Optional two-factor authentication is available on certain accounts.

10. Your rights and choices

Depending on your location and role, you may have the right to:

• Access or receive a copy of certain personal information;
• Correct inaccurate information;
• Request deletion of certain information, subject to legal exceptions;
• Object to or restrict certain processing;
• Opt out of certain communications;
• Withdraw consent where processing is consent-based.

To exercise rights, contact support@levrg.ai. We may need to verify your request. If you are an end user of a business Customer, we may route requests through that Customer’s administrator where appropriate. Authenticated users may also request a copy of their personal data from inside the product (for example, via the in-app data export endpoint at /users/me/data-export).

11. U.S. state privacy notices

If you are a resident of a U.S. state with a consumer privacy law, you may have additional rights regarding personal information. We describe our practices in this Policy. To exercise applicable rights, contact us at the email above. We do not use personal information for cross-context behavioral advertising as a core part of the Service; if that changes, we will update this Policy.

Website visitor identification on our public marketing pages (Apollo.io, Microsoft Clarity, and related partners) may involve sharing online identifiers and page-activity signals for B2B prospecting and site improvement. To opt out of those technologies or exercise other applicable rights, contact us at the email above or use profile settings where available (for example, Do Not Sell or Share).

To exercise your Do Not Sell or Share right, visit your profile settings or contact support@levrg.ai.

12. Children

The Service is not directed to children under thirteen (13), and we do not knowingly collect personal information from children under thirteen. The Service is intended for business users who are adults.

13. International users

LEVRG is based in the United States. If you access the Service from other countries, you understand that information may be processed in the United States and other locations where we or our service providers operate.

14. Changes to this Policy

We may update this Policy from time to time. We will post the updated Policy with a new effective date and, where appropriate, provide additional notice. Your continued use of the Service after the effective date may be subject to the updated Policy.

15. Third-party links

The Service may contain links to third-party sites. We are not responsible for their privacy practices.