What we collect, why, and how long we keep it.
In plain language, not legalese. This policy may change; the 'Last updated' date shows when.
Last updated: 2026-11-20. This policy applies to computeforge.com, www.computeforge.com, the forgepanel.computeforge.com control panel, the cf CLI, and the agent you install on your servers.
What we collect
Account information
Your e-mail address (required for login and notifications). An optional display name. A phone number, if you give us one. We do not collect government IDs.
Billing information
For paid tiers: payment data is held by our payment processor, not by us. We retain only the last four digits of the card and the billing address you supplied for invoicing.
SSH key fingerprints
Public keys (and their fingerprints) you upload for VM access. We use these only to provision the keys onto VMs at your request. We never see private keys.
Agent telemetry from your VMs
The agent installed on your connected VMs records changes to tracked files (time, path, operation, size, permissions, owner, a content hash, and which process, user and login session made the change), package installs, upgrades and removals, service state changes, listening ports opening and closing, and local user and group changes. By default it tracks system configuration and software locations (/etc, /usr/local, /opt, cron spools, SSH authorized_keys), not home directories, logs, temporary or data directories.
We store the full text of tracked text files up to 1 MiB in /etc, /usr/local/etc, /opt/*/etc, cron spools, authorized_keys and scripts in /usr/local/bin, so cf show /path @{time} works; other tracked files, binaries and larger files are kept by hash only. If you add your own tracked paths and mark them to record content, text files there are stored the same way. We do not collect file contents from outside the tracking set, except that a security scan you start (cf scan) may upload encrypted copies of suspicious files it finds.
Files recognized as secrets (private keys, password databases such as /etc/shadow, .env files, credential files, and any file containing a private key or a recognized access token) are never stored: the agent records only a keyed fingerprint that shows they changed. A password written into an ordinary configuration file is not recognized as a secret, so exclude such files if you track them. If you move a server with cf push (in testing, not open to every account yet), files travel to the new server inside an encrypted stream between the two servers; our relay sees only ciphertext.
On ComputeForge servers, we also hold the snapshots, backups and server archives you create — the same data your server's disk holds.
Operational logs
Web server access logs (IP, request path, status code, timestamp) for computeforge.com and the panel — kept indefinitely, for security and debugging. Panel-side action logs (which user clicked what, what API call resulted) — kept indefinitely as part of the usage data below, and exported to your activity log if relevant to your account.
Outbound mail you send
Sending e-mail from servers is not open to every account yet. Where it is open to you, we check every message that goes out through our mail relay (signed in on port 587 or 465, or routed from your server's port 25) before it is delivered, to stop spam, phishing and malware leaving our network:
- Automatic checks. The message's text, attachments and links go through a spam filter (SpamAssassin), a virus scanner, lists of known bad web addresses, and an AI model that runs on our own servers. Shortened links (bit.ly and the like) are followed to see where they lead; other links are not opened.
- Images. Images attached to or embedded in a message may be checked as well, including the text inside them. We don't accept mail that loads images from remote addresses, because that is a common spam and tracking technique; attach or embed images instead.
- Review of flagged mail. A message the checks flag, a held message you ask us to release, and a message someone complains about may be read by an automated AI reviewer. It sees the subject, the sender, the number of recipients, up to 2 KB of the text, the web addresses of links and the names of attachments. It runs on our own servers first; only if they are unavailable does it use an outside AI provider that does not keep the data (see Subprocessors). Our staff may also look at a held message to decide on it.
- Bulk-campaign detection. To spot the same message sent to many people, we may keep short-lived fingerprints of message content and salted hashes of recipient addresses, not the text itself, for about 7 days.
- Improving our filters. We keep each message's check results and scores, may keep hashed word-pattern features that cannot be read back as text, and may train our own filtering models on them. They stay on our servers.
What we keep. A copy of each message we check: its sender and recipient addresses, headers, subject, text and attachments, with the result of the checks. We keep it on our own servers to handle complaints, investigate abuse and improve our filters. We do not use it for advertising and we do not sell it. Outbound messages sent through our relay are stored for delivery, abuse and spam review, and are visible to the account holder (on the Email activity page of the panel) and to our staff.
Mail sent to you: inbound filtering and ComputeForge Mail
Inbound filtering and ComputeForge Mail mailboxes are not open to every account yet. Where they are open to you, we scan incoming messages automatically to protect you from spam, phishing and malware: spam and virus filters, lists of known bad senders and web addresses, and AI models that run on our own servers. No outside AI provider reads mail sent to you. The servers that receive and filter your mail are run by us; some of them are in third-party data centers. There, a message is handled in memory while it is received and filtered, anything written to disk is encrypted with a key held only on our own servers, and filtered mail is passed on to our own servers.
- What we keep, and for how long. We keep quarantined messages and copies of delivered messages for the retention period you set for each domain, from 0 to 7 days (7 by default), and none at all for senders, domains or addresses you mark as no-retention. When that period ends the copies become unreadable everywhere, including our backups, within 24 hours. Activity records (time, sender domain, recipient, verdict, size; no message content) are kept for the period you set, up to 13 months, or not at all.
- Your mailboxes. Mail you keep in a ComputeForge Mail mailbox stays until you delete it. Once it has left your deleted items it leaves our backups within 30 days, and mail filed under a no-retention rule is never backed up. Mailboxes are stored encrypted on our own servers. We also keep an encrypted off-site copy in a third-party data center: it is stored only as ciphertext, the keys to it are not kept there, and mail is never served from it.
- Improving our filters (you can turn this off). We use the results of scans and your reports, never the content of your messages, to improve our filters for all customers: numeric features, labels and hashed word pieces that cannot be read back as text. This is on by default; an organization admin can turn it off for the whole organization in the panel, and then none of your mail feeds our training. If you set a domain's retention to 0, we learn only from messages your users report.
- Who may read a message. Your organization's admins can see your own quarantine and kept copies; mailbox users see their own. Our staff do not read your messages except when you ask us to, to investigate abuse, or when the law requires it, and every such access is logged and shown to you in the domain's audit log.
Messages you send us
What you write in our contact form, with the e-mail address and name you give, goes into our help desk so that a person can handle it. Nothing is sent to you automatically.
Sign-up and payment screening
To protect our customers and ourselves from fraud, we screen sign-ups and payments automatically, using signals such as your IP address, its approximate location and your browser. A sign-up can be flagged automatically. Card payments go through our payment processor's checks.
Usage data
To run and improve ComputeForge we record how our website and panel are used — for example which pages you visit, the steps you complete, your IP address and browser, and the outcome of sign-ups, server creation and payments — and we link this to your account.
Why we collect it
Account and billing data: to operate your account and bill you. SSH keys: to do what you ask us to. Agent telemetry: to power cf log, cf diff, cf blame, and the rest of the version-control verbs — these literally cannot work without the change stream. Web logs: to detect abuse, debug issues, and meet our obligations under abuse-reporting law.
We do not sell customer data. We do not run analytics SDKs from third parties on the panel. We do not embed third-party trackers in the product. The one thing we tell an advertising company is described under "Google Ads measurement" below. We pay service providers to process some data for us, in standard processor relationships, and they get only the data required to do their job: payments, e-mail delivery, DNS and the bot check on sign-up, fraud screening, a fallback for reviewing flagged outbound mail, and encrypted storage for object storage and backups. The Subprocessors section below says what each one receives.
Google Ads measurement
If you sign up after clicking one of our Google ads, we keep that ad click's identifier with your account. When you sign up, when you add a card, and when you pay an invoice in your first 90 days, we report it to Google Ads: the click identifier, which of those things happened, when, and for a payment the amount. That tells us which ads work. We do not send Google your name, your e-mail address or anything else from your account.
The click identifier reaches us through a cookie. When you arrive on this website from one of our ads, a small script on our own pages saves the identifier in your browser as a cookie called secmx for computeforge.com and its subdomains, for 90 days. If you sign up within that time, the sign-up page reads it and we keep it with your account. The cookie holds only that identifier, and it is only set when you arrive from one of our ads. The script is our own: no Google code, tag or pixel runs in your browser, and nothing is sent to Google from your browser. The reports to Google Ads described above come from our servers. You can delete the cookie in your browser's settings at any time.
Do Not Track
Our website and panel do not respond to browser Do Not Track signals: they work the same way whether or not your browser sends one. Apart from the Google Ads measurement above, we do not track you across other companies' websites, and we do not let advertising or analytics companies track you through ours. What we record about the use of our own website and panel is described under "Usage data" above. A few pages load a provider's script so it can do its job: our payment processor's on the pages where you enter a card, and our DNS provider's bot check on sign-up and password reset. Those providers handle what your browser sends them under their own privacy policies. This website's typefaces are served from our own server.
How long we keep it
Agent change history: kept for 90 days. When you remove a server from the panel (Remove machine), its history is deleted 30 days later. Revoking its agent keeps the history.
Snapshots and backups: nothing is snapshotted automatically by default. A snapshot you take, or an archive you make, is kept until you delete it. Backups, if you switch them on for a server, follow the schedule and retention you choose.
Operational logs: web access logs are kept indefinitely. Panel action logs and usage data are kept indefinitely. The account audit log is kept for the life of your account.
Outbound mail we check: the copy of each message and the result of its checks are kept indefinitely, like our other operational records. A held message stays held until it is released or refused. Bulk-campaign fingerprints and recipient hashes, where we keep them, are kept for about 7 days.
Mail sent to you (inbound filtering, ComputeForge Mail): quarantined messages and kept copies for the retention you set per domain, 0 to 7 days, then unreadable everywhere within 24 hours; activity records up to 13 months as you set; filter-training features and labels (no text) up to 13 months; mailboxes until you delete them, then out of our backups within 30 days. Details in Mail sent to you.
Your rights
Regardless of where you live, you have the right to: access the data we hold about you (the panel already shows most of it), export it in an open format (we'll help if the panel doesn't already do it), correct anything that's wrong, and delete your account along with the data we control. Send any of these requests through our contact form with the topic "Privacy or data request".
Customers in the EU/UK have GDPR rights including data portability and the right to lodge a complaint with a supervisory authority. Customers in California have CCPA/CPRA rights including the right to opt out of "sale" — which is moot here because we don't sell data, but the right exists.
Subprocessors
Payment processor — payment processing. Receives card data and billing address. DNS provider — DNS for computeforge.com. It answers DNS lookups for our names; it does not carry our web traffic. Its bot check runs on the panel's sign-up and password-reset pages and receives what your browser sends it there. Fraud-screening service — fraud screening of sign-ups and card payments. Receives your IP address and browser details, your e-mail address in hashed form, your name, company and phone number, your billing and account addresses, and your card's country and last four digits. E-mail delivery service — e-mail (sign-in codes, invoices, notifications). Receives e-mail address and message body. AI review fallback — AI review of flagged outbound mail, used only when our own AI servers are unavailable. Receives what the reviewer sees (see "Outbound mail you send" above) for that one review, under terms that it does not keep it. ARIN (the American Registry for Internet Numbers) — when IP address allocation requires it, we share your contact details. Encrypted storage infrastructure — object storage and server backups are kept with a US storage infrastructure provider. Everything we send it is encrypted on our own servers first: contents, file and bucket names, and which customer it belongs to. The provider never receives a key and cannot read any of it; it sees only encrypted data, its size, and when our servers store or fetch it. Business customers can get the provider's name under our data processing agreement.
Some of our own systems run on servers we rent outside our datacenter: our off-site secondary nameserver (ns2.computeforge.com), which holds a copy of the DNS zones you host with Forge DNS, and our status page (status.computeforge.com), which only checks whether our services answer.
Security
Encryption in transit: this website, the panel and the API are served over TLS. Two-step sign-in (authenticator app, passkey or e-mailed code) is available for the panel, and an organization can require it for its members.
Changes to this policy
We'll update this page when our practices change; the "Last updated" date at the top shows when.
Contact
Privacy issues, requests or complaints, security issues and anything else: write to us with our contact form and choose the topic. Customers can also open a ticket from the Support page in the panel.