Skip to main content
privacy

Is tl;dv Safe for a Meeting Recording You Need to Keep?

Vemoir Team
Vemoir Team Mac meeting records by Aurum Avis Labs · Oberägeri, Switzerland
10 min read

Hero photo by hrsahatchiev on Unsplash

Is tl;dv safe is a storage and access question, not a legal verdict. tl;dv, from Tldx Solutions GmbH in Aachen, records and transcribes meetings and keeps that material so a team can share it. Their privacy policy, current version published 9 September 2026, says where that material goes, who may see it, and what they state they will not do with it. A badge on the marketing page is their wording. It does not decide whether your meeting may be recorded.

If the recording should never leave the Mac, tl;dv is the wrong shape. This page is what their own documents say, checked in September 2026, and the case for staying local.

Is tl;dv safe as four practical questions

People ask “is tl;dv safe” when they want four practical answers.

  • BotVisible

    tl;dv joins calls as a participant when you use the bot path.

  • StorageCloud

    Recordings sit in tl;dv’s service until you delete them or retention applies.

  • TrainingPolicy says no

    Section 9 refuses model training on Customer Content.

  • Local MacAlternative

    No bot when you record system audio on the device.

Will the audio be used to train a general model? Who else can open the meeting? How long does a free account keep the file? Does a sentence on their site (“GDPR-compliant”, “SOC 2 compliant”, hosted in the EU) replace your own decision to record?

The privacy policy applies to their online meeting recording and transcription tool, the site, and the app. It says user content is your responsibility: you have to make sure what you upload or make available complies with their terms and does not infringe other people’s privacy. That sentence matters more than the badge. tl;dv does not grant consent from the other participants. You do.

Their homepage and security pages describe recording and transcription for Google Meet, Zoom, and Microsoft Teams, calendar-based recording, CRM logs, and sharing into collaboration tools. That is a team product. A recording that exists so colleagues can replay it is not the same as a tape that stays on one laptop. If sharing is the point, the cloud is the feature. If sharing is the problem, read the next sections before you connect a calendar.

Before you connect a calendar

  • Read section 9 on AI training and section 8 on where AI summaries may run
  • Check workspace sharing defaults so a client call does not land in an open library by mistake
  • Confirm retention for your plan (three months on free, per the policy table, as of September 2026)
  • Tell participants you record; tl;dv’s policy also describes collecting non-client participant emails for consent workflows

If any line fails your internal rule, do not rely on a marketing claim to override it. Use a local capture path instead, or pick a vendor whose storage model matches the contract.

Training, which their policy refuses

Section 9 of the privacy policy, “AI Model Training,” says Tldx Solutions GmbH does not use Customer Content, including meeting recordings, transcripts, notes, files, or other data processed through the services, to train, fine-tune, or improve foundation models or other generative models for itself or any third party. Where they use third-party AI providers, they say Customer Content is processed only to provide the requested feature and is not used by them or those providers to train general-purpose models.

tl;dv fits when

  • Shared clips and a team library matter more than local-only audio
  • CRM logging and replay for the whole team are the job

Skip tl;dv when

  • Client contracts forbid a cloud meeting archive
  • A visible bot in the participant list is not allowed

The subprocessors list names Anthropic and Google Vertex as artificial intelligence providers, and AssemblyAI and ElevenLabs as transcription providers, among others (hosting, support, analytics, CRM). Transcription in this product is not described as something that stays on your computer.

On their security commitment page they describe extra limits for Anthropic (anonymized metadata, chunked meetings, randomized order), as of September 2026. That is still not a promise that no text leaves your machine. Limited transcript portions are sent so a summary can be written. AI features may run in the EU or the US depending on the hosting location you select in account preferences. Their marketing also says GDPR-compliant, SOC 2, and EU hosting. Those are their claims, not a reason you may record someone who has not been told.

Where the recording is stored

The policy says the software is hosted in Google Cloud Platform and Amazon Web Services facilities, and that the database sits in a VPC. The subcontractor table lists Google Cloud, Hetzner, and Wasabi for hosting and storage. Section 8 says personal data is primarily processed and stored in the EEA, with Google Cloud, Wasabi, and Hetzner data centers including locations in Germany, and Hetzner also in Finland. It then makes the exception already noted: part of the AI service can run outside that picture, based on the hosting location you choose.

Application security text on their commitment page says data is stored encrypted using AES-256. Transport is HTTPS, and they say plain HTTP is redirected.

None of that is the same as “the file never left the laptop.” A meeting tl;dv records is built to be stored, indexed, and shared. Their product copy talks about sharing transcripts and notes into team tools, CRM, and storage apps. Turn those integrations off if you do not want the note to travel, and still assume the recording exists in their service until you delete it or the retention rule deletes it.

Who else can open the meeting

Section 6 of the policy says Tldx Solutions GmbH does not access your recordings and transcriptions at any time, unless you personally share access with individual employees for technical assistance. Even then, only the recordings for which access was granted to that support person are accessible.

That is different from teammates inside your workspace. Sharing and collaboration are listed as purposes for storing video, audio, and written transcriptions. If your workspace is wide, assume anyone with the right seat can replay a meeting you stored there unless you use tl;dv’s sharing controls on purpose.

The retention table also lists support team and engineers as recipients for recording data. That is normal for a hosted product. It is another reason sensitive calls need an explicit internal rule, not only a vendor badge.

For people on the call who are not tl;dv customers, the policy describes collecting their email addresses to associate meetings and to collect consent from non-client participants. That row is about their product workflow, as of September 2026. It does not replace your duty to tell people you record.

How long a free recording lasts

The retention table in the privacy policy is specific. For video and audio recordings and written transcriptions, a free user is listed at 3 months. A paying user is listed as until account deletion. Recipients named in that row include the support team and engineers. Purposes named include the main service, sharing, and collaboration.

So “is tl;dv safe” for a free account includes a calendar: the recording is not described as gone the day the meeting ends. It is described as kept for three months, then the table stops. If you need a shorter life, delete it yourself inside the product and confirm what their current help says about backups. Do not assume a marketing line about encryption deletes the file early.

Paying retention follows the account. Closing the account is the event their table ties to deletion for those files. Export anything you are allowed to keep before you do that, if the notes matter and the recording does not.

When a local file is the clearer choice

Choose tl;dv when the team needs the shared library: several people replaying the same customer call, notes pushed toward a CRM, a calendar that records the meetings you already scheduled. That is the product they describe. A Mac that never uploads will not do that job.

Choose a local path when the audio should not be in a meeting library at all.

A file you already downloaded can go through transcribe recording if it is 15 minutes or less: three runs a week, nothing uploaded, no speaker labels, a model in the browser. Swiss German usually comes out as Standard German there.

A live call on a Mac can be captured from the menu bar with the microphone and system audio, no extra participant, transcription on the machine. Summaries stay on the machine unless you turn on your own text key. Audio does not go with that key. Vemoir is that app, on Apple silicon and macOS Sonoma 14.2 or later, from the Mac App Store. It does not join Google Meet, Zoom, or Teams as a recorder in the participant list. It also does not give you tl;dv’s shared workspace, CRM logging, or coaching playbooks. If those are the requirement, stay with tl;dv and use their retention and sharing settings on purpose. For a feature-by-feature swap, see tl;dv alternative.

Deleting a local meeting removes the transcript, the generated record, attached actions and decisions, and the recording folder on that Mac. It does not delete a copy already sent to a cloud service. If a copy exists in tl;dv, delete it there too.

For how a different vendor, Otter, describes its own storage, see is Otter safe. The limits are not interchangeable.

Frequently asked questions

Does tl;dv train on my meetings?

Their privacy policy dated 9 September 2026 says Customer Content, including recordings and transcripts, is not used to train or fine-tune foundation or generative models for them or third parties. Hold them to that page, not to a summary.

Is the recording only in Europe?

Primarily, in their words: Google Cloud, Wasabi, and Hetzner in the EEA, with German and Finnish locations named. AI summaries can be processed in the EU or the US based on the hosting location you select. That exception is in the same policy.

How long does a free tl;dv recording stay?

The policy’s retention table says 3 months for a free user’s video, audio, and written transcriptions. Paying users are listed until account deletion.

Do they record the meeting for me automatically?

Their site describes calendar recording and recording on Meet, Zoom, and Teams. If that is connected, the meeting can be captured without you pressing a separate record button in the call. Read the controls in the account before you rely on silence.

Is “GDPR-compliant” on the homepage a certification of my meeting?

No. It is their claim about the service. You still decide whether these participants may be recorded, and you still tell them. A Swiss meeting does not become settled because a vendor uses the word compliant.

What if I need the text and not their library?

Use a file you already have in the browser tool, within 15 minutes, or keep the live capture on the Mac. Neither of those creates a tl;dv workspace.

Can I get a copy deleted?

The policy lists a right to erasure within the limits of GDPR article 17, and it lists retention. Use their process, and do not treat a sent email as proof the backups are already gone until they say so.

If the team is supposed to share the call, tl;dv is built for that, with the retention and subprocessors above. If the tape should stay on the machine, skip the calendar connection and start from transcribe recording or from capture on the Mac.

privacy tl;dv meetings
Vemoir Team

Written by

Vemoir Team

Mac meeting records by Aurum Avis Labs · Oberägeri, Switzerland

We build Vemoir, a Mac app for local-first meeting records: capture from the menu bar, transcribe on your Mac, and turn calls into minutes and action items.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, and the free in-browser tools limit (timestamps of successful runs in the current week, no content).

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.