The SecurityNet Glossary provides quick, easy-to-understand explanations of the technologies and security concepts that make SecurityNet work.

Click a term to jump to its explanation.

Short answer:
The newest and most secure version of HTTPS — it protects everything your app sends over the internet.

More detail:
TLS 1.3 encrypts all communication between two computers so no one in the middle (ISP, government, Wi-Fi hotspot, employer, etc.) can read or modify it.
It also hides more metadata than older versions and connects faster.

Short answer:
A direct, private connection between two devices — no server in the middle.

More detail:
With P2P, your files or messages go straight from your computer to your contact’s. They don’t pass through our server, cloud storage, or any third-party system.

Short answer:
This hides your DNS lookups so nobody can see which websites your app is accessing.

More detail:
Normally DNS is unencrypted. DoH wraps it inside HTTPS (TLS 1.3), so even your ISP can’t read what hostname you’re requesting.

Short answer:
A phonebook for the internet — it turns a website name into an IP address.

More detail:
SecurityNet encrypts DNS requests using DoH so others can’t see which domains your app is looking up.

Short answer:
A unique number that identifies a device on the internet (similar to a house address).

More detail:
SecurityNet hides IP details inside encrypted tunnels so other people can’t see who’s connecting to whom.

Short answer:
A secret code used to lock and unlock encrypted data.

More detail:
SecurityNet generates new, random encryption keys for every connection, so even if someone intercepted old traffic, it wouldn’t help them decrypt future transfers.

Short answer:
A secure method two devices use to agree on a shared secret.

More detail:
SecurityNet exchanges encrypted session keys automatically — without storing them on the server and without exposing them to anyone else.

Short answer:
A unique username you choose that allows trusted contacts to connect to you.

More detail:
IDs are stored encrypted on the server and contain no personal information.
Each device has its own ID.

A second check (usually a code from an app like Google Authenticator) to confirm it’s really you logging in.

More detail:
SecurityNet supports 2FA inside the desktop app.
Codes are generated on your device — no SMS, no email interception risk.

Short answer:
Information about the data — like who you’re connecting to, when, or file sizes.

More detail:
SecurityNet hides or minimises almost all metadata using:

Short answer:
A highly locked-down server SecurityNet uses only when direct device-to-device connection is not possible.

More detail:
When networks block direct peer-to-peer communication (for example, mobile hotspots or restrictive firewalls), SecurityNet automatically routes encrypted data through a secure relay server.

The relay cannot read your files, cannot read your messages, and never receives your encryption keys, because all data remains end-to-end encrypted between devices.

Short answer:
A flood of unwanted traffic intended to overwhelm a server.

More detail:
Most transfers occur directly between devices. When direct connection is blocked by network restrictions, encrypted traffic may temporarily pass through a relay server.

Short answer:
A private, sealed communication path between two devices.

More detail:
SecurityNet builds a new encrypted tunnel each time a file or message is exchanged.

Short answer:
The “hello” two devices exchange to agree on encryption before data flows.

More detail:
Only the handshake is visible on the network — everything after is fully encrypted.

Short answer:
A temporary encryption key used for a single connection.

More detail:
SecurityNet generates new keys automatically for each session. Nothing is reused.

Short answer:
Trying millions of passwords until one works.

More detail:
Strong encryption, rate limits, and (optional) 2FA make brute-forcing SecurityNet essentially impossible.

Short answer:
We cannot read your data — even if we wanted to.

More detail:
The server knows only encrypted IDs and license info.
Messages, files, and encryption keys never pass through our server.