Workflow

Four steps from private memory to a public story page.

The archive stays bounded. Publishing is a single, deliberate export — and every link you share keeps working.

01

Capture and shape privately

Record voices, upload interviews, and collect fragments inside the app. AI helps organize them into memories and chapters without leaving the archive.

02

Approve the public version

Before publishing, Sipura assembles a sanitized snapshot — only the title, the narrative you've approved, and the media you've marked safe to share.

03

Publish to a stable page

Each story receives a permanent URL on sipura.space, ready for family, collaborators, or the public.

04

Revise without breaking the link

Republish a new approved version any time. As long as the slug stays the same, the URL doesn't change.

Guardrails

Boundaries that keep the private archive private.

Private by default

The archive lives on your device. Cloud features — backup, AI, publishing — are opt-in and scoped to what you explicitly invoke.

Publishing is deliberate

Public pages come from a sanitized snapshot you approve. They aren't a live mirror of your private edits, transcripts, or notes.

Safe-to-share only

Raw recordings, private relationships between people and places, and full edit history stay behind. Only the approved story reaches the web.