Liaison Reply
Privacy

How Liaison Reply handles your data.

This policy covers both liaisonkeyboard.com and app.liaisonkeyboard.com. It explains what data we collect, why we collect it, how it is used, and what choices you have.

Last updated

April 4, 2026.

Operating model

Liaison Reply drafts replies for your review. You decide what to edit, copy, or send.

Key principle

We use personal data only as needed to run, secure, support, and improve the service, subject to your rights and applicable law.

Scope and contact

This policy covers the site and the app

This policy explains what personal data we collect, how we use it, when we share it, and what choices you have. Privacy questions, access requests, deletion requests, and complaints can be sent to support@liaisonkeyboard.com.

Legal bases

Why we process personal data

Depending on the context, we process personal data on one or more of the following bases: your consent, performance of a contract with you, compliance with legal obligations, and our legitimate interests in operating, securing, supporting, and improving Liaison Reply.

Where processing is based on consent, you can withdraw that consent at any time by updating your settings or contacting support. Withdrawal does not affect earlier processing that was lawful when it occurred.

What we collect

Automatic and user-submitted data

  • Automatically collected data may include IP address, browser/device details, content viewed, clicked links, and similar telemetry needed for security, diagnostics, and analytics.
  • Data you provide may include email address, payment and subscription metadata, support communications, preferences, and the messages or context you submit for drafting.
  • We collect this information when you create an account, use the product, submit content, manage billing, update settings, or contact support.
How we use data

Service delivery, security, billing, and improvement

  • Providing and operating the service.
  • Creating and managing accounts.
  • Processing subscriptions, payments, and billing support.
  • Generating draft replies and related outputs you request.
  • Securing the service, preventing fraud, enforcing fair-use abuse guardrails, and diagnosing issues.
  • Analyzing product performance and improving the experience.
  • Communicating important service, support, and policy updates.

This can include limited account, billing, device, and usage telemetry needed to detect unusual activity, apply paid-plan guardrails, and prevent accidental or malicious runaway spend.

Cookies and storage

Small, named storage with user controls

  • liaison_cookie_consent stores your cookie preference.
  • lk_deeplink may store scenario or referral context if optional site memory is enabled.
  • liaison_auth_hint may store a lightweight session hint if optional site memory is enabled.

You can manage optional analytics and site memory from the cookie settings page or through supported browser controls.

Analytics

Measurement and traffic signals

This site and app use analytics and diagnostics tools, including Google Analytics 4, to understand page views, sessions, referral patterns, and device-level usage. Google handles analytics processing subject to Google's Privacy Policy.

Service providers

Who may receive personal data

  • Cloud hosting and infrastructure providers.
  • Authentication, database, and backend service providers.
  • Payment processors and subscription providers.
  • Product analytics and diagnostics providers.
  • Email, communications, and support providers.
  • AI or language model service providers needed to deliver requested outputs.
Why we share

Sharing is limited to operating the service

We share personal data only as reasonably necessary to host the service, authenticate users, process payments, provide requested outputs, deliver support communications, run analytics, prevent fraud, comply with the law, or support a corporate transaction such as a financing, merger, or sale.

Retention and security

We retain data as needed and protect it with reasonable safeguards

We keep personal data for as long as reasonably necessary to fulfill the purposes described in this policy, comply with legal obligations, resolve disputes, enforce agreements, and maintain business records. We use reasonable administrative, technical, and organizational safeguards, including encryption in transit, access controls, authentication measures, logging, monitoring, and secure third-party infrastructure. No method of transmission or storage is completely secure.

International transfers

Data may be processed outside your home jurisdiction

Personal data may be processed in countries including the United States and Canada. Where required by applicable law, we use appropriate safeguards for international transfers, including contractual protections and vendor commitments.

Your rights and choices

Access, deletion, correction, objection, and opt-out controls

Depending on your location, you may have rights to access, correct, delete, restrict, object to, or request portability of your personal data. You may also request information about how your data has been used or shared. To exercise those rights, contact support@liaisonkeyboard.com.

You can also opt out of optional analytics, non-essential cookies, and supported marketing communications through available settings, unsubscribe tools, or by contacting support.

Children and complaints

The service is not intended for children under 16

Liaison Reply is not intended for children under 16, and we do not knowingly collect personal data from them. If you believe a child under 16 has provided personal data, contact support so we can investigate and take appropriate action.

If you have concerns about how we process personal data, contact us first at support@liaisonkeyboard.com. If you are in the EU or UK, you may also lodge a complaint with the data protection authority in the place where you live, work, or believe an infringement occurred.

Policy updates

We may revise this notice as the product evolves

We may update this Privacy Policy from time to time to reflect changes to the service, legal requirements, or data practices. When we do, we will post the updated version here and revise the effective date shown on this page.