Information the service uses
LeadAnalyze uses your email address and profile name to maintain your account. We store uploaded lead files, address inputs, analysis results, credit balances, and transaction records to provide the service. Upload only information you are authorized to use, and include only the columns needed for your work.
How processing works
Cloudflare hosts the application and its private storage. Brevo delivers sign-in codes and company invitations. Stripe handles checkout and payment details; LeadAnalyze stores purchase references and credit records, not full card numbers. In the solar workflow, address inputs are sent to Esri’s ArcGIS World Geocoding Service for rooftop matching, and the matched coordinates are used only to request sunshine, capacity, and satellite imagery from third-party solar and mapping data providers. Geocoding results and satellite images are not stored. Customer contact columns are not sent to those analysis APIs. A satellite image of each analysed property is sent to a third-party image-analysis model to read roof material and visible panels. Lead files and contact columns are never sent to it, and the image is not stored.
Connected Airtable bases
If you connect Airtable, we store encrypted authorization credentials to access the bases you grant. We read table and view structure and the address and result fields you map, save a private snapshot for processing, and write analysis results to those mapped fields after you confirm a run. You can disconnect in your workspace to stop future access and write-back; analyses already started remain in your workspace. You can also revoke the authorization in Airtable. Abandoned preview record snapshots expire; scored records follow our analysis storage and deletion policy.
Address suggestions
As you type a single property address, the address text is sent through LeadAnalyze to a third-party address-suggestion provider; if that provider is unavailable, it is sent instead to the public Photon service operated by komoot, which uses OpenStreetMap data. We do not send your account name, email, uploaded list, or billing information with suggestion requests. LeadAnalyze does not store suggestion queries or unselected suggestions. Selecting a suggestion fills the address field; submitting the form then stores that address as part of your analysis input. Suggestions are optional, may be incomplete, and do not verify the property.
Property records and your private lead data
For new live analyses and reprocessing requests after this feature is enabled, we may standardize the address you submit and add it to an internal property registry. This helps connect future analyses of the same property and organize permitted property information. Only addresses that can be separated into structured address fields enter the shared registry; ambiguous or unparsed inputs remain in your private analysis records. A shared property record contains the standardized address and property observations; it does not contain account identifiers, source-list details, names, phone numbers, email addresses, or your other uploaded columns. Your original rows and their source history remain in a separate private layer associated with your personal or company workspace.
Property observations retain their source, date, confidence, and permitted-use information. Restricted third-party observations in this registry expire within 30 days, or sooner when required. The registry is for internal service enrichment; uploading a list does not grant rights to sell its contacts or use them for marketing. Existing saved analyses are not automatically added to this registry as part of the rollout, although a newly requested reprocessing run can contribute new permitted observations.
Storage and deletion
Analysis batches, their uploaded data, and results are kept in your workspace until an administrator deletes them. To request deletion, email support@leadanalyze.com from the address you sign in with. Deletion stops outstanding work and releases unused reserved credits; it does not reverse completed analyses or erase the credit ledger. It also removes the batch’s private source records and registry contributions. Property records with no remaining contributions are removed. Uploads that are never analysed are temporary and are removed by scheduled cleanup.
The existing shared analysis cache is separate from the new property registry. It is keyed by a one-way hash of the address and contains no account or lead-list information. Cache records are retained, while the current 30-day reuse window determines when they can serve another analysis. The new registry’s observation expiry does not delete historical workspace results or apply a new deletion schedule to that cache. Account, security, and payment records are retained separately as needed to operate accounts, resolve transactions, and meet applicable obligations.
Exports leave our storage and become your responsibility. An export does not establish permission to contact the people listed.
Company workspaces
When you accept an invitation or create a company workspace, its members can see company analyses, results, and shared credit activity. Owners and admins manage membership and credit purchases. Members can submit analyses and export company results; viewers can inspect results but cannot export or spend credits. Company members can see the names, email addresses, and roles of their teammates. Upload only information you are authorized to share with that company. Removing a member ends their future access; company records and purchased company credits stay with the company. Personal workspace data and credits stay separate.
Connected systems and export settings
API keys let an authorized external system read saved workspace results and, when granted write access, submit addresses using that workspace’s credits. We store a one-way hash of each key, its name, creator, permissions, expiration, and most recent use. The full key is shown only when created. Company API keys stop working if their creator loses company owner or admin access. Request identifiers help prevent repeated submissions from reserving credits twice. Your saved export preferences belong to your account within each workspace; they filter downloaded CSV files without deleting stored results. Data downloaded by an integration is handled by that system under its own policies.
Administrator support access
Authorized LeadAnalyze administrators can inspect account details, saved analyses, results, and credit activity to provide support. Our support viewing mode is read-only, expires after at most 30 minutes, and records when a view starts and ends. Administrators remain signed in as themselves. This mode cannot start analyses, spend credits, purchase credits, export data, or change your account.
Website analytics
We use aggregate counters to understand visits to our public website. Counters contain a fixed page category, mobile or desktop layout, date, and number of views. They do not contain names, emails, account identifiers, uploaded addresses, search text, full URLs, or referrers. The browser collector does not run on sign-in, workspace, administration, API, or setup pages, or during administrator support viewing. It respects Global Privacy Control and Do Not Track signals and uses no analytics cookies, browser storage, visitor identifiers, or session replay.
Cloudflare may supply approximate country, U.S. state, city, and five-digit ZIP information from its network metadata. Our aggregate analytics tables do not store visitor IP addresses or visitor coordinates. City locations are public city centers. City and ZIP reporting hides groups with fewer than five page views; this threshold counts views, not people, and does not guarantee anonymity. We keep these aggregate browser counters for up to 90 days and remove older rows through scheduled cleanup.
Separate Cloudflare network summaries can show estimated unique IP visitors, requests, and countries. These estimates can include bots, APIs, and assets and are not counts of verified people. Cloudflare's network reporting and infrastructure logs are separate from our browser collector, so the collector's exclusions do not apply to those summaries. Account creations, completed analyses, and verified credit purchases are separate aggregate reports from service records. A page visit is never treated as a signup or purchase, and anonymous counters are not linked to individual customer activity.
Cookies and local preferences
A secure session cookie keeps you signed in. Short-lived browser-bound challenges protect email sign-in. Your theme preference is stored locally in your browser. We do not use advertising cookies in this application.
Your choices
You can update your profile in your workspace. Contact support@leadanalyze.com to request account access, correction, batch or account deletion, or to raise a privacy concern. We may need to verify account ownership before acting. Transaction records that must remain for accounting or dispute handling are treated separately from lead data.
Service providers
Providers process information under their own applicable terms and privacy notices: Cloudflare, Brevo, Stripe, Esri, and komoot, along with third-party solar, imagery, and image-analysis providers. Address suggestions may use OpenStreetMap data. Services may process information outside your location. We do not sell uploaded lead files through this application.
Changes and questions
We will update this page when the service's data practices change. For questions, contact support@leadanalyze.com.