1. Scope and privacy roles
This notice applies when you visit leadvouch.com, create or use a LeadVouch account, connect an integration, contact us or interact with a website using the LeadVouch DNI snippet. It does not replace the separate privacy terms of Dodo Payments, Google, Twilio, Telnyx or a customer's website.
SF Web Tech determines why and how account, website, security, billing and support information is used. For caller, lead, client and recording data placed in a customer workspace, the customer generally determines the purpose and LeadVouch processes the data to provide the service on that customer's instructions. If you are a caller or lead, the business you contacted is normally the first place to send a privacy request.
2. Information we collect
- Account and identity data: name, work email, organization, role, login state and account settings.
- Google sign-in data: verified email, display name and stable Google account identifier. LeadVouch does not store Google access or refresh tokens and does not request Gmail, Drive or other Google-service access.
- Workspace and provider data: client records, websites, campaigns, tracking numbers, call flows, destinations, recording and retention settings, user permissions, encrypted provider credentials and connection status.
- Call and lead data: caller and destination numbers, timestamps, duration, routing events, attribution, qualification, outcomes, notes, recordings and related metadata when enabled by the customer.
- Website-attribution data: an anonymous browser ID, session ID, landing page, referrer, campaign parameters such as UTM values, supported ad-click identifiers and number-swap events from customer sites using LeadVouch DNI.
- Device, usage and security data: IP address, browser and device signals, request and audit history, diagnostics, service events, security alerts and feature usage.
- Billing data: selected plan, subscription, invoice, payment status, usage quantity and transaction identifiers received from Dodo Payments. LeadVouch does not store full payment-card details.
- Communications: support requests, contact-form submissions, feedback and related correspondence.
- Acceptance evidence: the policy versions, method, timestamp and a one-way hash of the signup IP when available.
3. Where information comes from
We receive information directly from customers and users, from their websites and browsers, from connected Twilio or Telnyx accounts, from Dodo Payments and Google identity, and automatically from use of the website, application, API and security systems. Customers decide what caller and lead information their call flows collect.
4. How and why we use information
We use information to:
- create accounts; authenticate users; and provide call tracking, routing, attribution, recordings, lead review, reporting, billing, APIs and integrations;
- follow customer configuration and support requests, communicate about the service and deliver transactional messages;
- measure plan capacity and processed-minute usage, administer subscriptions and reconcile transactions;
- secure accounts, prevent abuse and fraud, troubleshoot failures, maintain audit history and improve reliability;
- understand website and product operation using aggregated or de-identified information; and
- comply with law, enforce agreements and protect LeadVouch, customers and others.
Where a law requires a stated legal basis, we rely as appropriate on performance of a contract, legitimate interests in operating and securing the service, consent, and compliance with legal obligations. A customer is responsible for the lawful basis covering caller and lead data it directs LeadVouch to process.
5. Cookies, storage and DNI
LeadVouch uses cookies and similar browser storage needed for login, security, preferences and service operation. A customer-installed DNI snippet may use local storage, session storage and a first-party cookie to keep an anonymous visitor and attribution context, then swap an eligible phone number on that customer's website. If the host site signals that consent is withheld, the snippet keeps context in page memory rather than persisting it.
Each customer is responsible for describing its use of LeadVouch in its own privacy or cookie notice and collecting consent when required. Blocking storage may reduce attribution continuity but should not prevent the original phone number from remaining visible.
6. Google API data
LeadVouch uses Google only to authenticate the identity scopes shown during sign-in. Our use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
7. When we disclose information
We may disclose only what is reasonably needed to:
- Customer-authorized users and integrations: make workspace information available according to roles, tokens and configuration.
- Telephony providers: route calls and manage numbers through the customer's selected Twilio or Telnyx account.
- Dodo Payments: create checkout and portal sessions, report billable usage and administer transactions. Dodo acts as merchant of record and separately controls payment, tax, invoice, refund and dispute information under its privacy policy.
- Other service providers: use Google for identity, Resend for transactional email, Contabo-hosted infrastructure for production processing and Backblaze B2 for protected backups.
- Legal and safety purposes: comply with a lawful request, protect rights and safety, investigate fraud or enforce our agreements.
- Business transfers: support a merger, financing, reorganization or sale, subject to appropriate confidentiality and notice required by law.
LeadVouch does not sell personal information and does not share it for cross-context behavioral advertising. We do not disclose Customer Data to another customer except when directed by an authorized user or required by law.
8. Customer responsibilities
Customers must provide accurate notices, obtain required consent, configure access and retention appropriately, and limit collection to information needed for a lawful business purpose. Do not intentionally use LeadVouch to collect payment-card data, government identifiers, health information or other specially regulated data unless we have expressly agreed in writing to support that use. Callers may still volunteer sensitive information, so customers should train recipients and restrict playback and exports.
9. Retention and deletion
We keep account and service data while a workspace is active and as reasonably needed for service delivery, security, billing, disputes, fraud prevention and legal records. Authorized customers set call and recording retention within the current product limits; the selected deadline is fixed when a call starts. When automated retention removes a recording, LeadVouch confirms deletion from the connected provider before removing the corresponding local call record.
Encrypted backups may retain copies for a limited recovery period and are isolated from ordinary product access. Deleted data may remain in those backups until normal backup rotation. We may retain narrowly necessary records longer for legal holds, security evidence, financial reporting or to establish or defend claims. We will de-identify or delete information when it is no longer needed for those purposes.
10. Security
LeadVouch uses safeguards designed for the service, including tenant access controls, role and token scoping, encrypted transport, protected provider secrets, signed webhooks, audit history, restricted recording playback and encrypted off-site backups. We review access and operational alerts and limit production administration. No method of storage or transmission is completely secure, so we cannot guarantee absolute security.
Customers must protect their users, devices, provider credentials and API tokens and promptly report suspected misuse. If a security event affecting personal information requires notice, we will notify the responsible customer or individuals as required by applicable law and available contact information.
11. International processing
LeadVouch and its providers may process information in countries other than where a customer or caller is located. Those countries may have different privacy laws. Where required, we and our providers use contractual, organizational or other recognized safeguards for cross-border processing. Customers must determine whether their own use needs additional transfer terms.
12. Your privacy choices and rights
Depending on location and relationship, a person may have rights to access, correct, delete, restrict or object to processing, receive a portable copy, withdraw consent, appeal a decision or complain to a privacy regulator. We do not discriminate for exercising an applicable privacy right. These rights can have legal exceptions.
Account owners can manage some information in LeadVouch and may submit a request using the contact address below. Include the account email, relationship to the data and the right requested. We may verify identity and authority before acting. Authorized agents may submit a request where law permits, subject to verification. If LeadVouch holds the data for a customer, we may refer the request to that customer and help it respond.
13. Children
LeadVouch is a business service and is not directed to children under 18. We do not knowingly create accounts for children. If you believe a child submitted personal information directly to us, contact us so we can investigate and take appropriate action.
14. Changes to this notice
We may update this notice as the service, providers or law changes. We will post the new version and last-updated date and provide additional notice for material changes when required. An older version continues to be identified in the signup audit for the account that accepted it.
Contact
Questions about this policy can be sent to sohail@sfwebtech.com. You can also use the contact page.