---
title: "Natalia On-Premise Contractual Modes (Strict/+72h/Connected)"
description: "Canonical matrix of the 3 GDPR modes for Natalia On-Premise. Strict = zero DPA, +72h = remote support, Connected = standard SaaS with AI."
url: https://getnatalia.com/en/natalia-analytics-on-premise/contractual-modes
lang: en
---

[Home](https://getnatalia.com/en/) / [Documentation](https://getnatalia.com/en/documentation) / [On-Premise](https://getnatalia.com/en/natalia-analytics-on-premise) / Contractual modes

# Natalia On-Premise Contractual Modes

Three modes based on your sovereignty requirements. Choose at installation, adjustable later.

## Canonical matrix

| Criterion | Disconnected Strict Maximum sovereignty | \+ 72h Support Remote support on demand | Connected Standard SaaS, AI included |
| --- | --- | --- | --- |
| Outbound connectivity | None | One-off remote support access, on your trigger, 72 h at most, per the Support DPA | Permanent (encrypted) |
| GDPR art.28 DPA | Not required (pure software publisher) | Light Support-DPA | Full SaaS art.28 DPA |
| Declared sub-processors | None | Natalia support only (rolling 72h) | Full list on request |
| Data that leaves | None | Anonymized support logs only | Metrics + assisted AI |
| Conversational AI | Local only (MCP via your LLM) | Local only | Available (on-demand assisted AI) |
| CISO sales cycle | \-3 to -6 weeks (no DPA) | Standard | Standard SaaS |
| Typical use case | OIV, banks, mutuals, healthcare, defense | Regulated mid-market needing remote support | Standard SaaS, MCP/AI included |

## How to choose?

Three questions, in this order:

1\. Are you OIV/OES, or do you have a strict isolation requirement (NIS2, SecNumCloud)?

→ **Disconnected Strict**. No outbound, no DPA, no sub-processor.

2\. Do you need remote support with an SLA?

→ **\+ 72h Support**. One-off remote support access on your trigger, 72 h at most, light Support-DPA, anonymized logs only.

3\. Do you want conversational AI activated out of the box?

→ **Connected**. Standard SaaS billing, art.28 DPA, on-demand assisted AI.

## Migration between modes

Migration between modes is possible without reinstalling and without migrating data. The mode is a configuration parameter, not an architectural fork.

-   → Strict → +72h: amendment to enable Support-DPA, support access triggered by the customer.
-   → +72h → Connected: art.28 DPA signature + activation of permanent outbound (configurable IP/proxy filtering).
-   → Connected → Strict: contract termination of SaaS clauses, deactivation of outbound, data remains on the appliance.

Hybrid posture

Some customers run Strict in production and Connected in pre-production for AI feature evaluation. The two appliances are fully independent.

Last updated : October 5, 2026

[Suggest an edit](mailto:doc@getnatalia.com?subject=Doc%20edit%3A%20natalia-analytics-on-premise%2Fcontractual-modes)