privacy

the timeline details you set up — a title, description, and owner name.

each memory you add — a title, date, description, who contributed it, the people and tags mentioned in it, and its approval status.

any photos you attach to a memory — the file itself, plus alt text and when it was taken, if you provide those.

who you invite and how — a role (admin, contributor, or viewer), an invited person's name, and, for contributors, an optional email.

your browser locally remembers your display name and any in-progress, unsaved memory draft you're typing, so you don't lose it if you navigate away.

accepting an invitation sets a session cookie in your browser that keeps you signed in to that timeline for up to 30 days. it's how the app recognizes you on return visits — not a tracking or analytics cookie.

showing your family or friend group the timeline of memories they've contributed, and letting each contributor add or comment on their own.

sell your data, run ads against it, or make any memory or photo public — everything requires an invitation link to see.

in a private, access-controlled postgres database. photos live in a private storage bucket and are only ever served through short-lived, signed links — there is no public URL for any photo you upload. access to a timeline is granted through invitation links with hashed tokens, not a public account system.

if you open memory timeline from homebase, your homebase account email is shown in that session's page header only — memory timeline doesn't store it.

remove a memory, a photo, or a contributor's access any time from the admin page. email me if you want a timeline's data gone for good.

email hello@theafoundry.com.