Noekken
Create account

Legal

Privacy policy

Last updated 2026-10-13

What Noekken keeps about you, and what it does not. This page describes what the software actually does. If the software changes, this page changes with it.

01In short

  • An account is a random key. We store its hash, not the key, and nothing else that points to you: no email, no name, no password, no phone number.
  • Our servers see your IP address while you are connected, as any VPN server has to, and do not write it to their logs.
  • We do not record the websites you visit, the content of your traffic or your DNS queries.
  • This site has one small script of its own, no analytics and no third-party resources. It sets a cookie when you sign in, and another only if you pick a language.

02Your account

When you create an account, the site generates a random 20-character key and shows it to you once. The database keeps:

  • a SHA-256 hash of the key. That is enough to recognise it when you sign in, and not enough to recover it.
  • the account number, the date it was created, the day it was last used, and whether it is disabled.
  • your devices. For each one: its number in the account, a random name like Quiet Otter, the date it was added, and the key pair it uses to talk to our servers. We keep the private half so that we can give you its file again. For a device added by the app, also a random ID the app made up when it was installed, so the site knows it next time. Removing a device deletes all of this.
  • your passkeys, if you add any. For each one: the ID your device gave it, its public key, its name in your account, the signature counter the passkey keeps, whether it asked for your PIN or fingerprint the last time, the date it was added and the day it was last used. Also a random ID that tells your device these passkeys belong to one account. The private key never leaves your device. Removing a passkey deletes all of this.
  • your conversation with support, if you write to us: the messages and when they were sent. It is deleted 30 days after the last message, or sooner if you or we delete it. Deleting removes it from the database.

We cannot send your key again, reset it or tell you what it was. We never had it, only its hash. If you lose it, the account cannot be recovered, unless it has a passkey: with one you can still sign in here and get a new key.

03Plan, traffic and payments

  • Your plan and the start and end of its current period.
  • The traffic your account used in the current period, per server, in bytes. It is needed to enforce the plan's quota and is replaced at every new period.
  • Daily traffic totals per server for all users together. These cannot be split per person.
  • Orders: which plan, the amount and currency, when it was placed and whether it was paid, cancelled or expired. For a payment in cryptocurrency, also the network and the transaction it was paid with. If you ordered with a promo code, also the code and the price before it. A cancelled or expired order is deleted 30 days after it was placed.

Payments are made the way described next to your order. Whatever that payment channel shows us, for example a sender's name on a bank transfer, reaches us through that channel only. We use it to match the payment to the order number and do not enter it into the account database.

04On our VPN servers

  • A server sees the IP address you connect from for as long as you are connected. It does not write that address to its logs.
  • Its service log records that a session of an account number started and ended, through which entry point and with which speed limit, without your address. These records keep the service running, and the system log keeps them for at most a month.
  • It counts the traffic of each account to enforce quotas, and remembers when an account was last connected. When an account is no longer let in to the server and has not connected for 30 days, the server forgets both.
  • To keep each device key connected from only one computer at a time, a server remembers, while a device is connected, a random number the app picks each time it starts. It is not written anywhere and is forgotten when the device disconnects.
  • It does not record the destinations you connect to, the content of your traffic or your DNS queries. A connection that fails is logged with the error only. The one exception: an attempt to reach a private network address or the server itself through the tunnel is refused, and that refusal is logged with the address, but not with your account or your IP address.
  • Peer-to-peer file sharing (BitTorrent, its trackers and DHT) is recognised by the shape of its traffic and blocked. The log then records that a session of an account number was sharing and how it was recognised, without the addresses involved.

05On this website

  • One cookie, set when you sign in or create an account. It holds a random session token, and the database keeps only its hash. It expires after 14 days, or when you sign out. If you use passkeys, the database also notes which one opened or confirmed the session.
  • A second cookie only if you pick a language in the menu at the top of a page. It holds the language code and nothing else, and lasts a year. Until then the site follows the language your browser asks for and does not store it.
  • One small script of our own. It copies your account key or the payment address when you ask it to, remembers the colour theme you picked and closes the language menu when you click past it. When you add or use a passkey, it asks your browser for one and passes the browser's answer to this site. The theme is kept in your browser's local storage and is never sent to us.
  • No analytics, no advertising, no scripts, fonts or images from other sites. Your browser talks only to this site.
  • The web server keeps no access log. To stop key guessing and mass sign-ups, the site counts attempts per IP address in memory for at most an hour. Promo codes that turn out unknown are counted the same way, and also per account. Those counts are never written to disk.

06In the app

  • If you sign in with your account key, the app sends that key and its random installation ID to this site over HTTPS every six hours to fetch its current connection file. When the tunnel is not connected, that request comes from your own address.
  • Once connected, the app asks ipinfo.io, through the tunnel, where the connection appears to come from, to show it on the map. ipinfo.io sees our server's address, not yours.
  • Name lookups go through encrypted DNS resolvers inside the tunnel, as set by the server you connect to.
  • The app keeps a log on your computer to help with problems. It never leaves your computer by itself.

07How long we keep it

Everything above is kept while the account exists, unless this page says it is deleted sooner. An account that has never been paid for and has neither a paid plan running nor a plan given only by an administrator is deleted by itself after 30 days without use: no connection to our servers, no sign-in on this site and no request from the app. Whether it is deleted that way, by you in your account or by an administrator, the key hash, the devices, the passkeys, the plan, the traffic counts, the orders, the conversation with support and the sessions are removed together. The database tables that held them are rewritten without them, and the servers drop the account's devices from their access lists within about a minute. A promo code you used keeps the count of that use and its amount, with no link to the deleted account.

The database does not overwrite the disk space the removed records used to take up. Until that space is reused, someone with access to the server's disk could still recover recently deleted records.

The database is backed up once a day. Each backup is deleted 30 days after it was made, unless backups have been failing for more than a week: then the old ones are kept until a new one succeeds. A deleted account stays in the backups made before it was deleted until those backups are deleted too.

08Requests from third parties

We can only hand over what is listed on this page. We have no email address or name tied to an account. For a payment in cryptocurrency we have the transaction it was paid with, which the public blockchain links to the sending wallet, and nothing else about how you paid. We have no list of the sites you visited and no record of which IP address used which account.

09Changes

When this policy changes, the date at the top changes with it. A change that collects more about you will be announced on this site before it takes effect.

10Contact

Write to us through the contact given on this site. We answer without asking who you are. An account key is never needed for that, and we will never ask for it.