FAQ: Digital Legacy, Secure Access, and Family Continuity

Solexi is designed as a digital legacy platform: a structured place to store important digital materials such as memories, documents, and instructions, and to define controlled access for trusted people over time.

• Vault: organize files and narratives in a private structure.
• People & permissions: define who can access what and when.
• Delivery: future messages or instructions when conditions are met.

1. Create your private vault.
2. Add content such as photos, videos, documents, letters, and instructions.
3. Map trusted people and define permissions.
4. Set rules such as dates, milestones, or verified events.
5. Review and export so you keep control and portability.

No. Genealogy sites focus on discovering historical records. Solexi focuses on organizing modern digital legacy materials and controlling private access.

• Genealogy: records, archives, historical discovery.
• Solexi: private vault, permissions, future delivery, and continuity logic.

• Individuals: keep important materials structured and private.
• Families: reduce confusion and centralize what matters.
• Creators: preserve work, context, and instructions.
• Trusted contacts: receive controlled access when needed.

A trustworthy legacy system should document security controls clearly. Users should know how data is protected, who can access it, and how events are logged.

• Encryption in transit: TLS/HTTPS for network protection.
• Encryption at rest: encrypted storage for vault content.
• Strong authentication: support for MFA and secure recovery flows.
• Least privilege: permissions scoped by person, content, and time.
• Auditability: access logs and change history.

The answer depends on the architecture implemented. If a zero-knowledge model is used, the service cannot read content without user-held keys. If standard cloud encryption is used, restricted access may still exist in defined support or legal scenarios.

This should always be described transparently on the security page.

A modern service should state what data is collected, why it is collected, how long it is retained, how deletion works, and what remains in backups.

• Collection: account information, uploaded content, and security logs.
• Purpose: delivering the service, preventing abuse, and improving reliability.
• Retention: clear timelines and definitions.
• Deletion: a clear explanation of what delete means in practice.

See Privacy Policy and Security.

You define who can access what, when, and how.

• Date-based: release on a specific date.
• Milestone-based: release when a person reaches a defined milestone.
• Verified event: release after a validated event.
• Inactivity: release after a defined period without login.

Best practice is to support granular permission levels such as view-only, download, contribute, or administer. Preservation-first defaults are often safer unless edit rights are explicitly granted.

Yes, if the system supports trusted roles. Limited access can be assigned to an executor, lawyer, or designated contact for verification and controlled release.

If enabled, AI features should help users organize, search, summarize, or navigate content they have already chosen to preserve. They should remain optional and controlled by clear permissions.

Sensitive legacy content should not be used for public model training unless users explicitly opt in. The exact answer should be stated clearly in the privacy and AI policy pages.

See Privacy Policy and AI Policy.

In practice, AI search can mean better retrieval: semantic search, tagging of people or places, and summaries that link back to the original source material.

Pricing typically depends on storage, collaboration features, number of trusted contacts or heirs, and optional premium features.

• Starter: personal vault and essentials.
• Family: more storage and shared access.
• Pro: advanced governance and support.

See Pricing.

If the platform is in an early-stage release, a waitlist is often the cleanest approach to offer guided onboarding and phased access to core features.

Join the Waitlist

A credible digital legacy platform should support export paths such as a ZIP archive of uploaded files, human-readable summaries, and structured metadata export where available.

See Export documentation.

This is a critical trust question. Strong answers include documented export windows, continuity planning, and clear retention timelines.

No. Software can help organize information and express instructions, but legal advice requires a qualified professional. Estate planning decisions should be reviewed with counsel where appropriate.

Only frameworks that are truly supported should be listed publicly. If compliance work is still in progress, the language should clearly say so.

See Privacy, Security, AI Policy, and Terms.

It means fast pages, clear structure, helpful answers, accessible HTML, and structured data that matches visible content. The goal is to help real users first, while also making the page understandable to search engines and AI systems.

• Technical SEO: speed, semantic headings, crawlable links, clean HTML.
• Content SEO: direct answers about what, how, cost, security, export, and privacy.
• AI visibility: structured and factual content instead of keyword stuffing.