Kalamos← BACK TO HOME
LEGAL · PRIVACY

Privacy policy

LAST UPDATED · 19 OCT 2026

The short version

Kalamos connects to your LinkedIn, reads the notes and posts you give it to draft in your voice, and publishes only what you approve, from your own account. To do that we handle your writing and, through the engage and inspiration tools, other people's public posts. We treat it carefully, never sell it, and never use it to train AI models. This page explains exactly what we collect and why.

Who this covers

This policy applies to Kalamos ("Kalamos," "we," "us"), the website at kalamos.so and the Kalamos application, including access through an AI agent connected over MCP. By creating an account or connecting LinkedIn, you agree to the practices described here.

What we collect

  • Account details. Your email address and name, as provided by the sign-in provider you choose (Google, LinkedIn or email through Clerk). We never see or store a password.
  • Connected LinkedIn. When you connect LinkedIn, we store an opaque account identifier from our connector. We do not store your LinkedIn password or session; those stay with our connector (Unipile), which holds the provider integration.
  • Your writing. The posts you paste or import to build your voice, your notes and ideas, every draft and its versions, scheduled and published posts, the images and carousels you generate or upload, and your conversations with the copilot.
  • Your LinkedIn activity. Your own posts and their reactions, comments and impressions, and your follower count over time, so the growth report can show what worked.
  • Other people's public posts. To suggest comments and to study writing you admire, we fetch public LinkedIn posts and comments by people who may not be Kalamos users: their name, headline, post text, engagement counts and profile photo. This is used only inside your workspace and never published or sold.
  • Links you paste. When you paste an article, tweet or video, we fetch its public content to turn it into material for a draft.
  • Technical data. Standard logs such as IP address, browser and timestamps, used to operate, rate-limit and secure the service.
  • Product usage. We use PostHog to see how Kalamos is used and to catch errors: pages visited, actions such as scheduling a post or connecting LinkedIn, error reports, and recordings of dashboard sessions in which everything you type is masked. Events are tied to your account id and email. We run no advertising trackers, and this data is never sold or used for ads.

How we use it

  • To draft posts, comments and carousels in your voice and queue them for your review.
  • To check each draft against the writing bar and show you the score.
  • To publish, at the time you approved, the posts you approved, from your LinkedIn account.
  • To learn your voice from the edits you make, so the next draft needs fewer.
  • To operate, secure, debug and improve the service.
  • To email you about your account, a post that just went live, or your weekly report, each of which you can turn off in Settings.

We do not sell your data, we do not use it for advertising, and we do not use your writing to train generalised AI models.

AI processing

Drafting, checking and image generation run on models from OpenAI and Google, reached through OpenRouter. To write or judge a draft we send the relevant context: your voice samples and profile, the note or post being worked on, and, for comment suggestions, the public post being replied to. We use these services through their commercial APIs, whose terms state that data sent through the API is not used to train their models. Nothing is published without your approval.

Who we share it with

We share data only with the service providers that make Kalamos work, each acting on our instructions:

  • CLERKSign-in and session management; holds the Google and LinkedIn sign-in integration.
  • UNIPILEConnects to LinkedIn on your behalf: reads posts and stats, publishes what you approve.
  • OPENROUTERRoutes drafting, checking and image generation to OpenAI and Google models.
  • OPENAIEmbeds your own posts so voice memory can find the closest match.
  • EXASearches the news for topics in your field.
  • APIFYFetches public LinkedIn posts of creators you choose to study.
  • JINAReads the public content of links you paste.
  • RESENDSends the transactional emails you have turned on.
  • RAILWAYCloud hosting, the managed database and cache.

If you connect an AI agent of your own over MCP, that agent's provider (for example Anthropic or OpenAI) receives whatever the agent reads through the tools you granted it, under that provider's terms. We may also disclose information if required by law, or to protect the rights, safety and security of our users and the service.

LinkedIn data

Kalamos reads from and writes to LinkedIn through a connector using the account you linked. We use that access solely to provide the features you enable, we publish only what you approve, and we do not use it for advertising or to train generalised AI models. Your use of LinkedIn through Kalamos remains subject to the LinkedIn User Agreement.

Kalamos for Chrome

  • What it sees. The address of LinkedIn tabs, so the panel knows which profile or post you're on. It has no access to the address of any other site, and it never reads, changes or acts on the LinkedIn page itself: it injects nothing into the page.
  • What it sends to Kalamos. The LinkedIn handle or post address of the page you're on (to show that public profile's analytics or that post's comment options), drafts you paste into Check a draft, and your sign-in token. Product events say which panel showed and which button was pressed; they never contain page addresses, names or text. If you remove the extension and answer the one question that opens, we receive your answer and the extension version.
  • What it keeps in your browser. A random device id and your sign-in token. Uninstalling removes both; signing out revokes the token.

The use of information received from Kalamos for Chrome adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

How we protect it

  • All traffic is encrypted in transit with TLS.
  • We hold no LinkedIn password or session. Personal access tokens for agents are stored only as a hash and can be revoked at any time.
  • Each account's data is isolated by account at the database level.
  • Access to production systems is limited to what is needed to run the service.

No system is perfectly secure, but we work to protect your data and will notify you of a breach affecting it as required by law.

Retention & deletion

We keep your data while your account is active. Disconnecting LinkedIn from Settings pauses every scheduled post and keeps your drafts. To export your notes, drafts, history and voice profile, or to delete your account, email us and we will complete the request within 30 days. Deletion removes your stored data and disconnects LinkedIn. Some minimal records may persist in backups or where the law requires, and are purged on our normal cycle. If you started Kalamos from ChatGPT, we keep a keyed one-way fingerprint of your email after deletion, not the address itself, used only to offer the free trial once per email.

Your rights

Depending on where you live, you may have rights to access, correct, export or delete your personal data, and to object to or restrict certain processing. Contact us to exercise any of them. If you are not a Kalamos user and a public post of yours appears in a user's workspace, you can ask us to remove it.

Children

Kalamos is a business tool not intended for anyone under 18, and we do not knowingly collect data from children.

Changes to this policy

We may update this policy as the product evolves. When we make material changes, we will update the date above and, where appropriate, notify you in the app or by email.

Contact

Questions about privacy or your data? Email support@kalamos.so. See also our Terms of Service.

© 2026 KALAMOS
PRICINGPRIVACYTERMSREFUNDS & CANCELLATIONSUPPORTHOME