Privacy notice

This notice covers the Portdeck private beta: the websites and the software you install. It is written in plain words. Where it says what the software does not do, it means the version in the beta today.

Who this is

Portdeck is in a private beta run by Enoch Ayanwale, personally. No company is named here. Enoch Ayanwale is the person responsible for the details that testers send to the project: your name, your email address, and any logs or messages you email us.

What the websites collect

Nothing of our own. There are two sites. getportdeck.com is the landing site and the beta guide. get.getportdeck.com is the download host for the installer and upgrades. Both are hosted on Cloudflare.

The landing site sets no cookies, has no forms, runs no analytics and loads no scripts that send data anywhere. Its pages use one small script of their own for the theme, the menu and the tabs. It stores your light or dark choice in your browser's local storage and does not send it anywhere. The fonts are served from the site itself.

Like any host, Cloudflare handles ordinary request data, such as your IP address, browser type, the page asked for and the time, to serve and protect them. Cloudflare Web Analytics is switched off on both. Links to other sites are ordinary links; nothing is loaded from them.

The emails you send us

The addresses beta@getportdeck.com, privacy@getportdeck.com and security@getportdeck.com are forwarded by Cloudflare Email Routing to the owner's personal inbox at Gmail, which is run by Google.

• We keep beta request, feedback, privacy and security emails, and tester details (your name, your email address and which key we issued), while the private beta runs.
• When you ask, we delete them from our inbox and records. Write to privacy@getportdeck.com. Copies may stay in Google's deleted-mail storage and its own backups for a while.
• Your name is also inside the key itself. That key sits on your server, and we cannot delete it from your install. Data on your own install is yours to delete.
• Please do not put secrets or other people's personal data in an email. Take tokens, .env values and keys out of any logs before you send them.

The beta key

A beta key carries the tester's name. Portdeck checks the key on your own server, offline; nothing about the key is sent anywhere to check it. When you activate a key, your install stores the key text, and a separate record with the tester name, plan, expiry, a fingerprint of the key and the agreement acceptance (who accepted, when, and which version). All of it stays in your install's database. If you set the key in the install's .env file, it is there too, and backups include .env.

The software runs on your server

Portdeck is installed on a server you control. What it holds stays there and is not sent to the project. That includes:

• accounts: usernames, password hashes and two-factor secrets (there is no email address field on an account);
• IP addresses and browser details, in the activity log and in session records;
• the email addresses of people you invite to a workspace;
• API tokens (stored as hashes), deploy settings and the secrets you save;
• backups, which contain the whole database, the secrets and the .env file. They are encrypted, and you decide where they are copied.

On a shared install, the activity log is visible to workspace admins, and operators see their own actions and those on instances they own. Session records are visible to whoever runs the ops console.

The software does contact other services on its own account:

• Image registries. Every 6 hours by default it asks the registries of your container images (for example Docker Hub or ghcr.io) whether newer versions exist. Set UPDATE_CHECK_ENABLED=false to turn this off.
• Installs and upgrades. The install and upgrade scripts download from get.getportdeck.com, pull images from ghcr.io, and may fetch release files from GitHub. These are ordinary web requests; no install identifier is attached. Cloudflare handles them as it does for the websites.
• Install time. The installer asks api.ipify.org for the machine's public IP address, unless you set it yourself. In domain mode the web server asks Let's Encrypt for a certificate, with your domain name and the optional email address you gave for expiry notices.
• An IP check. After an alert that an agent's public IP may have changed, Portdeck asks Cloudflare (1.1.1.1) for its own public IP address.
• Services you switch on. Email, Discord alerts, GitHub, Cloudflare and the sign-up check receive what you send them, under their own terms.

The AI assistant

The assistant is off until an admin turns it on. When it is on, what a person types and the tool results it uses are sent to the AI provider the admin chose. Those results can include usernames, host and container names, and container log lines. Do not turn it on if you do not want that content to leave your server.

What the software does not do

The software contains no telemetry and no usage statistics, and it has no crash reporting. It has no field for age or location. It does not send your accounts, activity or backups to the project.

How long things are kept

On your install, these are deleted automatically:

• the record of commands run through agents, after 30 days;
• backups, after 14 days by default (a setting).

These are not deleted automatically, so you decide when to remove them:

• the activity log (it is removed if you delete the workspace);
• session records, which stay after sign-out;
• invitations, after they are used or expire;
• assistant conversations.

Your choices and contact

Write to privacy@getportdeck.com to ask what we hold about you, to correct it, or to have it deleted. Questions about the beta go to beta@getportdeck.com, and security issues to security@getportdeck.com. For data on your own install, you are in control: you can delete it there.

Changes

We will change this notice when the beta changes what it collects. The banner at the top of the page shows the date and the draft status.