Data Security

iKanban's AI features involve two sensitive things: the provider API keys you add, and the notification text those features send to an AI provider. Here's how each is protected.

Your provider keys are encrypted at rest

When you add an AI provider key (Settings → AI Provider Keys), it is encrypted before it's stored using industry-standard AES-256 encryption, with the encryption key managed by AWS KMS. The database holds only ciphertext — a database dump or backup never reveals a usable key.

Your iKanban API token (vk_…) is not involved in this — it authenticates your requests to iKanban and can't decrypt anything. The encryption is anchored to a server-side key you never see.

What's sent to an AI provider — minimized and redacted

When you turn on Prioritize in the Inbox, iKanban asks an AI provider to rank and summarize your notifications. Two safeguards apply:

• Only a little is sent. Just the notification title and a short snippet (up to 120 characters) per item — never full task descriptions, comment threads, or attachments.
• Secrets are stripped first. Before sending, the text is scrubbed of email addresses, phone numbers, and credential-like strings (things that look like API keys or tokens).
• It uses your key and your account. The request goes to the provider you configured, billed to your account. If you haven't added a key, nothing is sent to any AI provider — a built-in fallback ranks notifications locally instead.

Whatever is sent is then subject to your AI provider's own data policy. Review your provider's API data-usage terms.

In transit

Connections between your browser and iKanban, and between iKanban and your AI provider, use HTTPS/TLS. iKanban's databases run in a private, non-internet-facing network.

What you control

• Add or remove a key anytime in Settings → AI Provider Keys. Remove it and AI features stop sending data for you.
• AI is opt-in via your key. No key means no data leaves for AI; features fall back to non-AI behaviour.

Good to know

• Redaction matches common patterns (emails, phones, credential shapes) — it isn't a guarantee against every format, so avoid putting genuinely sensitive material in task titles and comments.
• At-rest encryption protects data stored in iKanban; it doesn't change how your AI provider handles data you send them.