Effective October 17, 2026
Privacy Policy
This policy explains how the Top Lead Recovery website, mobile application, and managed service handle information.
Information stored by the app
The app stores imported lead records, calculator values, readiness selections, lead decisions, message drafts, and locally recorded outcomes on your device so your work remains available when you reopen the app. These records are not uploaded merely because you import or analyze them.
Optional controlled email
If an authorized owner or manager requests a server preview or live send, the app transmits only the selected recipient names and email addresses, local record identifiers, sender and reply addresses, physical mailing address, subject and message, audience source, stated consent or relationship basis, and safety approvals needed to check and execute that campaign. Supabase processes authentication, workspace authorization, suppressions, approval fingerprints, campaign records, delivery state, and audit events. Resend processes the recipient address, sender details, subject, message content, unsubscribe headers, and delivery metadata needed to transmit and monitor the email.
Live email is blocked unless the sender domain is verified, the batch contains no more than 25 unique addresses, the server applies its suppression and recent-contact checks, and a person approves the exact server fingerprint. Every email includes a no-login unsubscribe link and the sender's physical mailing address.
Client workspace and sample mode
Authorized clients can sign in to a private workspace for their lead pipeline, calendar, notes, campaign drafts, quote drafts, and reports. Signed-in workspace data is stored in the connected Supabase service and isolated by workspace membership and row-level access controls. The optional sample mode is for evaluating the experience; its entries stay in that browser and are not synchronized. Use sample information only in sample mode. Enter real customer or lead information only after signing in to the correct authorized workspace.
Information we collect
The audit portion of the mobile app requires no account. Controlled email uses the existing secure workspace account and processes account and workspace identifiers needed for authentication and access control. Campaign delivery records may include accepted, delivered, delayed, opened, clicked, bounced, complained, failed, suppressed, and unsubscribed events supplied by the email provider. The app does not use advertising identifiers, third-party ads, cross-app tracking, or data brokers. When you request or use the managed service, we may also receive your name, business name, business email, business phone number, website, service area, approximate record count, qualification answers, communications, workspace activity, and payment-related identifiers.
Optional customer SMS requests
A business may provide a customer-specific notice for optional appointment and requested quote or service updates. That notice identifies the business, its dedicated sender, message purpose and frequency, support contact, and the business’s privacy and SMS terms pages. SMS is available only within Complete Service after the required account, registration, consent, delivery and usage checks. Our own company’s registration does not cover another business’s messages.
If you affirmatively request SMS through that notice, Supabase privately stores your phone number, the exact disclosure and its version, your choice, the server-recorded time, and the customer program and workspace needed to document the request. The request remains pending phone-holder verification. Saving it does not verify permission to send, send a confirmation text, create a HighLevel contact, clear existing STOP or do-not-contact choices, or enable messaging. An unselected SMS choice does not create a new SMS request.
We do not sell, transfer or disclose phone numbers or SMS opt-in data for another party’s marketing or promotions. Necessary service processors may handle messaging information only to provide, secure, support and document the requested service. Customer-specific requests are not transferred to another business’s SMS program.
The public SMS notice does not use analytics or browser storage. Its private notice reference is removed from the browser address after the page loads and is not sent as a referral URL. The server uses a keyed network-address hash and short-lived request counters to limit abuse. Hosting and server providers may process ordinary technical request records. Consent, suppression, delivery and financial evidence may need to be retained for compliance and recordkeeping; uninstalling or resetting the app does not delete those server records.
Optional company text-support requests
Our separate company form is for Top Lead Recovery walkthroughs and account support you request from SHOPPED SHIPPED SAVED LLC. If you choose to submit it, HighLevel/LeadConnector receives your name, phone number, message and the form’s displayed consent context, together with ordinary technical request records, to record and process the request. The form displays its contact-permission notice and links to provider policies. Our company SMS terms also describe this program. Email and phone support are available without using the SMS form.
Carrier registration and SMS activation are pending. This website form does not prove working SMS delivery, purchase a service, start a subscription or activate messaging for another contractor. Company requests are kept separate from customer-specific Complete Service SMS requests. An existing STOP or do-not-contact restriction must be honored before any future message is sent.
We do not sell or share phone numbers or SMS opt-in information for another party’s marketing or promotional purposes. Necessary service processors may handle the information to provide, secure and document your requested support. Contact us using the details below to withdraw a request or ask about eligible deletion; consent, communications and suppression evidence may need to be retained for compliance and recordkeeping.
Payments
Payments are processed by Stripe. We do not receive or store your complete card or bank-account number. Stripe processes payment, billing, fraud-prevention, receipt, and transaction information under its own privacy terms. For setup checkout, Stripe also collects the business name, contact details, website and service area, record location, and required policy acknowledgments needed to deliver and support the purchased service.
Lead-recovery service data
Approved business lead records may be processed through the signed-in client workspace, the mobile app's controlled-email flow, or another secure intake method provided for an accepted project. We use those records to perform the agreed audit, eligibility review, suppression and frequency checks, campaign delivery, reply routing, reporting, and support. When reply capture is configured, matched incoming email content and related sender, recipient, subject, and message identifiers are processed by Resend and Supabase and displayed to authorized workspace members in the Reply Command Center. Replies place the contact on hold for human review. Saving a review or draft response stores its classification, subject, message, and related identifiers; sending a response requires a separate preview and human approval. The native app does not scan an entire personal mailbox. Clients must not provide unnecessary sensitive information and must have lawful authority and an applicable consent or relationship basis to provide and use the records.
How information is used
We use information to evaluate qualification, communicate about setup, process and document purchases, provide requested audits and owner-approved email campaigns, protect recipients through suppression and frequency controls, measure delivery, secure and operate our systems, prevent misuse, meet legal obligations, and improve reliability. We do not sell customer or lead records or use them for third-party advertising.
Quote recovery and customer feedback
Client workspaces may store original quote identifiers, amounts, currencies, document links, versions, review decisions, and customer-specific booking or won-job results. Original opportunity value and recorded won-job value are separate from payments collected. Completed-job review requests may store the customer relationship, job reference, completion evidence, request link, submitted star rating, written feedback, and optional testimonial permission. Feedback is shared privately with the business that requested it. Submitting feedback does not post a review on another platform, and testimonial permission does not automatically publish it.
Support help and AI answers
Support help searches verified product guides. If live AI answers are enabled, your question and a limited recent conversation may be sent to OpenAI to produce a support answer. The support assistant does not retrieve private workspace records or perform account or customer-message actions. AI response storage is disabled in our API requests; OpenAI may retain limited technical or abuse-monitoring records under its data policies. Technical usage checks use a keyed network-address hash and short-lived request counters. Do not enter passwords, API keys, payment details, or customer records in support chat.
Optional AI drafting and document review
Where enabled, an authorized workspace owner or manager can ask OpenAI to draft a customer reply or extract fields from a selected estimate. Reply drafting uses the selected saved incoming message, limited prior outgoing text, the linked customer name, and an eligible quote only when the user selects it. Estimate extraction uses the document or pasted email text the user explicitly submits. Submit only information you are authorized to process and avoid passwords, payment-card details and unrelated sensitive information.
These requests do not send a customer message, approve an offer or save extracted fields automatically. Your team reviews and edits the result before using the separate save, preview and approval controls. Request storage is disabled in our OpenAI API calls; the provider's technical and abuse-monitoring retention may still apply under its data policies linked above. Usage receipts record identifiers, timing, token counts and cost without storing the prompt or generated answer. A reply or quote you choose to save follows the workspace's normal record retention.
Optional website lead assistant
A business may enable an AI assistant that answers questions using the public business facts it has approved. The visitor is told before a question is sent to OpenAI. This assistant does not look up private customer records. It uses a short-lived session and a keyed network-address hash to limit abuse and usage. Visitors should not put personal, payment or account credentials in chat. A separate contact form lets a visitor review their details and explicitly request contact; submitting it saves a request for the business to review and does not send marketing, charge a payment or confirm an appointment.
Retention and deletion
Business communications, campaign approvals, send attempts, delivery events, transaction records, and project records are retained only as reasonably needed for service delivery, security, deliverability, recordkeeping, disputes, and legal obligations. Unsubscribe, complaint, invalid-address, and hard-bounce suppressions may be retained for as long as needed to prevent unwanted or unsafe future sending. Requests to review or delete eligible information may be sent using the contact information below. Some suppression, financial, audit, or legal records may need to be retained even after other content is deleted.
Deleting app data
Select Reset my local entries on the Send screen to erase imported leads, calculator values, local decisions, drafts, outcomes, and audit selections stored by the app. Use Sign out separately to remove the saved account session. Reset local entries and sign out before uninstalling: operating-system secure storage, including iOS Keychain data, can remain after an app is uninstalled. If the reset reports an error, retry it or contact support. A local reset or uninstall does not erase server-side campaign, delivery, audit, or suppression records. Contact us for an eligible server-data request.
External links and voluntary submissions
The app can open qualification, support, and website pages in your browser. If you voluntarily submit information through an external email or contact page, that service may process the information needed to complete your request. Review the notice presented on that page before submitting personal information, and do not email customer or lead records.
Website and service records
Our website host and service providers may process ordinary technical records needed to deliver and secure their services, such as request time, device or browser information, and network address. Local calculator and audit entries are not included in ordinary website requests. Supabase and Resend process the controlled-email information described above only when that feature is used.
Website visits and demo requests
Selected public website pages and the web portal record page views, clicks on links to the audit tool or demo form, time, an allowlisted page path, and a broad source category such as direct, referral, Google Search pilot, or Hunter outreach. Recognized Google Ads and outreach links may add an allowlisted campaign code and ad variant, not the recipient. A random event identifier prevents duplicate submissions; it is not a persistent visitor identifier. These first-party page-view and click records do not contain names, email addresses, customer records, full referral URLs, search terms, advertising click identifiers, or arbitrary URL query strings. We do not set analytics cookies. Only the source category, recognized campaign code, and ad variant may be kept in the current browser session so a demo request can be associated with its landing source. We honor browser Do Not Track and Global Privacy Control signals by not sending page-view or click events or retaining source categories and campaign codes. A browser-local exclusion preference keeps administrator visits and internal checks out of the updated traffic report.
Voluntarily submitting the demo form sends your name, business name, email, optional phone number, trade, selected goal, and contact permission to Supabase. These private requests are visible only to the platform administrator. A genuine saved request queues a private email notification to our owner so it can be reviewed. Labeled tests and internal requests are excluded from lead conversions and these notifications. Submission does not send an automated message to you, enroll you in an outreach campaign, charge you, or start a subscription. Network addresses are converted on the server into a daily keyed hash for abuse-rate counters; raw network addresses are not stored in our marketing tables. Hosting and server providers may still process ordinary technical records as described above.
These counts measure recorded website page views and saved requests, not verified unique people, native-app installs, or sales. Refreshes and some automated visits may be included, while privacy settings, blockers, or connection failures may prevent a visit from being counted. This website measurement does not add tracking to the native Android or iOS application.
Optional Google Ads measurement
Public marketing pages offer a separate, optional ad-measurement choice. We do not load the Google advertising tag before you allow measurement. If you allow it, Google can store advertising cookies and receive browser and network information, including your network address, permitted advertising click references, and an event when a genuine demo request is saved. The event uses a random request reference to prevent duplicate counting. It is not a purchase or a sale.
We do not send the name, business name, email, phone number, or customer records entered in our form to Google Ads. We do not enable enhanced conversions, advertising personalization, or Google Analytics through this feature. Google may process the technical information needed to provide advertising measurement; see how Google uses information from sites that use its services.
Allowing measurement is optional and separate from permission for Jonathan to contact you. Declining has no effect on submitting a demo request. The Privacy choices button on these public pages lets you withdraw or change the choice. Withdrawal stops future measurement from our integration; it does not remove data already sent or automatically erase existing Google cookies. You can also use your browser's cookie controls. We store only your granted or denied choice in local browser storage and honor Do Not Track and Global Privacy Control even when a prior choice allowed measurement. Internal visits and labeled tests do not emit conversion events. These Google advertising tags do not load inside the signed-in portal or native app.
Service providers and security
We use Supabase for authentication, authorization, database, and server functions; Resend for email delivery and signed delivery events; Stripe for payments; HighLevel for customer-authorized phone-number and communications operations when configured for that business; and hosting, CRM, data-transfer, and security providers as needed to operate the service. Provider credentials stay on the server, internal email tables are not directly available to mobile clients, and workspace actions are access-controlled and audited. No internet transmission or storage system can be guaranteed completely secure.
Email choices and complaints
Recipients may use the unsubscribe link in any recovery email without signing in or reply directly to the monitored sender address. Unsubscribes, spam complaints, hard bounces, and invalid-address suppressions block later controlled sends from that workspace. Questions or complaints may also be sent to the contact below.
Children
The app is a business utility for home-service contractors and is not directed to children.
Changes to this policy
If our data practices change, we will update this page and revise the effective date before the affected service or application release.
Account deletion
In mobile app version 2.1.1 and later, or in the browser app preview, open Account, then Account deletion, to submit a deletion request for your account and associated personal data. The request is saved privately with a reference and an estimated completion date, normally within 30 days. You do not need to email or call us to initiate it. We retain your contact email while processing the request, send a completion confirmation, and clear that contact email from the request record when complete.
Requesting deletion does not immediately cancel a subscription or erase a shared business workspace. Billing, business ownership and connected services are reviewed during processing. Financial, security, consent and suppression evidence may be retained where required. The app also provides Reset my local entries for device-only records; signing out or requesting account deletion does not itself erase those local entries.
Contact
For older app versions, account deletion requests may be sent by email below. Questions or eligible privacy requests may be sent to contact@topleadrecovery.com or made by phone at (978) 606-9208.
