Frequently asked questions

Questions families may ask before they begin.

Clear answers about how the family archive works, who can access it, and what to expect during public beta.

What is Memories for Tomorrow?

Memories for Tomorrow is a private family archive for preserving stories, photos, videos, audio, documents, family history, and legacy messages in one connected place.

Is my family archive private?

Family archive records and uploaded media are private. Access is controlled through authenticated family membership and database security policies. Private media is accessed through temporary signed links.

Who can see my memories?

Only people with access to the relevant family can view its archive. Family owners can manage access, while editor, archivist, and viewer capabilities follow their assigned roles.

What are legacy messages?

Legacy messages are personal written messages associated with a family member. They can be available immediately or scheduled for a specific future date. Owners, editors, and archivists can preserve messages, while delivery controls remain with owners and editors.

Can I invite family members?

Yes. Family owners can create private invitation links and assign an owner, editor, archivist, or viewer role. Invitation email automation is not currently included.

Can I upload photos, videos, and audio?

Yes. Owners and editors can create memories and upload supported photos, videos, and audio. Viewers have read-only access.

Can I use it on mobile?

Yes. The Expo mobile app supports authentication, family browsing, memory creation, media uploads, and media playback. Android beta testing currently uses a development build.

Are delivered messages public?

A delivered legacy message can be viewed without an account only through its unique, difficult-to-guess recipient link. Undelivered messages are not available through that public route, and the link does not expose the wider family archive.

Is this currently in beta?

Yes. Memories for Tomorrow is in public beta. Features, availability, storage practices, and policies may evolve as the service is tested and improved.