How SecurityNet Works

Main App:

The Control Panel

Everything begins here — nothing happens without instruction.

Configure settings
Select contacts & files
Send and receive files and messages

Scanner:

Background Monitor

Runs automatically in the background, checking for:

incoming files & chats
items to send
matches sender and receiver

Why SecurityNet Doesn’t Use the Cloud — And Why That Matters

Cloud services are convenient — but they come with serious trade-offs for privacy and security. When your files or messages are stored on someone else’s infrastructure, you lose control over where they go, who can see them, and how long they exist. Even if encrypted, data stored in the cloud is never truly private.

Here’s why relying on the cloud puts your information at risk:

Permanent copies you can’t erase:
When data is stored in the cloud, it’s automatically replicated, backed up, and cached — often across multiple servers and jurisdictions. Even if you delete a file, copies can persist indefinitely beyond your control.
Legal access and government orders:
Cloud providers can be compelled to hand over your data to governments, law enforcement, or even private litigants — often without your knowledge. If it’s stored on their servers, it’s no longer solely yours.
Metadata exposure:
Even if the content is encrypted, cloud systems still record metadata such as who you communicated with, when, how often, and the size or type of data transferred. This digital trail can reveal sensitive patterns about your activities and relationships. SecurityNet eliminates this risk by operating without the cloud — no servers, no logs, and no metadata collected or stored by SecurityNet.
Data mining and profiling:
Some cloud providers analyse usage data, metadata, and behavioural patterns to improve their services — or monetise them. Even if the content is secure, the context can still be exploited. SecurityNet never collects or analyses metadata or behavioural information — your activity remains entirely private.
Jurisdictional vulnerabilities:
Your data might be stored in countries with weaker privacy laws, or in locations where foreign authorities can gain access. Once it’s on the cloud, it’s subject to the policies and politics of wherever it resides.
SecurityNet avoids all of this by design.
We never store your data — not on our servers, not in backups, not anywhere. Files and messages are transmitted directly and privately from one device to another, leaving no residual copies and no digital footprint. Once delivered, they disappear from the network. Use SecurityNet when control, privacy, and confidentiality truly matter — and you want your data to belong to you and no one else.

How to Stay in Control of Your Data

Where Should You Store Your Data?
For maximum privacy and control, avoid storing sensitive information on cloud services altogether. Instead, keep your data in-house — on encrypted local drives, secure network-attached storage (NAS), or removable USB devices that you physically control. This ensures you alone decide where your data resides, who can access it, and when it’s deleted. With regular offline backups, you gain both security and resilience — without exposing your information to third parties, hidden copies, or unexpected legal demands.
Best Practice Tip:
Many privacy-focused organisations use a two-layer approach: SecurityNet for encrypted transmission, and encrypted local or NAS storage for long-term retention. This combination virtually eliminates the most common data-security risks — ensuring that your information remains fully private, under your control, and inaccessible to anyone else.

Why “end-to-end encrypted” is no longer enough

What is “client-side scanning”?
Client-side scanning means that messages, images, or files are examined on your own device before they are encrypted and sent.
Instead of trying to break encryption in transit, the software is required to look at the content in plain form first, using government-approved detection systems. Only after this inspection does encryption take place.
The result is that encryption still exists, but it no longer protects what the scanner decides to inspect or report. The surveillance happens upstream of the cryptography, inside the application itself.
Why cloud and mobile platforms make this enforceable.
Modern messaging platforms are typically:
- Centrally operated
- Cloud-dependent
- Distributed through controlled app stores
- Automatically updated
- Running on locked-down mobile operating systems
This creates a single point of legal and technical control. Governments can compel the platform provider or the OS vendor to modify the software, and those changes can be silently deployed to millions of devices.
When the operating system and the application update mechanism are both outside the user’s control, client-side scanning can be introduced universally and enforced by design.
Why peer-to-peer and desktop architectures make this far harder.
In a true peer-to-peer system:
There is no central service relaying or processing content
There is no cloud key authority
There is no mandatory update channel
There is no platform operator through which all traffic flows

On desktop systems, users also retain control over:
What software runs
What versions are installed
What network connections are permitted
Whether updates are accepted at all
Without a central control plane and without a locked execution environment, there is no practical way to impose a universal scanning layer across all endpoints.
How SecurityNet keeps the trust boundary at the user.
SecurityNet is architected so that:
- Encryption and decryption occur entirely on the user’s own machines
- Keys are generated and stored locally
- Communication takes place over direct, peer-to-peer encrypted tunnels
- No central service ever sees plaintext or controls the session
- No cloud infrastructure is required for message content
- No mobile operating system mediates or inspects the data path
This means the point of trust remains where it belongs:
with the communicating parties themselves.
There is no central platform that can be compelled to insert inspection logic at scale, and no cloud or mobile control layer through which such surveillance can be silently enforced.
A fundamental limit.
No application can protect privacy on an operating system that has itself become a surveillance platform.
SecurityNet’s design ensures that there is no central service, mobile control layer, or mandatory update infrastructure through which such surveillance can be universally imposed.

How SecurityNet Works

What actually runs on your systems

How You Use SecurityNet

SecurityNet creates private communication networks between people you choose — and you control exactly who joins.

See the complete step-by-step guide →

Communicate Without the Cloud

Why SecurityNet Does Not Use Phones

Visual Architecture & Privacy Diagrams

SecurityNet uses a different communication architecture from other systems:

View SecurityNet Explained Visually →

How SecurityNet Protects Your Communication

Your data moves directly between computers.

It is never stored or retained on external servers.

View Privacy Verification →

Why SecurityNet Doesn’t Use the Cloud

If it’s in the cloud, it’s out of your control.

Control Where Your Data Lives

What this means in practice:

**Transmit your data directly from computer to computer**

**And by directly we mean:**

How do we do this?

Why Trust SecurityNet?