Built for boards that take confidential material seriously.

Encryption at rest

Sensitive fields — agendas, minutes, transcripts, decisions, and attachments — are encrypted at rest using a per-organization data key. No other organization's key can decrypt your data.

Encryption in transit

All traffic to BoardKite is encrypted in transit using TLS to protect data between users, integrations, and the platform.

AI provider control

When AI is turned on, BoardKite uses a hosted AI provider by default. An organization can turn AI off, or connect a provider of its own from the supported AI plugins under Settings → Plugins. Which providers we use, and where they process data, is listed with our subprocessors. View subprocessors

Transcription privacy

Meeting transcription via supported transcription plugins is opt-in and enabled per-meeting by your team, not automatically. At launch, the supported plugin is Recall.ai. The transcription bot is only registered when a member explicitly enables “Record & transcribe” for a specific meeting. Transcripts are encrypted at rest with your org data key as soon as they arrive. Organizations that prefer not to use a third-party bot can upload VTT, SRT, or plain text transcripts manually — the same AI pipeline applies either way.

Role-based permissions

Granular organization and meeting roles control who can view, edit, approve, and administer sensitive board workflows.

Audit logs

Security-sensitive actions are logged to support reviews, traceability, and governance accountability.

Hosting in the EU

BoardKite and its database are hosted in the EU. Some optional services, such as AI, may process data outside the EU; where each provider processes data is listed with our subprocessors. View subprocessors

Subprocessor transparency

We maintain a clear list of subprocessors used to deliver infrastructure, AI, transcription, payments, analytics, and messaging services. View subprocessors