---
title: Networking and security
description: Who may reach Human Plugin, why it has no inbound authentication, which connections it makes, and the security responsibilities that stay with you.
canonical: https://developer.unico.io/human-plugin/self-hosting/networking-and-security
locale: en
generated_by: markdown-export
---

# Networking and security

Human Plugin trusts its network. You control who can reach it.

## Trust boundary

Human Plugin serves plain HTTP and **does not authenticate or authorize callers**, does not scope requests to a client, and does not terminate TLS. Anyone who can reach the port can create processes with your access key and read any process of the installation.

Therefore:

- Expose the port only to your back-end: localhost, a sidecar, or a private network with network policies or security groups.
- Never publish it through a public ingress or load balancer.
- If you need TLS or caller authentication, provide it in front of Human Plugin, in a gateway, a service mesh or a reverse proxy that you operate.

## Connections Human Plugin makes

| Destination | When | Notes |
| --- | --- | --- |
| `humantoken.unico.app` (443) | While processes run | Uses your access key |
| `human-token-assets.unico.app` (443) | Once at startup | The [attribute catalog](/human-plugin/additional-resources/attribute-catalog) |
| `pkg.unico.run` (443) | When the image is pulled | Unico's registry. Needed by Docker or the kubelet, not by Human Plugin |
| Your PostgreSQL | Always | SSL required by default |

Allow these destinations in your egress rules.

## Secrets

The access key and the database password come from the environment. Inject them from your secret store. Human Plugin never logs them. Changing either one requires restarting the container.

## Data handling

- Sensitive data stays in your infrastructure: the documents you send in `credential`, your client ids and the intelligence are kept in your database.
- Responses carry the Human Token and, for Journey flows, the SDK token and link. Human Plugin does not log them, and your gateway and application logs should not either.
- Human Plugin does not store the selfie, and the selfie response is not cached. Treat it as biometric data in your own systems.
- Human Plugin logs never contain images, document values, tokens or the access key.
- Isolation between clients or brands is the installation and its database. `clientId` is a counting dimension for the intelligence, not an access boundary.