Database and sign-in
Supabase — managed PostgreSQL on Amazon Web Services, region eu-north-1 (Stockholm, Sweden). Company data, users and sign-in sessions live here.
Reliability
Data lives in the European Union on certified infrastructure, roles define access, and the database is copied every day.
The database and the application run in European Union regions. The Kro assistant uses an outside provider’s models — see the separate block below.
Supabase — managed PostgreSQL on Amazon Web Services, region eu-north-1 (Stockholm, Sweden). Company data, users and sign-in sessions live here.
Google Cloud Run, region europe-north1 (Finland). The application server handles every request and checks permissions.
Firebase Hosting by Google — public pages served through a global delivery network. Company data lives only in the database.
Connections to Krokul are protected by HTTPS. The database provider encrypts data at rest (AES-256) and in transit (TLS).
Krokul runs on infrastructure that independent auditors review regularly. The certificates and reports are published by the providers themselves.
SOC 2 Type 2 with an annual audit, and ISO 27001.
Supabase securityHow Supabase goes through its SOC 2 audit and what it covers.
SOC 2 at SupabaseISO/IEC 27001, 27017 and 27018, SOC 1, 2 and 3 reports, PCI DSS — per the Google Cloud services table.
Services in scopeISO/IEC 27001, SOC 1, 2 and 3 reports, PCI DSS — per the same Google Cloud table.
Services in scopeSOC 2 Type I and II, ISO 27001:2022 and ISO/IEC 42001:2023 — the international standard for AI management systems.
Anthropic certificationsA role decides what each person sees and does — and the server enforces it.
Owner, head, manager, accountant and other roles set who sees and changes what. Cost and margin are a separate permission.
The server checks permissions on every request — the same for the screen, an API key and the Kro assistant.
After the password, the system asks for a one-time code from an authenticator app. An administrator can require two-factor sign-in for everyone in the company and reset it for a user who lost a device.
Every change is logged with its author and time. Deleted items go to the trash, where you can restore them.
The assistant answers with Anthropic models. Here is what that means for your data.
The conversation with the assistant and the records it opens to answer. The assistant acts with the rights of the user who is talking to it, so it cannot see what that user cannot.
Under Anthropic’s terms for the commercial API, prompts and responses are not used to train models unless the company itself agrees.
Anthropic policyUnder its standard policy, Anthropic deletes prompts and responses on its side within 30 days.
Retention periodsA conversation with Kro is kept in Krokul for 30 days after the last message. You can delete it at any time — permanently.
The request to the model is processed on Anthropic’s infrastructure, which may be outside the European Union. The Krokul database stays in the EU.
The assistant can be switched off for the whole company or for individual roles in the settings.
When Kro analyses a call recording, the Krokul server sends the audio to Google Cloud Speech-to-Text for transcription, and this processing may take place outside the European Union. Krokul keeps the transcript and the summary; it does not store the audio — the recording stays with the telephony service. Only the company administrator can turn on analysis of all new calls, and turns it off in the same place, under Usage.
Every day the system makes a full copy of the database and ships it to separate private storage outside Supabase. The system reads each copy back and verifies it before counting it as saved; older copies rotate on a schedule.
The data belongs to your company, and you can take it with you at any time.
Tables to Google Sheets, documents to Google Docs, contacts to vCard. The free plan included.
Public API v1 covers everything in the interface; the documentation is in English.
API documentationEvents reach your systems through a queue, with delivery retries and a log.
The Kro assistant answers right away — about setup, your data and what the system can do. When a question needs a person, Kro hands it to the Krokul team together with the conversation. A partner implementer takes on complex setup and data migration.
In the European Union: the database in region eu-north-1 (Stockholm), the application in region europe-north1 (Finland).
Our providers’ infrastructure is certified: Supabase holds SOC 2 Type 2 and ISO 27001, while Google Cloud Run and Firebase Hosting are in scope of Google Cloud’s ISO/IEC 27001 certification and SOC reports. The providers publish the certificates and reports themselves.
No. Krokul does not train models on company data, and under the commercial API terms Anthropic, whose models the Kro assistant uses, does not use prompts and responses for training unless the company itself agrees.
The database and the application stay in the EU. A request to the Kro assistant is processed by Anthropic, and that processing may take place outside the EU; the assistant can be switched off.
Every day. The copy goes to separate private storage outside the database provider and is verified by reading it back.
Export to Google Sheets, Docs and vCard is available on every plan, and the public API returns everything in the interface.
Roles, the action log and export — on a company already filled with deals, projects and hours.