Error rendering macro 'rw-search'

null

Downloads

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page follows the data that iDNA Applications reads from your Notes environment. It covers where the data is stored, how it is processed, who sees it, and what leaves your network, including to AI clients. The reading itself is described on What iDNA Applications Reads from Your Notes Environment. This page describes iDNA Applications 3.5.0 and later.


Table of Contents
maxLevel2

Overview

  1. Read: iDNA reads from your Domino servers with the collection Notes ID
    (see What iDNA Applications Reads from Your Notes Environment).
  2. Stored on the appliance, a Linux host in your network.
  3. Processed every night on the appliance into the analyses.
  4. Shown to the people you give an iDNA login.
  5. Retrieved by AI clients, only if you enable the MCP server.

...

  • Inbound connections: a standard installation accepts browser connections on port 443 (HTTPS) and redirects port 80 to it. Behind port 443 are the Portal, the admin interface, the Metabase reports, DataMiner and, when enabled, the MCP server. Two more ports are optional and closed by default. VNC (TCP 5901) is open only while an administrator runs the VNC server on the appliance host for its graphical desktop. PostgreSQL (TCP 5432) is open only if the database port is published for direct database access.
  • Logins: the Portal and the admin interface use local iDNA accounts or your LDAP directory, set up separately for each. Metabase has its own login. You decide who gets a login.
  • Roles: Portal users have a role (for example Admin, Editor or User) that decides which pages they can use. Separate roles cover MCP and API access. The admin interface and the system pages are for administrators only.
  • Pseudonymization applies to the prepared data, so every view built on it shows the pseudonyms. Per-user views in the Portal show pseudonyms while pseudonymization is on.
  • Outgoing connections for logins and email: iDNA connects to your LDAP directory if you use it for logins. It connects to your mail server to send alerts and report subscriptions to the recipients you configure.
  • On a trial license, some names and databases are masked or hidden. iDNA Applications Trial License explains which.


What Leaves Your Network

ConnectionFrom → toWhat is sentWhen
Software imagesAppliance → panagenda's download server (docker.panagenda.com)Requests for the iDNA container imagesOnline installation and upgrades. The offline installer needs no connection.
Update checkThe user's browser → panagenda's file server (files.panagenda.com)A request for a version file, without iDNA dataWhen the Portal login page is shown, unless the license has expired
Content analysis tokensThe user's browser → panagenda's licensing server (licensing.panagenda.com)The license key and the replica ID of the database to scan. Only the license key when the token status is shown.When a user starts a scan of a replica set not yet authorized on the appliance, or opens the token status
Help linksThe user's browser → panagenda's documentationA normal page requestWhen a user clicks a help link
AI clientsAppliance → the user's AI assistant platformThe results of the tools the assistant callsOnly when the MCP server is enabled. See AI Clients and the MCP Server
Support bundlesAn administrator → panagenda supportThe appliance's configuration and log files. Review the bundle before you send it.Only when an administrator downloads a bundle and sends it
  • The license is a file you upload, and iDNA checks it on the appliance. iDNA's own components send no usage statistics or crash reports to panagenda.
  • Metabase, the reporting component, has its own settings for anonymous usage tracking and for checking for updates. Check them in Metabase's admin settings.

...