LDLeadDecide
For agenciesCTM integrationAI reviewsPricingResources
Sign inBook a walkthrough
Menu
For agenciesCTM integrationAI reviewsPricingResourcesSign inBook a walkthrough

LeadDecide policies

Privacy Policy

This policy explains how LeadDecide, operated by Website Genii, handles personal information in the public site, customer accounts, lead workspaces, connected services, and support.

Effective
August 13, 2026
Version
2026-08-13
Customer policiesTerms of ServicePrivacy PolicyRefund & Cancellation PolicySubprocessorsSupport & Service Expectations

A paying account decides which workspaces, providers, users, email recipients, AI options, and outbound destinations it configures. LeadDecide processes the resulting data to provide those requested functions. Website Genii also handles limited account, security, support, and billing information to operate the service.

1. Information LeadDecide handles

  • Account and identity data: names, email addresses, roles, account and workspace memberships, password-security records, invitations, sessions, and authentication events.
  • Lead and communication data: names, companies, phone numbers, email addresses, inquiry content, calls, forms, text or chat evidence, provider identifiers, attribution fields, transcripts when supplied, and links to provider-hosted recordings.
  • Review and outcome data: qualification decisions, reasons, AI suggestions and evidence, notes, journey stages, job values, revenue, reviewer attribution, and audit history.
  • Integration data: encrypted provider and AI credentials, webhook configuration, delivery status, connection health, and provider responses.
  • Billing data: plan, subscription and payment status, billing contact, Stripe customer and transaction identifiers, and AI credit activity. LeadDecide does not store full payment-card numbers.
  • Technical and support data: device and request metadata used for sessions and security, errors, operational logs, and information a user provides in a support request.

2. Where information comes from

Information comes from account owners and users, connected CTM or CallRail accounts, provider webhooks and imports, configured email and webhook workflows, Stripe, optional AI providers, and ordinary use of the service. The public marketing site currently uses document navigation and does not require an advertising cookie to display its pages.

3. How information is used

  • authenticate users and enforce account and workspace access;
  • import, normalize, display, review, and report on lead activity;
  • create optional AI suggestions and client-specific feedback examples;
  • send invitations, password resets, trial notices, weekly digests, instant lead alerts, and secure review links;
  • import provider activity, add supported namespaced LeadDecide tags in CTM when enabled, and deliver customer-configured signed webhooks;
  • process billing and account lifecycle events;
  • prevent abuse, investigate failures, maintain audit history, and support customers; and
  • comply with applicable legal obligations.

4. AI processing

AI is optional. When enabled, LeadDecide sends the configured provider the lead communication, relevant contact details and contact-quality results, the workspace review policy, and selected confirmed examples needed to produce a suggestion. Marketing attribution fields are not used as AI decision evidence. Managed AI uses LeadDecide's configured providers; bring-your-own-key mode sends requests using encrypted keys supplied by the paying account.

5. When information is shared

LeadDecide shares information only as needed with:

  • authorized users in the paying account and the workspaces assigned to them;
  • the service providers listed on the Subprocessors page;
  • CTM, CallRail, email recipients, Zapier, and other destinations that the customer directs LeadDecide to use;
  • advisers or authorities when reasonably necessary to protect the service, users, rights, safety, or comply with applicable law; and
  • a successor involved in a business transaction, subject to this policy and applicable law.

LeadDecide does not sell customer lead data.

6. Cookies and local browser data

The authenticated product uses essential cookies to maintain sign-in, select the active paying account and workspace, and support security. These cookies are required for the requested service. If analytics or advertising technologies are added later, this policy and any required consent controls must be updated before those tools are enabled.

7. Retention, deletion, and account closure

LeadDecide retains account, lead, review, delivery, billing, and audit data while needed to provide and secure the service, maintain accurate records, resolve disputes, and meet applicable legal obligations. The current release does not publish one fixed deletion period for every data category.

An authorized account owner can request account closure or deletion at [email protected]. We will verify the requester's authority, identify data that can be deleted, and explain any information that must be retained. A LeadDecide deletion does not remove copies already held by CTM, CallRail, Stripe, email recipients, AI providers, customer-configured destinations, or exports controlled by the customer.

Production launch requires backups to be verified as encrypted at rest and access-restricted. After a deletion, residual copies may remain in those protected backups until the provider retention period expires. Backups are for recovery, not ordinary product use. Before a restored backup is reconnected to normal service, completed erasures must be re-applied. This operational safeguard is a launch gate and is not represented as verified until a documented restore exercise proves it.

8. Security and access

LeadDecide uses tenant and workspace boundaries, role-based access, encrypted stored credentials, signed webhooks, secure session cookies, and audit records. More detail appears on the Security page. No system can guarantee absolute security, so users must protect credentials and report suspected incidents promptly.

9. Privacy requests and customer responsibilities

Depending on applicable law, a person may have rights to ask about, access, correct, delete, restrict, or object to certain processing. A lead should normally contact the business or agency that collected the lead information, because that customer controls the workspace and the connected provider. Website Genii will help the customer address a verified request when required.

LeadDecide is designed for business lead-review workflows, not for intentionally collecting children's personal information. Customers should not configure the service to collect information they are not legally permitted to process.

10. Updates and contact

The effective date and version identify this policy. Material changes may require an account owner to review and accept an updated policy set before continuing affected use.

Questions or requests can be sent to [email protected].

LDLeadDecide

The lead review layer for agencies using CTM and CallRail.

PricingSecurityResourcesTermsPrivacyRefundsSubprocessorsSupportSign inWebsite Genii
© 2026 LeadDecide