Skip to the page
FenrisEarly access

Privacy you can read.

Your server never writes down the sites you visit, the names you look up or what is inside your traffic. What it does keep is listed in every app, item by item, with how long.

Your serverEvery device

What your server does with it
The sites you visit
An open connection’s addresses are held in memory only while it lasts.
The names you look up
An answer stays in memory as long as its records allow, a day at most, and is not tied to you.
What is inside your traffic
No content and no app names. Your device sorts your traffic, not your server.
Each session
A year, in the audit log.
Data used each day
About 400 days.
How each link is doing
24 hours, in memory.
That a device is enrolled
For good, so its number is never used again.
Fig. 1A summary. The whole list, item by item, is on the privacy page.

What happens

  1. Your server reads where each packet is going, to pass it on. An open connection’s addresses are held in memory only while it lasts.
  2. It answers your name lookups from memory. An answer stays only as long as its records allow, a day at most, and is not tied to you.
  3. It never looks inside your traffic. Your device sorts each connection, so your server has no need to.
  4. What it does keep has a stated time. Each session in the audit log for a year, daily usage for about 400 days, link health for 24 hours in memory.
  5. Every app has a page that lists all of it, for the server it has joined.

What it costs

It keeps some things, and says which.

Not “no logs”
A year of sessions is kept, each with the public address it came from, so you can see what connected and when. That is a log, and it is yours.
Fixed times
The times are the program’s own. A year for the audit log and about 400 days for usage are not settings.
A backup
A sealed backup of your server holds everything it keeps on disk. Guard its passphrase.

Turn it on

There is nothing to turn on. The list is in every app, under Servers, then Server privacy. These show the rest.

ToCommand lineRouter UI and app
See what each link carried, on the devicefenris usageUsage
See what Fenris did, and whyfenris activityActivity
Make a file for a bug report, with addresses and names hiddenfenris diagnosticsDiagnostics, For a bug report
Keep addresses and names in itfenris diagnostics --fullDiagnostics, For a bug report

Where to find it

The consoleAudit log. Kept a year: each session, each sign-in and each change.

The productOne of its own screens, with example data.

What it keeps

Everything it keeps is in one table, with how long: that a device is enrolled, what it runs and where it connects from, each session, the device’s log, daily usage, its links, how they are doing, and what admins did.

Where it stops

Whoever runs the machine
The list is what the program keeps. Whoever runs the machine controls it, and can see what leaves it.
Your own monitoring
If you turn on metrics, your monitoring may keep the same counts for longer.
The system’s log
A few lines go to the server’s own log, kept as the system keeps logs: when a device enrols, when a port is forwarded to it, when it stays offline.
This website
This page is about your server. What this website collects is on its privacy page.