Server record.
This page separates settings visible in the published configuration from statements that only the operator can verify. A snapshot cannot prove future behaviour, complete deletion or the absence of every possible log.
What is documented
The configuration snapshot was published on . Each entry states whether its evidence is published configuration, an operator statement or an unresolved question.
- SERVER SOFTWARE
- PUBLISHED CONFIG
The published configuration snapshot and installed package identify ejabberd 24.12-3+deb13u2.
- MESSAGE ARCHIVE
- PUBLISHED CONFIG
The published snapshot shows that message archiving (MAM) is disabled.
- OFFLINE QUEUE
- PUBLISHED CONFIG
The published snapshot limits the offline queue to 10 messages per account.
- HTTP FILE UPLOAD
- PUBLISHED CONFIG
The published snapshot shows that HTTP file upload is enabled.
- COMMUNITY ROOMS
- PUBLISHED CONFIG
The published snapshot requires membership for rooms and excludes them from public listings.
- SERVER LOCATION
- OPERATOR STATEMENT
The operator states that the server is in Switzerland. The XMPP provider record lists the country code CH.
- WEB AND SERVICE LOGS
- OPERATOR STATEMENT
The main website records the client IP address, time, response status and request path without its query string. Access logging is disabled for registration, CAPTCHA and NKNW Share. Error and anti-abuse logs can contain connection data. NKNW does not intentionally log message content.
- LOG RETENTION
- OPERATOR STATEMENT
At the daily UTC rotation, current service log files are deleted and no rotated copies are kept. The system journal is configured for one day of retention and is pruned hourly. This policy covers logs, not stored accounts, queued messages or uploads.
- BACKUPS
- OPERATOR STATEMENT
The operator does not back up account data or uploaded files.
Evidence has limits.
Message content, connection data, logs, offline queues, backups and user devices are separate layers. Evidence about one layer does not prove anything about the others.
What the server cannot protect
- 01CONTENT
- OMEMO can encrypt message content
A compatible client can use OMEMO to encrypt message content end to end. Confirm that it is active in the conversation and includes every intended device.
- 02IDENTITY
- A separate identity reduces easy links
Use a username, avatar and biography that you have not used elsewhere. Contacts, writing style and repeated details can still reveal who you are.
- 03METADATA
- Routing data remains visible
The server receives your source IP address and processes account and routing data to deliver messages. Other XMPP servers and network observers may see additional metadata along the route.
- 04DEVICES
- OMEMO cannot secure your device
An unlocked, infected or monitored device can expose decrypted messages. Notification previews, screenshots and unencrypted backups can create more copies.
- 05VERIFICATION
- Verify who owns each key
For a high-risk conversation, compare fingerprints or security codes through a separate trusted channel. Encryption alone does not prove who controls the device at the other end.
Account controls
You can change the password or delete the account through the account page. Deletion cannot remove copies already held by contacts, other XMPP servers or devices. A lost password may be impossible to recover.