Privacy
Small list, plainly stated
What we collect, why, and what we deliberately do not do. This page is written by the people who built the forms, not adapted from a template.
01What we collect, and why
Release notifications. When you ask to be notified about an image, we store your email address and which image you asked about. We use it to send release notes and availability updates for that request. Every email includes an unsubscribe link, and unsubscribing removes you from the list.
Contact form. Messages sent through the contact form carry your name, email, message, and — only if you provide them — your company, interest area, and cloud preference. We use them to reply to you, and for nothing else.
Page analytics. The site uses Google Analytics 4 to count page views and see which pages help people find what they came for. It records the page you viewed, how you arrived, your browser and device type, and an approximate location derived from your IP address, which Google does not store. Advertising features are off, and we do not join analytics data to anything you type into a form. Details are in the analytics section below.
That is the whole list for this site. Browsing the catalog and every image page requires no account. Buying an image through a marketplace is separate, and is covered in the next section.
02Marketplace purchases
When you obtain an image through AWS Marketplace or Azure Marketplace, that marketplace gives us, as the publisher, the contact details recorded against your purchase — typically your name, email address, company and country. We do not choose what is sent and we cannot turn it off; it is how a marketplace tells a publisher who bought what.
We use it for three things: fulfilling the purchase, answering your support requests, and telling you about security fixes for the image you bought. We do not add you to a marketing list, and we do not use it to sell you anything else.
The purchase itself is the marketplace's transaction, not ours: it takes the payment, issues the invoice, and its own privacy policy governs how it handles your data. The details it passes to us are kept as ordinary business records and removed on request, exactly as described under retention below.
03Analytics, cookies and local storage
Google Analytics sets two first-party cookies on this domain, _ga and _ga_*, so that a returning visitor is counted once rather than as a new person on every page. They carry a random identifier, not your name or email. Google processes this data on our behalf under its partner sites terms, and keeps it for the retention period set in our Analytics property; we do not export it anywhere else.
If you would rather not be counted, the Google Analytics opt-out add-on or any content blocker stops the tag, and every page of this site works exactly the same without it.
One further cookie exists on this domain and it belongs to our internal admin panel; it is only ever set for our own staff signing in, never for visitors. Your light/dark theme choice is kept in your browser's local storage, on your device. It never leaves it.
04What we deliberately do not do
No ad pixels, no session recording, no fingerprinting, no advertising identifiers. Page analytics is the only third-party service on the site, and it is described above in full. Fonts are self-hosted, so page loads make no requests to font networks. We do not sell, rent, or share your details with anyone — including the details a marketplace passes to us — and we never will as a business model: we sell machine images.
05Retention and removal
Notification emails are kept until you unsubscribe or the updates for your request have been sent. Contact messages, and the purchase details a marketplace passes to us, are kept as ordinary business records. Analytics data is aggregate and expires on the schedule set in our Analytics property. To have anything removed, email [email protected] and we will delete it and confirm — no form, no waiting period.
06Questions
Anything unclear, or a practice you would like documented here in more detail? Ask us — a real engineer answers, and this page gets updated rather than lawyered.