Skip to content

Data Processing Agreement

Viestivastaaja's data processing agreement for business customers under Article 28 GDPR, including the description of processing, security measures and sub-processors.

Updated 24 Oct 2026Version 1.3The Finnish version is legally binding.
Contents
  1. 1. Definitions
  2. 2. Scope and order of precedence
  3. 3. Subject matter, duration, nature and purpose of the processing
  4. 4. Obligations of the controller
  5. 5. Obligations of the processor
  6. 6. Sub-processors
  7. 7. Transfers outside the European Economic Area
  8. 8. Personal data breaches
  9. 9. Deletion and return of data
  10. 10. Audits
  11. 11. Liability
  12. 12. Term
  13. 13. Changes
  14. 14. Governing law and disputes
  15. Annex 1 – Description of the processing
  16. Annex 2 – Technical and organisational measures
  17. Annex 3 – Sub-processors

Effective from 24 October 2026. Version 1.3.

This data processing agreement (the "DPA") forms part of Viestivastaaja's Terms of Service and applies to the business plans (Starter, Team, Scale and Enterprise). The parties to the DPA are

  • the customer as controller (the "controller"), and
  • Viestivastaaja Oy (also registered as Message Voicemail Ltd; business ID 3590805-1, registered office Sipoo, postal address Hansaksentie 15c, 01150 Söderkulla, Finland) as processor (the "processor").

The DPA enters into force when the customer accepts the Terms of Service, and it meets the requirements of Article 28(3) of the EU General Data Protection Regulation ((EU) 2016/679). The DPA does not apply to the Personal plan, because Viestivastaaja Oy is itself the controller on that plan as described in the Privacy Policy.

1. Definitions

1.1 This DPA uses the terms defined in the GDPR, such as personal data, processing, controller, processor, data subject and personal data breach.

1.2 Applicable data protection law means the GDPR, the Finnish Data Protection Act (1050/2018), the Finnish Act on Electronic Communications Services (917/2014) and other EU and Finnish legislation applicable to the processing of personal data.

1.3 Customer personal data means the personal data that the processor processes on behalf of the controller to provide the Service, as described in Annex 1.

1.4 Sub-processor means another processor engaged by the processor that processes customer personal data.

1.5 Other capitalised terms have the meaning given to them in the Terms of Service.

2. Scope and order of precedence

2.1 This DPA applies to all processing of customer personal data carried out by the processor on behalf of the controller.

2.2 This DPA does not apply to data for which Viestivastaaja Oy is itself the controller, such as the account, sign-in, security and billing data of the customer's users. Their processing is described in the Privacy Policy.

2.3 If this DPA and the Terms of Service conflict in a matter concerning the processing of personal data, this DPA prevails. If the parties have concluded standard contractual clauses, those clauses prevail.

3. Subject matter, duration, nature and purpose of the processing

3.1 Subject matter. The processing concerns data on calls routed to the Service and messages left by callers, including messages and callback requests left through the message link, and content the customer stores in the Service.

3.2 Nature. The processing consists of receiving calls; recording, storing, transcribing and summarising messages with AI; classifying and extracting data; delivering summaries to the channels chosen by the customer; sending the message link by SMS to a caller who left no message, when the customer has turned it on; receiving messages and callback requests on the link's page; and deleting data.

3.3 Purpose. Customer personal data is processed only to provide the Service to the customer in accordance with the Terms of Service.

3.4 Duration. The processing continues for the term of the agreement and thereafter until the data has been deleted in accordance with section 9.

3.5 The categories of personal data and of data subjects are described in Annex 1.

4. Obligations of the controller

4.1 The controller is responsible for ensuring that

  • the processing has a legal basis under applicable data protection law;
  • callers are told in the greeting that the message is recorded and processed with AI, and that data subjects receive the information required by Articles 13 and 14 of the GDPR;
  • its employees and other users are informed and legislation on privacy in working life is complied with;
  • the processing of special categories of personal data is lawful if such data is to be expected in messages in its sector;
  • retention periods are set to match its needs and obligations; and
  • the delivery channels it chooses (for example Telegram, Slack, Microsoft Teams and webhooks) are suitable and lawful for its purposes.

4.2 The controller's instructions must comply with applicable data protection law.

5. Obligations of the processor

5.1 Processing on instructions

5.1.1 The processor processes customer personal data only on documented instructions from the controller, including with regard to transfers to third countries, unless required to do so by EU or Finnish law. In such a case the processor informs the controller of that legal requirement before processing, unless the law prohibits such information.

5.1.2 The controller's instructions are the Terms of Service, this DPA, the settings and choices the controller makes in the Service or through the API (for example greetings, delivery channels, rules, the message link and retention periods), and other written instructions agreed between the parties. The controller instructs the processor to show and deliver each call only to the users it belongs to (Annex 2, section 3): the messages on a user's own phone to that user and whoever they have shared them with, and the messages on a shared number or phone to the teams the controller has chosen. The controller can make a number other than the Service's own shared only once the phone itself has confirmed it (Annex 2, section 3).

5.1.3 The processor informs the controller without delay if, in its opinion, an instruction infringes applicable data protection law.

5.2 Confidentiality

The processor ensures that persons authorised to process customer personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. Access to the content of messages is limited to those who need it for their duties and requires a recorded reason.

5.3 Security

The processor implements the technical and organisational measures required by Article 32 of the GDPR, as described in Annex 2. The processor may update the measures provided that the level of protection is not reduced.

5.4 Data subject rights

5.4.1 The processor assists the controller by appropriate technical and organisational measures in responding to requests from data subjects exercising their rights. For this purpose the Service includes functions for finding, exporting and deleting data. The controller's users find and delete the calls they see (Annex 2, section 3). For a request concerning a caller, the processor on request helps find and delete the caller's data across the whole account.

5.4.2 If the processor receives a request concerning customer personal data directly from a data subject, it forwards the request to the controller without delay and does not respond to it itself unless the controller has authorised it to do so.

5.5 Other assistance

5.5.1 The processor assists the controller in ensuring compliance with the obligations under Articles 32 to 36 of the GDPR, taking into account the nature of the processing and the information available to the processor. This applies in particular to security, notification of personal data breaches, data protection impact assessments and prior consultation.

5.5.2 The processor provides its standard documentation (such as the annexes to this DPA and the list of sub-processors) free of charge. For more extensive assistance, the processor may charge reasonable compensation agreed in advance, unless the need for assistance results from the processor's own breach.

5.6 Records of processing activities

The processor maintains a record of the processing activities carried out on behalf of the controller in accordance with Article 30(2) of the GDPR.

5.7 Requests from authorities

If an authority requests customer personal data from the processor, the processor notifies the controller unless the law prohibits this. The processor discloses data only where required by law and only to the extent required by the request.

6. Sub-processors

6.1 The controller gives the processor general written authorisation to engage sub-processors. The current sub-processors are listed in Annex 3 and in the list of sub-processors.

6.2 The processor concludes a written contract with each sub-processor imposing on it substantially the same data protection obligations as those in this DPA. The processor remains liable for the performance of its sub-processors' obligations as for its own.

6.3 The processor gives at least 30 days' notice of any intended addition or replacement of sub-processors by email to the customer's administrators and by updating the list of sub-processors.

6.4 The controller may object to the change in writing within the notice period on reasonable grounds relating to data protection. The parties will first try to find a solution. If no solution is found, the controller may terminate the service affected by the change with effect before the change takes effect, and the processor refunds any fees paid in advance for the period after termination.

6.5 If a sub-processor must be replaced urgently to safeguard security or the continuity of the Service, the processor gives notice of the change as soon as possible, and the controller has the rights set out in section 6.4.

6.6 Delivery channels chosen by the controller itself, such as Slack, Microsoft Teams and the controller's own webhook addresses, are not sub-processors of the processor. Data delivered to them is received by the controller, and the controller is responsible for choosing the channel. Telegram is not a sub-processor either: it is a channel the controller's users choose themselves, and when a user adds a Telegram channel, the controller instructs the processor to deliver notices there. Telegram receives only a notice of a new call (the time and a link) and the chat's id, not callers' details or the content of messages. The WhatsApp Business Platform (Meta Platforms Ireland Ltd) is a sub-processor only when the controller turns on WhatsApp notifications, and WhatsApp too receives only a notice of a new call and a link.

7. Transfers outside the European Economic Area

7.1 The processor stores customer personal data in the EU. The processor transfers, or permits the transfer of, data outside the EEA only in accordance with Chapter V of the GDPR.

7.2 Transfers are based on

  • a European Commission adequacy decision, including the EU–US Data Privacy Framework (EU–US DPF) for recipients certified under it;
  • the standard contractual clauses adopted by European Commission Decision (EU) 2021/914 (Module 3 for processor-to-processor transfers); or
  • approved binding corporate rules.

7.3 The processor assesses the risks of transfers and uses supplementary measures where necessary. For example, the telephony provider Twilio processes calls, recordings and SMS in its Ireland region. Recordings are deleted from Twilio as soon as they have been transferred to storage in the EU, call logs after a day and SMS messages after two hours. Notices to WhatsApp and Telegram contain no callers' details and no message content.

7.4 Where the controller chooses a delivery channel that processes data outside the EEA (for example Telegram), the controller is responsible for assessing the lawfulness of the transfer. A Telegram channel can be added only once the user adding it has given explicit consent to the transfer in the app (Article 49(1)(a) GDPR) after being told its risks. The time of consent is recorded, and consent can be withdrawn by removing the channel. The processor describes known transfers in the list of sub-processors.

8. Personal data breaches

8.1 The processor notifies the controller of a personal data breach affecting customer personal data without undue delay and in any event within 48 hours of becoming aware of it.

8.2 The notification contains the information referred to in Article 33(3) of the GDPR to the extent available: the nature of the breach, the categories and approximate numbers of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact person. Where not all information is available at the same time, it is provided in phases without undue further delay.

8.3 The processor takes reasonable measures without delay to contain the breach and mitigate its adverse effects, documents the breach and assists the controller with notifications to the supervisory authority and to data subjects.

8.4 The controller decides on notifications to the supervisory authority and to data subjects. The processor does not notify the controller's data subjects of the breach in its own name unless required by law or otherwise agreed.

8.5 A notification or assistance does not constitute an admission of liability.

9. Deletion and return of data

9.1 During the term of the agreement, the controller can export and delete data in the Service. An export holds the calls that the person exporting sees (Annex 2, section 3). The processor deletes recordings, transcripts and summaries, and the caller's phone number and the notes written on the call, automatically according to the retention periods set by the controller (Annex 1).

9.2 When the agreement ends and deletion of the account has been requested, the processor deletes customer personal data 14 days after the request, and backups roll over within 30 days. The controller should export any data it needs before then.

9.3 The processor may retain data for longer only if EU or Finnish law requires it. In that case the data is processed only for that purpose.

9.4 The processor confirms the deletion in writing on request.

9.5 If the account's subscription ended at least 12 months ago and the account has had no calls and no sign-ins for 12 months, the processor deletes the account and the customer personal data without a request. The account's owners are told of the deletion by email (or by SMS if there is no email address) 30 days in advance, and the account can be kept by signing in and cancelling the deletion. This does not apply to an account the processor has suspended; deletion of such an account is decided separately.

10. Audits

10.1 The processor makes available to the controller all information necessary to demonstrate compliance with this DPA and with the obligations under Article 28 of the GDPR.

10.2 Audits are carried out primarily on the basis of documentation: the processor's security description, the annexes to this DPA, the certifications and audit reports of sub-processors, and the processor's answers to the controller's reasonable written questions.

10.3 If the documentation does not sufficiently demonstrate compliance, the controller may carry out an on-site audit on the following conditions:

  • the audit is notified in writing at least 30 days in advance;
  • audits take place at most once per calendar year;
  • the controller bears its own costs and the reasonable costs incurred by the processor;
  • the audit is carried out by the controller or by an independent auditor who is bound by confidentiality and is not a competitor of the processor; and
  • the audit is carried out during business hours without disrupting the processor's operations or jeopardising other customers' data.

10.4 The once-a-year and cost limitations do not apply if a supervisory authority requires the audit or if the audit is necessary because of a significant personal data breach for which the processor is responsible.

10.5 Sub-processors are audited on the basis of their own certifications and audit reports.

10.6 The controller provides the audit report to the processor, and the report is confidential.

11. Liability

11.1 Each party is liable towards data subjects in accordance with Article 82 of the GDPR. The processor is liable for damage caused by processing only where it has not complied with obligations of the GDPR specifically directed to processors or where it has acted outside or contrary to the controller's lawful instructions.

11.2 Between the parties, the limitations of liability in the Terms of Service (section 34) apply to the extent permitted by mandatory law.

11.3 Each party bears any administrative fines imposed on it.

12. Term

12.1 This DPA remains in force for as long as the agreement under the Terms of Service is in force and the processor processes customer personal data.

12.2 Provisions intended to survive the end of the agreement (in particular sections 5.2, 9 and 11) remain in force.

13. Changes

13.1 The processor may amend this DPA where the change results from legislation, a decision or guidance of an authority, or new standard contractual clauses adopted by the Commission.

13.2 Other changes are notified and governed by section 14 of the Terms of Service (notice at least 30 days in advance and the right to terminate the agreement).

14. Governing law and disputes

14.1 This DPA is governed by the laws of Finland, excluding its choice-of-law rules.

14.2 Disputes are settled in the Helsinki District Court as the court of first instance.


Annex 1 – Description of the processing

Categories of data subjects

  • callers whose calls are routed to the Service;
  • people mentioned in messages;
  • the controller's users and employees, to the extent their data appears in the content of messages, greetings, delivery rules, delivery channel addresses or sharing settings (teams, sharing rules and sharing history).

Categories of personal data

  • call details: the caller's phone number (if transmitted), the number and line called, the time, duration and status of the call;
  • messages: audio recordings, and spoken messages, written messages and callback requests (the preferred time and a note) left through the message link, with the name the caller gave;
  • AI-generated data: transcripts, summaries, classifications and extracted details, such as name, company and callback number;
  • delivery data: delivery channels, recipients and delivery status;
  • message link: details of the text message and link sent to the caller (times and status, and a hash of the link's code; no phone number), while the link is live a one-way hashed form of the account and the number (so that only one link is sent at a time), and the caller's refusal of the controller's message links (a one-way hashed form of the account and the number);
  • notes: notes the controller's users have written on calls;
  • greetings: greetings uploaded, recorded or synthesised by the controller, which may contain a user's voice;
  • visibility: which of the controller's users each call is shown to (decided when the call arrives), teams, lines' sharing rules with their working hours and away periods, and lines' sharing history;
  • settings: delivery channel addresses (phone numbers, email addresses, messaging app identifiers, webhook addresses), business hours and rules.

Special categories of personal data

The Service is not intended for collecting special categories of personal data. However, callers may mention, for example, health information in their messages. The controller is responsible for the lawfulness of processing such data.

Processing operations

Receiving calls, playing the greeting, recording and storing messages, transcribing and summarising them with AI (Google's Gemini models in the EU), classification, extracting details, delivering summaries, notifying missed calls, sending the message link by SMS to a caller who left no message under the controller's settings, receiving a spoken or written message or a callback request on the link's page and adding it to the call, displaying data in the app and the API to the users each call belongs to, and deleting data.

Retention periods

The controller may set a shorter retention period and delete data at any time. Default and maximum retention periods per plan on 20 October 2026:

The values in force are shown in the Service's settings.

When the retention period for a call's content ends, the caller's phone number and the notes written on the call are erased together with the transcript and summary. A row without the caller's details remains, to count calls and costs.

Nothing is recorded for calls a person answers in the "Try a person first" step. Their details are kept as for the plan's transcripts, and the caller's details are then erased in the same way.

For calls the Service rejects or cannot route (for example a blocked caller or an inactive account), the caller's phone number and the call details are kept for 90 days, after which the caller's details are erased in the same way. If the caller had already left a message that cannot be routed to anyone, the recording is also kept for 90 days, and only Viestivastaaja Oy's customer service can listen to it, with a stated reason, to find out whom the message was for.

A line's sharing history is kept for three years, to be able to show who could see which message. A withdrawn sharing rule stays on the line for 7 days. Teams and sharing rules in force are kept until deleted.

A message left through the message link is kept like other messages: a spoken message like recordings, and a written message or a callback request like transcripts. A spoken message waits in temporary storage for at most a day before it is processed. The message link's details are kept for 30 days after the link's 72 hours end, to look into support requests and misuse; whether a link was sent (or why not), and when it was opened and used, is also kept on the call like its other details. The hashed form that ensures a caller has only one live link at a time is kept until the link's 72 hours end, and the caller's refusal until the account is deleted.

Duration of the processing

The term of the agreement and thereafter the deletion period under section 9.


Annex 2 – Technical and organisational measures

1. Location and infrastructure

  • The Service runs on Google Cloud in the EU. The database and files are in Finland (europe-north1), and task queues and scheduling run in Belgium (europe-west1). Analytics (BigQuery) is in the EU.
  • The AI models (Gemini) and speech synthesis are used within the EU.
  • Calls, recordings and SMS are processed in Twilio's Ireland region (ie1) through an EU edge location. The production service does not start unless Twilio's EU region is configured.
  • Physical security of the data centres is provided by Google in accordance with its certifications.

2. Encryption

  • Data in transit is encrypted with TLS 1.2 or later.
  • Stored data is encrypted with AES-256.
  • Webhook addresses and third-party tokens (for example messaging app keys) are additionally encrypted at application level with AES-256-GCM.

3. Access control

  • The database can be accessed only from our servers. Browsers and client apps have no direct access to the database.
  • Service accounts follow the principle of least privilege, and their keys are never exported from the platform.
  • In the controller's account each call is shown only to the users it belongs to. That is decided when the call arrives: calls on a user's own phone (a personal line) are seen by its owner and by whoever the owner has shared them with, calls on a shared number by the teams the controller has chosen or the whole organisation, and calls whose line cannot be told by the account's owners and administrators. A role gives no access by itself. A phone other than the Service's own number is shared only once whoever holds it has confirmed the sharing after the phone was told, by text or by a call, who sees its messages, or once the processor's staff have verified, from the controller's evidence, a number that takes neither texts nor calls. The processor tells a shared phone who its messages are shown to about every 90 days and whenever that changes. A confirmation is valid for a year; if it lapses, new calls are seen only by those its calls were shown to while it was confirmed (the account's owners and administrators among them or, if there are none, all of them, as at the lapse), and if whoever holds the phone objects, calls forwarded from it are no longer answered until it confirms again. The same limits apply to deliveries, notifications, the "Try a person first" step, search, statistics, exports, the API and the MCP server.
  • An API key acts for the user who created it, with that user's permissions, and is revoked when the user leaves the account.
  • Only a line's owner can change the line's sharing, signed in with their own session and after an explicit confirmation; not another user whatever their role, not an API key and not our staff. Sharing covers only calls that arrive afterwards. Every change is written to the audit log and to the line's sharing history.
  • Staff sign in to the administration console with Google accounts, and permissions are role-based.
  • Staff access to call content requires a recorded reason, and every access is written to an audit log.
  • The audit log is kept for two years.

4. Data minimisation and retention

  • Recordings are copied from the telephony provider to storage in the EU and deleted at the provider immediately.
  • Call logs (who called and when) are deleted at the telephony provider 24 hours after the call, and SMS messages, including their text, 2 hours after they were sent or received.
  • Retention periods are configurable, and data is deleted automatically when the retention period ends. The caller's phone number is erased together with the call's content (Annex 1).
  • Notices to WhatsApp and Telegram contain only that a new call came in, its time and a link that opens the call in the Service after sign-in; they contain no caller details and no message content. The controller can set other channels too, except webhooks, to show only the time and a link.
  • An account whose subscription ended at least 12 months ago and which has had no calls and no sign-ins for 12 months is deleted, and its owners are told 30 days in advance (section 9.5).
  • Logs never contain transcripts, summaries, full phone numbers or secret keys and credentials, and server logs are kept for 30 days.
  • One-time sign-in codes are stored only as a hash, for 10 minutes.

5. Availability and recoverability

  • The database can be restored to a point in time (point-in-time recovery).
  • Data is backed up daily, and backups roll over within 30 days.

6. Application security

  • Sign-in is based on one-time codes, and sign-in attempts are rate-limited.
  • Owners and admins of the customer's account sign in in two steps: a code to their phone and a code to their email or their Google account. The owner or admin role can be given only to a user with two-step sign-in set up, and a session that lacks the second step reaches no data until it is confirmed.
  • The sign-in cookie is an HttpOnly cookie, and cookies are only sent over encrypted connections.
  • The websites use browser security headers.
  • Software dependencies are updated regularly.

7. Monitoring and incident management

  • The operation of the Service is monitored, and anomalies trigger alerts.
  • There is a process for security incidents: detection, containment, investigation, remediation, documentation and notification of the controller under section 8.

8. Personnel and sub-processors

  • Personnel are bound by confidentiality, and access to data is limited to what their duties require.
  • Sub-processors are assessed before they are engaged, and contracts under Article 28 of the GDPR and, where necessary, standard contractual clauses are concluded with them.

Annex 3 – Sub-processors

The current list is on the sub-processors page. Sub-processors on 20 October 2026: