Built for boards that can’t compromise on compliance.

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 Stride is encrypted in transit using TLS to protect data between users, integrations, and the platform.

AI provider control

Stride includes a hosted Anthropic AI default that works out of the box. Organizations with stricter requirements can connect their own provider — a custom Anthropic key, an Azure OpenAI deployment in a specific region, OpenAI, or a self-hosted model via Ollama or vLLM. Board data is only sent to the provider your organization configures. You can verify and change the active provider from Settings → Plugins.

Transcription privacy

Meeting transcription via Recall.ai is opt-in and enabled per-meeting by your team, not automatically. The 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 compliance reviews, traceability, and governance accountability.

Hosting in EU region

Stride supports EU-region hosting so governance data remains in-region for organizations with EU data residency requirements.

Subprocessor transparency

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