← Hologram Pro
Privacy Policy
MirrorEthic LLC · effective 2026-10-07
The short version: your code and your project state never leave your machine, we
collect the minimum needed to sell and support licenses, and we don't sell or share data for
advertising.
What the software sends
- License validation: your license key, a hashed machine identifier, and the product
version, sent to our license service (a Cloudflare Worker) on activation and periodic recheck, and
when downloading updates from your licensed index. That is the software's only routine network use.
- Optional semantic memory: with the
[memory] extra, a one-time download of an
open embedding model. Recall itself never leaves your machine.
- Never: your code, prompts, files, graph, memory, blackboard, or any telemetry. The
complete inventory is published at FOOTPRINT.md, and the package carries a
test that fails if anything outside it is touched.
What we hold about you
- Purchases are processed by Polar (the merchant of record), who handle payment data
under their own policy; we receive your name, email, and order details to issue and manage your key.
- License records: your key (hashed at rest), plan, activation machine identifiers,
and validation timestamps, kept in Cloudflare KV for as long as the license is active and a
reasonable period after.
- Support email you send to
[email protected].
- Website: hologram-pro.dev is static, served by Cloudflare; we run no advertising or
cross-site trackers. Cloudflare's infrastructure logs (e.g. IP addresses) are handled under their policy.
How it's used, shared, and kept
Only to deliver the product, validate licenses, provide support, and process refunds. Processors:
Polar (payments), Cloudflare (hosting, license service, storage), our email provider. No sale of
personal data, no advertising use. To access, correct, or delete your data — or to ask anything —
write to [email protected]; we answer from the same records described above. The
product is not directed at children under 16. Material changes to this policy are announced in the
changelog with the effective date above updated.