Privacy Policy
Last updated: 2026-10-06
This policy covers the image-forge.net website, ImageForge purchases, and the ImageForge software itself. The short version: the software runs on your network and sends us only limited licensing data when you choose connected licensing features; purchases collect what a purchase needs; the website uses cookie-free traffic analytics and doesn't build a profile of you individually.
The ImageForge software
ImageForge is on-premises software. Your images, machine inventory, audit logs, technician accounts, and deployment profiles live on your Forge server and are never transmitted to us. The software may make these outbound connections:
- A daily check of a static version file, to show an update notice in your console.
- A daily fetch of a static license-revocation list.
- When a license activates, and daily while it remains active, a best-effort report containing a one-way hash of the license key, the Forge's hashed install ID, and the customer name embedded in the key. The raw key is never sent and a failed report never blocks licensed operation.
- Only when an administrator requests a self-service trial: the name and email entered in the trial form plus the Forge's hashed install ID. This is required to issue and node-lock the trial, and is not sent merely because the software was installed.
- While a self-service trial is installed, periodic validation sends a one-way hash of its license key and the Forge's hashed install ID. The service returns a vendor-signed active or expired status and authoritative check time. The raw key, images, inventory, and usage details are never sent.
The update and revocation checks are plain HTTPS downloads of public static files and carry no account or license identifier. Purchased keys still activate offline, and air-gapped installations remain supported with purchased licenses. The self-service trial requires a connection to start and at least once every 72 hours afterward while it remains active.
There is no image, machine-inventory, feature-usage, performance, crash, or advertising telemetry in the software.
Trials
For each self-service trial we retain the submitted name and email, the hashed Forge install ID, issuance and expiration times, and the signed trial key. Periodic status checks update the service's ordinary request logs but do not add image or feature-usage data to the trial record. We use this information to deliver and validate the trial, make retries safe, provide support, and enforce one trial per Forge install. It is not added to a marketing list.
Purchases
Payments are processed by Stripe; we never see or store your card number. After a purchase we retain a fulfillment record: your name (if provided), email address, the license key we issued, and the Stripe checkout session reference. We use your email to deliver the license key and for matters relating to your purchase — not for marketing lists.
Campaign links may include standard UTM parameters such as source, medium, and campaign name. If you submit a pilot request or begin checkout, those parameters are included with that request so we can tell which campaign led to it. They are not used to build a cross-site profile.
The website
We also keep daily aggregate counts of homepage views, trial and tester button clicks, installer link clicks, demo starts and endings, and accepted tester forms. The report covers the last 90 days; older counters are removed on the next event. Counters contain only the UTC date, event name and count. They do not include form contents, URLs, campaign values, IP addresses, cookies, install IDs or visitor identifiers. The browser skips these events when Do Not Track or Global Privacy Control is enabled. Counts cannot tell us whether a download completed, software was installed, or a deployment succeeded.
Download buttons pass through an ImageForge redirect before reaching the public Cloudflare download. We retain only aggregate counts by artifact and version; we do not add IP addresses, user agents, cookies, or other visitor identifiers to the download record. A count represents a request for a download, not a unique person or confirmation that the transfer completed.
image-forge.net uses Cloudflare Web Analytics to see aggregate traffic like page views and referrers. It's cookieless and uses no persistent client-side identifier — Cloudflare's own privacy policy for this product states it does not track individuals across websites over time. We don't use it to build a profile of any individual visitor. Campaign attribution is limited to UTM values already present in the page URL and is kept only for the current browser session. Our hosting providers (Netlify for pages, Cloudflare for downloads and web analytics) may keep standard access logs, and Stripe sets cookies during checkout per its own policy.
Tester and guided-evaluation requests
If you submit our form, Netlify processes the name, email and optional role, environment notes and setup-help preference you provide, along with any campaign attribution described above. We use this information to reply, arrange onboarding and understand your feedback. It is not added to a marketing list. You can request deletion by emailing contact@image-forge.net. Capture and deployment outcomes are shared by you during support; the software does not automatically report them.
Support email
If you email us (contact@ or licenses@image-forge.net), we keep the correspondence so we can help you, including in the future.
Your choices
You can request a copy or deletion of the purchase, trial, or support information we hold about you by emailing contact@image-forge.net. Note that we must retain records required for tax and accounting purposes, and the fulfillment record backing an active license for as long as the license is in use. We may retain a minimal anti-abuse record after deleting trial contact details so a completed trial cannot simply be reissued.
Changes
If this policy changes, the date above changes with it. Material changes will be noted on this page.