All references

Logging policy

What DinoLink does and doesn't store, in three short sections.

On this page 3 sections

DinoLink never logs the content of your traffic. To run the service, bill it and fix problems, we do keep some records. This page sums them up; the privacy policy has the full list and the reasons.

What we don’t keep

  • No traffic content (the data inside the tunnel)
  • No IP addresses in our account and billing database

What we record

  • VPN server logs: your IP address, account, destination domains and ports (no URLs or page paths) and connection times
  • Website and API logs: IP address, request path and request headers
  • App DNS resolver: domains looked up and a truncated IP address, kept for 7 days
  • How much traffic each account uses, recorded hourly for pay-as-you-go billing (billing is also set up to aggregate usage per account and service per day)
  • App error reports sent to Sentry (with IP address and device information); in-app support runs on Chatwoot
  • Account and payment status, the current data balance on each account, and aggregate server load (not per-user)

What you can check yourself

Watch the traffic with a packet inspector on your own device or router while connected through DinoLink. You’ll see that traffic between your device and the DinoLink endpoint is encrypted. A local capture can’t show what happens on our servers, so it can’t show what our servers record — for that, see the privacy policy.

For the broader picture of what a VPN protects (and what it doesn’t), see What a VPN is and why you need one in Russia in 2026.