# i9 Privacy Policy

*Effective date: October 1, 2026*
*Last updated: October 10, 2026*


---

## What i9 collects

### Telemetry (opt-out)

When i9 streams an image from a.i9.io, the first request of that restore
carries three facts: your operating system, your CPU architecture, and
the i9 version. That is the whole beacon.

It carries **no identifier**. There is no install id, no account id, no
hostname, no username and no hardware fingerprint, and nothing is written
to your machine for telemetry to read back later. i9 does keep a signing
key under `~/.i9`, used so that archives you create are attributable to
your own installation; it never leaves your machine and is not part of the
beacon. Two runs on the same computer are
indistinguishable from two runs on different computers, and neither can
be connected to you.

| Setting | What's sent | How to set |
|---|---|---|
| `telemetry.enabled = true` (default) | OS, architecture, version — on an image fetch | `i9 config set telemetry.enabled true` |
| `telemetry.enabled = false` | Nothing | `i9 config set telemetry.enabled false` |

`DO_NOT_TRACK=1` in the environment opts a single invocation out.

At our edge, each request that is part of the launch funnel writes one
analytics data point: which step it was (landing, installer, agent page,
download, image fetch), which public asset or image it concerned, the
three facts above, and a timestamp. We do not store your IP address and
we keep no location data, user agent, or identifier, so a data point
records *a request* and cannot be tied to you or to your machine.

Each ranged read of a published image writes one more data point: which
image line and version it was, your operating system and CPU
architecture, and which part of the image was read (the byte offset and
length). We read these only summed across everyone, to learn which parts
of an image restores actually need. They carry no identifier, so they
cannot be grouped by person, machine or run.

We read them only in aggregate — counts per platform, version and funnel
step. The analytics store (Cloudflare Workers Analytics Engine) keeps
them for its own bounded retention window and then deletes them; we keep
no copy anywhere else.

Telemetry does **not** include: anything inside the virtual machine, the
commands you ran in it, file paths, project names, or personally
identifiable information. The beacon does not say which image you ran; the
edge records which published image line the request was for, from our own
fixed list.

### Why there is nothing to request erasure of

GDPR rights attach to personal data: information that can single out a
person, directly or through an identifier held alongside it. The beacon
is built so that no such information reaches us. It carries no
identifier, we store no IP address and no location, and the analytics
data points described above hold only closed sets of values — a step
name, a platform, a version — with nothing in them that points back to a
person or a device.

So a subject-access or erasure request has nothing to match: there is no
record of your machine to find, amend or delete — not because we decline
to look, but because none was ever created. The same property is why the
beacon can default to on: storing an identifier on your device and
reading it back later would need your consent under the ePrivacy
Directive (Art. 5(3)), and we store nothing to read back.

This covers the default beacon only. Anything you choose to send us
explicitly, such as an attachment on a support request, is covered by the
sections below.

The sections below state what the binary sends. The edge data point is
the eight fields the Terms list: the funnel step, which published image
line the request concerned, the name of the public file if one was
downloaded, your operating system, CPU architecture and i9 version,
the format it was served in, and a timestamp. The image-read data point is the image line,
version, operating system, CPU architecture, byte offset and length. None
identifies you or your machine; each named value comes from a fixed list
rather than from text your machine supplies, and the offset and length are
numbers.
`i9 docs DATA-HANDLING` prints the same in operational terms, offline.

## What i9 does NOT collect

- Your files, or anything inside a virtual machine you run
- The commands you run in a guest, or their output
- Which image you ran, or any name you gave a machine or snapshot
- File paths, directory structures, or repository URLs
- Raw error messages or stack traces
- IP addresses (the server sees one in transit; it is not stored)
- Hardware fingerprints or machine identifiers

---

## Identity

- **No telemetry identifier at all**: the beacon carries no install id,
  and nothing is stored on your machine for telemetry to read back later.
  There is nothing to reset for telemetry, because nothing is kept for it.
  The signing key described above is read back, to sign archives you
  create; it reaches no one.
- **No accounts**: i9 does not require registration or login.
- **No tracking across devices or across runs**: with no identifier, two
  runs cannot be linked to each other, on one machine or across many.

---

## Local discovery

i9 makes no announcement on your local network, and opens no port that
your network can reach. A session started with `i9 run --session` listens
on `127.0.0.1` and is reachable from this machine only; a guest port is
reachable from elsewhere only if you forward it yourself.

---

## Your rights

- **Opt out of the telemetry beacon**: `i9 config set telemetry.enabled
  false` for good, or `DO_NOT_TRACK=1` for one invocation
- **Send nothing at all**: run an image already on your disk. With no
  remote fetch there is no request to carry a beacon
- **Delete everything i9 holds**: stop any running VM, then `i9 uninstall
  --force` (`i9 uninstall --dry-run` first lists all of it and removes
  nothing). Plain `i9 uninstall` removes `~/.i9/`, the agent wiring, and
  the per-run state in `/tmp` and under `$TMPDIR`, but refuses while
  saved snapshots, session traces or the secrets store exist; `--force`
  deletes those too
- **Questions, or a request about anything you sent us explicitly**:
  email privacy@i9.io. The default beacon leaves us no record of your
  machine, so there is nothing for us to look up from it.

---

## Traces are yours and stay local

A run writes a trace under `~/.i9`. i9 never uploads one: there is no
upload path in the product, so we hold no trace of yours to disclose,
correct or delete.

Because the file is yours, removing it is a local operation. `i9 archive
ls` lists what is on your disk, `i9 archive rm` deletes one, and deleting
`~/.i9` removes all of them along with every image and snapshot. For
removing specific content from an archive you intend to keep, see
`i9 archive redact` and `i9 archive purge` in `i9 docs cli`.

If you have passed an `.i9io` archive — the file format a snapshot and
its trace are stored in — to someone else, that copy is outside your
control and outside ours; nothing in i9 reaches it.

---

## Email you send us

Mail to support@, security@, privacy@ or legal@i9.io is received and stored
by Google Workspace, our mail provider. We keep a message, with the address
it came from and anything attached, for as long as we need it to answer you
or as the law requires, and delete it when you ask unless we must keep it.

---

## Feedback you send

<https://feedback.i9.io> accepts a text you choose to submit. We store that
text with the time it arrived, the user agent your client sent, and the
i9 version and agent name if your client sent them, in Cloudflare R2. We
do not store your IP address with it. Each stored text is deleted
automatically 60 days after it arrives.

To limit abuse, the service keeps a one-way hash of the start of your
network address, salted and changed every day, so it can count posts per
day. The hash cannot be turned back into an address and is deleted within
two days. Feedback is anonymous: no reply is sent, and there is no account
to look it up by. To ask us to delete a text before then, email
privacy@i9.io with its text or the id the service returned.

---

## Purchases

Nothing is sold today — grants are free. `i9 grant request` sends
nothing beyond the request itself; `i9 grant renew` sends the grant id,
to https://i9.io/grant. A feature request (`i9 grant request --feature
<id>`) sends the feature id, and the grant id when the machine holds
one, to the same endpoint; the issuer records the feature id, the grant
id and the time, and no IP address.

The remainder of this section is kept as the record of the paid-sales
design (Stripe Link as reseller and merchant of record) that the
free-grant surface replaced. It describes a purchase flow that is not
currently operating, and would apply again only if paid sales return:

Grants were to be sold through Link, a Stripe service, as reseller and
merchant of record, using Stripe Checkout. Stripe would receive your
payment details, email address and billing address (used to work out
sales tax or VAT) and process them under its own privacy policy; we
would never see your card number. We would keep, for each purchase,
which pack was bought, when, the grant token issued, the Stripe
Checkout session id, which links the token to Stripe's record of the
payment, and, if the payment was refunded instead, why. That record
would be deleted 30 days after the grant expires; a checkout that was
never paid would be deleted after 7 days. Stripe and the law may
require payment records to be kept longer, in Stripe's systems.

---

## Third parties

| Service | What they receive | Their policy |
|---|---|---|
| Cloudflare | The requests that reach i9.io, a.i9.io and feedback.i9.io, as our infrastructure provider: it serves the images, operates the analytics store described above, and stores feedback | https://www.cloudflare.com/privacypolicy/ |
| Google (Workspace) | Email you send to an i9.io address, as our mail provider | https://policies.google.com/privacy |
| Stripe (including Link) | Your payment details, email address and billing address if a paid grant sale happens — no paid sales are operating today (see Purchases) | https://stripe.com/privacy |

Cloudflare and Google process this data on our behalf and under our
instructions. Stripe's row records the dormant paid-sales design: as
merchant of record for grants it would process payment and tax data as an
independent controller when paid sales operate.
Beyond that, Kurosea, Inc. shares telemetry data with no one, and sells it to no
one.

No command contacts anyone but i9.io and a.i9.io, which serve these pages
and the virtual machine images.

---

## Children

i9 is not intended for use by individuals under 16.

---

## Changes

We may update this policy. The current text is always the one served at
<https://i9.io/privacy>, and each release carries the text that was current
when it was built, readable offline with `i9 docs`. Continued use after changes
constitutes acceptance.

---

## Who is responsible, and how to reach us

Kurosea, Inc., a Delaware corporation that operates i9 and i9.io, is the
controller for the data described in this policy; its postal address is on
<https://i9.io/vm/contact>. Write to privacy@i9.io with a privacy question
or request, or to legal@i9.io for notice under the Terms of Service.

As set out above, the default telemetry stores no identifier, no IP
address and no location, so there is no record of your machine for us to
retrieve, correct or delete in response to a request.
