Jexity Meet
Security

What happens to your meetings, step by step

This page answers the questions data protection officers and IT ask before deployment. Every statement matches what the app does, with no certificates and no promises beyond that.

The data flow

Recording, processing and storage stay inside your machine. Everything outside the frame is a connection you or your IT switch on explicitly, or licence and update traffic without content.

Your machinemacOS or Windows, no bot in the meetingRecordingMicrophone, system audio, screenLocal processingTranscript, speakers, minutesLocal storageDatabase, media files, exportsCloud modelsonly when switched onDMS and actionsWebhook or folder, optionalLicence and update serveractivation data, never content
Solid: the local path. Dashed: optional connections that only exist when you switch them on, plus the licence and update traffic.
  1. Recording → Local processing
  2. Local processing → Local storage
  3. Local processing → Cloud models (optional, dashed)
  4. Local storage → DMS and actions (optional, dashed)
  5. Your machine → Licence and update server (optional, dashed)

Transcription and speaker separation never leave the device, not even with cloud models switched on. Cloud models only affect the language-model steps: minutes, visual evidence, chat, translation and name suggestions.

What is encrypted, and what is not

The statement is deliberately precise, because a data protection officer needs it precise.

  • Encrypted: transcripts, minutes, chat and other sensitive text in the local database, plus the working files of processing (raw transcript, speaker turns) and the licence proof. The key is managed by the operating system keychain (Keychain on macOS, DPAPI on Windows).
  • Encrypted: API keys for cloud models, also in the keychain.
  • Not encrypted: audio and video files, visual evidence (JPG) and exports. Protect the drive with FileVault or BitLocker. The encryption policy does not check the drive; it blocks every recording while the keychain is unavailable.

We do not train models on your content. As long as no cloud models are switched on and no hand-off (DMS, Slack, MCP) is set up, no third party sees your content.

Policies for your organisation

In the Enterprise plan an organisation licence carries policies the app enforces on every device. A user cannot switch them off.

  • Consent confirmation: before every recording the user confirms that all participants have given their consent. The time is noted in the minutes.
  • Encryption enforcement: a recording starts only when the operating system keychain is available.
  • Allow or block screen video.
  • Retention: recordings are deleted automatically after a set period.
  • Block cloud models so that no user can switch them on.

How policies, dictionary, templates and update rings are distributed is described on the IT administration page (German). IT administration

Storage locations

Recordings belong to a named storage location on a drive you choose. The location is bound to that drive; an encrypted external drive works too.

Exports (Markdown, PDF, DOCX, MP4) are written where you say. Handover to a DMS via webhook or folder and the post-meeting actions (Slack recap, ticket bundle, MCP) are connections you set up; without setup they do not exist.

What the licence server sees

The app talks to our server for the licence and to the update server for updates. Add to that the model download and, only when you click, sending a log file. These are all connections, as implemented in the app:

  • On activation: licence key, a random device identifier and the operating system (macOS or Windows). The app does not send a computer name.
  • At start and every 24 hours: a validity check with licence key and device identifier. Without a connection an activated licence keeps working for up to 30 days.
  • At start and every six hours: the request for the current version. If there is a new one, the app downloads the signed installer from updates.jexitymeet.de by default; it installs once you confirm.
  • On first start and when you change the tier: the download of the AI models from huggingface.co and github.com. Only the request itself is sent.
  • Only when you click under Settings, Logs: a cleaned log file to our support, without meeting content.

Never meeting content. Recordings, transcripts and minutes do not reach our server. The app sends no telemetry, no usage statistics and no automatic crash reports. For environments without internet there is offline activation (Enterprise).

What this website collects

Traffic measurement runs on a self-hosted, cookieless Umami instance operated by Evelan GmbH: pages viewed, referrer, browser and device type, approximate region. No cookies, no sharing with third parties, no way to identify a person.

Forms (newsletter, licence request) store only what you enter. All details are in the privacy policy.

Further reading

Network cable test

Pull the cable and check for yourself

Local processing can be proven without our help. The procedure takes a few minutes and works on any computer with Jexity Meet installed.

  1. Load the models

    On first launch the app downloads the AI models for your device. From then on they sit on the disk.

  2. Activate the licence

    The trial starts on first launch. A purchased licence is activated online; after that the app checks at start and every 24 hours whether it is still valid. Without a connection an activated licence keeps working for up to 30 days.

  3. Disconnect the network

    Pull the network cable or switch off Wi-Fi. The computer is now offline.

  4. Record

    Start a recording, in a meeting or in the conference room, with microphone and system audio.

  5. Process

    After you stop, the transcript, speaker separation and topic minutes are produced. All without a connection.

  6. Export

    Save the minutes as PDF or Markdown, from Pro also as DOCX. Only then plug the cable back in.

What you see at the end is finished minutes that were produced without a network. Only cloud models you switch on yourself need a connection.