1. The agreement
When the client uses PRM.no, Desken AS processes personal data on the client's behalf: the client's users and contact persons, the client's own recipient lists, and people mentioned in the press releases. The client is the controller. Desken AS is the processor.
The text of the agreement is the European Commission's standard contractual clauses between controllers and processors under Article 28(7) of the General Data Protection Regulation: Implementing Decision (EU) 2021/915 of 4 June 2021. The clauses apply together with Annexes I–IV below, which describe the processing in PRM.no.
Choices made in the standard clauses:
- Clause 5 (docking clause) is not used.
- Clause 7.7: option 2, general written authorisation of the sub-processors in Annex IV. Desken AS informs the client in writing at least 30 days before a sub-processor is added or replaced, and the client may object within that period.
This data processing agreement is entered into and ends together with the client agreement. In the event of a conflict between the standard clauses and the terms, the standard clauses prevail.
Annex I. The parties
Controller: the client, with name, organisation number and contact person as stated in the offer or order confirmation.
Processor: Desken AS, org. no. 984 358 202, Oslo. Contact for data protection: knut@prm.no.
Annex II. The processing
Purpose: to produce, assess, distribute and publish the client's press releases, and to report on the sendings.
Nature of the processing: storage, structuring, sending by email, publication in the newsroom, assessment of the release text by a language model, and reporting on delivery.
Coverage search: when the client uses the coverage search, Desken AS, on the client's instruction, sends the release's headline, the organisation's name and keywords from the text to Google's search services, before and after sending. Google processes the search as an independent controller and is not a sub-processor.
Data subjects and personal data:
| Data subjects | Personal data |
|---|---|
| The client's users of the portal | Name, email, role and sign-ins. |
| The client's contact persons | Name, job title, email, phone, and a photo if one has been added. |
| People on the client's own lists and individual addresses | Name, email, and where given, media outlet and job title. Delivery status, bounces and complaints. Opens and clicks only when the client has switched on tracking for the sending. |
| People mentioned, quoted or pictured in the press releases | What the client writes about them, and photos. |
Special categories of personal data are not foreseen. The client must not enter them in lists or contact fields.
Not covered: the media register (editorial addresses and journalists) and journalists' own sign-ups. For these, Desken AS is itself the controller. See the privacy policy.
Duration: for as long as the client agreement runs. When it ends, the client's own lists and releases are handed over on request, and then deleted within 90 days. Press releases published in the newsroom are removed at the same time, unless otherwise agreed.
Retention during the agreement: recipients in the sending log are pseudonymised 12 months after the sending. Address, name, merge fields and the link to the client's list are removed, while counts and timestamps remain, so the reports are kept. Raw data from the email provider is deleted 30 days after it has been processed.
Annex III. Technical and organisational measures
- The database, files and sign-in are in Stockholm (EU), and the press releases are sent from there. The server functions run in the Supabase region nearest the user.
- All traffic to the website and the interface is encrypted. Unencrypted traffic is redirected to encrypted.
- Each client sees only its own data. This is enforced in the database, row by row, not only in the user interface.
- Users can change only the fields their role gives them access to, also when they go directly to the interface.
- Sign-in can use a one-time link by email, valid for one hour.
- Service keys are kept on the server only, never in the browser.
- An approved press release cannot be changed without the approval being withdrawn.
- Unsubscribes and blocks are enforced across all clients, before a message is built.
- When a recipient is blocked or asks to be erased, the sending log is pseudonymised for that person.
- Each sending is logged before the email is sent, so no message goes out twice, and everything can be verified.
- Only Desken AS' platform administrators have access across clients.
- Daily backup of the database.
Annex IV. Sub-processors
| Provider | What they do with the client's data | Where |
|---|---|---|
| Supabase | Database, sign-in, files and server functions. | Stockholm, EU. The server functions run in the Supabase region nearest the user. |
| Amazon Web Services (SES) | Sends the press releases, and reports back on delivery, bounces and complaints. | Stockholm, EU |
| Brevo | Sends sign-in links and invitations to the client's users. | France and Belgium, EU |
| Domeneshop | Hosts the prm.no website and the newsrooms. | Norway |
| Anthropic | The language model that assesses the release text, which may contain names. | USA |
Transfers outside the EEA. Data is stored in the EEA, with one exception: Anthropic stores it in the US. Our contracting party there is Anthropic Ireland, and the transfer to the US is based on the EU standard contractual clauses (SCC) in Anthropic's data processing agreement. Supabase (contracting entity in Singapore, and server functions that run in the region nearest the user), AWS and Brevo may give access from outside the EEA through their own affiliates and sub-processors, based on SCC, or the EU–US Data Privacy Framework where the recipient is certified. If you would like to know more about the basis, write to knut@prm.no.