Data Usage and Retention
Operational Purposes
Collected telemetry data is used exclusively for:
-
Service Reliability
- Real-time alerting on service degradation
- Capacity planning and resource allocation
- Incident root cause analysis
-
Performance Optimisation
- Identifying network bottlenecks
- Traffic engineering and QoS tuning
- Infrastructure scaling decisions
-
Security Monitoring
- Anomaly detection in traffic patterns
- DDoS identification and mitigation
- Abuse prevention
What We Do NOT Collect
| Data Type | Status |
|---|---|
| Packet payloads / DPI | Not collected |
| DNS query logs | Not collected |
| User browsing history | Not collected |
| VPN tunnel contents | Not inspected |
| Personal identifiable information | Not stored in metrics |
Traffic flow analysis operates at the metadata level only (source/destination IPs, ports, byte counts). We do not perform deep packet inspection or content analysis.
Data Retention
| Data Type | Retention Period | Storage Location |
|---|---|---|
| Prometheus metrics | 30 days | EU-West (Ireland) |
| NetFlow aggregates | Rolling (in-memory) | EU-West (Ireland) |
| Grafana dashboards | Indefinite | EU-West (Ireland) |
All monitoring data is stored within our EU infrastructure and is not shared with third parties.
Alerting
Automated alerts are configured for critical service thresholds:
| Alert | Threshold | Action |
|---|---|---|
| High CPU | > 90% for 5 minutes | Operations notification |
| Memory Pressure | > 85% used | Operations notification |
| Interface Errors | > 100/minute | Automatic investigation |
| Disk Space | < 10% free | Capacity alert |
| Service Down | No response for 2 minutes | Immediate escalation |
| WireGuard Handshake Stale | > 5 minutes | Peer health check |