Privacy policy

This policy applies to Lumivora's private beta, including browser use, installed-app use, and any downloadable build or app-style distribution used for testing.

It covers the information Lumivora collects, why it is collected, how it is used, and the practical choices available to beta users.

Lumivora collects the information needed to run the beta, secure accounts, and understand whether the product is actually useful.

• Account and profile data such as display name, email address, timezone, and preferences.
• Workspace data such as projects, milestones, wins, focus-session activity, and related timestamps.
• Structured beta feedback such as clarity, friction, execution-value ratings, and short comments submitted inside the product.
• Technical and security signals such as auth-throttle events, monitoring events, performance timings, app mode, and analytics events tied to product usage.
• Device-side data needed to keep the installed shell working, such as cached assets, session state, and install-state checks.

Lumivora uses beta data to operate the app, protect the service, improve clarity and execution flow, and decide whether the product is ready for broader use.

• To create and secure user accounts.
• To save and sync workspace data across sessions.
• To monitor reliability, diagnose failures, and understand performance problems.
• To measure product direction, install behavior, repeat use, and execution value during beta.
• To review structured feedback and decide what must change before wider rollout.

When Lumivora is installed or opened from an app-style shell, some files and session data may be stored on the device so the product opens faster and behaves more like an app.

Removing the installed shell or deleting browser storage clears device-side data on that device, but it does not automatically remove server-side account or workspace data.

Lumivora does not treat beta workspace data as public. Data may be shared only where it is necessary to run the product, comply with the law, enforce product rules, or protect the service.

During beta, Lumivora may use service providers for hosting, authentication, storage, delivery, error monitoring, and analytics support.

Lumivora keeps beta data for as long as it is reasonably needed to operate the beta, review product quality, resolve support issues, and protect the service.

Some records, such as backups, security logs, or monitoring history, may persist for a limited period even after a user stops actively testing.

Beta users can edit parts of their profile and workspace inside the product. For account removal or broader deletion requests, use the beta contact channel that provided access to Lumivora.

Because this is a limited beta, some deletion or export workflows may still be manual.

Lumivora is not intended for highly sensitive personal, medical, financial, or regulated data during beta.

Only put work into the product that you are comfortable using in an early-stage test environment.

This draft may change as the beta matures, especially if the product, hosting, or app distribution model changes.

When changes are material, Lumivora should update the effective date and make the revised draft available inside the app.