Notice about the recording of this meeting
You were invited to a meeting in which a representative of an organisation uses Tenure, a product of HighKnow SRL. This notice gives you the information the GDPR requires when your words are recorded (Article 13). It is an announcement. It is not a request for your consent, and the recording does not rely on your consent.
Who is responsible
The organisation whose representative invited you is the controller. It decides why the meeting is recorded. HighKnow SRL, which makes Tenure, is its processor: it provides the software and handles the data on the organisation's instructions. The invitation or the person who invited you can tell you which organisation that is.
What is done, and why
- The meeting is recorded and transcribed as it happens.
- Decisions, commitments, requirements, open questions, concerns raised, and facts about the organisations and people involved, such as a person's role, are extracted from the transcript. Each is added to the organisation's knowledge base with a short quote, one or two sentences, from the transcript.
- Statements about a named person's working relationships or preferences are extracted only if the organisation has turned them on. They are off by default.
- Members of the organisation can read these statements and their quotes. When the meeting or a statement is marked private, only the member who owns it can. The statements are used to show short suggestions during meetings, including to the representative in this one, and to answer members' questions.
The purpose is a correct, retrievable record of what was said in commercial discussions, so that later dealings start from an accurate account. Tenure is not used to assess, rank or compare any person, or to infer anyone's feelings or intentions. It works from the words said, not from the sound of anyone's voice.
Legal basis
The basis is the organisation's legitimate interest in keeping a record of its own commercial dealings (Article 6(1)(f)). Your interests were weighed against it. The points that count in your favour are that you have no relationship with the organisation's software, and that you may not expect to be recorded on an ordinary business call. The points that count for the organisation are that the record concerns a negotiation you take part in, and that it is about professional speech. The measures relied on are this notice before and during the meeting, a short retention period, a route to object that is honoured by stopping and deleting, and no feature that looks people up by name.
The announcement at the start of the meeting is a transparency measure. It is not a request for consent.
What data
- What is said in the meeting, as written text, with a label for each audio channel.
- The meeting's title and time, from the calendar. The invited attendees' email addresses are read to recognise the organisation's own members. For anyone else, only the company part of the address, after the @, is kept.
- Speech can contain details about health, beliefs or other sensitive subjects without anyone intending it. Tenure does not look for them and does not create a record type for them.
- Tenure does not write the audio to storage, and it does not create voiceprints or identify people by their voice.
Who else receives it
Inside the organisation, the transcript is available only to the members who attended the meeting. One of them may share it with colleagues in the organisation, whom they name. Each share names its recipients, is logged, and can be withdrawn. The transcript is never shared with the organisation as a whole.
Outside the organisation, these service providers process the data for HighKnow SRL:
- Soniox, for real-time transcription, through its EU endpoint.
- Cloudflare, which runs the platform, passes requests to the AI models, and stores the data in the EU.
- Neon, which hosts the database in Frankfurt.
- Google Cloud (Vertex AI), in EU regions, for extraction, suggestions and answers.
The data is stored only in the EU, and processed in the EU, with two exceptions. Where network routing requires it, traffic can pass through Cloudflare servers outside the EU, which do not store it. Soniox may carry out limited processing outside the EU for security, support and legal compliance. Both are covered by the safeguards in Chapter V of the GDPR. What each provider keeps is set by HighKnow SRL's agreement with it.
How long it is kept
- The transcript is kept for 90 days by default. The organisation can set a longer period for its own account, up to 24 months, and has to record why.
- The first part of a meeting, recorded before the announcement was answered, is kept apart from the transcript and does not enter the knowledge base. It is kept as evidence of what was announced and answered, for 30 days, and then deleted.
- Statements in the knowledge base, each with its short quote, have no fixed end date. They stay after the transcript is deleted, until the organisation removes them or a request below requires it.
Your rights, and how to object
You can ask for access to your data, for correction, for deletion, to restrict its use, and you can object to it. You can also complain to your data protection authority. No decision about you is made automatically.
To object, say so during the meeting. The representative stops the recording at once, and can delete what was captured on the spot. If it is not deleted then, what was captured is kept apart from the transcript, never enters the knowledge base, and is deleted after 30 days.
After the meeting, send your objection or request to the organisation that invited you, usually through the person who invited you. An objection is not contested. Within 30 days, your words are removed from the transcript, and statements that rest only on what you said are removed from the knowledge base. A statement that other people also made keeps only their part.
If you cannot reach the organisation, write to privacy@highknow.ai. HighKnow SRL will tell you which organisation to ask, and will pass your request on to that organisation within 7 days. How HighKnow SRL handles your message is in its privacy policy.
Status of this text
This version replaces disclosure-2026-10b. Earlier versions stay published as they were, for the meetings that used them.