Data sovereign secure collaboration | SSH

	Relevant aspect	How SalaX Supports data sovereignty

Deployment flexilibity	Control of hosting location	SalaX can be deployed on‑premises, air-gapped or in an organization‑controlled cloud, including within specific EU or national regions.




Independence	Organizational control of service	The organization operates its own SalaX environment (self‑hosting), including servers, configurations, and integrations.




Control	Customer‑owned encryption keys	Encryption keys can remain under the organization’s exclusive control, separate from the vendor or without the risk of ending up in the public cloud.




Security first	End‑to‑end encrypted communications	Messages, calls and file transfers are secured, so only authorized participants can read or listen.




Inter-organizational collaboration	Decentralized architecture for federation	SalaX’s Matrix‑based model lets each organization run its own server while still securely collaborating with external partners.




Jurisdictional boundaries	Data localization for content and files	Message histories and shared files stay in infrastructure the organization selects and controls.




Flexible governance	Policy‑driven governance	SalaX can be configured to follow internal security policies, data classification rules, and sector‑specific handling requirements with collaboration space and room specific security restrictions.




Evidence	Auditability and evidence	Communications and related events can be logged in an organization controlled environment for audit and incident investigation.




For your eyes only	Limited vendor access to data	The design minimizes provider access to content and restricts processing to what is strictly necessary for service operation.




For heavily-regulated organizations	Fit for high‑criticality use	SalaX is designed for organizations where confidentiality, operational continuity, and sovereign control are core requirements.




Operational under emergencies	Out‑of‑band secure communications	SalaX provides a separate secure messaging, voice, and video channel that runs independently of primary email, Teams/Slack, and corporate collaboration stacks. It's a good fit for crisis management, incident response, and classified or restricted discussions, with bridges used only when needed.

Deployment flexilibity

Relevant aspect

Control of hosting location

How SalaX Supports data sovereignty

SalaX can be deployed on‑premises, air-gapped or in an organization‑controlled cloud, including within specific EU or national regions.

Independence

Relevant aspect

Organizational control of service

How SalaX Supports data sovereignty

The organization operates its own SalaX environment (self‑hosting), including servers, configurations, and integrations.

Control

Relevant aspect

Customer‑owned encryption keys

How SalaX Supports data sovereignty

Encryption keys can remain under the organization’s exclusive control, separate from the vendor or without the risk of ending up in the public cloud.

Security first

Relevant aspect

End‑to‑end encrypted communications

How SalaX Supports data sovereignty

Messages, calls and file transfers are secured, so only authorized participants can read or listen.

Inter-organizational collaboration

Relevant aspect

Decentralized architecture for federation

How SalaX Supports data sovereignty

SalaX’s Matrix‑based model lets each organization run its own server while still securely collaborating with external partners.

Jurisdictional boundaries

Relevant aspect

Data localization for content and files

How SalaX Supports data sovereignty

Message histories and shared files stay in infrastructure the organization selects and controls.

Flexible governance

Relevant aspect

Policy‑driven governance

How SalaX Supports data sovereignty

SalaX can be configured to follow internal security policies, data classification rules, and sector‑specific handling requirements with collaboration space and room specific security restrictions.

Evidence

Relevant aspect

Auditability and evidence

How SalaX Supports data sovereignty

Communications and related events can be logged in an organization controlled environment for audit and incident investigation.

For your eyes only

Relevant aspect

Limited vendor access to data

How SalaX Supports data sovereignty

The design minimizes provider access to content and restricts processing to what is strictly necessary for service operation.

For heavily-regulated organizations

Relevant aspect

Fit for high‑criticality use

How SalaX Supports data sovereignty

SalaX is designed for organizations where confidentiality, operational continuity, and sovereign control are core requirements.

Operational under emergencies

Relevant aspect

Out‑of‑band secure communications

How SalaX Supports data sovereignty

SalaX provides a separate secure messaging, voice, and video channel that runs independently of primary email, Teams/Slack, and corporate collaboration stacks. It's a good fit for crisis management, incident response, and classified or restricted discussions, with bridges used only when needed.