Privacy and security
Calls contain personal data of your customers and employees. This page describes how BK Replay handles that, so you can include it in your record of processing activities, DPIA or works council consultation.
Where the data is stored
- Recordings, transcripts and summaries are stored in your own Azure subscription: your own storage account and your own Azure SQL database, in a European region you choose. See How BK Replay is set up.
- The speech recognition (Azure AI Speech) and the AI for summaries (Azure OpenAI) belong to your organisation as well. Microsoft does not use this data to train models.
- BK Replay reaches those resources without keys or passwords, with only the roles you assign yourself, and you can revoke that access at any time.
- BK IT's operational logs contain only technical data (IDs, times, error messages), never phone numbers, names or call text.
Who can access it
- You control access to the portal yourself, with roles in your own Entra ID (see Roles and access). Someone only sees calls they are entitled to; this is checked on the server for every request.
- Audio is never shared as a separate file or open link: the portal plays a call through a short-lived, personal key.
- Every time someone views, listens to, exports or deletes a call, it is recorded in the audit log.
- BK IT staff have no access to your organisation's calls by default.
How long
You set the retention periods yourself, separately for audio and for transcripts and summaries. After that, the data is deleted automatically. A Manager or Administrator can also delete a call earlier, for example at the request of a data subject.
Call data for Telephony (who called when, without a recording) has its own retention period of 13 months by default, so you can compare a year.
Data subject rights
- Access: export the call (Exporteren role) and use the audit log to show who viewed it.
- Erasure: delete the call permanently; the audit log only keeps that it was deleted, by whom and why.
- No more recording: put the number, contact or company on the Never record list.
What your organisation arranges itself
- Informing employees and, where needed, callers that calls are recorded (for example in a phone menu or on your website).
- Works council consent where required. This certainly applies to quality questions, promises, statistics per employee and recording meetings.
- A data processing agreement with BK IT. Telephony also uses call data of colleagues who are not recorded; check that your agreement covers this before BK IT switches it on.
