---
title: "Alfred Chaos (@alfredchaos) | Hashnode"
description: "Indie dev building Mori, a privacy-first period tracker. No account, offline, one-time purchase. Read the latest articles by Alfred Chaos on Hashnode."
url: "https://hashnode.com/@alfredchaos"
---

@alfredchaos

# Alfred Chaos

@alfredchaos · Joined October 2026

Indie dev building Mori, a privacy-first period tracker. No account, offline, one-time purchase.

### [An export is a promise the app has to keep after you leave](https://alfredchaos.hashnode.dev/an-export-is-a-promise-the-app-has-to-keep-after-you-leave?utm_source=hashnode&utm_medium=feed)

Every app claims your data is yours. The claim is testable in about ten minutes: ask for a copy, then try to live without the app for a day. For a period tracker the copy matters more than usual. The

3 min read · [alfredchaos.hashnode.dev](https://alfredchaos.hashnode.dev/an-export-is-a-promise-the-app-has-to-keep-after-you-leave?utm_source=hashnode&utm_medium=feed)

[19h ago](https://hashnode.com/posts/an-export-is-a-promise-the-app-has-to-keep-after-you-leave/6b022fc34dbbc85c2d16b2e0)

### [The tests we run on period math](https://alfredchaos.hashnode.dev/the-tests-we-run-on-period-math?utm_source=hashnode&utm_medium=feed)

Most bugs in a period tracker are not visual bugs. They are one day off. Someone logs a period at 11:40 pm on March 1. Stored as a timestamp and rendered somewhere else, that date can come back as Feb

3 min read · [alfredchaos.hashnode.dev](https://alfredchaos.hashnode.dev/the-tests-we-run-on-period-math?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/the-tests-we-run-on-period-math/6af8f620cece34ca42326c8b) [Nov 15](https://hashnode.com/posts/the-tests-we-run-on-period-math/6af8f620cece34ca42326c8b)

### [Why our predictions only look at your last six cycles](https://alfredchaos.hashnode.dev/why-our-predictions-only-look-at-your-last-six-cycles?utm_source=hashnode&utm_medium=feed)

If you've logged periods for three years, an app has thirty-something cycles of history to work with. Which of those should the next prediction use? We cap the window at your six most recent cycles. T

3 min read · [alfredchaos.hashnode.dev](https://alfredchaos.hashnode.dev/why-our-predictions-only-look-at-your-last-six-cycles?utm_source=hashnode&utm_medium=feed)

[Nov 7](https://hashnode.com/posts/why-our-predictions-only-look-at-your-last-six-cycles/6aefbb1114e178ab059b1a89)

### [Why my period tracker counts days, not seconds](https://alfredchaos.hashnode.dev/why-my-period-tracker-counts-days-not-seconds?utm_source=hashnode&utm_medium=feed)

A while ago I looked at how health apps store "the period started today" and felt a small chill. Most of them store a timestamp: 2026-11-01T22:15:00Z. Seconds since epoch. Precise, sortable, and quiet

3 min read · [alfredchaos.hashnode.dev](https://alfredchaos.hashnode.dev/why-my-period-tracker-counts-days-not-seconds?utm_source=hashnode&utm_medium=feed)

[Nov 1](https://hashnode.com/posts/why-my-period-tracker-counts-days-not-seconds/6ae68618c3e570c0ef35137c)

### [We couldn't call it "end-to-end encrypted," so we wrote down exactly what it is](https://alfredchaos.hashnode.dev/we-couldn-t-call-it-end-to-end-encrypted-so-we-wrote-down-exactly-what-it-is?utm_source=hashnode&utm_medium=feed)

Every app claims end-to-end encryption. Ours can't — so we wrote down exactly what the server can and cannot read.

4 min read · [alfredchaos.hashnode.dev](https://alfredchaos.hashnode.dev/we-couldn-t-call-it-end-to-end-encrypted-so-we-wrote-down-exactly-what-it-is?utm_source=hashnode&utm_medium=feed)

[Oct 24](https://hashnode.com/posts/we-couldn-t-call-it-end-to-end-encrypted-so-we-wrote-down-exactly-what-it-is/6add4600e9d4ec95af462b4a)
