Technical diagnostics explained

What this is

To keep LifeWeaver running smoothly and securely, we sometimes collect technical diagnostics. This is operational data about whether the system is working, not the content of your memories.

When we use it

We use de-identified or aggregated diagnostics in situations like:

• Reliability monitoring: making sure imports, uploads, and story generation succeed
• Debugging: finding and fixing bugs when something breaks
• Security: detecting unusual login attempts or abuse patterns
• Capacity planning: preparing for spikes in usage (for example, big events)
• Quality checks: measuring success rates and performance so features stay stable

Examples of diagnostics

These are the kinds of things we measure:

• Crash rate by app version
• Error counts and timeout rates (for example, when an import fails)
• Processing time for uploads or story generation
• Success and failure rates for features (import started, import succeeded, generation failed)
• Unusual sign-in patterns (to help prevent unauthorized access)

What this is not

Technical diagnostics are not used to:

• Read or mine your messages, emails, photos, or journal content for insights
• Build advertising profiles or target ads
• Sell your personal information
• Train general-purpose AI models using your private content

Who can access it

Access is limited to authorized personnel who need it for operations and security, and we restrict access based on role.

How long we keep it

Raw logs are kept only as long as needed for reliability and security. Aggregated metrics may be kept longer because they do not identify you and help us track system health over time.