Privacy policy.

1. Information we receive

• Account and business details: your name, email address, business or workspace name, settings, and the sign-in information needed to provide access. When a password is used, we store its hash rather than the original password.
• Connected-account information: platform account and business identifiers, account names, access permissions, time zones, and OAuth access or refresh credentials needed to maintain the authorized connection.
• Lead and conversation information: the records your connected platform makes available, such as lead identifiers, customer names and contact details, inquiry text, message content, participants, status, timestamps, and attachment information. Available fields depend on the platform and your permissions.
• Service and billing records: configured replies, schedules, delivery attempts, support correspondence, and subscription or payment-status information where billing is enabled. Payment processing is handled by the payment provider; we do not store complete payment-card details.
• Website and technical information: information used to operate and protect the service, such as IP addresses, browser and device information, page requests, timestamps, and error or security records. We use website analytics to understand aggregate traffic and performance.

2. How we use information

We use information to authenticate users, connect the accounts you authorize, show lead and conversation records in the correct workspace, apply your settings, and maintain the service. We use lead and conversation information to send replies and follow-up messages on your behalf, including automated responses according to your settings and authorization, and to track message history and delivery attempts. Messaging features depend on the connected platform, account permissions, and the features you enable.

We also use information to answer support and privacy requests, troubleshoot problems, prevent abuse or unauthorized access, administer billing where applicable, and meet applicable legal obligations. We do not sell Google user data or use Google lead or conversation data for advertising or retargeting.

4. Sharing and service providers

Lead records are available to the authorized users of the workspace that owns the connected account. We use service providers for website and application hosting, data storage, security, website analytics, payment processing, and support communications. We share information with these providers as needed to operate the service and with the lead platforms you choose to connect as needed to retrieve inquiries and send the messages you authorize.

Providers process information needed for their role under their applicable terms and privacy policies. We do not provide Google lead or conversation records to advertising platforms, data brokers, or information resellers.

Our personnel may access specific Google user data with your affirmative permission for support, or when necessary for security, legal obligations, or other uses permitted by Google’s Limited Use requirements. We use synthetic or sanitized examples for development and troubleshooting where possible.

We may disclose information when legally required or necessary to protect the service and its users. Any transfer of Google user data as part of a business transaction must satisfy Google’s requirements, including prior consent where required.

5. Storage and retention

We retain account, integration, lead, and communication records while needed to provide the service and for related support, security, or legal purposes. Stored OAuth credentials are encrypted. The service does not currently provide a fixed automatic deletion period for all imported records.

You can request deletion using the contact details below. After verifying the request and your authority over the relevant records, we delete information that is no longer needed unless retention is required for applicable legal, accounting, or security purposes. Where backups exist, remaining copies may persist until the applicable backup cycle expires.

Revoking platform permissions stops access under that grant; it does not automatically delete records already imported into LeadResponder. The original platform separately controls information retained in its own services.

6. Your choices and requests

You decide whether to connect a supported platform. You can revoke Google access through your Google Account connections, and manage other platforms’ permissions through their own account settings.

For access, correction, deletion, or privacy questions, email ori@sortech.dev. Include the workspace or connected business and enough context to help locate the relevant information. Please do not send passwords or access tokens. Requests are handled by the service operator; we may need to verify your identity or authority before taking action.

If your information was submitted to a business through a lead platform, that business also controls its use of the inquiry. You may contact the business directly, and we can help identify records handled by our service.

7. Security and processing locations

We use authentication, workspace access controls, password hashing where passwords are used, encrypted stored integration credentials, and HTTPS for public service connections. Cookies and similar session mechanisms are used for sign-in and security. Hosting and security providers may also use their own technical mechanisms.

Information may be processed in the United States and other locations where we or our providers operate. No method of transmission or storage can guarantee complete security.

8. Children’s information

LeadResponder is intended for business use and is not directed to children under 13. If you believe a child’s information has been provided to our service, contact us so we can review and address it.

9. Changes to this policy

We update this policy when our practices change and revise the effective date above. For material changes to how we use Google user data, we provide the necessary notice and obtain any required additional consent before applying the new use.