1. Who is responsible for your data
PortGoose is run by Andreas Claesson, an individual, who is the data controller for the purposes of the GDPR.
You can reach us about anything in this policy, including any right described in section 7, at support@portgoose.lol.
2. What we collect
When you sign up and use the service:
| What | Why |
|---|---|
| Your email address | It identifies the account, and it is how a password reset reaches you. |
| A hash of your password | To check your password without ever holding it. The hash itself is not a password and cannot be used as one. |
| Hashes of your session tokens and API keys | To recognise a signed-in browser or a tunnel credential. The values themselves are never stored. |
| The hostnames you claim | To serve them, and to know they are yours. |
| Per-connection counters: bytes in, bytes out, request counts | To show you what each tunnel carried, and to enforce the plan's limits. |
| Daily totals of the above | So the usage view does not have to keep every connection forever. |
| Abuse reports against a hostname | To act on reports. A report records the hostname and the reason, not who sent it. |
| A record of security-relevant events (see section 4) | So that "what happened to this account" has an answer. |
What you have to give us: an email address and a password. Without them there is no account to serve, and nothing to sign in to. Everything else in the table above either happens because you used the service, or is optional.
What we do not collect: your name, postal address, telephone number, payment details, browser or device information, or anything from a third party. There is no analytics, no advertising, no tracker, and no third-party script of any kind on this site. Nothing is inferred about you and nothing is profiled.
An IP address is never written to our database. It does reach the servers, because it has to: rate limiting counts attempts per address in memory, and an address is dropped from that memory after a few minutes of silence. It is never written to disk. It can also be left behind in a server log when a request is refused. Section 4 says for how long.
3. Why we are allowed to hold it
- To provide the service you asked for (contract): the email address, the password hash, your hostnames, your credentials, and the counters that make usage visible to you.
- To keep the service working and safe (legitimate interest): abuse reports, the security record, and rate limiting. This is what stops the service being used to phish somebody, and it is in everybody's interest, including yours.
- Consent, for one thing only: product update emails. Off by default, only ever sent if you tick the box, and one click to stop.
4. How long we keep it
- Your account and its hostnames: until you delete the account. Deletion is a button on the account page, it needs your password, and it takes effect immediately (see section 8).
- Daily usage totals: kept while the account exists and deleted with it.
- Abuse reports: kept while the hostname they concern exists and deleted with it.
- Security record: up to 12 months. It records when an account was created or deleted, whether a sign-in succeeded or failed, when a password was changed or reset, when a key was created or revoked, and when a hostname was claimed, released or suspended by us. It includes your email address so it can still be found after the account is gone. It contains no IP address and no user agent. We keep it this long because abuse reports and account-takeover claims often arrive weeks or months after the event, and this record is the only thing that can answer them.
- Server logs: kept short and rotated continuously, so the oldest are discarded once a service has written a fixed amount. They record events such as "an account was created" against an internal identifier, not an email address. A refused request or failed connection can leave an IP address in the log. They are not linked to an account and are only read when something has gone wrong. There is no number of days here on purpose: a busy day pushes the oldest out within hours, and a quiet week can leave the same few megabytes in place for longer, so a number would be a guess about your traffic rather than a fact about our records.
- Web server access logs: up to 14 days. They contain an IP address and the page requested. They are not linked to an account and are only read when investigating abuse.
- Emails we send you: we keep no copy. They remain in your mailbox and in our mail server's delivery logs, which are rotated automatically.
- Backups: taken every night and kept for 30 days. They are encrypted on our server before they leave it, with a key that is not on that server, and stored with a hosting provider; neither we nor that provider can read one. Because a backup is a copy, something you delete also stays in the copies until the one holding it is rotated out, which is at most 30 days. Section 8 says what that means for a deletion.
5. Who processes your data
Your account data is held and processed on servers in the EU (the Netherlands, Germany and Sweden). These are rented servers, so the hosting companies could technically access what is on them, as with any hosting provider. We run the email server ourselves, so no email company handles your address.
What you should know about tunnels: the server that handles your tunnel connections ends the public TLS connection for your hostname. Request contents therefore pass through it unencrypted on their way to your client. We do not inspect or record the requests that pass through it, with one exception, described next. But this is not end-to-end encryption, and we do not claim that the operator cannot see your traffic.
The exception: content checks. While a tunnel is connected we occasionally fetch the front page of it, the same way any visitor would, and look for two things: a password form that posts somewhere other than the tunnel, and a well-known brand name on a page that asks for a password. This is automated, it runs at most a few times a day on each live hostname, and what it produces is a note for a person to read. It cannot suspend anything by itself, and it does not look at anything behind a login or anything you did not make public by pointing a tunnel at it.
Other processors: we use bunny.net to distribute CLI downloads. It receives requests for files and no account data. It is a worldwide network, so a request may be handled outside the EU; such a request carries an IP address and nothing else about you. Where a provider processes data outside the EU/EEA, we will make sure the safeguards that apply to that transfer are in place, and you can ask us for a copy of them.
Backups are held by a hosting provider in Germany as encrypted files. Neither it nor the server that writes them can open one: the key that can is kept offline by us.
We do not sell personal data, share it for advertising, or use it to train AI models.
6. Cookies
Two, both set by this site, and no others.
The signed-in session. Without it there is no account to serve, so it is strictly necessary. It is deleted when you sign out.
Your light or dark choice, remembered for a year. It holds one of two words and nothing else, and it exists only because you made that choice. The site works without it: clear it and you are back to following your system's setting.
Nothing else is stored on your device for any other purpose. There is no analytics, no advertising and no third-party cookie, and adding any of them would mean changing this policy and adding a banner in the same release.
7. Your rights
You have the right to see what we hold, to have it corrected, to have it deleted, to have a copy of it in a portable form, to ask us to restrict what we do with it, and to object to processing we do on the basis of our legitimate interest. Where you have given consent, you can take it back at any time, and taking it back does not change anything done before you did.
Ask at support@portgoose.lol, from the address on the account: that is how we know it is you, since the account's address is the only identity this service has. We answer within a month.
Three of these are already a button: deleting your account is on the account page, your own usage is on the dashboard, and a copy of everything we hold is a download on the account page. The last one is the same document whether you ask us for it or fetch it yourself, and it needs no request to us: it contains the account and the terms version it accepted, the keys and what they are called, the hostnames, the daily usage, the reports made against those hostnames, and the security record. It contains no password, no key and no session token.
The one decision that happens without a person. Reports about a hostname are counted automatically, and if three credible ones arrive against the same name inside a day, that name is suspended before anybody reads them. It is the only automated decision this service makes that affects you, it is recorded, and it is visible to you. It is not a judgement about you: it counts reports about a hostname. If it happens to you, write to us. A person will look at the reports, you can say your piece, and the suspension can be lifted. That appeal is the safeguard the law gives you, and it goes to the same address as everything else in this section. Section 6 of the terms describes what a suspension means.
The content checks described in section 5 are automated too, and they are deliberately not a decision: what they produce is a record for a person to read, it is shown to nobody else, and on its own it cannot suspend, block or disconnect anything. If one of them is ever wrong about your tunnel, nothing happens to you until a person has looked at it.
If you think we have handled any of this badly, you can complain to the Swedish Authority for Privacy Protection (IMY), which is the supervisory authority for this controller.
8. Deleting your account
The account page deletes the account, and it takes the API keys, the claimed hostnames, the login sessions, the tunnel records and the usage history with it. Hostnames go back into circulation immediately, so anybody can claim them the moment you do this, and a tunnel that is connected stops being served.
What it cannot take with it, and why:
- Our server logs, which still describe what happened until the rotation replaces them, which section 4 says is measured in size rather than in days.
- The security record, which keeps the entry saying the account was created and the one saying it was deleted, with the address and no link to the account, until it ages out, within 12 months. It holds the record about the account rather than the account, which is the whole reason it survives.
- The email we sent you, which is in your mailbox. We cannot delete your copy, and would not.
- Backups, until the copy containing the account is rotated out. They are taken nightly and kept for 30 days, so a deleted account can still be in one of them for up to that long, and never longer.
9. Email
Two kinds, and the difference is the whole of this section:
- Service email: a confirmation link, a reset link. Sent whether or not you have opted into anything, because they are how the account works. There is no unsubscribe from them, and turning updates off does not turn them off.
- Product updates: only if you have opted in. The switch is off by default and lives on your account page, and every one of these messages carries a one-click unsubscribe that works without signing in. Turning it off is the withdrawal of the consent described in section 3, and you can do it at any time. Withdrawing it does not affect anything sent before you did.
10. Children
The service is not for anybody under 16, and the terms say so. We do not ask for a date of birth or attempt to verify age, because collecting that to check an age would mean collecting more about a child than the thing being protected; what we rely on is the statement in the terms and the fact that there is nothing here to attract or hold a child's attention.
11. Security
Passwords and credentials are stored only as hashes, so a copy of the database does not contain anything that can be presented as a password or a key. Everything travels over TLS, including the tunnel between your client and our servers. Credentials can be revoked individually, and a password change ends every other signed-in session.
One qualification, because it is the sort of thing a security section usually avoids saying: the tunnel server is an endpoint of your hostname's TLS, not a pipe. Section 5 says what it can see, and what we do and do not do with it.
12. Changes
When this policy changes, the date below changes and the change is announced on the site and by email to account holders, before it takes effect.
Last updated: 13 October 2026.