Legal
Data processing agreement
Last updated 21 November 2026
The short version
- This agreement applies when Opisense AS processes personal data for your organisation in the hosted service. It is part of our terms of service.
- You decide what is processed. We process it only to provide Opisense to you, on your instructions.
- Your content is stored on servers in Germany and encrypted per space. The providers that help us are listed below.
- We tell you about a personal data breach within 48 hours, and about new providers 30 days before they start.
- You can export your content and delete it at any time.
About this agreement
This data processing agreement (“DPA”) is between Opisense AS (organisation number 936 578 195), Lade alle 48A, 7041 Trondheim, Norway (“Opisense”, “we”, “us”), and the organisation that uses the hosted Opisense service (“you”).
It forms part of our terms of service and applies from the moment you accept them. You don’t need to sign anything separately. If your organisation needs a signed copy, write to support@opisense.com.
It covers personal data we process on your behalf in the hosted service at bots.opisense.com and the web, desktop and mobile apps that connect to it. It does not cover Opisense software you run on your own servers, where we process nothing for you.
Words such as “personal data”, “processing”, “controller”, “processor”, “data subject” and “personal data breach” mean what they mean in the General Data Protection Regulation ((EU) 2016/679, “GDPR”), which applies in Norway through the EEA Agreement and the Personal Data Act.
Roles
You are the controller of the personal data in the content your people and bots put into Opisense. If you process that data for your own clients, you are their processor, and we are your sub-processor.
We are your processor for that content.
Data we use to run our own business, such as account and sign-in details, billing, security records and support conversations, is covered by our privacy notice, where we are the controller.
What we process
| Subject matter | Providing the hosted Opisense service to you |
| Duration | For as long as you use the service, and until the data is deleted as described in End of the service |
| Nature and purpose | Storing, transmitting and processing content so that bots can chat, remember, use a computer, connect to apps, join meetings, make documents and pages, and run routines and workflows for you |
| Types of personal data | Whatever your people and bots put into Opisense: messages and chats, bot instructions and memory, files, documents, sheets, decks and pages, meeting transcripts with speaker names, data bots read or write in connected apps, and saved credentials |
| Data subjects | Your employees and other users, and people who appear in your content, such as your customers, contacts and meeting participants |
You decide what goes into Opisense. Don’t put in special categories of personal data, such as health data, unless you have a lawful basis for it and it is needed for your use.
Your instructions
We process personal data only on your documented instructions. Your instructions are these terms and this DPA, the settings you choose, and the way you and your bots use the service, including the apps you connect and the work you give bots.
We will not process your personal data for any other purpose. We don’t use it to train AI models, and we don’t sell it.
If we believe an instruction breaks data protection law, we will tell you. If the law requires us to process personal data in another way, we will tell you first, unless the law forbids it.
Confidentiality
Only people who need access to provide and support the service get it, and they are bound by confidentiality.
Opisense staff can see an organisation’s members, spaces, bots and skills, but not chats, memory, files or credentials. Their administrative changes are recorded in your audit log.
Security
We take technical and organisational measures that fit the risk, as GDPR Article 32 requires. They include:
- Location. Servers and the database are in Germany. Encrypted backups and bot computers are in the EU.
- Encryption. Chats, memory, files, meeting transcripts and credentials are encrypted before they are stored, with a separate key for each space (AES-256-GCM). Traffic to and from the service is encrypted with TLS.
- Credentials. Saved passwords and API keys are never shown to the model.
- Zero data retention. Recall.ai, Composio, OpenRouter, OpenAI and fal.ai are set up for zero data retention: they don’t keep your content after handling it, apart from the app connections Composio holds for you.
- Access inside your organisation. Spaces separate teams. Owners and admins can’t read other members’ chats. Team admins can see an audit log of invitations, roles, removals and space changes.
- Bot actions. Bots ask before actions that are hard to undo, unless you choose otherwise. Runs started from outside, such as webhooks, ask before every change. Content a bot reads is treated as information, not instructions.
- Bot computers. Each bot works in its own isolated computer.
- Meetings. Meeting recordings are deleted at the meeting provider once the transcript is saved, within 24 hours at the latest.
- Records. Sign-in and security events are kept for 90 days to investigate problems.
- Backups. Encrypted backups are kept for up to about three weeks, then overwritten.
Encryption protects stored data and backups. It is not end-to-end encryption, and some metadata, such as names, is stored in plain text.
We review these measures as the service changes, and we won’t reduce the overall level of protection.
Sub-processors
You give us general authorisation to use sub-processors. The current ones are listed in Sub-processors below.
We bind each sub-processor by contract to data protection obligations that give at least the protection this DPA requires, and we remain responsible to you for its work.
We will tell your organisation’s owner by email at least 30 days before a new sub-processor starts processing your personal data, and update the list on this page. If you have reasonable data protection grounds to object, tell us within that period. We will try to find a solution. If we can’t, you may end the affected service, and we will refund any fees you paid in advance for the time after it ends.
Services you choose to connect are not our sub-processors. When you connect your own model provider account, an app, or a voice or memory service, your content goes to that service on your instruction and under its terms.
Transfers outside the EEA
Most sub-processors process your personal data in the EU. Those that process it in the United States are covered by one of these safeguards:
- EU-U.S. Data Privacy Framework. ElevenLabs and Expo are certified under the framework, which the European Commission has found gives an adequate level of protection. You can check their certification on the Data Privacy Framework list.
- EU Standard Contractual Clauses. The European Commission’s standard clauses for transfers apply to Composio, OpenAI and fal.ai, through our data processing agreements with them.
Companies that need all processing inside their own network can run Opisense on their own servers, with the providers they choose.
Helping you
Requests from data subjects. You can answer most requests yourself: you can find, export, correct and delete content in the apps, and Export data in Account settings downloads a copy. If you need more help, we will assist you. If a data subject contacts us directly about your content, we will refer them to you.
Assessments and authorities. We will give you the information you reasonably need for data protection impact assessments and for consultations with a supervisory authority, taking into account what we process and the information we have.
Personal data breaches
If we become aware of a personal data breach affecting your personal data, we will tell your organisation’s owner without undue delay, and no later than 48 hours after we became aware of it.
We will tell you, as far as we know it then, what happened, which kinds of data and roughly how many people are affected, the likely consequences, and what we have done or plan to do. We will send more details as we learn them, and help you meet your own obligations to notify authorities and the people affected.
Audits
We will make available the information you reasonably need to show that we meet this DPA, including answers to security questionnaires.
If that isn’t enough, you may audit our processing yourself or through an independent auditor bound by confidentiality. Give us at least 30 days’ notice. Audits happen at most once a year, unless a supervisory authority requires one or there has been a personal data breach. You pay your own costs, and audits must not disrupt the service or expose other customers’ data.
End of the service
You can export your content at any time before you stop using Opisense.
When you delete your account or team, or ask us to delete it, we delete your content from our live systems. Copies leave our encrypted backups as they are overwritten, within about three weeks. We will confirm the deletion in writing if you ask.
We keep personal data longer only where the law requires it.
Liability and precedence
Each party’s liability under this DPA follows the limits in the terms of service.
If this DPA and the terms conflict on the processing of personal data, this DPA applies. If the Standard Contractual Clauses apply and conflict with this DPA, the clauses apply.
Norwegian law applies to this DPA, and disputes go to Trøndelag District Court, as in the terms.
Changes
We may update this DPA, for example when we add a sub-processor or the law changes, and we will change the date at the top. If a change materially reduces your protection, we will tell your organisation’s owner at least 30 days before it takes effect.
Current sub-processors
These providers process your personal data to run the hosted service. Each receives only what it needs for its task.
| Provider | What for | Where | When |
|---|---|---|---|
| Hetzner Online | Servers, database and encrypted backups | Germany and the EU | Always |
| OpenRouter, which forwards to the selected model provider | AI model requests | EU | When a bot works |
| Daytona | Bot computers: files, browser sessions and commands | EU | When a bot uses its computer |
| Composio | Connecting apps and holding the app connections you authorise | United States (SCCs) | When you connect an app |
| Recall.ai | Joining meetings and recording them to make a transcript | EU | When you send a bot to a meeting |
| ElevenLabs | Speech-to-text and text-to-speech, including meeting transcription | United States (DPF) | When you use voice or meetings |
| OpenAI | Live voice calls | United States (SCCs) | When you start a live call |
| fal.ai | Image generation | United States (SCCs) | When a bot makes images |
| Resend | Sending emails such as invitations and notifications | EU | Always |
| Mollie | Payments | EU | When you pay |
| Expo | Push notifications, with a short excerpt of the message | United States (DPF) | When you use the mobile app |
DPF means the provider is certified under the EU-U.S. Data Privacy Framework. SCCs means the EU Standard Contractual Clauses apply. See Transfers outside the EEA.
Bots search the web through DuckDuckGo. Searches are sent from our servers without your account details. Push notifications to iPhones also pass through Apple’s push service.
Contact
Opisense AS, Lade alle 48A, 7041 Trondheim, Norway · support@opisense.com