We're here to help.

LoreVia currently handles formal communication through email rather than through a large ticket portal or public forum. That keeps the contact surface small and makes it easier to route product support, legal notices, and security-sensitive issues to the right place.

If you are unsure which inbox to use, support is usually the best starting point for account and product questions. Legal is the better path for rights complaints, licensing questions, formal notices, or security reports that should not be discussed in public.

The support inbox at support@getlorevia.com is the main path for user help. Use it for account access problems, billing portal issues, refund review requests, bug reports, feature questions, manuscript workflow confusion, or anything else tied to how the product is behaving for you.

When you report a product issue, include enough context for a human to act on it. Helpful reports usually mention the account email, the page or feature involved, what you expected to happen, what actually happened, and whether the issue is repeatable.

The legal inbox at legal@getlorevia.com should be used for copyright complaints, takedown requests, rights disputes, licensing questions, privacy requests that need formal handling, and other issues where a normal support conversation is not the right venue.

If you are sending a formal notice, include the identifying details that make the request actionable. For example, tell us which account, file, or published page is involved, what legal right or issue is being asserted, and what action you are asking LoreVia to take.

If you believe you found a vulnerability, exposed route, account takeover path, or other security defect, email LoreVia directly instead of posting the issue publicly. Early private reporting gives us a chance to verify, contain, and fix the problem before it becomes a wider risk.

A strong initial report usually includes the affected URL or feature, the steps to reproduce, whether authentication was required, whether real user data may have been exposed, and whether you still have access to a safe test case that can help confirm the issue.

Clear reports move faster than emotional ones. If you need a response, send the shortest version of the facts that would let a teammate understand the problem without having to reconstruct the timeline from scratch.

LoreVia aims to respond as quickly as practical, but response time can vary depending on the type of request, business hours, and whether the issue requires legal or technical investigation. Security reports, access problems, and billing errors generally need triage sooner than general feature suggestions.

Sending the same request to both inboxes is not usually necessary unless the issue is truly both legal and operational. Duplicates can slow triage by creating parallel threads about the same incident.