Security and privacy at Kalko

How is each workspace kept apart?

• A workspace is an organization, and every app page needs a signed-in member of it.
• Tables that hold workspace data use row-level security, enabled and forced.
• Every query made for a workspace runs as a restricted database role, scoped to it for that transaction.
• With no workspace set, queries return nothing. Automated tests check reads and writes across workspaces.

What does Kalko store?

• Your brief: the product, the ideal customer and the buyers.
• Accounts, people and signals, with the source behind each claim.
• Drafted messages and the plays you approve.
• Slack thread history, so the app can follow a conversation.
• Not stored: the text of website pages read during onboarding.

How are keys and tokens protected?

• Keys you connect for Reply.io, Attio and Leadfeeder are checked with the provider, then encrypted with AES-256-GCM.
• Slack tokens are encrypted with a separate key.
• MCP keys belong to your organization in the sign-in service. Kalko does not store them.

What can connected apps do?

• Slack: three permissions. Uninstalling the app revokes the installation and its key.
• Only the person who installed the Slack app can approve plays from Slack.
• MCP: an API key or an OAuth sign-in, limited to 60 calls a minute.
• MCP cannot delete data, change billing or send email.

What does Kalko send, and who approves it?

• Kalko sends nothing from its own mailboxes.
• A draft is prepared and reviewed before approval, and the approval covers that exact version.
• An approved email goes to Reply.io as field values. You start the sequence there.
• You send LinkedIn messages yourself, then mark them as sent in Kalko.
• Autopilot is the one exception you can choose. You approve its policy and a sample once, then arm it.

How do deletion and export work?

• Deleting your organization deletes the workspace and everything in it.
• You can export all workspace data as JSON from the app or through MCP.
• Boards, people, lists and campaigns also export as CSV files.
• A suppression list keeps the people you exclude out of future plays.
• To erase one person's data, email konstantinos@kalko.ai.

How long is data kept?

• Usage records: 90 days.
• Signals: deleted once they are twice as old as the point where they count as stale.
• The credit ledger: kept, as the record of what you paid for.

What does this website load?

• Before you accept cookies: no analytics and no visitor pixels.
• If you accept: Google Analytics and four visitor-identification pixels, all named in the cookie banner.
• Declining is remembered in your browser.
• The Cookie settings link in the footer withdraws consent and clears those cookies.
• Signed-in visitors get no visitor pixels. Google Analytics still loads if they accepted.

What this page does not cover

This site does not publish a certification report, a data processing agreement or a subprocessor list. For a security questionnaire or a data processing agreement, email konstantinos@kalko.ai.

Questions people ask