Security and EU data
Floral holds your company's memory. That is a responsibility we take literally.
Meetings, sources and records are stored in the EU, the AI models run on an EU endpoint, and nothing you give Floral is used to train anyone's model. Inside the workspace, you decide who sees what, which meetings stay out of the AI features, and every AI action waits for a person to approve it.
In the EU, from storage to AI
It is easy to store data in Europe and quietly send it elsewhere for the AI part. Floral keeps the whole path in the EU - and checks it at build time.
Stored in the EU
Meetings, transcripts, summaries, sources and CRM records are stored in the EU. Your knowledge does not leave the region to be kept.
AI on an EU endpoint
The models run on an EU endpoint in Sweden with provider storage disabled. A build check blocks any direct use of US AI services, so the rule cannot be broken by accident.
Processing in the EU
Files are parsed and recordings are processed in the EU. The bot that joins your online meetings runs from Frankfurt.
Never used for training
Your data is never used to train models - not by Floral and not by the model providers. It exists to serve your team, nobody else.
Login and SSO via Clerk
Authentication is handled by Clerk, including single sign-on. Access is enforced on the server on every request, not just hidden in the interface.
Export at any time
CSV, PDF, XML or the API - take your data with you whenever you want. Trust is easier when leaving is easy.
You decide what the AI sees and does
A knowledge engine is only useful if the people running it stay in charge. These are the controls you have, per person, per meeting and per action.
Per-user feature access
Admins hide whole areas and specific actions from the people who do not need them. The assistant and every AI client inherit exactly the same limits.
The internal-meeting switch
Mark a meeting as internal and it stays searchable for your team, but is excluded from insights, CRM sync and AI record updates.
Transcript retention
Prefer not to keep word-for-word transcripts? Retention can be set to keep only the approved summaries. Available on request.
Approval and a log for every AI action
Nothing is written to a record without a person approving it, and every applied change is logged in the activity timeline with the meeting it came from.
Pairs well with
Per-user feature access
The access rules the assistant and every AI client inherit are the ones you set here.
API and MCP
Open by design - and every call re-checks membership, role and feature access.
Proactive intelligence
Proposed follow-ups with evidence attached - applied only when a person approves.
Frequently asked
In the EU. Files are parsed and recordings are processed in the EU as well, and the meeting bot runs from Frankfurt.
The models run on an EU endpoint in Sweden with the provider’s storage disabled, so prompts and outputs are not kept by the provider. A check in Floral’s build pipeline blocks any direct use of US AI services, so this is not something that can slip in by accident.
No. Customer data is never used to train models - neither Floral’s nor the providers’.
Yes. Mark a meeting as internal and it stays searchable for your team but is excluded from insights, CRM sync and AI record updates. No suggestions are ever made from an internal meeting.
No. Transcript retention can be set so that only the approved summaries are kept. Ask us and we will enable it for your workspace.
No. Every AI action that writes to a record requires a person’s approval first, and every applied change is logged in the activity timeline. Per-user feature access also lets admins hide entire areas and actions from the people who should not have them.
Login is handled by Clerk, with support for single sign-on. Access is checked on the server on every request, not just in the interface.
Yes, at any time. Export as CSV, PDF or XML, or pull everything through the API. And you can try Floral for 30 days without giving us a card.
Insights
Read more
11 min read
CRM vs meeting intelligence: where each belongs in a modern sales stack
CRM vs meeting intelligence is not a choice between two tools. One is a system of record, the other a system of evidence. Here is which jobs belong where, and why.
Try it on your own terms
30 days, no card, and your data is yours to export the day you decide to leave. Or let's meet and walk through the details together.