Twenty seconds in. A family history out.

Why twenty seconds is the whole design

Every family-memory product fails in the same place, and it is not the technology. It is that the unit of work is too large. A scrapbook needs a clear table and an afternoon. A memoir service needs somebody to write prose weekly. A proper oral-history interview needs a scheduling miracle and a level of emotional readiness on both sides that rarely coincides.

So the effort gets postponed to a quieter week, and the quieter week does not come. Then something changes — a diagnosis, a move, a death — and the window closes faster than anyone expected.

Twenty seconds is the length that survives a real week. It can be done in a kitchen with a child pulling at your sleeve. It needs no draft and no quiet room. That constraint is not a limitation of the product; it is the single decision the product is built around.

What the system does with what you give it

A recording is transcribed, so its words become searchable. Then it is examined for what it shares with the rest of your family's archive: recurring places, repeated traditions, and echoes — moments where two people described the same evening in almost the same words without ever comparing notes.

The result is that a search for a place returns a thread rather than a folder. A grandmother in 1972 saying her mother taught her the recipe the year she married; her daughter in 1995 learning it on a stool; a nine-year-old last summer being allowed to make the cookies alone. Nobody assembled that. Assembling it is the work the system is doing.

Some of this processing uses AI services inside our own cloud infrastructure — transcription, photo analysis, generated captions and insights. That is also exactly why we do not claim end-to-end encryption: content is encrypted in transit and at rest, but the system reads it in order to do that work, and claiming otherwise would be false.

Why the archive gives things back

Collecting is the easy half. Almost every product in this category is good at intake and silent afterwards, which is why so many family archives die at around week three — the effort is immediate and the payoff is promised to a generation that has not been born yet.

So KeepSaiQ returns things on a short loop. A ninety-second montage of last weekend. A recap the family actually opens, because it is made of their own week. A game whose questions come from your own photographs. Something arriving, made of everyone, is the most reliable way to pull in the family members who would never face a blank recording screen.

Who can see any of it

Only the family members you invite. There is no feed, no profiles, no followers, and no discovery surface — which means privacy is a property of the design rather than a setting you are responsible for defending as the product changes.

Your family's content is not used to train AI models, and the providers that process it do not use it to train theirs. Grouping photos by person is off unless you turn it on. Deleting a voice recording purges it within minutes along with its transcript, and deleting your account runs the same erasure across everything you added.