Skip to content
Kuro

No-logs policy

Last updated: 6 October 2026

"No logs" is easy to claim. This page describes how Kuro VPN is built so that the data isn't there in the first place. An independent audit of these claims is planned.

On our VPN servers

  • System logs live in memory only. The servers' journal is configured as volatile and capped at 64 MB. There is no syslog daemon and no log file on disk, so nothing survives a reboot.
  • Our DNS resolver logs nothing. It runs with query logging, reply logging and cumulative statistics off.
  • The firewall never logs packets. Our build process rejects any firewall rule that logs.
  • No packet capture tools are installed.
  • Our server software logs only state words ("connected", "updated"), never your public key, IP address or tunnel address. Its debug mode, used only for hands-on troubleshooting, is switched off afterwards.
  • Peer data is never written to disk. A server knows your device's public key, its tunnel address and whether your account is on Free or Kuro Pro (which sets your speed) only while you're registered on it. That list is kept in memory and in a RAM-only directory, and is deleted after 24 hours without use.
  • Your IP address is forgotten within minutes. While a device is connected, WireGuard has to know the address it connects from to send traffic back. Our servers drop that address 3 minutes after the device goes quiet; the registration itself stays so you can reconnect quickly.
  • Per-user byte counts exist only on free servers, to enforce the monthly allowance. Paid servers don't read or report per-user traffic, only totals for the whole server. If a paid account is placed on a free server because its location's paid servers are full, that server counts it like any other device and our API throws those counts away.

If a server were seized, it would hold its own private key, the public keys, tunnel addresses and plans of devices registered on it (removed after 24 hours of inactivity), and the IP addresses of devices connected in the last few minutes. No history and no traffic.

On our API and website

  • Request logs record only the route, the status code, the timing and a random request ID. A test in our build fails if a log line contains anything that looks like an IP address, a key or an account number.
  • Rate limiting uses salted hashes of IP addresses that expire within an hour.
  • The country you sign up from is looked up once and stored; your IP address is not.
  • We record when a device was last used as a date only, not a time. There is no "last connected" timestamp anywhere.
  • Our control plane knows which server each device is currently registered on, and when that registration was created, only for as long as the registration exists.
  • Our website and API sit behind Cloudflare, which carries the requests (never your VPN traffic) and so sees your IP address on the way to us.
  • If you watch an ad for extra data, we keep when you did it for 24 hours, to enforce the limits. Google's confirmation reaches us with a one-time code, so Google never learns which account it was for.

In our apps

No analytics SDKs and no crash reporting. The free Android app includes Google's ads SDK, which starts only when you choose to watch an ad; the ad loads outside the VPN tunnel, never through our servers. Problem reports go out only when you send one, with IP addresses and keys removed. Your WireGuard private key is generated on your device and never leaves it.

What we do keep

Your account, devices, subscription status, (free plan) monthly byte totals and, if you watch ads for extra data, when you did in the last 24 hours. See the privacy policy for the full list and how long each item is kept.