CMO Studio data processing agreement.
Version 1.0. Valid from 17 November 2026.
1. Parties
This agreement is between you, the customer that uses CMO Studio, as data controller, and CMO Partners AS, org. nr 935 854 148 MVA, Wetlesens vei 22, 0681 Oslo, Norway, as data processor. It is made under Article 28 of the General Data Protection Regulation (GDPR). It is concluded when you accept the CMO Studio terms of service, and forms part of them. In this agreement “we” means CMO Partners AS and “you” the customer.
2. Subject matter and duration
We process the personal data that you put into CMO Studio. This agreement applies for as long as you use CMO Studio, and after that until we have deleted your data as described in section 10.
3. Nature and purpose
We process personal data only to deliver CMO Studio to you: to host your apps, to store your data in databases and storage, to back it up, and to send email for you.
4. Types of data and data subjects
You decide what personal data you put into CMO Studio. Typically it is your end users’ contact data, account data and content. The data subjects are the people whose data your apps, databases, files and emails hold, typically your end users.
5. Our obligations
Instructions. We process personal data only on your documented instructions. The terms, this agreement and the actions you take in CMO Studio are your instructions. If we think an instruction breaks data protection law, we tell you.
Confidentiality. Everyone at CMO Partners who can access your personal data is bound by confidentiality.
Security. We take the technical and organisational measures required by Article 32 GDPR. They are described in Annex 1.
Subprocessors. We use subprocessors as described in section 6.
Data subject requests. We help you answer requests from data subjects who use their rights, as far as the nature of the processing allows.
Assistance. We help you meet your obligations under Articles 32 to 36 GDPR: security, breach notification, data protection impact assessments and prior consultation with the supervisory authority.
Deletion or return. When the service ends, we delete or return your personal data as described in section 10.
Audit information. We give you the information you need to show that this agreement is followed, and allow for and contribute to audits by you or an auditor you appoint.
6. Subprocessors
You give us general authorisation to use subprocessors. The current subprocessors are listed in Annex 2. We email you at least 30 days before we add or replace a subprocessor, and you can object in that time. We bind every subprocessor to the same data protection obligations as in this agreement, and we remain responsible to you for their work.
7. Personal data breaches
If a personal data breach affects your data, we tell you without undue delay, and at the latest within 48 hours after we become aware of it. We give you the information you need to meet your own obligations to notify.
8. International transfers
We do not plan to store your data outside the EU/EEA. Where a subprocessor may access data from outside the EU/EEA, the transfer is covered by the EU Standard Contractual Clauses or the EU-US Data Privacy Framework.
9. Retention
We keep email content for 30 days, then delete it. Backups are kept as described in the terms of service: Postgres databases are backed up daily by Azure and the backups are kept for 7 days; Relatude databases are backed up daily and the last 7 backups are kept. Other data stays until you delete it or the service ends.
10. End of the service
Before the service ends, you can export your data as database dumps and file downloads. After your account is terminated, we delete your data within 30 days. Copies in backups roll off within 35 days.
11. Law and disputes
This agreement follows Norwegian law. Disputes are handled as described in the terms of service.
Annex 1. Technical and organisational measures
Encryption. Data at rest is encrypted by Azure storage service encryption. Data in transit is encrypted with TLS 1.2 or newer.
Access. Only named CMO Partners staff have access, and they sign in with multi-factor authentication. Services use managed identities with the least privilege they need.
Audit log. Actions taken through the platform are logged in an audit log.
Approvals. Destructive actions, such as deleting a project, a database or a bucket, or making a bucket public, wait for approval from the owner of the account.
Secrets. Secrets of projects are never shown in full. Keys for signing sessions are kept in a separate store protected by Azure Key Vault.
Backups. A geo-redundant backup copy of platform data is kept within Sweden. Database backups are described in section 9.
Annex 2. Subprocessors
| Subprocessor | Purpose | Location |
|---|---|---|
| Microsoft Ireland Operations Ltd (Microsoft Azure) | Hosting, databases, storage, email delivery, key management | Apps, files and platform data in Sweden Central (Gävle/Sandviken, Sweden), with a geo-redundant copy in Sweden. Postgres databases in Norway East (Oslo). Email service (Azure Communication Services) with data location Europe. |
| Stripe Payments Europe Ltd | Card payments, billing details | Ireland |
| Vipps MobilePay AS | Vipps payments | Norway |
| Fiken AS | Accounting and invoicing (billing contact data only) | Norway |
| GitHub Inc. | Deploys from GitHub, only if you connect a GitHub repository | USA |
Stripe, Vipps and Fiken process your billing details as part of our own accounting, not the content of your projects.