AI Transparency Disclosure
Deep Thought Cloud
- Last Updated: September 10, 2026
- Version: 1.1
Provider
Dolutions AB Org.nr 556981-0293 Box 150, 101 22 Stockholm, Sweden VAT: SE556981029301
Contact: legal@deep-thought.cloud
1. AI-Powered Service
Deep Thought Cloud uses artificial intelligence to process your content. This document explains how AI is used in our service, in accordance with the EU AI Act transparency requirements.
2. AI Capabilities
Our service uses AI for the following functions:
| Function | Description |
|---|---|
| Transcription | Converting speech in audio/video files to text |
| Summarization | Generating concise summaries of transcribed content |
| Entity Extraction | Identifying people, organizations, locations, and topics |
| Keyword Extraction | Identifying key terms and concepts |
| Auto-Tagging | Automatically suggesting tags based on content |
| Content Analysis | Analyzing content type, language, and context |
3. AI Models and Processors Used
Processing happens in two stages with different guarantees. This section lists every service that may process your content.
Stage 1 — Speech-to-text and speaker identification (always our own hardware)
| Model | Purpose | Runs on | Jurisdiction |
|---|---|---|---|
| KB-Whisper | Swedish speech recognition | Our own GPUs | Sweden |
| OpenAI Whisper (local deployment) | Multilingual speech recognition | Our own GPUs | Sweden |
| pyannote (local deployment) | Speaker identification and separation | Our own GPUs | Sweden |
Your audio is never sent to a third party. No account setting changes this.
Stage 2 — Text analysis (depends on your account settings)
The transcribed text is analysed to produce titles, summaries, entities, keywords and insights. The processor depends on your settings and on availability, in this order:
| Order | Processor | Model | Jurisdiction | When it is used |
|---|---|---|---|---|
| 1 | Your own provider (BYOK) | Your choice | Per your contract | Only if you have configured an API key |
| 2 | Berget.ai | gemma-4-31B-it |
Sweden (EU/Nordic provider, Sweden-resident inference) | The default for accounts without their own key |
| 3 | Our own hardware (Ollama) | qwen3, gpt-oss, gemma4 |
Sweden, our own GPUs | When Berget.ai is unavailable, and always in local-only mode |
| 4 | OpenRouter (Anthropic Claude Haiku) | claude-haiku |
United States | Last resort only — when both the above are unavailable |
Additional processors that may appear in specific features: system Anthropic (United States) for certain synthesis tasks, and OpenAI’s Whisper API (United States) for cloud transcription spillover, which is off by default and requires explicit opt-in.
Berget.ai is a third party. It is a Swedish company performing inference in Sweden, which is why we chose it as the default — but your text does leave our systems to reach it. Any statement that no data is sent externally applies only to local-only mode (§4.2).
4. Controlling where your content is processed
4.1 BYOK (Bring Your Own Key)
If you configure your own API key (OpenAI, Anthropic):
- Your content is sent to that provider first, under your own contract
- Processing occurs according to their privacy policy
- This is optional and user-initiated
BYOK is a preference, not a restriction. If your provider fails or is unreachable, processing continues through the chain in §3 rather than stopping. BYOK alone does not guarantee that only your provider sees your content. If you need that guarantee, use local-only mode.
4.2 Local-only mode
Local-only mode (local_processing_only) prevents all external inference. With it enabled:
- All text analysis runs on our own hardware
- Cloud transcription spillover is disabled
- Cloud-dependent integrations, including meeting-bot capture, are unavailable and will refuse to start rather than proceed
The restriction is enforced at four independent points in our system. Two of them fail closed: if the privacy check itself cannot complete, processing is treated as local-only rather than being allowed to continue. A failure in our own systems cannot cause your content to be sent externally.
Trade-off: local-only mode uses smaller models than the default. In our own testing (2026-09-10) this cost processing speed rather than accuracy — the same meeting produced the same people, organisations and decisions, but took substantially longer. It is available on request — contact support@deep-thought.cloud.
5. AI Output Accuracy
Important: AI-generated outputs may contain errors.
- Transcriptions may have inaccuracies, especially with accents, technical terms, or poor audio quality
- Summaries are machine-generated interpretations, not human-verified
- Entity extraction may miss or misidentify items
- Auto-tagging suggestions are algorithmic recommendations
We recommend human review for:
- Legal or contractual content
- Medical or healthcare information
- Financial decisions
- Any critical business use
6. Human Oversight
- AI outputs are provided as-is without human verification
- You can edit, correct, or delete any AI-generated content
- Feedback mechanisms allow you to improve accuracy over time
- Final decisions should always involve human judgment
7. Data Usage
- Your content is NOT used to train our AI models
- Processing is performed only to deliver the requested service
- Audio files are deleted after transcription (only results retained)
- See our Privacy Policy for full data handling details
8. AI Risk Classification
Under the EU AI Act, our AI system is classified as limited risk, requiring transparency obligations. We provide this disclosure to ensure you are informed about AI usage in our service.
9. Your Rights
You have the right to:
- Know when AI is processing your content (this disclosure)
- Access AI-generated outputs
- Correct or delete AI outputs
- Opt out of optional AI features
- Request human review where applicable
10. Contact
Questions about AI usage: legal@deep-thought.cloud
This AI Transparency Disclosure is provided in compliance with EU AI Act transparency requirements.