Privacy Policy

Effective date: July 14, 2026
Last updated: July 27, 2026

This Privacy Policy explains how Klix Labs, the developer and operator of the Klix Chrome extension and related services, collects, uses, stores, and protects information when you use Klix.

In this policy, “Klix” means the product: the Chrome extension, website, backend, and related product features. “Klix Labs,” “we,” “us,” and “our” mean the team that develops and operates Klix. Klix is draft-only: it does not automatically send messages, automate connection requests, or run bulk messaging.

Klix helps users draft and refine professional LinkedIn messages using the active profile or active conversation they choose, plus writing preferences they control.

Profile context

When you open Klix or request a draft on a LinkedIn profile, Klix may read visible profile context such as name, headline, current role, company, location, About text, recent activity, profile URL, and profile photo URL for local display. Klix does not crawl LinkedIn or collect profile data in the background.

Conversation context

When you use Conversation Assist in a normal one-to-one LinkedIn Messaging thread, Klix may read a bounded set of visible messages from only the active conversation after you deliberately click Generate reply, Regenerate reply, More like me, Shorter, Warmer, or More direct. Klix does not scan your inbox, crawl unrelated conversations, continuously monitor direct messages, support group conversations in v1, or automatically send replies.

Backend processing

When you click Generate, Regenerate, Polish reply, Generate reply, Regenerate reply, More like me, Shorter, Warmer, or More direct, Klix sends relevant profile, reply, or bounded active-conversation context, selected tone, sender context when applicable, anonymous install ID, and a signed install token to the Klix backend. The backend uses this to authenticate the install, enforce quotas and rate limits, and request a draft, refined draft, polished reply, or conversation reply from OpenAI. Refinement actions use one normal generation and are subject to the existing quota.

Writing style

You may choose Writing style preferences in the packaged Klix settings page. Writing style fields include your current role, organization, primary goal, preferred sound, preferred length, greeting preference, emoji preference, ending preference, and phrases to avoid. Klix stores these fields in Chrome storage. Klix sends relevant structured preferences to the backend only when you deliberately request Generate, Regenerate, Polish reply, More like me, Shorter, Warmer, or More direct.

OpenAI

Users do not provide an OpenAI API key. OpenAI processing happens through Klix's backend integration using a server-side provider key controlled by Klix Labs.

Local storage

Klix stores local extension state in Chrome storage, including anonymous install ID, signed install token, sender context, usage display, cached Pro status, referral/review/feedback/quota prompt timing state, sidebar position, and first-run sidebar onboarding completion. The popup displays a safe Support ID. Do not send your install token to support.

Klix may also use local Chrome storage for count-only Writing style observations and local recent drafts. Smart suggestions are off by default. If enabled, Klix stores only local count/category signals such as selected tone, draft length bucket, refinement category, and repeated final-edit patterns. It does not store draft text, keystrokes, profile names, profile URLs, browsing history, or LinkedIn message contents for local learning. Recent drafts are off by default, local to this browser, bounded, user-controlled, saved only after explicit Copy or successful Insert actions, and can be disabled or cleared. Generated and polished drafts are not automatically added to Recent drafts, and Week 3 has no standalone Save action. Klix does not promise cross-device writing history.

Private beta access

Normal beta testers can install Klix from the unlisted Chrome Web Store link without entering an invitation code. If Klix uses an optional internal invite or promotional code, Klix stores only a cryptographic hash of that code, safe tester label or cohort if assigned, the anonymous install ID that activated it, activation date, last active date, and beta status. Klix does not store optional codes in plaintext after activation and does not store install tokens in beta records.

Feedback

If you send feedback from inside Klix, Klix Labs stores the category you selected, your short feedback message, and an optional email address if you provide one. Klix does not automatically attach generated drafts, rough replies, LinkedIn messages, or full profile text to feedback.

Analytics consent

Klix asks for a local opt-in before sending optional Lighthouse product analytics from the extension. You can review the disclosure and disable optional analytics from the Klix popup. Disabling optional analytics does not disable generation, insertion, onboarding, referrals, feedback, billing, authentication, rate limits, quota enforcement, security checks, or other essential service operations.

Referrals

Referral rewards are verified server-side. Klix stores referral codes, anonymous referrer and referred install IDs, conversion status, reward timestamps, and bonus-message counts. Copying a referral link alone does not award messages.

Backend records

The backend stores operational records needed for quotas, rate limits, billing, referrals, beta usage measurement, and abuse prevention, including anonymous install IDs, monthly quota counters, privacy-safe first-party Lighthouse product events when enabled or when you explicitly submit feedback, aggregate usage metadata, Stripe customer/subscription identifiers, subscription state, and Stripe event lifecycle records. Product events may include schema version, product ID, event name, timestamp, product version, beta cohort, success/failure, feature name, subscription tier, safe prompt or error category, and approximate character counts. Klix does not intentionally store generated messages, rough replies, polished replies, LinkedIn conversation text, full LinkedIn profile text, install tokens, provider credentials, Stripe secrets, or card numbers on the backend. Conversation Assist message text is treated as sensitive transient input for the single requested generation or refinement.

Klix does not intentionally store Writing style fields, local learning observations, or recent draft history in backend records. Writing style fields may be processed transiently during a deliberate generation, polishing, or refinement request.

Payments

Stripe processes Klix Pro payments and subscriptions. Klix stores Stripe customer and subscription identifiers plus subscription state, but Klix Labs does not directly receive or store full card numbers, billing addresses, or complete payment-method details.

Third-party providers

Klix Labs uses OpenAI, Stripe, Vercel, Redis/KV or Upstash, Chrome storage, and LinkedIn as described in the full privacy documentation. Klix is not affiliated with, endorsed by, or approved by LinkedIn or Microsoft.

Tracking and data sales

Klix uses Lighthouse, a small first-party internal analytics layer, to understand beta usage and operational reliability after local opt-in. Lighthouse analytics are product-scoped and do not merge Klix install IDs into a universal cross-product profile. Lighthouse analytics exclude generated drafts, rough replies, polished replies, LinkedIn profile text, LinkedIn conversation text, participant names, thread identifiers, tokens, credentials, payment details, and provider secrets. Referral, review, feedback, upgrade, quota, and Conversation Assist analytics use only safe event names, timestamps, success/failure status, approximate count buckets, and enum categories; they do not include message, conversation, or profile content. Feedback text and optional email are sent only when you submit feedback. Klix does not include third-party analytics SDKs, advertising pixels, cookies, or advertising profiling in the current public beta. Klix Labs does not sell personal information.

Limited use

Klix uses information from Chrome extension functionality and browser storage only to provide, secure, support, and improve user-facing Klix features. Klix Labs does not use or transfer this information for unrelated advertising, credit decisions, sale to data brokers, or purposes unrelated to Klix functionality. Klix does not receive Google API user data.

Retention and deletion

Monthly usage counters and aggregate usage metadata expire at the next monthly reset. Lighthouse product event and feedback records expire after 90 days by default unless a shorter retention value is configured. Stripe event lifecycle records expire after 90 days. Signed install tokens expire after 30 days. Beta invitation records and billing records are retained while needed for beta operations, subscription operation, support, abuse prevention, accounting, and legal obligations.

You can clear Writing style preferences, local learning observations, and local recent drafts from the Klix settings page. Uninstalling the extension or clearing browser extension data may remove local learning observations and recent drafts.

To request deletion, email Klix Labs at klix.support@gmail.com with your safe Support ID from the Klix popup. For billing requests, include the email used at Stripe Checkout. The Klix popup can open Stripe Billing Portal for installs with a trusted billing record. Do not send install tokens, passwords, API keys, or payment card details.

Security

Klix uses server-side provider keys, signed install tokens, rate limits, request-size limits, webhook signature verification, and production configuration checks. No system can guarantee absolute security.

Contact

Contact Klix Labs at klix.support@gmail.com or visit Klix Support.