5 files changed, 195 insertions, 0 deletions
diff --git a/content/privacy/_index.md b/content/privacy/_index.md
new file mode 100644
index 0000000..e271ced
--- /dev/null
+++ b/content/privacy/_index.md
@@ -0,0 +1,13 @@
++++
+title = "Privacy"
+description = "Privacy policies for krazy warez iOS apps."
+sort_by = "weight"
+template = "section.html"
+page_template = "page.html"
+
+[extra]
+plain = true
++++
+
+Privacy policies for our iOS apps. The short version: we don't collect anything,
+there are no accounts, and your data stays on your device.
diff --git a/content/privacy/daybyday.md b/content/privacy/daybyday.md
new file mode 100644
index 0000000..92963a7
--- /dev/null
+++ b/content/privacy/daybyday.md
@@ -0,0 +1,41 @@
++++
+title = "Day by Day — Privacy Policy"
+description = "Privacy policy for Day by Day, the calendar-learning app for children."
+weight = 4
++++
+
+_last updated: 2 august 2026_
+
+Day by Day is an educational app that helps children learn days, weeks, months,
+and seasons. it is built to be safe for young children.
+
+## what we collect
+
+nothing at all. Day by Day has no accounts, no analytics, no advertising, no
+in-app purchases, and no third-party trackers or SDKs.
+
+## network connections
+
+none. Day by Day works entirely offline. it makes no network requests and sends
+no data anywhere.
+
+## data on your device
+
+any progress or settings stay only on your device and never leave it. deleting
+the app removes them.
+
+## children's privacy
+
+Day by Day is designed for children and does not knowingly collect any personal
+information from anyone, including children under 13. because the app collects
+no data and has no network access, there is nothing to share, sell, or expose.
+this is consistent with the U.S. Children's Online Privacy Protection Act
+(COPPA) and Apple's Kids Category requirements.
+
+## changes
+
+if this policy changes, the updated version will be posted here with a new date.
+
+## contact
+
+questions: [[email protected]](mailto:[email protected]).
diff --git a/content/privacy/domain-dig.md b/content/privacy/domain-dig.md
new file mode 100644
index 0000000..ac798a3
--- /dev/null
+++ b/content/privacy/domain-dig.md
@@ -0,0 +1,46 @@
++++
+title = "Domain Dig — Privacy Policy"
+description = "Privacy policy for Domain Dig, the DNS and SSL inspector for iOS."
+weight = 2
++++
+
+_last updated: 2 august 2026_
+
+Domain Dig inspects DNS records, SSL/TLS certificates, ownership, and related
+signals for domains you enter. every lookup runs from your device. we operate no
+servers, and we receive none of your data.
+
+## what we collect
+
+nothing. no account, no analytics, no ads, no third-party trackers or SDKs.
+
+## what stays on your device
+
+recent lookups and their results are stored locally on your device so you can
+revisit them. deleting the app removes the local copy. if you turn on iCloud
+sync (off by default), your settings, monitoring configuration, domain notes,
+and history metadata are stored in your own private iCloud account so they carry
+across your devices — that data goes to Apple's iCloud, never to us, and you can
+turn it off in Settings.
+
+## network connections
+
+to answer a lookup, Domain Dig queries public DNS resolvers and connects to the
+hosts you inspect in order to read their certificates. it also contacts a few
+third-party lookup services to enrich the results — an IP-geolocation provider
+(ipapi.co), RDAP registries (via rdap.org), Certificate Transparency logs
+(crt.sh), and the HSTS preload list (hstspreload.org). the domains and IP
+addresses you look up are therefore visible to these resolvers and services, and
+may be logged by them under their own policies. we do not see or record any of
+it.
+
+if you configure a Webhook or Slack integration, Domain Dig sends alerts to the
+URL you provide; that destination is chosen and controlled by you.
+
+## changes
+
+if this policy changes, the updated version will be posted here with a new date.
+
+## contact
+
+questions: [[email protected]](mailto:[email protected]).
diff --git a/content/privacy/hutch.md b/content/privacy/hutch.md
new file mode 100644
index 0000000..397f9dc
--- /dev/null
+++ b/content/privacy/hutch.md
@@ -0,0 +1,58 @@
++++
+title = "Hutch — Privacy Policy"
+description = "Privacy policy for Hutch, the Sourcehut client for iOS."
+weight = 1
++++
+
+_last updated: 2 august 2026_
+
+Hutch is a native iOS client for [Sourcehut](https://sr.ht). it talks to
+Sourcehut directly from your device. we have no user accounts, and we never
+receive your Sourcehut credentials. the one exception — a small first-party
+service used to draw contribution graphs — is described below.
+
+## what we collect
+
+we have no krazy warez account system, no analytics, no ads, and no
+third-party trackers or SDKs. the only data that ever reaches a server we
+operate is described under "the Hutch Stats service" below, and it is limited
+to the public Sourcehut usernames you ask to see contribution graphs for.
+
+## what stays on your device
+
+your Sourcehut personal access token is stored in the iOS Keychain on your
+device. cached repositories, tickets, and activity are stored locally so the
+app stays fast and works offline. deleting the app removes all of it.
+
+## network connections
+
+most of Hutch connects only to the Sourcehut instance you point it at — sr.ht
+by default, or a self-hosted instance you configure. those requests carry your
+access token, go straight to that server, and are governed by its own terms and
+privacy policy. we are not a party to that traffic and never see it.
+
+## the Hutch Stats service
+
+to render contribution graphs (the calendar-style activity charts on user
+profiles), Hutch asks a small first-party service, `hutch-stats.krz.sh`, for a
+person's public Sourcehut activity. this happens when you open a profile,
+including your own.
+
+each request sends the public Sourcehut **username** you are viewing and a date
+range. it does **not** send your access token or any Sourcehut credentials; the
+only header is a generic `Hutch/<version>` user-agent that contains no device or
+account identifiers. as with any web request, the service also sees the network
+(IP) address it came from. we use this data only to answer the request and do
+not build profiles from it or share it.
+
+if you would rather not use this service, contribution graphs are the only
+feature that depends on it. advanced users and self-hosters can point Hutch at a
+different stats endpoint via the `HUTCH_STATS_BASE_URL` setting.
+
+## changes
+
+if this policy changes, the updated version will be posted here with a new date.
+
+## contact
+
+questions: [[email protected]](mailto:[email protected]).
diff --git a/content/privacy/solar.md b/content/privacy/solar.md
new file mode 100644
index 0000000..d8b8626
--- /dev/null
+++ b/content/privacy/solar.md
@@ -0,0 +1,37 @@
++++
+title = "Solar — Privacy Policy"
+description = "Privacy policy for Solar, the Cloudflare client for iOS."
+weight = 3
++++
+
+_last updated: 2 august 2026_
+
+Solar is a native iOS client for [Cloudflare](https://cloudflare.com). it talks
+to the Cloudflare API directly from your device. we run no servers of our own,
+and we receive none of your data.
+
+## what we collect
+
+nothing. no krazy warez account, no analytics, no ads, no third-party trackers
+or SDKs.
+
+## what stays on your device
+
+your Cloudflare API token or key is stored in the iOS Keychain on your device
+and is sent only to Cloudflare. zone data such as DNS records, analytics, and
+settings that Solar fetches for display may be cached locally. deleting the app
+removes all of it.
+
+## network connections
+
+Solar connects only to Cloudflare's API. that traffic is governed by
+Cloudflare's own [privacy policy](https://www.cloudflare.com/privacypolicy/). we
+are not a party to it.
+
+## changes
+
+if this policy changes, the updated version will be posted here with a new date.
+
+## contact
+
+questions: [[email protected]](mailto:[email protected]).