01
What LMA Stores
LMA stores account details, organization metadata, role and permission settings, lead records, lead activities, offer assignments, and location references required to run project lead workflows.
LMA
Privacy Policy
How LMA protects workflow data.
This policy explains how Project Lead Management System data is collected, used, protected, and reviewed across public access, authentication, lead operations, offer workflows, and organization-level administration.
Last Updated
May 11, 2026
This document applies to LMA public access, login flow, and authenticated organization workflows.
02
How Data Is Used
Data is used to authenticate users, assign work, manage lead follow-ups, review pipeline status, apply offers, support dashboards, and keep access scoped to the correct organization and role.
03
Session And Cookies
The portal uses secure session cookies and refresh-token cookies to keep authorized users signed in and to route them to the correct organization dashboard.
04
Access Controls
Users only receive access intended for their organization, role, enabled modules, permissions, and organization-specific overrides.
05
Lead And Activity Data
Lead records may include contact details, address information, status, source, priority, assignee, and activity notes. Activity records may include call outcomes, free-text notes, and next follow-up dates.
06
Offer And Campaign Data
Offer data is used to manage discount types, validity windows, assignments, and offer status. These records help teams apply campaigns consistently and audit operational decisions.
07
Retention And Review
LMA data is retained for business continuity, support, audit, and reporting needs. Administrators may review records when investigating access issues, lead ownership, offer assignment, or workflow errors.
08
Support Requests
When users contact support, the team may use organization code, user email, lead code, and error context to diagnose issues. Support information is used only to resolve portal and workflow problems.