Privacy Policy
How Viestivastaaja Oy processes the personal data of Viestivastaaja's customers, callers, website visitors and sales contacts, and how you can exercise your rights.
Contents
- 1. Controller and contact details
- 2. Who this policy covers and our role
- 3. In brief
- 4. Customers and users
- 5. Callers
- 6. Website visitors and enquiries
- 7. Retention periods
- 8. Recipients and sub-processors
- 9. Transfers outside the European Economic Area
- 10. AI and automated decision-making
- 11. Your rights
- 12. Security
- 13. Cookies
- 14. Right to lodge a complaint with a supervisory authority
- 15. Is providing data mandatory?
- 16. Changes
Effective from 27 October 2026. Version 1.4.
This policy explains how personal data is processed in the Viestivastaaja service. It has been prepared in accordance with Articles 13 and 14 of the EU General Data Protection Regulation ((EU) 2016/679, the "GDPR") and the Finnish Data Protection Act (1050/2018).
1. Controller and contact details
- Viestivastaaja Oy (also registered as Message Voicemail Ltd), business ID 3590805-1, registered office Sipoo
- Hansaksentie 15c, 01150 Söderkulla, Finland
- Privacy matters: tietosuoja@viestivastaaja.fi
- Customer support: tuki@viestivastaaja.fi
2. Who this policy covers and our role
This policy covers three groups:
- (a) customers and users – subscribers to the Service and users invited to business customers' accounts, and holders of phones that forward calls to the Service although they have no Service (section 4);
- (b) callers – people who leave a message, by phone or through the message link, or whose call is routed to the Service (section 5);
- (c) website visitors, people who contact sales, and contact persons at businesses we contact (section 6).
Our role depends on whose data it is and on the type of account:
| Data | Personal plan | Business plans |
|---|---|---|
| Account, sign-in, security and billing data of the customer and its users | Viestivastaaja Oy is the controller | Viestivastaaja Oy is the controller |
| Callers' data (messages, recordings, transcripts, summaries, call details) | Viestivastaaja Oy is the controller | The customer is the controller, and Viestivastaaja Oy is its processor under the Data Processing Agreement |
| Phones that forward calls to the Service without service (section 4.3) | Viestivastaaja Oy is the controller | Viestivastaaja Oy is the controller |
| Website and sales data | Viestivastaaja Oy is the controller | Viestivastaaja Oy is the controller |
Why are we the controller of callers' data on the Personal plan? An individual uses the Personal plan in their private life. The GDPR does not apply to processing by a natural person in the course of a purely personal activity (Article 2(2)(c)), but it does apply to a provider that supplies the means for such processing (Recital 18). We are therefore responsible as controller for the processing the Service carries out to receive messages and pass them on to the subscriber. The subscriber decides what to do with the summaries delivered to them. If the subscriber uses them in their business, they are responsible for their own use.
On business plans, the customer decides why and how callers' data is processed (for example greetings, delivery channels, rules, the message link and retention periods), so the customer is the controller. We process the data only on the customer's behalf and in accordance with its instructions. Callers should also read the privacy notice of the company they called.
3. In brief
- The Service records only messages that callers leave after the greeting or on the message link's page (section 5.7). The greeting and the message link's page tell callers that the message is recorded and processed with AI.
- Data is stored and processed in the EU. Our primary servers are in Finland.
- Recordings and summaries are deleted automatically when their retention period ends (section 7).
- In an account with several users, the messages left on a user's own phone are seen only by them and by whoever they share them with. A role, such as administrator, gives no access to them (section 5.6).
- We do not sell personal data and do not use messages for advertising or to train AI models (section 10).
- Our website does not use tracking or advertising cookies (section 13).
4. Customers and users
4.1 Data we process
| Category | Examples |
|---|---|
| Identity and contact details | name, phone number, email address, language; for business customers also the company name, business ID, billing address and the user's role |
| Sign-in data | one-time codes (stored only as a hash for 10 minutes), sessions and the ways of signing in they confirmed, sign-in times, which phone numbers and email addresses were confirmed with a code, recovery codes for two-step sign-in (only as hashes), for those who sign in with Google a hash of the Google account's id and the account's email address, and technical data needed to limit sign-in attempts |
| Settings | greetings (including the customer's own voice if they record a greeting), call forwarding details, delivery channel addresses (phone numbers, email addresses, Telegram and WhatsApp identifiers, webhook addresses, per-device subscriptions for app notifications), business hours and rules, and the time consent was given when a Telegram channel was added |
| Sharing and teams | teams (name and members); a line's sharing rules, that is who sees the line's messages and when, and who added or withdrew each rule and when; the working hours and away periods set for sharing (name and dates, which only the line's owner sees); a shared phone's confirmation (who confirmed it, how and when, and what the phone was told), the confirmation codes sent to the phone (as hashes only), the notices and objections, and the evidence our staff recorded if staff verified the number; the line's sharing history; the line's former owners and when they stopped owning it |
| Usage and cost data | numbers of calls, SMS messages and other deliveries, and their costs |
| Billing data | Stripe customer ID, subscription, invoices and payment status. A consumer's request to start the Service at once (time and terms version) and any withdrawal and refund. We do not process payment card details; Stripe processes them. |
| Identifiers for the first-month price | identifiers derived with a key from the account, the person ordering, their phone numbers and email address, and the business ID, from which the details cannot be recovered |
| Customer support | emails, SMS conversations and other contacts with our customer support |
| Log data | changes made in the account, and access to data by our staff with the reason for it |
We receive the data from the customer, from a business customer's administrator (when they invite a user or add them to a team), from whoever holds a shared phone (a confirmation or an objection), from Google (if the user signs in with their Google account: the account's id and email address), from Stripe (payment status) and from the use of the Service.
4.2 Purposes and legal bases
| Purpose | Legal basis (Article 6 GDPR) |
|---|---|
| Creating the account and providing the Service | performance of a contract (1)(b) |
| Sign-in, two-step sign-in (required for owners and admins of business accounts, optional for others) and session management | performance of a contract (1)(b); legitimate interest in protecting accounts and, through them, other users' and callers' data (1)(f); the security obligation (Article 32) |
| Granting the first-month price once per customer | legitimate interest (1)(f): the offer is meant for new customers, and the identifiers stop it being used again |
| Billing and payment processing | performance of a contract (1)(b); legal obligation, such as the Finnish Accounting Act (1)(c) |
| Customer support | performance of a contract (1)(b); legitimate interest in responding to enquiries (1)(f) |
| Security, prevention of misuse (for example SMS fraud) and logging | legitimate interest in protecting the Service, customers and callers (1)(f); security obligation (Article 32) |
| Measuring usage and costs, and developing the Service | performance of a contract as regards allowances and extra use (1)(b); legitimate interest in developing the Service (1)(f) |
| Service announcements (for example changes to terms and outages) | performance of a contract (1)(b); legal obligation (1)(c) |
| Direct marketing to customers | legitimate interest (1)(f). We send electronic direct marketing to consumers only about our own similar services or with consent (1)(a). You can object to direct marketing at any time. |
| Recording a line's sharing and its changes, to be able to show who could see which message | performance of a contract (1)(b); legitimate interest in showing that messages were handled as the user chose (1)(f) |
| Establishing, exercising or defending legal claims | legitimate interest (1)(f) |
| Complying with obligations towards authorities | legal obligation (1)(c) |
Where processing is based on legitimate interest, we have assessed that our interest is not overridden by your rights. You can request more information about this assessment.
4.3 When a phone forwards calls to us without service
If a phone forwards calls to a Service number although it has no Service (for example because the subscription has ended, the account is closed, or the phone was never added to an account or confirmed), the forwarded calls are not answered and callers hear a busy tone. The phone's holder may then not know that their calls do not reach them.
So we record the phone's number, the Service number its calls are forwarded to, the account and phone the number last belonged to (when we know them), how many calls were turned away each day, and our staff's notes on contacting the holder. We do not record callers' numbers here. Our staff may tell the phone's holder by SMS or email how to remove the forwarding. That message is a service notice, not marketing. The data comes from the telephone network (the forwarding phone's number) and from the Service.
The legal basis is legitimate interest (Article 6(1)(f)): the phone's holder has an interest in their calls reaching them, and we have an interest in not receiving calls we cannot serve. The data is erased 90 days after the last call turned away, or with the account (section 7).
5. Callers
5.1 Data we process
| Category | Examples |
|---|---|
| Call details | the caller's phone number (if it is transmitted), the number and line called, the time and duration of the call, the call status (for example message left or missed call) |
| Message | the audio recording; a spoken message, a written message (up to 2,000 characters) or a callback request (as soon as possible, or a day and a part of the day, and a note of up to 200 characters) left through the message link, and the name the caller may give |
| AI-generated data | transcript, summary, classification (for example urgency or likely marketing call) and details extracted from the message, such as name, company and callback number |
| Delivery data | the channels the summary was delivered to and delivery status |
| Message link | details of the text message and link sent to the caller (when it was sent, opened and used, or why it was not sent), a hash of the link's code, 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 customer's message links (a keyed hash of the account and the number; the number itself is not kept) |
We receive the data from the caller (the message) and from the telephone network (call details). If the caller has blocked their number from being displayed, we do not receive it.
5.2 Purposes and legal bases
Personal plan (Viestivastaaja Oy as controller). We process the caller's data so that the caller's message reaches the person they called. The legal basis is legitimate interest (Article 6(1)(f)): the caller has an interest in their message reaching the recipient, and the subscriber has an interest in receiving messages left for them. The caller initiates the processing by leaving a message after the greeting has told them about the recording and the use of AI. The caller can always hang up before the tone. We process only the data needed to pass the message on, keep it for a limited time and do not use it for other purposes such as marketing. A notification of a missed call where no message was left is based on the same legitimate interest: it corresponds to an ordinary missed-call notification on a phone. If the subscriber has turned on the message link (section 5.7), the text message to a caller who left no message is based on the same legitimate interest: the caller set out to reach the subscriber, and the subscriber has an interest in receiving their message. The caller gets one text message, whose default wording does not say whom they called. The number of texts is limited, and they are not used for marketing. The caller can refuse the texts on the link's page. We also process call details to protect the Service against misuse and nuisance calls (legitimate interest). If one number calls the same subscriber more than five times in the same hour, its further calls are turned away as busy. The calls are counted for an hour under a keyed hash of the number and the account, from which the number cannot be recovered.
Business plans (customer as controller). We process the data on the customer's behalf and in accordance with its instructions. The customer determines the legal basis for the processing and describes it in its own privacy notice.
5.3 Special categories of personal data
We do not ask callers for sensitive data such as health information. However, a caller may choose to mention, for example, their state of health in a message. Such data is processed only to pass the message on to the recipient and is not used for any other purpose. A business customer in a sector where such data is to be expected (for example healthcare) is responsible as controller for the lawfulness of the processing and for setting appropriate retention periods.
5.4 How a caller can request erasure of their message
Email tietosuoja@viestivastaaja.fi and tell us
- the number you called from;
- the number you called; and
- the approximate time of the call.
We may ask you to confirm that the number is under your control, for example with a code sent by SMS, so that we do not delete or disclose anyone else's data. If you called a Personal plan subscriber, we handle the request ourselves. If you called a business customer, we forward the request to the customer as controller without delay and assist it in handling the request.
5.5 Copies delivered to the recipient
Once a summary has been delivered to the channel the recipient chose (for example SMS or email), a copy is held in the recipient's own service. We delete the data from our own systems but cannot delete copies that have already been delivered. If needed, please also contact the person or company you called.
WhatsApp and Telegram only ever receive a notice of a new call: the time of the call and a link that opens the call in Viestivastaaja after sign-in. They do not receive the caller's number or name, the summary, the transcript, or the urgency or classification, so no personal data about the caller is transferred to Meta or Telegram. The recipient can choose the same notice with only a link for other channels too, except webhooks.
5.6 Who in an account sees a message
When an account has several users, a message is seen only by those it belongs to. That is decided when the call arrives:
- A user's own phone. The message is seen by the phone's owner and by whoever the owner has shared the phone's messages with: the whole organisation, chosen teams or named people, either always or by the owner's own working hours and away periods. Only the phone's owner can share its messages, and only when signed in to the app, after being told what sharing means. Sharing covers only messages that arrive after it. When the owner withdraws it, messages that arrive afterwards are no longer shared, but messages already shared stay visible to those they were shared with. A message shared with a team is seen by those who were in the team when it arrived.
- A company's shared number. The message is seen by the teams, or the whole organisation, that the customer has chosen for the number. Someone added to the team later also sees the number's earlier messages.
- A company's shared phone (for example a support phone whose calls are forwarded to the Service). Its messages are seen like a shared number's, but only once the phone itself has confirmed the sharing: we text or call the phone and say who its messages would be shown to, and whoever holds the phone confirms on the confirmation page with the code or by pressing 1 on the call, or refuses. An administrator can't make another user's own phone shared; the user can do it themselves. A number that takes neither texts nor calls (a switchboard, for example) can be verified by our staff from evidence the customer gives. We tell the phone who its messages are shown to about every 90 days and whenever that changes. Whoever holds it can object through the link in the message, and the Service then stops answering calls forwarded from the phone until the phone confirms again. A confirmation is valid for a year. If it isn't renewed, or the forwarding stops working, then until the phone confirms again new messages are seen only by those its messages were shown to while it was confirmed: the account's owners and administrators among them or, if there are none, all of them, as they were when the confirmation lapsed. We also tell the phone that its confirmation lapsed.
- A call whose line cannot be told (for example when the Service cannot tell whose phone forwarded it): the message is seen by the account's owners and administrators.
A user's role, such as owner or administrator, gives no right to see other people's messages. The same limits apply to delivering summaries and notifications, the "Try a person first" step, search, statistics and data exports, and an API key sees only the messages of the user who created it. Changes to sharing are logged, and the phone's owner sees them in the line's sharing history. A shared phone's confirmations, notices and objections are shown to the account's owners and administrators in the phone's sharing history. Our staff's access is described in section 12.
5.7 The message link
A customer can turn on the message link. If a caller hangs up during the greeting or at the tone, or leaves a recording that the AI judges to hold no message, we send them one text message at once, with a link. On the link's page the caller can record a message in the browser, write one or ask for a call back, and may give their name. The page offers a call back only to the number the text was sent to; if the caller's spoken or written message gives another number, the summary shows that number.
- Who gets it. The text goes only to mobile numbers in Finland (including Åland), and not to callers who withheld their number, the Service's own numbers, the phone that forwarded the call or the phones of the account's users. Nor is it sent when the AI judges the caller to be an answering machine, an automated call or a sales call.
- The text. It is sent under Viestivastaaja's sender name and cannot be replied to. The default text does not say whom the person called. The customer may write its own text, which may not contain links, email addresses or phone numbers and is reviewed before use (section 10).
- Limits. A caller has at most one live link from the same customer at a time, and each of the customer's call flows has a daily limit. Limits and refusals apply per customer, and a caller's data in one customer's account is never used for another customer's message links.
- The link. The link works for 72 hours and only once, without signing in. Its code is only in the text message, and we keep only a hash of it. About the customer, the page shows only its account's name and on which of the next seven days it is closed; it also shows the time of the call, until when the link works and, partly masked, the number a call back would go to.
- The message. A message left through the link is added to the same call and handled like other messages: the AI summarises spoken and written messages, a callback request on its own does not go through the AI, and the message is delivered to those who see the call (section 5.6). A spoken message waits in temporary storage for at most a day before it is processed.
- Refusing. With the page's I don't want texts like this button, the caller can refuse message links from that customer, also after using the link and for 30 days after it has expired. The refusal covers only that customer.
6. Website visitors and enquiries
6.1 Cookieless analytics
We measure use of our website with anonymous analytics that does not use cookies or any other identifiers stored on your device. IP addresses are not stored. To count unique visitors within a single day, a hash formed with a salt that changes daily is used; it cannot be linked across days. The legal basis is our legitimate interest in understanding and developing the use of the website (Article 6(1)(f)).
6.2 Technical data and security
Our servers process your IP address and the technical data your browser sends in order to deliver the pages and to protect the Service, for example to fend off denial-of-service attacks and to limit sign-in attempts. The legal basis is legitimate interest (Article 6(1)(f)). Our servers' request logs contain IP addresses, and the logs are kept for 30 days (section 7).
6.3 Sales and business contacts
When you contact sales (myynti@viestivastaaja.fi or the website form), we process the data you provide, such as your name, email address, phone number, company and message, and the content of our correspondence. The purpose is to respond to your enquiry and to conduct sales. The legal basis is legitimate interest (Article 6(1)(f)) or steps taken at your request prior to entering into a contract (Article 6(1)(b)).
We also market the Service to businesses we choose ourselves, and talk with possible partners and investors. We start from company data, which we get mostly from the open data of the Finnish Patent and Registration Office (PRH, YTJ). We get the details of contact persons at these businesses from public sources, such as company websites and the trade register, from events and business cards, and from people who contact us other than through the form. We process only work-related data: name, role, company, work email address and phone number, where we got the details, and notes on our contacts (for example when we called and what was agreed). If you are a sole trader, we also process your trade name and business ID. The legal basis is our legitimate interest in marketing the Service to businesses (Article 6(1)(f)). We do not buy marketing lists and do not pass the data on. We tell you about this in our first message at the latest.
Our sales staff are helped by an AI assistant (Claude, by Anthropic), which looks up information about businesses and keeps our sales records up to date. It processes the sales data described here on our behalf, as our processor. It has no access to messages left in the Service or to our customers' data, and Anthropic does not use the data to train its models (sections 8 and 9). It does not see what you say in a voicemail or text message to our sales number, nor hear call recordings.
Our sales staff may connect their own work email and calendar (Google Workspace) to our sales records. Only emails with one of our business contacts' addresses as the sender or a recipient are then recorded, and meetings the contact attends that our salesperson organised or accepted. From an email we keep the subject, who it was between, the time, the text without earlier quoted messages (at most 5,000 characters) and the names of attachments, but not the attachments. From a meeting we keep its title, time, length and attendees. If an email we record has a new address on the domain of the same business, whose contact we already have, the address and name are suggested to our salesperson as a contact. Emails we do not record suggest nobody. Nobody is added unless the salesperson decides to, and the suggestion is deleted after 90 days. Emails our sales staff send from the console always carry a link with which you can tell us not to contact you.
We call and text businesses from our sales number. Calls, text messages and voicemails left on the number go through Twilio in Ireland, and our sales records note the number, the time, how the call went and the text of the messages. We record a call only if we tell you during the call, and you can ask us not to. Google's AI in the EU summarises voicemails and turns our spoken notes into text. We delete a recording, a voicemail and a kept audio note 90 days after it was made. A message from a number we do not know is deleted after 30 days unless we connect it to a contact person. If we call and you do not answer, we may send you one text message saying who called and why, once. If you are a sole trader, we text you only in reply to your own message. When you call our sales number and the call is put through to our salesperson's mobile, the mobile shows the sales number as the caller, and the salesperson's device gets a notification at the same time with only your name and company. The notification travels end-to-end encrypted through the device's push service (section 9) and is not stored.
We keep a contact person's data for two years (730 days) from the last contact or update, after which it is deleted automatically together with our notes. We keep a business's data for three years from when we were last in touch with it or updated its details. If you become our customer, the data about the customer relationship is processed as described in section 4.
You can at any time tell us not to contact you and object to the processing of your data for marketing (Article 21): reply to our message, use the link in our sales emails or write to tietosuoja@viestivastaaja.fi. We will then stop contacting you and delete your data, including your address and what you wrote in emails and meetings recorded for our other contacts. So that we can respect your objection, we keep only a one-way hashed form of your email address and phone number, from which the address or number cannot be recovered.
6.4 Customer support
When you leave a message on our customer support number or have an SMS conversation with us, we process the contact in the same way as other messages (section 5), and we keep customer support SMS messages for two years from when they were sent (section 7).
7. Retention periods
| Data | Retention period |
|---|---|
| Message recordings | Personal plan 90 days. Business plans 180–730 days depending on the plan, Enterprise plan 3,650 days or as agreed. The customer may set a shorter period or delete a recording at any time. |
| Transcripts, summaries and extracted details, and the caller's phone number and the notes users have written on the call | Personal plan 365 days. Business plans 730–1,825 days depending on the plan, Enterprise plan 3,650 days or as agreed. The customer may set a shorter period or delete the data at any time. The caller's number and the notes are erased together with the transcript and summary. |
| Other call details and delivery data, without the caller's details (for example time, duration, status, costs and which of the account's users may see the call) | until the account is deleted, to count calls and costs |
| The caller's number and call details when a person answered in the "Try a person first" step (nothing is recorded) | as for the plan's transcripts, after which the caller's details are erased as for other calls |
| The caller's number and call details when a call is rejected or cannot be routed (for example an unknown number, a blocked caller, an inactive account or repeated calls from one number) | 90 days, after which the caller's details are erased as for other calls |
| A message already left (the recording) that cannot be routed to anyone | 90 days. Only our customer service can listen to it, with a stated reason, to find out whom it was for, and every listen is logged. |
| A phone that forwards calls to the Service without service (its number, the Service number, the account and phone it belonged to, how many calls were turned away and our staff's notes; no callers' numbers) | 90 days after the last call turned away. Erased with the account. |
| The count of calls from one number to the same subscriber (a keyed hash of the number and the account) | one hour |
| A message left through the message link (a spoken message, a written message, a callback request and the name the caller gave) | like other messages: a spoken message like recordings, and a written message, a callback request and the name like transcripts and summaries |
| A spoken message sent through the message link, before it is processed | in temporary storage for at most a day; deleted once the message has been processed |
| The message link's details (a hash of the link's code, times and status; no phone number) | 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 shown on the call and kept like the call's other details. |
| A caller's live message link from a customer (a one-way hashed form of the account and the number), so that only one is sent at a time | until the link's 72 hours end |
| A caller's refusal of the customer's message links (a one-way hashed form of the account and the number) | until the customer's account is deleted |
| Copies held by the telephony provider (Twilio) | Recordings are deleted as soon as our own copy is stored; a recording that arrives only after the caller has already left a message through the message link is deleted after 7 days, in which our staff can look into it. Call logs (who called and when) are deleted 24 hours after the call, and SMS messages, including their text, 2 hours after they were sent or received. Twilio may keep deleted data in its backups for up to 30 days. |
| Greetings and settings | until the customer deletes them or the account is deleted |
| Teams, a line's sharing rules, and the working hours and away periods set for sharing | until the customer or the line's owner deletes them, or the line or the account is deleted. A withdrawn sharing rule stays on the line for 7 days, and the record of it stays in the sharing history. The line's last five former owners stay on the line, so that a call processed late belongs to whoever had the phone when it arrived. |
| A line's sharing history (sharing given and withdrawn, schedule changes, hand-overs of the line, team changes that affected the line's sharing, and a shared phone's confirmations, notices, objections and lapses) | three years, to be able to show who could see which message. Deleted with the account. |
| A shared phone's confirmation request and its codes (as hashes only) | A code is valid for 15 minutes. The request is deleted 7 days after it was started (37 days for a request to our staff), and how it ended stays in the sharing history. |
| The audio played in a confirmation or notice call, and the call's details | The audio is deleted when the call ends, after 30 minutes at the latest, and the call's details after a day at the latest. |
| Notices sent to a shared phone and their objection links | 180 days from the notice. An objection stays in the sharing history. |
| A shared phone's confirmation (who confirmed it, how and when) and the evidence our staff recorded | as long as the phone is shared or the line exists, after which the record stays in the sharing history |
| Account data | for as long as the account exists. Once deletion of the account has been requested, the data is deleted 14 days after the request, and backups roll over within 30 days. 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 account is scheduled for deletion. Its owners are told 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 accounts our staff have suspended; we decide on deleting those separately. |
| A user's data (phone number, email address, name and consents) when the user belongs to no account | one year from when the user stopped belonging to an account, for example when they signed in but never created an account, or left their last account. The data of a user who belongs to an account is deleted with the account, unless they belong to other accounts. |
| One-time sign-in codes | only as a hash, for 10 minutes |
| Sessions | up to 90 days |
| An unfinished sign-in (the first step done, the second awaited) | 10 minutes |
| Two-step sign-in data (confirmed contact details and hashes of recovery codes) and a linked Google account | like the user's data. The link to the Google account is deleted when the user unlinks it. |
| Billing vouchers | six years from the end of the year in which the financial period ended (Finnish Accounting Act) |
| Identifiers for the first-month price | three years from the first payment, also after the account is deleted, because their only purpose is to recognise a returning customer |
| An order page's details (its identifiers and a request to start the Service at once) | 30 days from when the order page was opened. The first-month price is held for the order page for 45 minutes, a little longer than it takes payments (half an hour). |
| A request to start the Service at once, and a withdrawal | the request with the subscription's data for as long as the account exists. A withdrawal, its refund and the request the Service started under, as billing vouchers: six years from the end of the year you withdrew, also after the account is deleted. |
| Books of account | ten years from the end of the financial period (Finnish Accounting Act) |
| Usage data on which invoices are based | as for billing vouchers |
| Log data (changes made in the account and staff access to data) | two years |
| Server request and application logs, including IP addresses | 30 days |
| Customer support SMS messages | two years from when they were sent. If the number has replied STOP, only the number and the opt-out are kept, so that the opt-out can be honoured. |
| Sales enquiries and business contacts, with our notes on them | two years (730 days) from the last contact or update, or until you object. Businesses' data three years from when we were last in touch with the business or updated its details. If you object: a one-way hashed form of your email address and phone number, for as long as we market to businesses, so that the objection can be respected. |
| Emails and meetings recorded from our sales staff's email and calendars, and suggested contacts | The emails and meetings with the contact's data. A suggested contact (address and name) 90 days from when the address was last seen; of a dismissed suggestion, only a one-way hashed form is kept for a year, so that it isn't suggested again. |
| Recordings of our sales calls, voicemails left on our sales number and our audio notes | 90 days from when they were made; the notes written from them are kept with the contact person's data. A voicemail or text message from a number we do not know: 30 days, unless we connect it to a contact person. |
| Analytics events | 13 months; anonymous aggregate statistics indefinitely |
We delete or anonymise data automatically when the retention period ends. We may keep data for longer if required by law or if the data is needed for a pending legal claim.
8. Recipients and sub-processors
- The recipient of the message. A caller's message and its summary are delivered to the person or company the caller called, and to the delivery channels they have chosen (section 5.5).
- Sub-processors. We use service providers that process data on our behalf under contracts: Google Cloud (servers, database, files, AI models and speech synthesis in the EU), Twilio (calls, recordings and SMS in Ireland), Stripe (payments) and Scaleway (email). Meta (WhatsApp) is a sub-processor only if the customer turns on WhatsApp notifications. WhatsApp receives only a notice of a new call and a link, and Meta processes only the recipient's WhatsApp number, the time of the notice, the language and the link. The current list is on the sub-processors page.
- Channels chosen by the customer. If the customer chooses, for example, Slack, Microsoft Teams or its own webhook address as a delivery channel, the summary is delivered to that service at the customer's choice. For Slack and Teams the customer can also choose only a notice and a link; webhooks always receive the full content. Telegram receives only a notice of a new call and a link, and the chat's id. Telegram is an independent controller for its own service.
- App notifications. If a user turns on app notifications on a device, the notification (the caller's name or number and the first sentence of the summary or, if the user has chosen so, only the time and a link) is passed through the push service of the device's browser maker (Apple, Google, Mozilla or Microsoft). The notification is end-to-end encrypted for the device, so the push service cannot read it; it sees only the device's notification address, the time and the size of the encrypted message.
- Google sign-in (the user's choice). If a user links their Google account and signs in with it, Google learns of the sign-in to Viestivastaaja, and we receive the account's id and email address from Google. Google is the controller of the user's own Google account. No data about the account, calls or other users is given to Google.
- Our sales assistant. Anthropic (Claude) processes the sales data described in section 6.3 on our behalf, as our processor. It has no access to callers' messages or to our customers' data.
- Sales email and calendar. Our sales staff's work email and calendar are in Google Workspace, which Google Ireland provides to us as our processor. Only the data described in section 6.3 is recorded from there in our sales records.
- The trade register. Before a business's first-month price applies, we check that its business ID belongs to an active company in the open data of the Finnish Patent and Registration Office (PRH, YTJ). Only the business ID is sent.
- Authorities. We disclose data to authorities only where required by law.
- Advisers and corporate transactions. Auditors and legal advisers bound by confidentiality, and a potential buyer of the business in a corporate transaction.
We do not sell personal data.
9. Transfers outside the European Economic Area
Data is stored in the EU: primarily in Finland (Google Cloud europe-north1) and, for task queues, in Belgium (europe-west1). Data may be transferred outside the EEA in the following situations:
| Service | Transfer | Safeguards |
|---|---|---|
| Twilio (calls, recordings, SMS) | Calls, recordings and SMS are processed and stored in Twilio's Ireland region. Our contracting party is Twilio Ireland Limited. Twilio Inc. may process data about the Twilio account, billing and usage in the United States. We delete data at Twilio as described in section 7. | Twilio's Binding Corporate Rules (approved in 2018), the EU–US Data Privacy Framework (EU–US DPF) and standard contractual clauses |
| Stripe (payments) | Stripe, Inc., United States | standard contractual clauses and EU–US DPF |
| Google Cloud | Data is stored in the EU. Possible access by Google from outside the EU, for example for support. | standard contractual clauses and EU–US DPF |
| WhatsApp (only if the customer turns it on) | WhatsApp runs on Meta's WhatsApp Business Platform (Cloud API). It receives only a notice of a new call: the time and a link. No data about the caller is transferred. Meta processes the recipient's WhatsApp number, the time of the notice, the language and the link. Meta's local storage in Germany covers only data at rest, so data may be processed outside the EU, including by Meta Platforms Inc. and WhatsApp LLC in the United States. | Meta Platforms Ireland Ltd acts as our processor under Meta's WhatsApp Business data processing terms. Transfers to the United States rely on the EU–US DPF, with standard contractual clauses as a fallback (WhatsApp Business Data Transfer Addendum). |
| App notifications (the user's choice) | The push service of Apple, Google, Mozilla or Microsoft, depending on the device's browser, including in the United States. The content is end-to-end encrypted, so the service sees only the device's notification address, the time and the size. Notifications to our salespeople's devices when a contact calls the sales number (section 6.3) travel the same way. | End-to-end encryption (Web Push, RFC 8291), and the providers' standard contractual clauses and EU–US DPF. Notifications can be turned off at any time. |
| Google sign-in (the user's choice) | Google Ireland provides Google accounts to users in the EEA; Google LLC may process data about the sign-in in the United States. We send Google only the one-time code it issued and receive the account's id and email address. | EU–US DPF. Google sign-in is optional: codes to the phone and email always work. |
| Telegram (the user's choice) | Telegram receives only a notice of a new call (the time and a link) and the chat's id. No callers' details or messages are sent. Telegram is run from outside the EU: the companies that act as its controllers are in the British Virgin Islands and the United Arab Emirates, and the data of EEA users is stored in the Netherlands. There is no European Commission adequacy decision for these countries, so the data may be less protected than in the EU. Telegram is an independent controller for its own service. | The user's explicit consent (Article 49(1)(a) GDPR). Consent is asked for in the app before the channel is added, with the information and risks described here, and the time of consent is recorded. Consent can be withdrawn by removing the channel. Instead of Telegram, you can choose email or app notifications, for example. |
| Anthropic (only the sales data in section 6.3) | Anthropic processes the data in the United States. | standard contractual clauses (Anthropic's data processing addendum) |
| Google Workspace (our sales staff's email and calendar, section 6.3) | Our contracting party is Google Ireland Limited. Google LLC may process data in the United States. | standard contractual clauses and the EU–US DPF (Google's Cloud Data Processing Addendum) |
Standard contractual clauses means the clauses adopted by European Commission Decision (EU) 2021/914. You can obtain more information about the safeguards from tietosuoja@viestivastaaja.fi.
10. AI and automated decision-making
Messages are transcribed and summarised with Google's Gemini AI models, which are used within the EU, and messages spoken or written through the message link are summarised in the same way. Under its agreement, Google does not use the data to train its models. Synthesised greetings are created at the EU endpoint of Google Cloud Text-to-Speech. A customer's own text for the message link is reviewed before use, with a Gemini model in the EU and/or by our staff: the text may not, for example, market anything, pretend to be someone else, pressure the reader or ask for sensitive details.
We use message recordings, transcripts and summaries only to provide the Service to the subscriber. We do not use them to train AI models or for any other purpose.
AI-generated content is labelled: in the app the summary is headed "AI summary", and emails state that the summary was made by AI. In webhook messages, the fields produced by AI are marked in a machine-readable way (Article 50(2) of the EU Artificial Intelligence Act).
Summaries and classifications are aids for the recipient. They are not decisions based solely on automated processing producing legal effects or similarly significant effects within the meaning of Article 22 of the GDPR. The recipient decides how to act on the message, and the original recording is available to them within the retention period. AI can make mistakes, so a summary should not be the sole basis for important decisions.
11. Your rights
Under the GDPR you have the right to
- access your data (Article 15);
- have inaccurate data rectified (Article 16);
- have your data erased (Article 17);
- have processing restricted (Article 18);
- receive your data and transfer it to another system where the processing is based on a contract or consent (Article 20);
- object to processing based on legitimate interest on grounds relating to your particular situation, and object to direct marketing at any time (Article 21); and
- withdraw your consent at any time without affecting the lawfulness of earlier processing.
Customers can also download and delete their data in the app. Otherwise, send your request to tietosuoja@viestivastaaja.fi. Requests from callers are described in section 5.4. We reply within one month. This may be extended by up to two months if the request is complex. We may ask for further information to verify your identity. Requests are free of charge unless they are manifestly unfounded or excessive.
If your data is stored in a business customer's account, the customer is the controller. In that case we forward your request to the customer and assist it.
12. Security
We protect data with measures including the following:
- data is stored in the EU in Google Cloud (Finland) and encrypted in transit (TLS 1.2 or later) and at rest (AES-256);
- webhook addresses and third-party tokens are additionally encrypted at application level (AES-256-GCM);
- the database can only be accessed from our servers, never directly from browsers or apps;
- within an account, each message is shown only to the users it belongs to (section 5.6);
- staff access requires Google sign-in and role-based permissions, and access to message content requires a recorded reason and is written to a log kept for two years;
- recordings are deleted from the telephony provider immediately after transfer, call logs after a day and SMS messages after two hours;
- logs never contain transcripts, summaries, full phone numbers or secret keys and credentials, and server logs are deleted after 30 days;
- data is backed up daily, and the database can be restored to a point in time;
- sign-in uses one-time codes, and sign-in attempts are rate-limited;
- owners and admins of business accounts sign in in two steps: a code to their phone and a code to their email or their Google account. Other users can choose the same. Users are told by email and SMS about changes to their sign-in's security.
A more detailed description is in Annex 2 of the Data Processing Agreement.
13. Cookies
We use only cookies and browser local storage that are strictly necessary for the Service to work, for example to renew the subscription for app notifications. More information is in the Cookie Notice.
14. Right to lodge a complaint with a supervisory authority
If you consider that the processing of your personal data infringes data protection law, you have the right to lodge a complaint with a supervisory authority. In Finland, the supervisory authority is the Office of the Data Protection Ombudsman (tietosuoja.fi). You may also lodge a complaint with the supervisory authority of the member state where you live or work. We hope you will contact us first so that we can look into the matter.
15. Is providing data mandatory?
The customer's contact and billing details are required to conclude the agreement; without them we cannot provide the Service. A caller is under no obligation to leave a message: they can hang up before the tone. If the customer has turned on the message link, the caller may get one text message with a link for leaving a message, but using the link is voluntary (section 5.7). Using the website does not require providing personal data.
16. Changes
We update this policy when the Service or the law changes. The update date and version are shown at the top of the policy. We notify customers of material changes by email or in the app at least 30 days in advance.