Skip to content

Lead Rescue

Privacy Policy

Effective date: October 3, 2026

This policy describes how A TO Z VENTURES LLC handles information in connection with Lead Rescue. It is not a legal-compliance certification or legal advice.

Information we collect

Account information includes authentication identifiers and account information supplied through our authentication provider. Business information includes business names, industries, contact details, time zones, team memberships, and configuration.

Business users may enter customer names, email addresses, phone numbers, addresses, inquiry details, notes, tags, lead assignments, pipeline stages, estimated values, follow-up dates, and consent or opt-out records. Do not submit information you lack authority to process.

When communications features are enabled, communications data may include message content, sender and recipient numbers, call identifiers and metadata, timestamps, delivery outcomes, and opt-out events. Production SMS and call-recovery features are not currently live. We do not claim to record calls, generate transcripts, or use AI analysis today.

Technical and usage information may include request paths, response status, timing, browser/device information made available to service providers, and information needed to operate and protect the service. Application request logs are designed not to include message bodies, passwords, or authentication headers.

How information is used

We use information to provide accounts and tenant-scoped workspaces, organize customer inquiries, support authorized business users, maintain security, troubleshoot problems, and operate the service. Communications information will be used to deliver and track permitted messages when those features are enabled.

Providing a phone number or submitting a general inquiry does not by itself grant consent for SMS or marketing. Businesses must obtain and maintain the consent required for their intended communications.

Service providers and sharing

Hosting, infrastructure, database, and authentication providers process information needed to operate the platform. The current application uses Replit infrastructure and Clerk authentication. Authorized members of the applicable business can access its customer information according to their role.

If communications are configured, Twilio or similar communications providers may receive phone numbers, message content, and delivery/call metadata required to perform those services. Their own terms and privacy practices also apply.

Stripe TEST-mode checkout and billing infrastructure is implemented. Live Stripe billing is not enabled. Stripe may process information submitted through TEST-mode billing flows; these flows do not represent live charges.

AI receptionist functionality is currently simulated/test-mode where applicable. Twilio production SMS and Vapi production voice are disabled. Prepared communications integrations do not mean those providers are handling live customer communications. When enabled, communications and AI providers may process the information needed to deliver the configured services. Google Calendar integration is prepared, but live production operation has not been verified. Provider processing and applicable disclosures must be reviewed before enabling production services.

We do not sell mobile information obtained for SMS consent for third-party marketing purposes. SMS opt-in information and consent are not shared with third parties for their own marketing. Limited disclosure to service providers to deliver messages and operate the service, or where legally required, is different from marketing sharing.

Information may be disclosed where required by law or to address security, fraud, or enforce applicable terms. We do not claim that information is never shared with providers.

Cookies, local storage, and analytics

Authentication providers may use cookies and related browser storage to maintain sessions and protect sign-in. The app uses local storage to remember the selected business; that selection does not grant access.

No separate advertising analytics or marketing tracking integration has been added to this application. Hosting and authentication providers may collect operational usage information under their own policies. Review and update this section before adding optional analytics or tracking.

Retention and deletion

Information is retained while needed to operate the service, support business records, address disputes, or meet applicable obligations. There is no promised automatic deletion schedule or self-service account/customer deletion feature at present.

Contact the operator to request access, correction, or deletion. The operator must evaluate the request, its relationship to the business controlling the data, technical capabilities, and any required retention. Backups and provider-held records may follow separate retention cycles.

Security and customer responsibilities

The application uses managed authentication, business membership checks, role restrictions, validated inputs, and tenant-preserving database relationships. No system can guarantee absolute security, and these measures do not certify compliance with every law or standard.

Businesses are responsible for lawful data collection, appropriate staff access, accurate consent records, handling consumer requests, and complying with communications rules. Protect account access and do not enter unnecessary sensitive information.

Consumer choices and SMS opt-out

You may contact the applicable business about its customer records and communications, or contact the operator about platform account information. Reply STOP to a participating business’s text message to request SMS opt-out; HELP requests help where messaging is configured.

Opting out of SMS does not automatically delete business records. Re-opt-in must be explicit and valid under the applicable provider configuration and rules. Separate marketing consent must not be inferred from service-related consent.

U.S. service context and policy changes

Lead Rescue is designed primarily for U.S. local service businesses. This statement is not a guarantee that all data is stored or processed only in the United States. Infrastructure and provider processing locations must be reviewed by the operator.

The operator should update this policy when practices change and publish an accurate effective date. Material changes may require additional notice or consent depending on applicable law.

For support, contact support@inboundhelm.com. For legal or privacy inquiries, including requests about platform account information, contact support@inboundhelm.com. These contacts are also published on our Contact page.