en
No-Log Server Hosting in Latvia - Minimized Log VPS
"No-log hosting" covers two distinct layers: what the hosting provider logs about your account and server, and what your server applications log about their own users. Both matter. Latvia jurisdiction affects the legal context for any logs that do exist: Latvia's DVI enforces GDPR rights proactively. EU member with independent courts outside major intelligence-sharing networks. This guide addresses both provider-side and application-side logging for maximum privacy on your Latvia VPS.
Need this done for your project?
We implement, you ship. Async, documented, done in days.
What Hosting Providers Log - The Reality
Every hosting provider logs some things. Understanding what is standard and what can be minimized:
**What providers typically log**:
- SSH connection source IPs (all providers, usually)
- Panel login events with IP and timestamp
- Billing records (amount, payment method, date)
- Abuse reports received about your server
- Support ticket content
**What Anubiz Host minimizes**:
- Payment records use crypto transaction hashes, not bank account or card data
- No identity document collection means no ID stored
- Access logs from your side (SSH, panel) exist but require Latvia legal process to access
**What you control**:
- Application logs on your server: you configure nginx, apache, syslog, application logging
- Whether to use full-disk encryption (LUKS) on sensitive data directories
- Whether to configure log rotation and rapid deletion policies
Latvia's DVI enforces GDPR rights proactively. EU member with independent courts outside major intelligence-sharing networks. Even if logs exist at the provider level, they are accessible only via Latvia legal process.
Minimizing Application Logs on Your ${c.name} VPS
Application-level logging on your Latvia VPS is fully under your control. Common applications and how to minimize their logging:
**Nginx (web server)**: By default logs all requests with client IP, URL, referer, and user agent. To disable IP logging:
```nginx
# /etc/nginx/nginx.conf
log_format no_ip '- [$time_local] "$request" $status $body_bytes_sent';
access_log /var/log/nginx/access.log no_ip;
```
Or disable access logging entirely: `access_log off;`
**SSH daemon**: Reduces auth logging:
```bash
# /etc/ssh/sshd_config
LogLevel ERROR # Only log errors, not every connection
```
**Tor hidden service**: Tor itself does not log client IPs - this is by design. Ensure your application behind the hidden service also does not log.
**Database** (PostgreSQL/MySQL): Disable query logging in production: `log_statement = 'none'` in postgresql.conf or `general_log = OFF` in MySQL.
**System logs**: Configure systemd journal for minimal retention:
```bash
# /etc/systemd/journald.conf
MaxRetentionSec=1d
MaxFileSec=1d
```
Disk Encryption on ${c.name} VPS - What It Covers
Full-disk encryption (LUKS) on your Latvia VPS protects data at rest - if the physical server is accessed or imaged, encrypted data is unreadable without the key.
**The limitation**: VPS disk encryption is only fully effective if you control the encryption key and the server is powered off at time of seizure. A running encrypted VPS has decrypted data in memory - a memory dump can capture in-use data.
**What LUKS protects against on VPS**: Disk image cloning at the data center without your knowledge. If the physical host's disk is imaged while your VPS is powered off, the data is encrypted.
**Alternative approach for VPS**: Use application-level encryption rather than full-disk. Encrypt sensitive database content and files at the application layer. The OS and applications run unencrypted, but the sensitive data within them is encrypted with keys you hold.
For dedicated servers: LUKS full-disk encryption is more meaningful because you control whether the server reboots (and requires key entry) versus runs continuously.
Latvia's DVI enforces GDPR rights proactively. EU member with independent courts outside major intelligence-sharing networks. Encryption adds a layer independent of jurisdiction.
Tor Hidden Services and Log Minimization on ${c.name} VPS
Running a Tor hidden service (.onion) on your Latvia VPS eliminates the IP logging issue at the network layer - clients connect to your onion address via the Tor network, and your server never sees their real IP.
Tor hidden service setup with no-log nginx:
```bash
# Install Tor
apt install tor -y
# /etc/tor/torrc additions:
HiddenServiceDir /var/lib/tor/hidden_service/
HiddenServicePort 80 127.0.0.1:80
# Restart Tor - get .onion address:
systemctl restart tor
cat /var/lib/tor/hidden_service/hostname
# Configure nginx to only listen on localhost (Tor proxy):
server {
listen 127.0.0.1:80;
# Do not listen on public interface
access_log off; # No logs
}
```
With this setup: clients access your service via .onion, Tor routes the connection to your Latvia VPS, nginx serves the request. No client IPs in nginx logs, no client IPs in application logs, and Tor prevents the Latvia VPS IP from being exposed to clients.
Anubiz Host Tor Hosting Basic at $25.74/mo is purpose-built for this use case.
Related Services
Why Anubiz Host
100% async — no calls, no meetings
Delivered in days, not weeks
Full documentation included
Production-grade from day one
Security-first approach
Post-delivery support included
Ready to get started?
Skip the research. Tell us what you need, and we'll scope it, implement it, and hand it back — fully documented and production-ready.