Documentation
Use Primentra
Getting Started
Data Grid
Approvals
Set up
Modeling
Business Rules
Users & Roles
Sign-in & Security
Install and run
Installation
Administration
Integration & API
Architecture
Migrate from MDS
Migrating from MDS
Documentation/Architecture/Security & Compliance

Security & Compliance

On this page

What Primentra holds, what leaves your network, and which certifications exist. This page answers the questions a vendor security review asks.

Certifications

Primentra holds no third-party security certification. There is no ISO 27001 certificate, no SOC 2 report, and no external audit report to reference.

Primentra is a small vendor. At that size a certification audit costs more than it demonstrates, so we publish the architecture instead and let you verify it against your own installation.

That trade is only reasonable because of what Primentra is. A cloud MDM vendor holds your master data and has to prove it protects it. Primentra never receives your master data at all.

What leaves your network

The Primentra API server opens three kinds of outbound connection, and no others. The third exists only when an administrator turns it on:

ConnectionWhenDestination
SQL Server (TDS)AlwaysThe database server you configure
SMTPOnly when you configure emailThe mail server you configure
HTTPSOnly when an administrator turns on AI assist for LookalikesThe AI provider and address the administrator sets: Anthropic, OpenAI, Azure, Gemini, xAI, or a model server on your own network

There is no telemetry, no usage reporting, and no license call-home. License keys are decoded on your own server from the key itself, so an installation with no route to the internet behaves exactly like one that has it.

The update check runs in the browser, not on the server

Primentra tells an administrator when a newer release exists. That check runs in the administrator's browser against the GitHub releases API. The server never makes it.

This is deliberate. On-premises servers frequently have no outbound internet while the administrator's laptop does, and a server-side check would need an outbound firewall rule your security team has to approve.

Block it and nothing breaks. Every failure is silent, and the rest of Primentra behaves the same.

Where your data lives

Your master data lives in your SQL Server, in a database you created, on hardware you control.

  • Backups are yours. Primentra creates none and reads none.
  • Retention is yours to set. See Data Retention.
  • Deletion happens when you delete. Nothing is copied elsewhere first.

We are not a processor of your master data, because none of it reaches us.

When a license or trial ends

The application becomes read-only. Nothing is deleted and nothing is transmitted. The data stays in your SQL Server, where you can still read and query it directly. Entering a valid key restores editing. See Licensing.

Personal data the company holds

Separate from the product, we hold the records any supplier holds about a customer:

  • The contact and order record: name, email address, company name, billing address, VAT number, and any purchase-order reference.
  • Website analytics, and only when a visitor accepts cookies.
  • A report on the issue tracker: the name and email address you give, and the screenshot or errorlog you attach. Only Primentra sees them, and your colleagues on the Issues page of your Primentra account when the report belongs to your company. A report marked Private is not on the public tracker at all, and a report from the public form shows there only after its reporter confirms it from our mail. The attachment is deleted 90 days after the issue is closed.

Primentra never sends us anything by itself. A file from your installation reaches us only when you attach it to a report. The full statement is the Privacy Policy.

Technical controls

The controls are documented in full on Three-Tier Design & Security. In summary:

  • The API server listens on its port (3001 by default) on every network interface. For HTTPS, IIS terminates TLS in front of it.
  • Every database call is a parameterized stored procedure. The application contains zero raw SQL.
  • The service account holds rights inside the Primentra database and nowhere else, with no server-level permissions.
  • Role-based permissions are enforced server-side before every read and write.
  • SQL error numbers, stack traces and connection strings go to the server log, never to the browser.
  • Every write is recorded in the audit log with the user, the timestamp, and the old and new value.

Questions

Do you have any ISO certification or DSPP information I could reference?

No. There is no ISO 27001 certificate, no SOC 2 report, and no DSPP documentation.

We are a small company, and at that size a certification audit costs more than it demonstrates. We would rather say that than point you at a badge we do not hold.

What we can give you is the thing a vendor review is usually trying to settle: where your data sits, and who can reach it. Primentra installs on your own server, against your own SQL Server, and never receives your master data. The sections above list every outbound connection the API server makes — there are two, and neither carries your records.