Security & Compliance

This page is for teams and individuals evaluating whether LoreVia is appropriate for their manuscript workflows. It provides a clear overview of the product's practical security posture, data handling approach, and the boundaries of the service so you can make an informed decision.

LoreVia prioritizes authenticated accounts, strong session handling, scoped access controls, and clear boundaries around uploads, processing, and billing. We use proven third-party services for core functions so we can focus on manuscript intelligence. Billing is handled through a third-party provider rather than storing raw payment card data in the main application.

When you upload text into LoreVia, your manuscript may be stored, processed, and analyzed to provide continuity tools, summaries, and other product features. Content moves through standard application workflows, secure storage, and model-assisted processing where applicable to deliver insights, notes, and outputs you request.

LoreVia uses third-party providers for authentication, storage, payments, and infrastructure. Each provider handles a specific part of the workflow, such as secure sign-in, data storage, processing capacity, or billing. Paddle is used to manage payments so we do not store raw payment card data.

LoreVia is intended for creative and editorial workflows including draft review, continuity checking, note-taking, and manuscript intelligence. It is not designed for highly regulated, classified, or unusually sensitive workloads unless those use cases are reviewed and approved separately.

You remain responsible for what you upload, how you secure your account, and how you classify or handle sensitive content inside your organization. We provide the platform and operational safeguards; you apply your own internal policies, approvals, and risk decisions.

If you believe you have found a security issue, exposed data, account compromise, or policy mismatch, contact LoreVia directly using the addresses below. Operational incidents are communicated through our public status page so you can investigate without turning an active issue into a wider risk event.

Teams can contact LoreVia with concrete trust, compliance, or procurement questions. Narrow, workflow-specific questions are usually more useful than generic security questionnaires. We are happy to discuss how LoreVia fits into your environment.